On Tue, 2003-02-18 at 11:24, Rupp,Heiko wrote: > On the other hand, the task of Xdoclet is to abstract from the > underlying technology. It does this already when implementing ejbCreate() > for you or providing CMP PK classes and so on. > > This could even lead to abstract it more > > @ejb.ejb-external-reference > jndi-name=xxx > ejb-ref=xxx > server="jboss" > server="bea" > > Or leave the server attribute out and include the reference in all > deployment descriptors for which a subtask in the ejbdoclet task > exists.
Except the example you yourself used on Monday had >In my source I now have: > * @jboss.ejb-ref-jndi > * jndi-name="jnp://entw05:1099/ejb/Hello" > * ref-name="RemoteHello" > * > * @weblogic.ejb-reference-description > * jndi-name="t3://192.168.100.131:7001/ejb/Hello" > * ejb-ref-name="RemoteHello" Notice how the jndi-name is different for each app server? With the consolidated version you have above, you couldn't do that... Andrew. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
