Are we talking about the same. When you drop a SAR file then
you have to drop everywhere but when you call the Configuration-
Service with an URL it will download the SAR file. Both works
with an deployment descriptor within the SAR file.
If you drop it with an URL (pointing to the deployment descriptor)
I don't think you will gain something.
My idea was to drop the SAR file for simple JBoss installations but
using a management tool when you want to deploy services over
a large number of JBoss instances which then use send a URL to
the ConfigurationService where to pick up the SAR file.
Andy
----- Original Message -----
From: "marc fleury" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 20, 2001 6:48 PM
Subject: RE: [JBoss-dev] Deployable service archives & new configuration
system
>
> |> Do you want to contain the configuration file (service.xml)
> |> be part of the *.sar file or separate. I would like to
> |> have it within the SAR file (like the EJB, WAR or EAR files).
> |+1 for it to be part of the *.sar file
>
> Actually I don't know... can't we use the URL base in teh XML description?
> would simplify my farm management life, otherwise imagine dropping 10,000
> files in 10,000 servers...
> I would rather give the URL and let them work from that.
>
> marcf
> |
> |/Lennart
> |
> |
> |_______________________________________________
> |Jboss-development mailing list
> |[EMAIL PROTECTED]
> |http://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
