I am new at implementing a resource connector and was wondering what the best way is to have dynamic ActivationSpec properties.
The EIS that I am connecting to can possible move and/or login information can change. From what I have read the properties are normally either configured via annotations on an MDB that is associated with the JCA or in the ra.xml.
Both of these options will mean at the least repackaging of the rar/ear. Can the activation spec not be written to get the required information from a EJB call or from a db?
I think the EJB option is not going to work due to load sequence, is this correct?
Thanks in advance
Frans van Niekerk
posted 7 years ago
What I am trying to do is have the MDB provide the properties required for the JCA to connect. That way the MDB can lookup the configuration information via normal EJBs.
Obviously, this is assuming: * MDBs are automatically started. * I can invoke the activateEndpoint when the MDB is pointed with a MessageEndPoint constructed from the method to invoke.