ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chaganthi, Madhusudan R." <>
Subject RE: WebLogic 4.x EJB Tasks
Date Fri, 21 Jul 2000 20:11:55 GMT
You can, if you modify the and the to
accept an argument.
FOr example I added the following line (position 119)
ddCreatorTask.setJvmargs("-ms128m -mx128m");// in the

-----Original Message-----
From: Ken Liu []
Sent: Friday, July 21, 2000 3:55 PM
Subject: RE: WebLogic 4.x EJB Tasks


I just got around to trying out the DDCreator and ejbc tasks.  I'm following
up here on a post from last week:

My questions:
1) Did anyone ever come up with a patch to EjbcHelper to allow the
"-compiler jikes" to be passed in?  I may do this if it hasn't already been
done.  It's great to be able to skip the ejbc, but ejbc is really really
slow without jikes.

2) I am using TOPLink for Weblogic, which requires that the System variables
"weblogic.home" and "weblogic.system.home" be set in the JVM for the
DDCreator.  When you install TOPLink it installs some jar file into
/weblogic/lib which DDCreator then finds using those System variables.  This
is only for TOPLink beans of course.  So my current DDCreator task looks
something like this:

<java classname="${ejb.ddcreator}" fork="yes"
jvmargs="-Dweblogic.home=${lib.weblogic.dir} -Dweblogic.system.home=${lib.we
blogic.dir} -cp ${classpath}" args="-dir /build/classes/[path to
bean] -outputfile SomeEjbDD.ser ${src.dir}/[path to bean]SomeEjbDD.txt"/>

So my question is: Can I pass the jvmargs to the <ddcreator> task?


> -----Original Message-----
> From: Conor MacNeill []
> Sent: Monday, July 10, 2000 6:47 AM
> To:
> Subject: RE: WebLogic 4.x EJB Tasks
> Paul,
> > From: Paul Hodgetts []
> >
> > I've been using the new WebLogic 4.x EJB tasks and I have a few
> > comments/questions.  These tasks are very cool and help us out a
> > whole lot with our builds.  Thank you!
> Thanks for the feedback.
> >
> > DDCreator works great.  No issues there.
> >
> > Ejbc works well, with the following comments/questions:
> >
> > 1.  There are some command line parameters that are not passed in.
> >      For example, -g -nowarn -debug can't be set.  -keepgenerated is
> >      hard coded as always on.  I was playing around in EjbcHelper by
> >      just putting them on the command line, and they seem to work
> >      fine.  It looks pretty straightforward to pass them through (if
> >      I understand the design).
> I developed these tasks initially to serve the EJB builds we are doing at
> Cortex without much regard for supporting all options. It
> shouldn't be hard
> to add those options. The whole split between ejbc and ejbcHelper was done
> for classpath reasons and I just put the things I needed into the
> interface.
> I am happy if you want to make changes and submit patches.
> >
> > 2.  I was trying to add -compiler jikes to the EjbcHelper command
> >      line, and it didn't work.  It seemed to generate the first bean
> >      that it came across, but didn't continue on to any more.  I
> >      think it may have something to do with how it's invoked, but I
> >      don't understand it enough to know why and how to fix it.  The
> >      reason I want to use Jikes is because Jikes is twice as fast as
> >      the JDK compiler.  We have a lot of beans to generate, and it
> >      cuts 5 minutes off a full build.
> I haven't tried to use Jikes with ejbc. I have heard from someone who has
> done it. They added

View raw message