Hi James, No problem - understand you've been busy, thanks for the reply.
I tried the recent b3 release and this seemed to clear some of my other problems. Using the Jelly task from Ant still seems to cause problems. For the time being I'm using a workaround - using the Ant Java task and forking a separate process, then load my Ant defined properties from the Jelly script. At least I've now got a working prototype for a set of functional test scripts for our application. One piece of functionality I think I'm missing from the current set of tag libraries is a way of comparing an expected result set against the result of a query against the database. I'd like a test analyst to be able to construct (or extract from an existing database) the expected result set in XML. I'm thinking of wrapping some of the behaviour in DBUnit to achieve this. Not sure if this more widely applicable to the community ? I'd like to go back and investigate the source of the problems with the Jelly task (+Ant/Jelly interactions) - hopefully I can find some time this week and I'll report back. Anything I can do to help... Darren -----Original Message----- From: James Strachan [mailto:[EMAIL PROTECTED]] Sent: 27 September 2002 14:25 To: Jakarta Commons Users List Subject: Re: Jelly and Ant Exec output property Hi Darren Sorry for the delay getting back to you, nearly missed this mail. Is this still an issue? Some work was done to try ensure that the JellyTask reuses the Project from Ant so there should only be 1 Ant Project used throughout. James ------- http://radio.weblogs.com/0112098/ ----- Original Message ----- From: "Darren Syzling" <[EMAIL PROTECTED]> To: "Jakarta Commons User Mailing List" <[EMAIL PROTECTED]> Sent: Monday, September 02, 2002 1:23 PM Subject: Jelly and Ant Exec output property > I'm trying to automate a set of functional tests using the 1.0 development > release of Jelly and Ant 1.5. > > My Ant build script calls a Jelly script (via the Jelly Ant task) which then > itself can use other Ant tasks - in particular Exec. The Ant 1.5 exec task > provides a facility to specify an output property for the return code of the > process. I'm trying to read this value from the calling Jelly script, > however even though the property is set by the Ant task it cannot be seen by > the Jelly script. > > A quick look through the Jelly source code it appears that multiple Ant > projects are being created - the second one during the AntTagLibrary > initialisation. The result is that the call to Ant exec sets a property > within the second project rather than the Ant environment passed originally > passed to the Jelly script. > > The initial Ant project is passed down to the Jelly script and can be used > to read Ant project properties correctly. The tag library is registered > with the JellyContext (as a TagLibrary object) with the calling Ant project > (AntTagLibrary(Project) constructor is used). This is fine since the > JellyContext will now find the tag library when the jelly:ant name space is > used. However following this initialisation the XML parser initialises the > tag libraries within the Jelly script using the tag library class names > (Strings) which removes the previously initialised Ant tag library - so we > now lose the original Ant project. The new AntTagLibrary is then > constructed, a new Ant project is constructed and we lose the ability for > Ant tasks to set properties that the jelly script can see. > > May be I've missed something in the way I'm trying to use Ant with Jelly and > wasn't sure whether anyone was aware of this problem ? > > > > Darren > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
