Hi! Is there any way to avoid getting a <local-jndi-name> or <jndi-name> TAG in the weblogic-ejb-jar.xml?
Even if I use the following without local-jndi-name and jndi-name xDoclet always generates a local-jndi-name TAG with a default content of compname, just because it has view-type local * @ejb:bean name="bm/CustomerFacade" * display-name="Bestseller Mail CustomerFacade" * type="Stateless" * transaction-type="Container" * view-type="local" But neither local-jndi-name nor jndi-name is mandatory in weblogic-ejb-jar.xml. We have to avoid both of them, because we have to deploy two completely independend applications on the same BEA Weblogic server. Both of them use the same subcomponent, but in a different version. So the component JAR is in both EAR files. Now when I deploy the second app, I get a NameAlreadyBoundException because the component in the first app has already bound the name for the component. Because I use java:comp/env to access the EJBs I don't need any JNDI name. Still worse, the produce the Exceptions during deployment. After modifying the weblogic-ejb-jar.xml after xDoclet run, the app works. Now I would like to get the same result with xdoclet itself. I already patched the source to get it working, but there should be another solutions, because I don't know about any side effects of my patch. Anybody out there, who can give me a hint? Bye, Torsten ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
