done it , so no parameter is required to control that . Both module and
service can be deploy as either archive file or exploded directory
Thanks,
Deepal
................................................................
~Future is Open~
----- Original Message -----
From: "Davanum Srinivas" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, September 15, 2005 7:28 PM
Subject: Re: [Axis2] Deploying Service Exploded directory
+1 go for it.
On 9/15/05, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
Hi all ;
Sorry for delaying to reply the mail ,
I can make the required changes to take both service archive and exploded
service without using a parameter
( <parameter
name="extract_service_archive"locked="xsd:false">true</parameter> )
Thanks,
Deepal
................................................................
~Future is Open~
----- Original Message -----
From: "Sanjiva Weerawarana" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, September 14, 2005 6:23 AM
Subject: Re: [Axis2] Deploying Service Exploded directory
> +1 to supporting arbitrary mixtures of exploded and unexploded
> directories.
>
> Deepal, do we really need a parameter to control whether this feature is
> on or not? It seems to me this should always be turned on, period. I
> can't think of a reason why one would not allow an exploded aar or mar
> to be deployed even in a production setting?? (Not likely, I agree, but
> seems absolutely harmless to me.)
>
> Sanjiva.
>
> On Tue, 2005-09-13 at 16:35 -0400, Glen Daniels wrote:
>> Tom Jordahl wrote:
>> > I think it would be nicer if Axis2 would load exploded directories
>> > AND
>> > read archive files directly (not explode them).
>>
>> +1! Modules should be OK exploded too:
>>
>> axis/
>> modules/
>> exploded1/
>> META-INF/
>> module.xml
>> lib/
>> myClasses.jar
>> archived.mar (used in place - doesn't need expanding)
>> services/
>> exploded1/
>> META-INF/
>> services.xml (assuming new name :))
>> classes/
>> org/...
>> resources/
>> ...other files...
>> modules/
>> ...just like modules/ above...
>> archived.aar (doesn't need to be expanded)
>>
>> Essentially the deployment engine should look for each file under
>> services/ - if it's a data file, treat it as an aar, and if it's a
>> directory, treat it as an exploded service....
>>
>> --Glen
>>
>> > From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
>> > Sent: Tuesday, August 30, 2005 7:34 AM
>> > To: [email protected]
>> > Subject: [Axis2] Deploying Service Exploded directory
>> >
>> >
>> >
>> > Hi all;
>> >
>> >
>> >
>> > The exploded directory only allowed for services not for modules ,
>> > and
>> > the support for exploded directory handle by the parameter in
>> > axis2.xml,
>> > if and only if its value is true exploded directory will be
>> > supported.
>> >
>> > The parameter look like follows;
>> >
>> > <parameter name="extarct_service_archieve"
>> > locked="xsd:false">true</parameter>
>> >
>> > if the value is true , first extract all the archive file in the
>> > /service directory and load those exploded directory and if someone
>> > drop
>> > exploded directory as a service that will take into account.
>> >
>> > If the parameter not there or value is false, then none of the
>> > archive
>> > file will be extracted and if someone drop exploded directory as
>> > service
>> > that wont take into account. Only load archive files into account.
>> >
>> > Thanks,
>> > Deepal
>> > ................................................................
>> > ~Future is Open~
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>
>
--
Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform
