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 Davanum Srinivas <da...@gmail.com> on 2007/02/16 16:00:24 UTC
[Axis2] Deployment options for JSR 181 artifacts
Folks,
Picking back up from the old thread [1]. We already support specifying
JAXWSMessageReceiver in a services.xml and the ServiceClass pointing
to a class that has annotations.
Here are some additional options, we need to pick one or more of these:
Option #1: User drops jar into services directory. One or more of the
classes in the jar have a @Webservice Annotation. (Like the multiple
services in our services.xml). We could just pick up the Main-Class
attribute in the manifest like sanjiva mentioned instead of scanning
the whole jar. If that is absent then scan the whole jar.
Option #2: User creates a directory under services and drops the
class(es) under the directory. This is equivalent to creating a
services.xml under a directory like we have now.
repo/services/MyService/org/apache/sample/MyService.class
{Question here is, do we need the additional MyService directory layer)
Option #3: Variant of Option #1. But look under beans directory
(instead of services)
Option #4: Variant of Option #3. But look under beans directory
(instead of services). In this case the single class deployment looks
like this
repo/beans/org/apache/sample/MyService.class
Note: For both #1 and #2, we have to update the processing for
services.list to pick up the jars/classes for unpacked war deployment.
Since we can't traverse the directories in unpacked war. Right now we
specify the name of the aar(s) in services.list.
Did i miss anything? Please chime in quickly since we need to wrap
this up to get something working for 1.2's experimental support.
thanks,
dims
[1] http://marc.theaimsgroup.com/?t=116371698300001&r=1&w=2
--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Deployment options for JSR 181 artifacts
Posted by Davanum Srinivas <da...@gmail.com>.
Deepal,
Ok. Let's start with Option #1.
thanks,
dims
On 2/19/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
> Hi Dims;
>
> I have slightly different idea in mind , after we introduce Deployer
> concept I am thinking of writing a new Deployer for this scenario. Since
> with the new deployer mechanism user have flexibility of selecting the
> directory (he might select pojo or bean directory). And user can deploy
> his service either as .jar file or .class (or .jws) file.
>
> I am not happy with option2 since he can easily create a jar and drop that.
>
> So let's provide user flexibility of deploying a pojo as a jar file or
> class file , if the file is jar then as you suggested in option1 we scan
> though the jar and find the annotated files and make them a services.
>
> Thanks
> Deepal
>
> Davanum Srinivas wrote:
>
> > Folks,
> >
> > Picking back up from the old thread [1]. We already support specifying
> > JAXWSMessageReceiver in a services.xml and the ServiceClass pointing
> > to a class that has annotations.
> >
> > Here are some additional options, we need to pick one or more of these:
> >
> > Option #1: User drops jar into services directory. One or more of the
> > classes in the jar have a @Webservice Annotation. (Like the multiple
> > services in our services.xml). We could just pick up the Main-Class
> > attribute in the manifest like sanjiva mentioned instead of scanning
> > the whole jar. If that is absent then scan the whole jar.
> >
> > Option #2: User creates a directory under services and drops the
> > class(es) under the directory. This is equivalent to creating a
> > services.xml under a directory like we have now.
> >
> > repo/services/MyService/org/apache/sample/MyService.class
> >
> > {Question here is, do we need the additional MyService directory layer)
> >
> > Option #3: Variant of Option #1. But look under beans directory
> > (instead of services)
> >
> > Option #4: Variant of Option #3. But look under beans directory
> > (instead of services). In this case the single class deployment looks
> > like this
> >
> > repo/beans/org/apache/sample/MyService.class
> >
> > Note: For both #1 and #2, we have to update the processing for
> > services.list to pick up the jars/classes for unpacked war deployment.
> > Since we can't traverse the directories in unpacked war. Right now we
> > specify the name of the aar(s) in services.list.
> >
> > Did i miss anything? Please chime in quickly since we need to wrap
> > this up to get something working for 1.2's experimental support.
> >
> > thanks,
> > dims
> >
> > [1] http://marc.theaimsgroup.com/?t=116371698300001&r=1&w=2
>
>
> --
> Thanks,
> Deepal
> ................................................................
> "The highest tower is built one brick at a time"
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Deployment options for JSR 181 artifacts
Posted by Deepal Jayasinghe <de...@opensource.lk>.
>
>
>>So let's provide user flexibility of deploying a pojo as a jar file or
>>class file , if the file is jar then as you suggested in option1 we scan
>>though the jar and find the annotated files and make them a services.
>>
>>
>
>If we provide the ability to deploy a pojo that isn't a jar, isn't that
>what option 2 is? I could be missing something here.
>
>
Yes it is all most equal to option2 , but not allow to create folder
inside the directory (I mean you want be able to deploy services which
has package like org.xx.xx)
Thanks
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Deployment options for JSR 181 artifacts
Posted by Nicholas L Gallardo <nl...@us.ibm.com>.
Deepal,
> So let's provide user flexibility of deploying a pojo as a jar file or
> class file , if the file is jar then as you suggested in option1 we scan
> though the jar and find the annotated files and make them a services.
If we provide the ability to deploy a pojo that isn't a jar, isn't that
what option 2 is? I could be missing something here.
We don't have to do it for 1.2, but this is something that would be just
as useful for JAX-WS endpoints as it is for Axis2 endpoints. Using this
in conjunction with a hot deployment capability would make service
development more developer friendly, as I'm guessing it does today for
Axis2 endpoints.
Regards,
Nicholas Gallardo
WebSphere - WebServices Development
nlgallar@us.ibm.com
Phone: 512-838-1182
Building: 901 / 5G-016
Deepal Jayasinghe <de...@opensource.lk>
02/19/2007 12:12 AM
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org
cc
Subject
Re: [Axis2] Deployment options for JSR 181 artifacts
Hi Dims;
I have slightly different idea in mind , after we introduce Deployer
concept I am thinking of writing a new Deployer for this scenario. Since
with the new deployer mechanism user have flexibility of selecting the
directory (he might select pojo or bean directory). And user can deploy
his service either as .jar file or .class (or .jws) file.
I am not happy with option2 since he can easily create a jar and drop
that.
So let's provide user flexibility of deploying a pojo as a jar file or
class file , if the file is jar then as you suggested in option1 we scan
though the jar and find the annotated files and make them a services.
Thanks
Deepal
Davanum Srinivas wrote:
> Folks,
>
> Picking back up from the old thread [1]. We already support specifying
> JAXWSMessageReceiver in a services.xml and the ServiceClass pointing
> to a class that has annotations.
>
> Here are some additional options, we need to pick one or more of these:
>
> Option #1: User drops jar into services directory. One or more of the
> classes in the jar have a @Webservice Annotation. (Like the multiple
> services in our services.xml). We could just pick up the Main-Class
> attribute in the manifest like sanjiva mentioned instead of scanning
> the whole jar. If that is absent then scan the whole jar.
>
> Option #2: User creates a directory under services and drops the
> class(es) under the directory. This is equivalent to creating a
> services.xml under a directory like we have now.
>
> repo/services/MyService/org/apache/sample/MyService.class
>
> {Question here is, do we need the additional MyService directory layer)
>
> Option #3: Variant of Option #1. But look under beans directory
> (instead of services)
>
> Option #4: Variant of Option #3. But look under beans directory
> (instead of services). In this case the single class deployment looks
> like this
>
> repo/beans/org/apache/sample/MyService.class
>
> Note: For both #1 and #2, we have to update the processing for
> services.list to pick up the jars/classes for unpacked war deployment.
> Since we can't traverse the directories in unpacked war. Right now we
> specify the name of the aar(s) in services.list.
>
> Did i miss anything? Please chime in quickly since we need to wrap
> this up to get something working for 1.2's experimental support.
>
> thanks,
> dims
>
> [1] http://marc.theaimsgroup.com/?t=116371698300001&r=1&w=2
--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Deployment options for JSR 181 artifacts
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Dims;
I have slightly different idea in mind , after we introduce Deployer
concept I am thinking of writing a new Deployer for this scenario. Since
with the new deployer mechanism user have flexibility of selecting the
directory (he might select pojo or bean directory). And user can deploy
his service either as .jar file or .class (or .jws) file.
I am not happy with option2 since he can easily create a jar and drop that.
So let's provide user flexibility of deploying a pojo as a jar file or
class file , if the file is jar then as you suggested in option1 we scan
though the jar and find the annotated files and make them a services.
Thanks
Deepal
Davanum Srinivas wrote:
> Folks,
>
> Picking back up from the old thread [1]. We already support specifying
> JAXWSMessageReceiver in a services.xml and the ServiceClass pointing
> to a class that has annotations.
>
> Here are some additional options, we need to pick one or more of these:
>
> Option #1: User drops jar into services directory. One or more of the
> classes in the jar have a @Webservice Annotation. (Like the multiple
> services in our services.xml). We could just pick up the Main-Class
> attribute in the manifest like sanjiva mentioned instead of scanning
> the whole jar. If that is absent then scan the whole jar.
>
> Option #2: User creates a directory under services and drops the
> class(es) under the directory. This is equivalent to creating a
> services.xml under a directory like we have now.
>
> repo/services/MyService/org/apache/sample/MyService.class
>
> {Question here is, do we need the additional MyService directory layer)
>
> Option #3: Variant of Option #1. But look under beans directory
> (instead of services)
>
> Option #4: Variant of Option #3. But look under beans directory
> (instead of services). In this case the single class deployment looks
> like this
>
> repo/beans/org/apache/sample/MyService.class
>
> Note: For both #1 and #2, we have to update the processing for
> services.list to pick up the jars/classes for unpacked war deployment.
> Since we can't traverse the directories in unpacked war. Right now we
> specify the name of the aar(s) in services.list.
>
> Did i miss anything? Please chime in quickly since we need to wrap
> this up to get something working for 1.2's experimental support.
>
> thanks,
> dims
>
> [1] http://marc.theaimsgroup.com/?t=116371698300001&r=1&w=2
--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Deployment options for JSR 181 artifacts
Posted by Rajith Attapattu <ra...@gmail.com>.
Dims,
sure ping me on the list when you are ready.
Rajith
On 2/16/07, Davanum Srinivas <da...@gmail.com> wrote:
>
> Ok. Let's go with #1 and #2. Let me read up on the "Axis2 annotated
> services vs JAX-WS annotated services" and get back.
>
> thanks,
> dims
>
> On 2/16/07, Rajith Attapattu <ra...@gmail.com> wrote:
> > folks,
> >
> > I would also go for option 1 and 2.
> >
> > If we do dupport option 1, then as Nick mentioned we need a few
> additional
> > annotations to distinguish
> > Axis2 annotated services from JAX-WS annotated services.
> >
> > regards,
> >
> > Rajith
> >
> >
> > On 2/16/07, Nicholas L Gallardo <nl...@us.ibm.com> wrote:
> > > Dims, thanks for bringing this one up again.
> > >
> > > My vote would be for #1 and if possible #2. My detailed knowledge of
> the
> > > deployment code is limited, but it seems like if we can handle #1 with
> > > scanning the full jar, then #2 shouldn't be much more on top of that.
> Just
> > > a different entry point into the same code.
> > >
> > > As for whether you would need the "services/MyService" directory, I
> > > believe so. This seems like a better scoping mechanism than all
> classes
> > > for any number of different services in the same bucket.
> > >
> > > Introducing this also means we would need to complete the proposal
> Rajith
> > > and I talked about for an additional set of annotations to distinguish
> > > Axis2 annotated services from JAX-WS annotated services.
> > >
> > > Thanks,
> > >
> > > Nicholas Gallardo
> > > WebSphere - WebServices Development
> > > nlgallar@us.ibm.com
> > > Phone: 512-838-1182
> > > Building: 901 / 5G-016
> > >
> > >
> > >
> > > "Davanum Srinivas" < davanum@gmail.com>
> > > 02/16/2007 09:00 AM
> > > Please respond to
> > > axis-dev@ws.apache.org
> > >
> > >
> > > To
> > > " axis-dev@ws.apache.org" <ax...@ws.apache.org>
> > > cc
> > >
> > > Subject
> > > [Axis2] Deployment options for JSR 181 artifacts
> > >
> > >
> > >
> > >
> > >
> > >
> > > Folks,
> > >
> > > Picking back up from the old thread [1]. We already support specifying
> > > JAXWSMessageReceiver in a services.xml and the ServiceClass pointing
> > > to a class that has annotations.
> > >
> > > Here are some additional options, we need to pick one or more of
> these:
> > >
> > > Option #1: User drops jar into services directory. One or more of the
> > > classes in the jar have a @Webservice Annotation. (Like the multiple
> > > services in our services.xml). We could just pick up the Main-Class
> > > attribute in the manifest like sanjiva mentioned instead of scanning
> > > the whole jar. If that is absent then scan the whole jar.
> > >
> > > Option #2: User creates a directory under services and drops the
> > > class(es) under the directory. This is equivalent to creating a
> > > services.xml under a directory like we have now.
> > >
> > > repo/services/MyService/org/apache/sample/MyService.class
> > >
> > > {Question here is, do we need the additional MyService directory
> layer)
> > >
> > > Option #3: Variant of Option #1. But look under beans directory
> > > (instead of services)
> > >
> > > Option #4: Variant of Option #3. But look under beans directory
> > > (instead of services). In this case the single class deployment looks
> > > like this
> > >
> > > repo/beans/org/apache/sample/MyService.class
> > >
> > > Note: For both #1 and #2, we have to update the processing for
> > > services.list to pick up the jars/classes for unpacked war deployment.
> > > Since we can't traverse the directories in unpacked war. Right now we
> > > specify the name of the aar(s) in services.list.
> > >
> > > Did i miss anything? Please chime in quickly since we need to wrap
> > > this up to get something working for 1.2's experimental support.
> > >
> > > thanks,
> > > dims
> > >
> > > [1]
> > http://marc.theaimsgroup.com/?t=116371698300001&r=1&w=2
> > > --
> > > Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services
> Developers
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > axis-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >
> > >
> > >
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > axis-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >
> > >
> >
> >
>
>
> --
> Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
Re: [Axis2] Deployment options for JSR 181 artifacts
Posted by Davanum Srinivas <da...@gmail.com>.
Ok. Let's go with #1 and #2. Let me read up on the "Axis2 annotated
services vs JAX-WS annotated services" and get back.
thanks,
dims
On 2/16/07, Rajith Attapattu <ra...@gmail.com> wrote:
> folks,
>
> I would also go for option 1 and 2.
>
> If we do dupport option 1, then as Nick mentioned we need a few additional
> annotations to distinguish
> Axis2 annotated services from JAX-WS annotated services.
>
> regards,
>
> Rajith
>
>
> On 2/16/07, Nicholas L Gallardo <nl...@us.ibm.com> wrote:
> > Dims, thanks for bringing this one up again.
> >
> > My vote would be for #1 and if possible #2. My detailed knowledge of the
> > deployment code is limited, but it seems like if we can handle #1 with
> > scanning the full jar, then #2 shouldn't be much more on top of that. Just
> > a different entry point into the same code.
> >
> > As for whether you would need the "services/MyService" directory, I
> > believe so. This seems like a better scoping mechanism than all classes
> > for any number of different services in the same bucket.
> >
> > Introducing this also means we would need to complete the proposal Rajith
> > and I talked about for an additional set of annotations to distinguish
> > Axis2 annotated services from JAX-WS annotated services.
> >
> > Thanks,
> >
> > Nicholas Gallardo
> > WebSphere - WebServices Development
> > nlgallar@us.ibm.com
> > Phone: 512-838-1182
> > Building: 901 / 5G-016
> >
> >
> >
> > "Davanum Srinivas" < davanum@gmail.com>
> > 02/16/2007 09:00 AM
> > Please respond to
> > axis-dev@ws.apache.org
> >
> >
> > To
> > " axis-dev@ws.apache.org" <ax...@ws.apache.org>
> > cc
> >
> > Subject
> > [Axis2] Deployment options for JSR 181 artifacts
> >
> >
> >
> >
> >
> >
> > Folks,
> >
> > Picking back up from the old thread [1]. We already support specifying
> > JAXWSMessageReceiver in a services.xml and the ServiceClass pointing
> > to a class that has annotations.
> >
> > Here are some additional options, we need to pick one or more of these:
> >
> > Option #1: User drops jar into services directory. One or more of the
> > classes in the jar have a @Webservice Annotation. (Like the multiple
> > services in our services.xml). We could just pick up the Main-Class
> > attribute in the manifest like sanjiva mentioned instead of scanning
> > the whole jar. If that is absent then scan the whole jar.
> >
> > Option #2: User creates a directory under services and drops the
> > class(es) under the directory. This is equivalent to creating a
> > services.xml under a directory like we have now.
> >
> > repo/services/MyService/org/apache/sample/MyService.class
> >
> > {Question here is, do we need the additional MyService directory layer)
> >
> > Option #3: Variant of Option #1. But look under beans directory
> > (instead of services)
> >
> > Option #4: Variant of Option #3. But look under beans directory
> > (instead of services). In this case the single class deployment looks
> > like this
> >
> > repo/beans/org/apache/sample/MyService.class
> >
> > Note: For both #1 and #2, we have to update the processing for
> > services.list to pick up the jars/classes for unpacked war deployment.
> > Since we can't traverse the directories in unpacked war. Right now we
> > specify the name of the aar(s) in services.list.
> >
> > Did i miss anything? Please chime in quickly since we need to wrap
> > this up to get something working for 1.2's experimental support.
> >
> > thanks,
> > dims
> >
> > [1]
> http://marc.theaimsgroup.com/?t=116371698300001&r=1&w=2
> > --
> > Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Deployment options for JSR 181 artifacts
Posted by Rajith Attapattu <ra...@gmail.com>.
folks,
I would also go for option 1 and 2.
If we do dupport option 1, then as Nick mentioned we need a few additional
annotations to distinguish
Axis2 annotated services from JAX-WS annotated services.
regards,
Rajith
On 2/16/07, Nicholas L Gallardo <nl...@us.ibm.com> wrote:
>
> Dims, thanks for bringing this one up again.
>
> My vote would be for #1 and if possible #2. My detailed knowledge of the
> deployment code is limited, but it seems like if we can handle #1 with
> scanning the full jar, then #2 shouldn't be much more on top of that. Just
> a different entry point into the same code.
>
> As for whether you would need the "services/MyService" directory, I
> believe so. This seems like a better scoping mechanism than all classes
> for any number of different services in the same bucket.
>
> Introducing this also means we would need to complete the proposal Rajith
> and I talked about for an additional set of annotations to distinguish
> Axis2 annotated services from JAX-WS annotated services.
>
> Thanks,
>
> Nicholas Gallardo
> WebSphere - WebServices Development
> nlgallar@us.ibm.com
> Phone: 512-838-1182
> Building: 901 / 5G-016
>
>
>
> "Davanum Srinivas" <da...@gmail.com>
> 02/16/2007 09:00 AM
> Please respond to
> axis-dev@ws.apache.org
>
>
> To
> "axis-dev@ws.apache.org" <ax...@ws.apache.org>
> cc
>
> Subject
> [Axis2] Deployment options for JSR 181 artifacts
>
>
>
>
>
>
> Folks,
>
> Picking back up from the old thread [1]. We already support specifying
> JAXWSMessageReceiver in a services.xml and the ServiceClass pointing
> to a class that has annotations.
>
> Here are some additional options, we need to pick one or more of these:
>
> Option #1: User drops jar into services directory. One or more of the
> classes in the jar have a @Webservice Annotation. (Like the multiple
> services in our services.xml). We could just pick up the Main-Class
> attribute in the manifest like sanjiva mentioned instead of scanning
> the whole jar. If that is absent then scan the whole jar.
>
> Option #2: User creates a directory under services and drops the
> class(es) under the directory. This is equivalent to creating a
> services.xml under a directory like we have now.
>
> repo/services/MyService/org/apache/sample/MyService.class
>
> {Question here is, do we need the additional MyService directory layer)
>
> Option #3: Variant of Option #1. But look under beans directory
> (instead of services)
>
> Option #4: Variant of Option #3. But look under beans directory
> (instead of services). In this case the single class deployment looks
> like this
>
> repo/beans/org/apache/sample/MyService.class
>
> Note: For both #1 and #2, we have to update the processing for
> services.list to pick up the jars/classes for unpacked war deployment.
> Since we can't traverse the directories in unpacked war. Right now we
> specify the name of the aar(s) in services.list.
>
> Did i miss anything? Please chime in quickly since we need to wrap
> this up to get something working for 1.2's experimental support.
>
> thanks,
> dims
>
> [1] http://marc.theaimsgroup.com/?t=116371698300001&r=1&w=2
> --
> Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
Re: [Axis2] Deployment options for JSR 181 artifacts
Posted by Nicholas L Gallardo <nl...@us.ibm.com>.
Dims, thanks for bringing this one up again.
My vote would be for #1 and if possible #2. My detailed knowledge of the
deployment code is limited, but it seems like if we can handle #1 with
scanning the full jar, then #2 shouldn't be much more on top of that. Just
a different entry point into the same code.
As for whether you would need the "services/MyService" directory, I
believe so. This seems like a better scoping mechanism than all classes
for any number of different services in the same bucket.
Introducing this also means we would need to complete the proposal Rajith
and I talked about for an additional set of annotations to distinguish
Axis2 annotated services from JAX-WS annotated services.
Thanks,
Nicholas Gallardo
WebSphere - WebServices Development
nlgallar@us.ibm.com
Phone: 512-838-1182
Building: 901 / 5G-016
"Davanum Srinivas" <da...@gmail.com>
02/16/2007 09:00 AM
Please respond to
axis-dev@ws.apache.org
To
"axis-dev@ws.apache.org" <ax...@ws.apache.org>
cc
Subject
[Axis2] Deployment options for JSR 181 artifacts
Folks,
Picking back up from the old thread [1]. We already support specifying
JAXWSMessageReceiver in a services.xml and the ServiceClass pointing
to a class that has annotations.
Here are some additional options, we need to pick one or more of these:
Option #1: User drops jar into services directory. One or more of the
classes in the jar have a @Webservice Annotation. (Like the multiple
services in our services.xml). We could just pick up the Main-Class
attribute in the manifest like sanjiva mentioned instead of scanning
the whole jar. If that is absent then scan the whole jar.
Option #2: User creates a directory under services and drops the
class(es) under the directory. This is equivalent to creating a
services.xml under a directory like we have now.
repo/services/MyService/org/apache/sample/MyService.class
{Question here is, do we need the additional MyService directory layer)
Option #3: Variant of Option #1. But look under beans directory
(instead of services)
Option #4: Variant of Option #3. But look under beans directory
(instead of services). In this case the single class deployment looks
like this
repo/beans/org/apache/sample/MyService.class
Note: For both #1 and #2, we have to update the processing for
services.list to pick up the jars/classes for unpacked war deployment.
Since we can't traverse the directories in unpacked war. Right now we
specify the name of the aar(s) in services.list.
Did i miss anything? Please chime in quickly since we need to wrap
this up to get something working for 1.2's experimental support.
thanks,
dims
[1] http://marc.theaimsgroup.com/?t=116371698300001&r=1&w=2
--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org