ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Higginbotham" <>
Subject RE: Calling a task from another task directly?
Date Mon, 10 Jul 2000 15:08:17 GMT
Let me clarify:

Although the EJBC tool for 4.5.1 accepts a .jar or .ser, the task expects to
find a .ser. It then reads in the serialized object, casts it to a
descriptor, and tries to locate the home/bean/etc. files to do time stamp
comparisons. I have a EJB 1.1 XML descr. and a WL 5.1 XML descriptor which I
need to jar with the home, bean, etc. files and run through EJBC 5.1.
Apparently, Tim Fennell has written a 5.1 task, so I will try it out.


-----Original Message-----
From: Chaganthi, Madhusudan R. []
Sent: Monday, July 10, 2000 9:30 AM
To: ''
Subject: RE: Calling a task from another task directly?

4.5.1 too needs .jar and NOT .ser for bean deployment.
So what seems to be the issue here in 5.1 which is different from 4.5.1??
Let me  know

-----Original Message-----
From: James Higginbotham []
Sent: Friday, July 07, 2000 6:16 PM
To: Ant-Dev
Subject: Calling a task from another task directly?


I have a possible need to execute the building of a JAR for generating a
pre-deployment EJB in WebLogic. I have considered constructing a custom task
to handle the creation of the JAR and calling WebLogic's EJBC althougher,
rather than forcing the build.xml file to first define a JAR task and then
calling my EJBC task. If I did this, would this break a design guideline of
Ant? Is there a better alternative? I know that Conor is working on a
WebLogic task, but it is only supporting WL 4.5.1, and my beef is with WL
5.1 which uses .jar files rather than .ser files for doing all of the
generation magic. Thoughts, suggestions?


View raw message