I committed a change to ServiceDeployer a couple of days ago that means you
can now add a directory to the classpath of a deployment (does that make
sense) as well as jars.
This means you should be able to simply extract your sar into a directory of
your choosing, edit the jboss-service.xml file so that it contains
<classpath ... /> elements for your directory and the jars in that directory
you want to be able to access, and then simply copy the *service.xml file to
the deploy directory and everything should work ("should" meaning I haven't
tried this exactly but I can't think of any reason it won't work).
Is this what you mean by running unpacked?
I do something similar and find it works very well, it means I have all my
resources in one directory and after I make a change to them I simply
redeploy the *service.xml file and the new changes take effect.
Cheers
David.
PS:syntax
to add directory
<classpath codebase="directoryURL" />
to add specific jars in directory
<classpath codebase="directoryURL" archives="jar1.jar,jar2.zip" />
to add all jars in directory
<classpath codebase="directoryURL" archives="*" />
> -----Original Message-----
> From: Julian Gosnell [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, November 29, 2001 1:58 PM
> To: [EMAIL PROTECTED]
> Subject: [JBoss-dev] RH: running SARs unpacked ? and other
> questions...
>
>
>
>
> Can a sar be run unpacked - I had the impression this was not so.
>
> It would be nicely consistant if I could unpack my SAR and
> rebuild into
> the dir hierarchy, touching the descriptor (jboss-service.xml) when I
> was ready to undeploy/redeploy ?
>
> Whilst we are on the subject of SARs, would it also be more consistant
> to put the descriptors into a separate dir as in META-INF, WEB-INF -
> only I don't know what it should be called - so forget it !
>
> Lastly - assume that I am writing a service (Jetty) which wants to use
> EJBs as part of it's implementation. Access to these EJBs needs to be
> local and optimised. Does this mean that they need to be
> deployed in the
>
> same ClassLoader as Jetty ? I guess I am asking if we can have EARs
> within SARs ? - or am I not ? Maybe Local interfaces will solve the
> problem, but I would rather use optimised Remote interfaces, as then I
> preserve the possibility of deploying several Jetty instances, all
> talking to a single remote EJB server. I don't see why an optimised
> Remote interface call should be any slower than an optimised Local
> interface call, within the same ClassLoader - but then "I only do
> eyes!".
>
>
> Jules
>
>
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
> ---
> Incoming 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
>
>
---
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
