Hi All, well Hi David Jencks mostly I guess ;-), With the new deployment system I have started deploying my application by simply deploying the *service.xml file and including all the jars it uses in a <classpath /> element.
This works very well, I can easily keep all my jars together in a lib directory and the *service.xml file is easily available for editing and redeploying. There is one draw back though. I have several *.properties files used by my service that need to also be added to the classpath. Currently the only way I can find to do this is by putting them in one of the jars, however I would like to be able to simply place them in my lib directory (which is specified by my codebase attribute of the classpath element) so that I can edit them and then redeploy the *service.xml to have the changes take effect. I think that in general the ability to add directories to the classpath as well as jars would be very useful to developers. Currently if a classpath element is specified with a codebase attribute but no archives attribute the directory specified by the codebase is searched for jars which are added to the classpath, I would prefer it if the directory itself were simply added. So my questions are: 1) Is there a way to add a simple directory to the classpath of a service? 2) If not, is there a good reason why not? 3) If there is no good reason why not then how difficult do you think this would be to add? 4) Would you have time to do it, or do you want me to have a hack at it? Thanks David --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.298 / Virus Database: 161 - Release Date: 11/13/2001 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
