You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Deepal Jayasinghe <de...@opensource.lk> on 2006/01/02 06:35:06 UTC
Re: [axis2] Module versions support
I think we are done with the format of the version number ,
but I have some other problem to solve now say we have multiple version of
the same module in the system , and right now at the deployment time I call
the init method of each module (since we don't have the notion of module
version yet) , there if the module want to do some stuff they can do that ,
as an example in RM case if it has saved some data they can get them back at
the initialization stage.
But the problem is what are we going to do if there are multiple versions of
the same module , should we need to call init method of all the modules ?
where they are going to be engaged or not.
Thanks,
Deepal
................................................................
~Future is Open~
----- Original Message -----
From: "Sanjiva Weerawarana" <sa...@opensource.lk>
To: <di...@apache.org>
Cc: <ax...@ws.apache.org>
Sent: Saturday, December 31, 2005 12:12 PM
Subject: Re: [axis2] Module versions support
> On Sat, 2005-12-31 at 00:50 -0500, Davanum Srinivas wrote:
>> just reviewed the original email again...it talks about
>> xyz-00.0000.mar hence the confusion.
>>
>> So, we should go with say security-1.23.mar. Right? just to be absolutely
>> clear.
>
> Right .. or security-1.235486.mar etc... basically we expect the format
> to be modulename-{majorversion}.{minorversion}.mar where the two version
> #s are integers. (Major should not have any leading zeros but that's
> just a redundant comment - anyone who puts that deserves whatever
> behavior they get.)
>
> Sanjiva.
>
>
>
Re: [axis2] Module versions support
Posted by Davanum Srinivas <da...@gmail.com>.
+1 from me.
On 1/2/06, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> +1!
>
> Sanjiva.
>
> On Mon, 2006-01-02 at 16:24 +0600, Deepal Jayasinghe wrote:
> > Hi all;
> >
> > Without having a knowledge of module version user should be able to engage a
> > module . In that case we have to get the default version
> > (there will be two ways of engaging a module )
> > 1. engageModule(String moduleName);
> > 2 . engageModule(String moduleName , String moduleVersion);
> >
> > Finding default version of some module if there are more than one module,
> > 1. If there are multiple versions of the same module it can possible to
> > specify the default version in axis2.xml as follows
> > <defaultModuleVersions>
> > <module name="abc" version="1.23">
> > <module name="foo" version="0.89">
> > </defaultModuleVersions>
> > 2. If there are multiple versions of the same module and user does not
> > specify that in axis2.xml then the default version will be the latest
> > version
> >
> > comments .....?
> >
> > Thanks,
> > Deepal
> > ................................................................
> > ~Future is Open~
> >
> > ----- Original Message -----
> > From: "Deepal Jayasinghe" <de...@opensource.lk>
> > To: <ax...@ws.apache.org>
> > Sent: Monday, January 02, 2006 11:35 AM
> > Subject: Re: [axis2] Module versions support
> >
> >
> > >I think we are done with the format of the version number ,
> > > but I have some other problem to solve now say we have multiple version of
> > > the same module in the system , and right now at the deployment time I
> > > call the init method of each module (since we don't have the notion of
> > > module version yet) , there if the module want to do some stuff they can
> > > do that , as an example in RM case if it has saved some data they can get
> > > them back at the initialization stage.
> > >
> > > But the problem is what are we going to do if there are multiple versions
> > > of the same module , should we need to call init method of all the modules
> > > ? where they are going to be engaged or not.
> > >
> > > Thanks,
> > > Deepal
> > > ................................................................
> > > ~Future is Open~
> > >
> > > ----- Original Message -----
> > > From: "Sanjiva Weerawarana" <sa...@opensource.lk>
> > > To: <di...@apache.org>
> > > Cc: <ax...@ws.apache.org>
> > > Sent: Saturday, December 31, 2005 12:12 PM
> > > Subject: Re: [axis2] Module versions support
> > >
> > >
> > >> On Sat, 2005-12-31 at 00:50 -0500, Davanum Srinivas wrote:
> > >>> just reviewed the original email again...it talks about
> > >>> xyz-00.0000.mar hence the confusion.
> > >>>
> > >>> So, we should go with say security-1.23.mar. Right? just to be
> > >>> absolutely clear.
> > >>
> > >> Right .. or security-1.235486.mar etc... basically we expect the format
> > >> to be modulename-{majorversion}.{minorversion}.mar where the two version
> > >> #s are integers. (Major should not have any leading zeros but that's
> > >> just a redundant comment - anyone who puts that deserves whatever
> > >> behavior they get.)
> > >>
> > >> Sanjiva.
> > >>
> > >>
> > >>
> > >
> > >
> > >
> >
> >
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: [axis2] Module versions support
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
+1!
Sanjiva.
On Mon, 2006-01-02 at 16:24 +0600, Deepal Jayasinghe wrote:
> Hi all;
>
> Without having a knowledge of module version user should be able to engage a
> module . In that case we have to get the default version
> (there will be two ways of engaging a module )
> 1. engageModule(String moduleName);
> 2 . engageModule(String moduleName , String moduleVersion);
>
> Finding default version of some module if there are more than one module,
> 1. If there are multiple versions of the same module it can possible to
> specify the default version in axis2.xml as follows
> <defaultModuleVersions>
> <module name="abc" version="1.23">
> <module name="foo" version="0.89">
> </defaultModuleVersions>
> 2. If there are multiple versions of the same module and user does not
> specify that in axis2.xml then the default version will be the latest
> version
>
> comments .....?
>
> Thanks,
> Deepal
> ................................................................
> ~Future is Open~
>
> ----- Original Message -----
> From: "Deepal Jayasinghe" <de...@opensource.lk>
> To: <ax...@ws.apache.org>
> Sent: Monday, January 02, 2006 11:35 AM
> Subject: Re: [axis2] Module versions support
>
>
> >I think we are done with the format of the version number ,
> > but I have some other problem to solve now say we have multiple version of
> > the same module in the system , and right now at the deployment time I
> > call the init method of each module (since we don't have the notion of
> > module version yet) , there if the module want to do some stuff they can
> > do that , as an example in RM case if it has saved some data they can get
> > them back at the initialization stage.
> >
> > But the problem is what are we going to do if there are multiple versions
> > of the same module , should we need to call init method of all the modules
> > ? where they are going to be engaged or not.
> >
> > Thanks,
> > Deepal
> > ................................................................
> > ~Future is Open~
> >
> > ----- Original Message -----
> > From: "Sanjiva Weerawarana" <sa...@opensource.lk>
> > To: <di...@apache.org>
> > Cc: <ax...@ws.apache.org>
> > Sent: Saturday, December 31, 2005 12:12 PM
> > Subject: Re: [axis2] Module versions support
> >
> >
> >> On Sat, 2005-12-31 at 00:50 -0500, Davanum Srinivas wrote:
> >>> just reviewed the original email again...it talks about
> >>> xyz-00.0000.mar hence the confusion.
> >>>
> >>> So, we should go with say security-1.23.mar. Right? just to be
> >>> absolutely clear.
> >>
> >> Right .. or security-1.235486.mar etc... basically we expect the format
> >> to be modulename-{majorversion}.{minorversion}.mar where the two version
> >> #s are integers. (Major should not have any leading zeros but that's
> >> just a redundant comment - anyone who puts that deserves whatever
> >> behavior they get.)
> >>
> >> Sanjiva.
> >>
> >>
> >>
> >
> >
> >
>
>
Re: [axis2] Module versions support
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi all;
Without having a knowledge of module version user should be able to engage a
module . In that case we have to get the default version
(there will be two ways of engaging a module )
1. engageModule(String moduleName);
2 . engageModule(String moduleName , String moduleVersion);
Finding default version of some module if there are more than one module,
1. If there are multiple versions of the same module it can possible to
specify the default version in axis2.xml as follows
<defaultModuleVersions>
<module name="abc" version="1.23">
<module name="foo" version="0.89">
</defaultModuleVersions>
2. If there are multiple versions of the same module and user does not
specify that in axis2.xml then the default version will be the latest
version
comments .....?
Thanks,
Deepal
................................................................
~Future is Open~
----- Original Message -----
From: "Deepal Jayasinghe" <de...@opensource.lk>
To: <ax...@ws.apache.org>
Sent: Monday, January 02, 2006 11:35 AM
Subject: Re: [axis2] Module versions support
>I think we are done with the format of the version number ,
> but I have some other problem to solve now say we have multiple version of
> the same module in the system , and right now at the deployment time I
> call the init method of each module (since we don't have the notion of
> module version yet) , there if the module want to do some stuff they can
> do that , as an example in RM case if it has saved some data they can get
> them back at the initialization stage.
>
> But the problem is what are we going to do if there are multiple versions
> of the same module , should we need to call init method of all the modules
> ? where they are going to be engaged or not.
>
> Thanks,
> Deepal
> ................................................................
> ~Future is Open~
>
> ----- Original Message -----
> From: "Sanjiva Weerawarana" <sa...@opensource.lk>
> To: <di...@apache.org>
> Cc: <ax...@ws.apache.org>
> Sent: Saturday, December 31, 2005 12:12 PM
> Subject: Re: [axis2] Module versions support
>
>
>> On Sat, 2005-12-31 at 00:50 -0500, Davanum Srinivas wrote:
>>> just reviewed the original email again...it talks about
>>> xyz-00.0000.mar hence the confusion.
>>>
>>> So, we should go with say security-1.23.mar. Right? just to be
>>> absolutely clear.
>>
>> Right .. or security-1.235486.mar etc... basically we expect the format
>> to be modulename-{majorversion}.{minorversion}.mar where the two version
>> #s are integers. (Major should not have any leading zeros but that's
>> just a redundant comment - anyone who puts that deserves whatever
>> behavior they get.)
>>
>> Sanjiva.
>>
>>
>>
>
>
>