On another topic which we are also addressing (and I'm pretty sure this is not purely a weblogic problem , rather any EJB 1.1 impl. will have this), how do you handle the issue of multiple EJBs per package and the current restrictions on naming the xml dds? For example, if I have a session bean, then I need to have two xml files: ejb-jar.xml and weblogic-ejb-jar.xml. For an entity, I need another which describes the persistence mapping.
I've looked and I don't see a way to change the naming of these files.
One workaround is to prefix the name of the bean to the deployment descriptors to give each file uniqueness at storage time, then your EJB task could strip this prefix off at build time before building the beans in their own working directory (this was suggested on the weblogic news groups - there doesn't appear to be a more elegant solution out there).
If you post your task and haven't already addressed this problem, I'll take on extending it to do this.
Humphrey
-----Original Message----- From: Tim Fennell [mailto:[EMAIL PROTECTED] Sent: 05 July 2000 11:48 To: [EMAIL PROTECTED] Subject: Optional EJB tasks (was RE: Subpackages of ...taskdefs.optional)
On the topic of EJB tasks, has anyone written anything for EJB1.1 and/or Weblogic 5.1?
If not, then I'd like to offer up what I have. I hava an EJB task that inherits from directory scanner, scans for deployment descriptors and assembles the EJB1.1 jars from the contents of the descriptor (XML only, not the 1.0 serialized classes), then optionally calls weblogic's ejbc. Works very well for me, and now I can have only one task for all of my EJBs. It should also be really easy to extend to call other vendors' compilers.
Is there any interest? If so then I'll post the code here (I assume this is the right forum?).
-t
________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
