What's the best way to support the following? We have a "core" ejb-jar.xml that has in it session beans that have ejb refs to other beans that are not in the same jar.
e.g.
<session>
<display-name>CoreSessionEJB</display-name>
<ejb-name>ejb/CoreSession</ejb-name>
<home>com.armanta.ejb.CoreSessionHome</home>
<remote>com.armanta.ejb.CoreSession</remote>
<ejb-class>com.armanta.ejb.CoreSessionBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<ejb-ref>
<ejb-ref-name>ejb/SpecializedSession</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.armanta.ejb.SpecializedSessionHome</home>
<remote>com.armanta.ejb.SpecializedSession</remote>
<ejb-link>ejb/SpecializedSession</ejb-link>
</ejb-ref>
</session>
The idea here is that each install may have a different implementation of
the Specialized Session Bean.
There would then be a specialized jar in the same ear with the following
ejb-jar.xml.
<session>
<display-name>SpecializedSessionEJB</display-name>
<ejb-name>ejb/SpecializedSession</ejb-name>
<home>com.armanta.ejb.SpecializedSessionHome</home>
<remote>com.armanta.ejb.SpecializedSession</remote>
<ejb-class>com.armanta.ejb.SpecializedSessionBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
Then, each install would have the same specialized ejb-jar but just package
their own implementation of ejb-jar.xml.
The trouble now happens. We have two installations, each with their own
implementation of specialized.
We decide that the core bean should support an additional way of interacting
with the specialized bean
to better support install 2, but install 1 has no interest in it and we
can't go back to them to tell them they
need to add methods to their specialized session bean. How can we best deal
with this?
We can't create a new ejb-ref to ejb/SpecializedSessionNew, because the ear
won't deploy for the install 1 that
doesn't actually define the new ejb. We would rather not have multiple
versions of ejb-jar.xml.
Any help with this problem would be much appreciated.
Regards
Eric Kaplan
Armanta, Inc.
<<attachment: winmail.dat>>
