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 Glen Daniels <gl...@thoughtcraft.com> on 2005/10/26 01:12:01 UTC

[axis2] VOTE : *Description

For the record, I continue to really dislike 
ServiceDescription/OperationDescription as class names for these things. 
  Consider Deepal's message below - the Service"Description" is the 
place you get the ClassLoader from!  It contains metadata, sure, but in 
a real way it IS the runtime representation of the service itself.  As 
such, I think these classes should be what we originally called them at 
the F2F:

AxisService
AxisOperation

This seems much more logical to me.  The AxisService, for instance, is 
the Java representation of everything Axis needs to know about this 
service at runtime - it's not just a "Description".

Also right now it's a little confusing in that AxisConfiguration is the 
corresponding class to ConfigurationContext, and all the others are 
*Description... it would be nice to have it consistent.

This was discussed before:

http://marc.theaimsgroup.com/?l=axis-dev&m=112666988223509&w=2

But I couldn't find an actual VOTE where we decided to make the change 
from AxisService -> ServiceDescription....(can anyone point me to it?) 
so I'd like to have a VOTE for the record.  So here we go....

PROPOSAL :

Make the hierarchy as follows:

s/ServiceDescription/AxisService/
s/OperationDescription/AxisOperation/
s/ServiceGroupDescription/AxisServiceGroup/

Here's my +1.

--Glen

Yves Langisch wrote:
> Deepal,
> 
> Thanks, I'll give it a try.
> 
> Yves
> 
> On Tue, 2005-10-25 at 09:21 +0600, Deepal Jayasinghe wrote:
> 
>>Hi Yvess;
>>
>>The correct way is get the ServiceDescription from , MessageContxt and then 
>>you can get the correct classloader for that service (which has all you lib 
>>files) from serviceDescription
>>ClassLoader cl = sd.getClassLoader();
>>
>>next you can load the properties you want.
>>
>>
>>Thanks,
>> Deepal
>>................................................................
>>~Future is Open~
>>
>>----- Original Message ----- 
>>From: "Yves Langisch" <li...@langisch.ch>
>>To: <ax...@ws.apache.org>
>>Sent: Monday, October 24, 2005 7:42 PM
>>Subject: [Axis2] Access a resource inside of a Axis2 archive
>>
>>
>>
>>>Hi
>>>
>>>I've a Axis2 archive file (.aar) which contains several libraries in
>>>the /lib folder.  In my *PortSkeleton class I'm looking for a way to
>>>load a properties file that is in one of this libs. I tried with
>>>this.getClass().getResource("my.properties") (also with
>>>"lib/my.properties") without success. How can I achieve this?
>>>
>>>Thanks
>>>Yves
>>>
>>>
>>
>>
> 

Re: [axis2] VOTE : *Description

Posted by Samisa Abeysinghe <sa...@gmail.com>.
What about the package name then? Are we going to retain "description"?
As the argument goes, as it is not meta data, "description" does not 
sound correct.

Tanks,
Samisa...

Glen Daniels wrote:

> For the record, I continue to really dislike 
> ServiceDescription/OperationDescription as class names for these 
> things.  Consider Deepal's message below - the Service"Description" is 
> the place you get the ClassLoader from!  It contains metadata, sure, 
> but in a real way it IS the runtime representation of the service 
> itself.  As such, I think these classes should be what we originally 
> called them at the F2F:
>
> AxisService
> AxisOperation
>
> This seems much more logical to me.  The AxisService, for instance, is 
> the Java representation of everything Axis needs to know about this 
> service at runtime - it's not just a "Description".
>
> Also right now it's a little confusing in that AxisConfiguration is 
> the corresponding class to ConfigurationContext, and all the others 
> are *Description... it would be nice to have it consistent.
>
> This was discussed before:
>
> http://marc.theaimsgroup.com/?l=axis-dev&m=112666988223509&w=2
>
> But I couldn't find an actual VOTE where we decided to make the change 
> from AxisService -> ServiceDescription....(can anyone point me to it?) 
> so I'd like to have a VOTE for the record.  So here we go....
>
> PROPOSAL :
>
> Make the hierarchy as follows:
>
> s/ServiceDescription/AxisService/
> s/OperationDescription/AxisOperation/
> s/ServiceGroupDescription/AxisServiceGroup/
>
> Here's my +1.
>
> --Glen
>
> Yves Langisch wrote:
>
>> Deepal,
>>
>> Thanks, I'll give it a try.
>>
>> Yves
>>
>> On Tue, 2005-10-25 at 09:21 +0600, Deepal Jayasinghe wrote:
>>
>>> Hi Yvess;
>>>
>>> The correct way is get the ServiceDescription from , MessageContxt 
>>> and then you can get the correct classloader for that service (which 
>>> has all you lib files) from serviceDescription
>>> ClassLoader cl = sd.getClassLoader();
>>>
>>> next you can load the properties you want.
>>>
>>>
>>> Thanks,
>>> Deepal
>>> ................................................................
>>> ~Future is Open~
>>>
>>> ----- Original Message ----- From: "Yves Langisch" <li...@langisch.ch>
>>> To: <ax...@ws.apache.org>
>>> Sent: Monday, October 24, 2005 7:42 PM
>>> Subject: [Axis2] Access a resource inside of a Axis2 archive
>>>
>>>
>>>
>>>> Hi
>>>>
>>>> I've a Axis2 archive file (.aar) which contains several libraries in
>>>> the /lib folder.  In my *PortSkeleton class I'm looking for a way to
>>>> load a properties file that is in one of this libs. I tried with
>>>> this.getClass().getResource("my.properties") (also with
>>>> "lib/my.properties") without success. How can I achieve this?
>>>>
>>>> Thanks
>>>> Yves
>>>>
>>>>
>>>
>>>
>>
>


Re: [axis2] VOTE : *Description

Posted by Eran Chinthaka <ch...@opensource.lk>.
+1 from me too.

Are you all ok with the names of Context hierarchy ?

-- Chinthaka

Sanjiva Weerawarana wrote:

>On Tue, 2005-10-25 at 19:12 -0400, Glen Daniels wrote:
>  
>
>>Make the hierarchy as follows:
>>
>>s/ServiceDescription/AxisService/
>>s/OperationDescription/AxisOperation/
>>s/ServiceGroupDescription/AxisServiceGroup/
>>    
>>
>
>+1 from me for consistent names too. 
>
>I have one additional request- whenever people see any variables or
>comments in the code which use old names, *PLEASE* change them to be
>consistent. We currently have several places in the code which use
>"axisXYZ" when referring to an XYZDescription object. Of course in
>hindsight that works nicely now :) but let's not keep it inconsistent;
>it makes the code that much harder to read.
>
>Sanjiva.
>
>
>
>
>  
>

Re: [axis2] VOTE : *Description

Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Tue, 2005-10-25 at 19:12 -0400, Glen Daniels wrote:
> Make the hierarchy as follows:
> 
> s/ServiceDescription/AxisService/
> s/OperationDescription/AxisOperation/
> s/ServiceGroupDescription/AxisServiceGroup/

+1 from me for consistent names too. 

I have one additional request- whenever people see any variables or
comments in the code which use old names, *PLEASE* change them to be
consistent. We currently have several places in the code which use
"axisXYZ" when referring to an XYZDescription object. Of course in
hindsight that works nicely now :) but let's not keep it inconsistent;
it makes the code that much harder to read.

Sanjiva.



Re: [axis2] VOTE : *Description

Posted by Davanum Srinivas <da...@gmail.com>.
+1 from me.

-- dims

On 10/25/05, Glen Daniels <gl...@thoughtcraft.com> wrote:
> For the record, I continue to really dislike
> ServiceDescription/OperationDescription as class names for these things.
>   Consider Deepal's message below - the Service"Description" is the
> place you get the ClassLoader from!  It contains metadata, sure, but in
> a real way it IS the runtime representation of the service itself.  As
> such, I think these classes should be what we originally called them at
> the F2F:
>
> AxisService
> AxisOperation
>
> This seems much more logical to me.  The AxisService, for instance, is
> the Java representation of everything Axis needs to know about this
> service at runtime - it's not just a "Description".
>
> Also right now it's a little confusing in that AxisConfiguration is the
> corresponding class to ConfigurationContext, and all the others are
> *Description... it would be nice to have it consistent.
>
> This was discussed before:
>
> http://marc.theaimsgroup.com/?l=axis-dev&m=112666988223509&w=2
>
> But I couldn't find an actual VOTE where we decided to make the change
> from AxisService -> ServiceDescription....(can anyone point me to it?)
> so I'd like to have a VOTE for the record.  So here we go....
>
> PROPOSAL :
>
> Make the hierarchy as follows:
>
> s/ServiceDescription/AxisService/
> s/OperationDescription/AxisOperation/
> s/ServiceGroupDescription/AxisServiceGroup/
>
> Here's my +1.
>
> --Glen
>
> Yves Langisch wrote:
> > Deepal,
> >
> > Thanks, I'll give it a try.
> >
> > Yves
> >
> > On Tue, 2005-10-25 at 09:21 +0600, Deepal Jayasinghe wrote:
> >
> >>Hi Yvess;
> >>
> >>The correct way is get the ServiceDescription from , MessageContxt and then
> >>you can get the correct classloader for that service (which has all you lib
> >>files) from serviceDescription
> >>ClassLoader cl = sd.getClassLoader();
> >>
> >>next you can load the properties you want.
> >>
> >>
> >>Thanks,
> >> Deepal
> >>................................................................
> >>~Future is Open~
> >>
> >>----- Original Message -----
> >>From: "Yves Langisch" <li...@langisch.ch>
> >>To: <ax...@ws.apache.org>
> >>Sent: Monday, October 24, 2005 7:42 PM
> >>Subject: [Axis2] Access a resource inside of a Axis2 archive
> >>
> >>
> >>
> >>>Hi
> >>>
> >>>I've a Axis2 archive file (.aar) which contains several libraries in
> >>>the /lib folder.  In my *PortSkeleton class I'm looking for a way to
> >>>load a properties file that is in one of this libs. I tried with
> >>>this.getClass().getResource("my.properties") (also with
> >>>"lib/my.properties") without success. How can I achieve this?
> >>>
> >>>Thanks
> >>>Yves
> >>>
> >>>
> >>
> >>
> >
>


--
Davanum Srinivas : http://wso2.com/blogs/