Jelly

[Robert McIntosh]

I have worked up a simple Avalon service for running Jelly scripts. James Strachan (the lead on Jelly for those who don't know) has put it in cvs ( http://cvs.apache.org/viewcvs/jakarta-commons-sandbox/jelly/jelly-tags/avalon/ ) if you want to look.
Its purpose is to allows a client/user to run Jelly scripts by either a URL (the standard Jelly fashion), or you can configure 'named' scripts in the config to run. The idea being that you could swap scripts or whatever via the config.
If anybody has any suggestions for improvements, please let me know.

I'll be writing up some JUnit tests for it here shortly and was curious about how you guys do unit testing on your components. My first thought was to just have the JUnit TestCase load an example config via the configuration builder and manually supply it to the service, then let loose on the tests. Basically test it outside of any container. Is this the common practice?

I took a brief looks at the excalibure test case, but it looks to still use ComponentManagers instead of the new ServiceManager stuff, so I didn't think it would apply.

Any thoughts or directions to lead me in?

Thanks,
Robert McIntosh


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>