You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by Isuru Suriarachchi <is...@gmail.com> on 2010/03/08 12:04:32 UTC
Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Hi all,
Andreas has already reported an issue [1] regarding the inability to
configure JAX-WS services. That is because we've removed support for a
services.xml. But there are many use cases where the user should be able to
configure the service according to his requirements. Following are some of
the very common examples.
[1] Ability to deploy JAX-WS services in different scopes (session,
application etc.)
[2] Ability to set ServiceTCCL
[3] Ability to specify service parameters
In order to support these use cases, we have to support service
customizations somehow. If allowing a services.xml file is not a proper
solution, I think defining Axis2 specific annotations whould be a good
solution for this issue.
WDYT?..
Thanks,
~Isuru
[1] https://issues.apache.org/jira/browse/AXIS2-4611
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Andreas Veithen <an...@gmail.com>.
My proposal (to add an extension point to ServiceDeployer to allow
JAX-WS to inject AxisService descriptions built from JAX-WS
annotations) has the following advantages:
* The familiar services.xml syntax applies. No new descriptor formats
or annotations are necessary.
* No need for a new deployer; JAX-WS services can be deployed from an AAR.
* JAX-WS services can benefit from the other advantages of AAR files
(e.g. embedded JARs).
* Works with WARs (i.e. with an exploded AAR bundled inside the WAR).
* Restores compatibility with earlier Axis2 versions (and with what is
promised in the Axis2 documentation).
* Possibility to mix JAX-WS services with other types of services in a
single AAR.
* Relatively easy to implement and not much new code required.
However, it will require a refactoring of ServiceDeployer to introduce
a new API (which could be useful for other purposes in the future).
Andreas
On Tue, Mar 9, 2010 at 11:15, Sagara Gunathunga
<sa...@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi
> <am...@gmail.com> wrote:
>>
>>
>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen
>> <an...@gmail.com> wrote:
>>>
>>> I also created a proof-of-concept [1] that shows the feasibility of
>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>> implements a custom deployer that is based on ServiceDeployer, but
>>> replaces the code that builds the initial AxisService object from the
>>> WSDL by code that uses
>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>> introduces massive code duplication and is thus only valid as a
>>> proof-of-concept.
>>
>> Apart from this I think when we introduce a new deployer then we need to
>> have a different folder to
>> deploy files and a different extension.
>>
>>
>>>
>>> To do this properly, it would be necessary to modify
>>> ServiceDeployer to create some sort of extension point that allows
>>> JAX-WS to supply the initial AxisService description.
>>
>> I think your intention here is to let users to deploy JAX-WS services as
>> aar files which already
>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>> services. ie. jaxws jar files can have an optional service.xml file in the
>> META-INF.
>>
>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>> not have the concept of custom deployers. So at that time (time when JAX-WS
>> started) every thing deployed as .aar files. But latter there were problems
>> with JAX-WS support in aar files and introduced thin new custom deployer
>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>> may not be the best approach.
>
> Another important use case is to support JAX-WS based WAR archive deployment
> , lot of people want to integrate web services as a part of their web
> applications by adding AxisServlet in the web.xml file , this works fine
> for native services.xml based web service deployment but AFAIK we can't use
> WAR deployment with JAX-WS , It's going to be a valuable feature if we can
> support for this.
>
>>
>> These are the options I can think of adding axis2 specific custermizations
>> to JAX-WS.
>>
>> 1. Support optional services.xml file in META-INF
>> Services.xml file is a too generic file. So people may confuse
>> with some options with services.xml file.
>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>> May have to duplicate some exising code in ServiceBuilder
>> 3. Introduce axis2 specific anotations to JAX-WS
>> May have problems with writting annotations to set the security
>> polices.
>
>
> Personally I like to have a descriptor file such as axis2-jaxws.xml or usual
> service.xml rather introducing another set of axis2 specific annotations.
> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
> great if we can utilize same JAR file with WAR deployment only adding a
> descriptor file into the WEB-INF directory.
>
> Thanks,
>
>>
>> Thanks,
>> Amila.
>>>
>>> Andreas
>>>
>>> [1]
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>
>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>> wrote:
>>> > Hi all,
>>> >
>>> > Andreas has already reported an issue [1] regarding the inability to
>>> > configure JAX-WS services. That is because we've removed support for a
>>> > services.xml. But there are many use cases where the user should be
>>> > able to
>>> > configure the service according to his requirements. Following are some
>>> > of
>>> > the very common examples.
>>> >
>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>> > application etc.)
>>> > [2] Ability to set ServiceTCCL
>>> > [3] Ability to specify service parameters
>>> >
>>> > In order to support these use cases, we have to support service
>>> > customizations somehow. If allowing a services.xml file is not a proper
>>> > solution, I think defining Axis2 specific annotations whould be a good
>>> > solution for this issue.
>>> >
>>> > WDYT?..
>>> >
>>> > Thanks,
>>> > ~Isuru
>>> >
>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by chris roberts <ca...@gmail.com>.
can somebody help me unsubscribe? The unsubscribe link doesn't work and my
inbox is filling up with axis emails every day. I never registered for axis
in the firs place so I'm wondering if some changes have happened recently,
meaning that one mailing list has merged with another.
Thanks for any help,
Chris
On 9 March 2010 13:07, Amila Suriarachchi <am...@gmail.com>wrote:
>
>
> On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
> sagara.gunathunga@gmail.com> wrote:
>
>>
>>
>> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
>> amilasuriarachchi@gmail.com> wrote:
>>
>>>
>>>
>>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com> wrote:
>>>
>>>> I also created a proof-of-concept [1] that shows the feasibility of
>>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>>> implements a custom deployer that is based on ServiceDeployer, but
>>>> replaces the code that builds the initial AxisService object from the
>>>> WSDL by code that uses
>>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>>> introduces massive code duplication and is thus only valid as a
>>>> proof-of-concept.
>>>
>>> Apart from this I think when we introduce a new deployer then we need to
>>> have a different folder to
>>> deploy files and a different extension.
>>>
>>>
>>>
>>>> To do this properly, it would be necessary to modify
>>>> ServiceDeployer to create some sort of extension point that allows
>>>> JAX-WS to supply the initial AxisService description.
>>>>
>>>
>>> I think your intention here is to let users to deploy JAX-WS services as
>>> aar files which already
>>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>>> services. ie. jaxws jar files can have an optional service.xml file in the
>>> META-INF.
>>>
>>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>>> not have the concept of custom deployers. So at that time (time when JAX-WS
>>> started) every thing deployed as .aar files. But latter there were problems
>>> with JAX-WS support in aar files and introduced thin new custom deployer
>>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>>> may not be the best approach.
>>>
>>
>> Another important use case is to support JAX-WS based WAR archive
>> deployment , lot of people want to integrate web services as a part of their
>> web applications by adding AxisServlet in the web.xml file , this works
>> fine for native services.xml based web service deployment but AFAIK we can't
>> use WAR deployment with JAX-WS ,
>>
>
> I have not tried this but I think it is possible. if you deploy a .jar file
> under WEB-INF/servicejars I think it is possible.
>
>
>> It's going to be a valuable feature if we can support for this.
>>
>>
>>>
>>> These are the options I can think of adding axis2 specific
>>> custermizations to JAX-WS.
>>>
>>> 1. Support optional services.xml file in META-INF
>>> Services.xml file is a too generic file. So people may confuse
>>> with some options with services.xml file.
>>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>>> May have to duplicate some exising code in ServiceBuilder
>>> 3. Introduce axis2 specific anotations to JAX-WS
>>> May have problems with writting annotations to set the
>>> security polices.
>>>
>>
>>
>> Personally I like to have a descriptor file such as axis2-jaxws.xml or
>> usual service.xml rather introducing another set of axis2 specific
>> annotations.
>>
>
> Think about a scenario like this. Lets say some one has wirten a jax ws
> service already and they need to deploy it under 'transportSession' in that
> case isn't it easy to just add an anotation to existing jax ws web service
> class instead of writtng a new services.xml file?
>
> Infact there can be instances where services.xml is useful and annotations
> useful.
>
> thanks,
> Amila.
>
>
>> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
>> great if we can utilize same JAR file with WAR deployment only adding a
>> descriptor file into the WEB-INF directory.
>>
>> Thanks,
>>
>>
>>>
>>> Thanks,
>>> Amila.
>>>
>>>>
>>>> Andreas
>>>>
>>>> [1]
>>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>>
>>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>>> wrote:
>>>> > Hi all,
>>>> >
>>>> > Andreas has already reported an issue [1] regarding the inability to
>>>> > configure JAX-WS services. That is because we've removed support for a
>>>> > services.xml. But there are many use cases where the user should be
>>>> able to
>>>> > configure the service according to his requirements. Following are
>>>> some of
>>>> > the very common examples.
>>>> >
>>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>>> > application etc.)
>>>> > [2] Ability to set ServiceTCCL
>>>> > [3] Ability to specify service parameters
>>>> >
>>>> > In order to support these use cases, we have to support service
>>>> > customizations somehow. If allowing a services.xml file is not a
>>>> proper
>>>> > solution, I think defining Axis2 specific annotations whould be a good
>>>> > solution for this issue.
>>>> >
>>>> > WDYT?..
>>>> >
>>>> > Thanks,
>>>> > ~Isuru
>>>> >
>>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>>> >
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Amila Suriarachchi
>>> WSO2 Inc.
>>> blog: http://amilachinthaka.blogspot.com/
>>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Amila Suriarachchi <am...@gmail.com>.
On Tue, Mar 9, 2010 at 8:01 PM, Sagara Gunathunga <
sagara.gunathunga@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 6:37 PM, Amila Suriarachchi <
> amilasuriarachchi@gmail.com> wrote:
>
>>
>>
>> On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
>> sagara.gunathunga@gmail.com> wrote:
>>
>>>
>>>
>>> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
>>> amilasuriarachchi@gmail.com> wrote:
>>>
>>>>
>>>>
>>>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>>>> andreas.veithen@gmail.com> wrote:
>>>>
>>>>> I also created a proof-of-concept [1] that shows the feasibility of
>>>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>>>> implements a custom deployer that is based on ServiceDeployer, but
>>>>> replaces the code that builds the initial AxisService object from the
>>>>> WSDL by code that uses
>>>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>>>> introduces massive code duplication and is thus only valid as a
>>>>> proof-of-concept.
>>>>
>>>> Apart from this I think when we introduce a new deployer then we need to
>>>> have a different folder to
>>>> deploy files and a different extension.
>>>>
>>>>
>>>>
>>>>> To do this properly, it would be necessary to modify
>>>>> ServiceDeployer to create some sort of extension point that allows
>>>>> JAX-WS to supply the initial AxisService description.
>>>>>
>>>>
>>>> I think your intention here is to let users to deploy JAX-WS services as
>>>> aar files which already
>>>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>>>> services. ie. jaxws jar files can have an optional service.xml file in the
>>>> META-INF.
>>>>
>>>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2
>>>> does not have the concept of custom deployers. So at that time (time when
>>>> JAX-WS started) every thing deployed as .aar files. But latter there were
>>>> problems with JAX-WS support in aar files and introduced thin new custom
>>>> deployer concept to address this issue. Therefore adding JAX-WS support to
>>>> .aar files may not be the best approach.
>>>>
>>>
>>> Another important use case is to support JAX-WS based WAR archive
>>> deployment , lot of people want to integrate web services as a part of their
>>> web applications by adding AxisServlet in the web.xml file , this works
>>> fine for native services.xml based web service deployment but AFAIK we can't
>>> use WAR deployment with JAX-WS ,
>>>
>>
>> I have not tried this but I think it is possible. if you deploy a .jar
>> file under WEB-INF/servicejars I think it is possible.
>>
>
>
> Nice to hear about such workaround for JAX-WS WAR deployment, I will try
> out too . But having a descriptor file or annotations based JAX-WS
> deployment approach will increase the 'ease of use ' of the project
> specially when some one use build tools like Maven.
>
> 1.) In my experience service.xml based WAR based deployment is very simple
> and fit well with build tools like Maven and Ant. Only requirement is to add
> a services.xml into the WEB-INF/services directory no need to care about
> location of the .calss files. we can use Maven/ant default behavior for
> .class file locations ( classes or lib) and packaging . But in the
> mentioned approach we have to place a JAR file inside the
> WEB-INF/servicejars directory this may require to modify build script little
> bit. It would be great if we can come up with a solution so that we only
> place meta data file in the WEB-INF or WEB-INF/servicejars directory and
> classes are loaded from default Classpath ( like in service.xml based WAR
> deployment).
>
>
> 2.) Most of the other Java web service frameworks support JAX-WS WAR
> deployment only by placing a meta data file in the WEB-INF directory, if
> we can support to similar approach it will help out for people who move in
> to Axis2 from other frameworks. If they have a existing JAX-WS service they
> only need to write a descriptor file in order to deploy on Axis2 container.
>
> Above scenarios can be specific for few use cases but IMO with the maturity
> level of Axis2 project now we have to think about those aspects too.
>
>
>
>>
>>
>>> It's going to be a valuable feature if we can support for this.
>>>
>>>
>>>>
>>>> These are the options I can think of adding axis2 specific
>>>> custermizations to JAX-WS.
>>>>
>>>> 1. Support optional services.xml file in META-INF
>>>> Services.xml file is a too generic file. So people may confuse
>>>> with some options with services.xml file.
>>>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>>>> May have to duplicate some exising code in ServiceBuilder
>>>> 3. Introduce axis2 specific anotations to JAX-WS
>>>> May have problems with writting annotations to set the
>>>> security polices.
>>>>
>>>
>>>
>>> Personally I like to have a descriptor file such as axis2-jaxws.xml or
>>> usual service.xml rather introducing another set of axis2 specific
>>> annotations.
>>>
>>
>> Think about a scenario like this. Lets say some one has wirten a jax ws
>> service already and they need to deploy it under 'transportSession' in that
>> case isn't it easy to just add an anotation to existing jax ws web service
>> class instead of writtng a new services.xml file?
>>
>> Infact there can be instances where services.xml is useful and annotations
>> useful.
>>
>
> I can agree with your ideas, each of this approaches have their own
> specific usages, as an example sometimes people want to change some settings
> when they deploy the application without recompiling source codes having a
> descriptor file is a ideal for such use case. what about to support both
> options ?
>
+1.
I think that is the best way. For an example if we take a user who have
deployed a jax-ws jar in a standalone server like WSO2 WSAS then they may
not interested going for a web app or .aar file, but want to just put a
services.xml file inside the .jar file itself or add some annotaions.
On the other hand as you and Andreas has pointed out there are senarios
where .aar support is important as well.
thanks,
Amila.
>
> Thanks,
>
>
>
>>
>> thanks,
>> Amila.
>>
>>
>>> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
>>> great if we can utilize same JAR file with WAR deployment only adding a
>>> descriptor file into the WEB-INF directory.
>>>
>>> Thanks,
>>>
>>>
>>>>
>>>> Thanks,
>>>> Amila.
>>>>
>>>>>
>>>>> Andreas
>>>>>
>>>>> [1]
>>>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>>>
>>>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>>>> wrote:
>>>>> > Hi all,
>>>>> >
>>>>> > Andreas has already reported an issue [1] regarding the inability to
>>>>> > configure JAX-WS services. That is because we've removed support for
>>>>> a
>>>>> > services.xml. But there are many use cases where the user should be
>>>>> able to
>>>>> > configure the service according to his requirements. Following are
>>>>> some of
>>>>> > the very common examples.
>>>>> >
>>>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>>>> > application etc.)
>>>>> > [2] Ability to set ServiceTCCL
>>>>> > [3] Ability to specify service parameters
>>>>> >
>>>>> > In order to support these use cases, we have to support service
>>>>> > customizations somehow. If allowing a services.xml file is not a
>>>>> proper
>>>>> > solution, I think defining Axis2 specific annotations whould be a
>>>>> good
>>>>> > solution for this issue.
>>>>> >
>>>>> > WDYT?..
>>>>> >
>>>>> > Thanks,
>>>>> > ~Isuru
>>>>> >
>>>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>>>> >
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Amila Suriarachchi
>>>> WSO2 Inc.
>>>> blog: http://amilachinthaka.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Sagara Gunathunga
>>>
>>> Blog - http://ssagara.blogspot.com
>>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>>>
>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Amila Suriarachchi <am...@gmail.com>.
On Tue, Mar 9, 2010 at 8:01 PM, Sagara Gunathunga <
sagara.gunathunga@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 6:37 PM, Amila Suriarachchi <
> amilasuriarachchi@gmail.com> wrote:
>
>>
>>
>> On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
>> sagara.gunathunga@gmail.com> wrote:
>>
>>>
>>>
>>> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
>>> amilasuriarachchi@gmail.com> wrote:
>>>
>>>>
>>>>
>>>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>>>> andreas.veithen@gmail.com> wrote:
>>>>
>>>>> I also created a proof-of-concept [1] that shows the feasibility of
>>>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>>>> implements a custom deployer that is based on ServiceDeployer, but
>>>>> replaces the code that builds the initial AxisService object from the
>>>>> WSDL by code that uses
>>>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>>>> introduces massive code duplication and is thus only valid as a
>>>>> proof-of-concept.
>>>>
>>>> Apart from this I think when we introduce a new deployer then we need to
>>>> have a different folder to
>>>> deploy files and a different extension.
>>>>
>>>>
>>>>
>>>>> To do this properly, it would be necessary to modify
>>>>> ServiceDeployer to create some sort of extension point that allows
>>>>> JAX-WS to supply the initial AxisService description.
>>>>>
>>>>
>>>> I think your intention here is to let users to deploy JAX-WS services as
>>>> aar files which already
>>>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>>>> services. ie. jaxws jar files can have an optional service.xml file in the
>>>> META-INF.
>>>>
>>>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2
>>>> does not have the concept of custom deployers. So at that time (time when
>>>> JAX-WS started) every thing deployed as .aar files. But latter there were
>>>> problems with JAX-WS support in aar files and introduced thin new custom
>>>> deployer concept to address this issue. Therefore adding JAX-WS support to
>>>> .aar files may not be the best approach.
>>>>
>>>
>>> Another important use case is to support JAX-WS based WAR archive
>>> deployment , lot of people want to integrate web services as a part of their
>>> web applications by adding AxisServlet in the web.xml file , this works
>>> fine for native services.xml based web service deployment but AFAIK we can't
>>> use WAR deployment with JAX-WS ,
>>>
>>
>> I have not tried this but I think it is possible. if you deploy a .jar
>> file under WEB-INF/servicejars I think it is possible.
>>
>
>
> Nice to hear about such workaround for JAX-WS WAR deployment, I will try
> out too . But having a descriptor file or annotations based JAX-WS
> deployment approach will increase the 'ease of use ' of the project
> specially when some one use build tools like Maven.
>
> 1.) In my experience service.xml based WAR based deployment is very simple
> and fit well with build tools like Maven and Ant. Only requirement is to add
> a services.xml into the WEB-INF/services directory no need to care about
> location of the .calss files. we can use Maven/ant default behavior for
> .class file locations ( classes or lib) and packaging . But in the
> mentioned approach we have to place a JAR file inside the
> WEB-INF/servicejars directory this may require to modify build script little
> bit. It would be great if we can come up with a solution so that we only
> place meta data file in the WEB-INF or WEB-INF/servicejars directory and
> classes are loaded from default Classpath ( like in service.xml based WAR
> deployment).
>
>
> 2.) Most of the other Java web service frameworks support JAX-WS WAR
> deployment only by placing a meta data file in the WEB-INF directory, if
> we can support to similar approach it will help out for people who move in
> to Axis2 from other frameworks. If they have a existing JAX-WS service they
> only need to write a descriptor file in order to deploy on Axis2 container.
>
> Above scenarios can be specific for few use cases but IMO with the maturity
> level of Axis2 project now we have to think about those aspects too.
>
>
>
>>
>>
>>> It's going to be a valuable feature if we can support for this.
>>>
>>>
>>>>
>>>> These are the options I can think of adding axis2 specific
>>>> custermizations to JAX-WS.
>>>>
>>>> 1. Support optional services.xml file in META-INF
>>>> Services.xml file is a too generic file. So people may confuse
>>>> with some options with services.xml file.
>>>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>>>> May have to duplicate some exising code in ServiceBuilder
>>>> 3. Introduce axis2 specific anotations to JAX-WS
>>>> May have problems with writting annotations to set the
>>>> security polices.
>>>>
>>>
>>>
>>> Personally I like to have a descriptor file such as axis2-jaxws.xml or
>>> usual service.xml rather introducing another set of axis2 specific
>>> annotations.
>>>
>>
>> Think about a scenario like this. Lets say some one has wirten a jax ws
>> service already and they need to deploy it under 'transportSession' in that
>> case isn't it easy to just add an anotation to existing jax ws web service
>> class instead of writtng a new services.xml file?
>>
>> Infact there can be instances where services.xml is useful and annotations
>> useful.
>>
>
> I can agree with your ideas, each of this approaches have their own
> specific usages, as an example sometimes people want to change some settings
> when they deploy the application without recompiling source codes having a
> descriptor file is a ideal for such use case. what about to support both
> options ?
>
+1.
I think that is the best way. For an example if we take a user who have
deployed a jax-ws jar in a standalone server like WSO2 WSAS then they may
not interested going for a web app or .aar file, but want to just put a
services.xml file inside the .jar file itself or add some annotaions.
On the other hand as you and Andreas has pointed out there are senarios
where .aar support is important as well.
thanks,
Amila.
>
> Thanks,
>
>
>
>>
>> thanks,
>> Amila.
>>
>>
>>> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
>>> great if we can utilize same JAR file with WAR deployment only adding a
>>> descriptor file into the WEB-INF directory.
>>>
>>> Thanks,
>>>
>>>
>>>>
>>>> Thanks,
>>>> Amila.
>>>>
>>>>>
>>>>> Andreas
>>>>>
>>>>> [1]
>>>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>>>
>>>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>>>> wrote:
>>>>> > Hi all,
>>>>> >
>>>>> > Andreas has already reported an issue [1] regarding the inability to
>>>>> > configure JAX-WS services. That is because we've removed support for
>>>>> a
>>>>> > services.xml. But there are many use cases where the user should be
>>>>> able to
>>>>> > configure the service according to his requirements. Following are
>>>>> some of
>>>>> > the very common examples.
>>>>> >
>>>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>>>> > application etc.)
>>>>> > [2] Ability to set ServiceTCCL
>>>>> > [3] Ability to specify service parameters
>>>>> >
>>>>> > In order to support these use cases, we have to support service
>>>>> > customizations somehow. If allowing a services.xml file is not a
>>>>> proper
>>>>> > solution, I think defining Axis2 specific annotations whould be a
>>>>> good
>>>>> > solution for this issue.
>>>>> >
>>>>> > WDYT?..
>>>>> >
>>>>> > Thanks,
>>>>> > ~Isuru
>>>>> >
>>>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>>>> >
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Amila Suriarachchi
>>>> WSO2 Inc.
>>>> blog: http://amilachinthaka.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Sagara Gunathunga
>>>
>>> Blog - http://ssagara.blogspot.com
>>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>>>
>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Amila Suriarachchi <am...@gmail.com>.
On Tue, Mar 9, 2010 at 8:01 PM, Sagara Gunathunga <
sagara.gunathunga@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 6:37 PM, Amila Suriarachchi <
> amilasuriarachchi@gmail.com> wrote:
>
>>
>>
>> On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
>> sagara.gunathunga@gmail.com> wrote:
>>
>>>
>>>
>>> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
>>> amilasuriarachchi@gmail.com> wrote:
>>>
>>>>
>>>>
>>>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>>>> andreas.veithen@gmail.com> wrote:
>>>>
>>>>> I also created a proof-of-concept [1] that shows the feasibility of
>>>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>>>> implements a custom deployer that is based on ServiceDeployer, but
>>>>> replaces the code that builds the initial AxisService object from the
>>>>> WSDL by code that uses
>>>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>>>> introduces massive code duplication and is thus only valid as a
>>>>> proof-of-concept.
>>>>
>>>> Apart from this I think when we introduce a new deployer then we need to
>>>> have a different folder to
>>>> deploy files and a different extension.
>>>>
>>>>
>>>>
>>>>> To do this properly, it would be necessary to modify
>>>>> ServiceDeployer to create some sort of extension point that allows
>>>>> JAX-WS to supply the initial AxisService description.
>>>>>
>>>>
>>>> I think your intention here is to let users to deploy JAX-WS services as
>>>> aar files which already
>>>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>>>> services. ie. jaxws jar files can have an optional service.xml file in the
>>>> META-INF.
>>>>
>>>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2
>>>> does not have the concept of custom deployers. So at that time (time when
>>>> JAX-WS started) every thing deployed as .aar files. But latter there were
>>>> problems with JAX-WS support in aar files and introduced thin new custom
>>>> deployer concept to address this issue. Therefore adding JAX-WS support to
>>>> .aar files may not be the best approach.
>>>>
>>>
>>> Another important use case is to support JAX-WS based WAR archive
>>> deployment , lot of people want to integrate web services as a part of their
>>> web applications by adding AxisServlet in the web.xml file , this works
>>> fine for native services.xml based web service deployment but AFAIK we can't
>>> use WAR deployment with JAX-WS ,
>>>
>>
>> I have not tried this but I think it is possible. if you deploy a .jar
>> file under WEB-INF/servicejars I think it is possible.
>>
>
>
> Nice to hear about such workaround for JAX-WS WAR deployment, I will try
> out too . But having a descriptor file or annotations based JAX-WS
> deployment approach will increase the 'ease of use ' of the project
> specially when some one use build tools like Maven.
>
> 1.) In my experience service.xml based WAR based deployment is very simple
> and fit well with build tools like Maven and Ant. Only requirement is to add
> a services.xml into the WEB-INF/services directory no need to care about
> location of the .calss files. we can use Maven/ant default behavior for
> .class file locations ( classes or lib) and packaging . But in the
> mentioned approach we have to place a JAR file inside the
> WEB-INF/servicejars directory this may require to modify build script little
> bit. It would be great if we can come up with a solution so that we only
> place meta data file in the WEB-INF or WEB-INF/servicejars directory and
> classes are loaded from default Classpath ( like in service.xml based WAR
> deployment).
>
>
> 2.) Most of the other Java web service frameworks support JAX-WS WAR
> deployment only by placing a meta data file in the WEB-INF directory, if
> we can support to similar approach it will help out for people who move in
> to Axis2 from other frameworks. If they have a existing JAX-WS service they
> only need to write a descriptor file in order to deploy on Axis2 container.
>
> Above scenarios can be specific for few use cases but IMO with the maturity
> level of Axis2 project now we have to think about those aspects too.
>
>
>
>>
>>
>>> It's going to be a valuable feature if we can support for this.
>>>
>>>
>>>>
>>>> These are the options I can think of adding axis2 specific
>>>> custermizations to JAX-WS.
>>>>
>>>> 1. Support optional services.xml file in META-INF
>>>> Services.xml file is a too generic file. So people may confuse
>>>> with some options with services.xml file.
>>>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>>>> May have to duplicate some exising code in ServiceBuilder
>>>> 3. Introduce axis2 specific anotations to JAX-WS
>>>> May have problems with writting annotations to set the
>>>> security polices.
>>>>
>>>
>>>
>>> Personally I like to have a descriptor file such as axis2-jaxws.xml or
>>> usual service.xml rather introducing another set of axis2 specific
>>> annotations.
>>>
>>
>> Think about a scenario like this. Lets say some one has wirten a jax ws
>> service already and they need to deploy it under 'transportSession' in that
>> case isn't it easy to just add an anotation to existing jax ws web service
>> class instead of writtng a new services.xml file?
>>
>> Infact there can be instances where services.xml is useful and annotations
>> useful.
>>
>
> I can agree with your ideas, each of this approaches have their own
> specific usages, as an example sometimes people want to change some settings
> when they deploy the application without recompiling source codes having a
> descriptor file is a ideal for such use case. what about to support both
> options ?
>
+1.
I think that is the best way. For an example if we take a user who have
deployed a jax-ws jar in a standalone server like WSO2 WSAS then they may
not interested going for a web app or .aar file, but want to just put a
services.xml file inside the .jar file itself or add some annotaions.
On the other hand as you and Andreas has pointed out there are senarios
where .aar support is important as well.
thanks,
Amila.
>
> Thanks,
>
>
>
>>
>> thanks,
>> Amila.
>>
>>
>>> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
>>> great if we can utilize same JAR file with WAR deployment only adding a
>>> descriptor file into the WEB-INF directory.
>>>
>>> Thanks,
>>>
>>>
>>>>
>>>> Thanks,
>>>> Amila.
>>>>
>>>>>
>>>>> Andreas
>>>>>
>>>>> [1]
>>>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>>>
>>>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>>>> wrote:
>>>>> > Hi all,
>>>>> >
>>>>> > Andreas has already reported an issue [1] regarding the inability to
>>>>> > configure JAX-WS services. That is because we've removed support for
>>>>> a
>>>>> > services.xml. But there are many use cases where the user should be
>>>>> able to
>>>>> > configure the service according to his requirements. Following are
>>>>> some of
>>>>> > the very common examples.
>>>>> >
>>>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>>>> > application etc.)
>>>>> > [2] Ability to set ServiceTCCL
>>>>> > [3] Ability to specify service parameters
>>>>> >
>>>>> > In order to support these use cases, we have to support service
>>>>> > customizations somehow. If allowing a services.xml file is not a
>>>>> proper
>>>>> > solution, I think defining Axis2 specific annotations whould be a
>>>>> good
>>>>> > solution for this issue.
>>>>> >
>>>>> > WDYT?..
>>>>> >
>>>>> > Thanks,
>>>>> > ~Isuru
>>>>> >
>>>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>>>> >
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Amila Suriarachchi
>>>> WSO2 Inc.
>>>> blog: http://amilachinthaka.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Sagara Gunathunga
>>>
>>> Blog - http://ssagara.blogspot.com
>>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>>>
>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Amila Suriarachchi <am...@gmail.com>.
On Tue, Mar 9, 2010 at 8:01 PM, Sagara Gunathunga <
sagara.gunathunga@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 6:37 PM, Amila Suriarachchi <
> amilasuriarachchi@gmail.com> wrote:
>
>>
>>
>> On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
>> sagara.gunathunga@gmail.com> wrote:
>>
>>>
>>>
>>> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
>>> amilasuriarachchi@gmail.com> wrote:
>>>
>>>>
>>>>
>>>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>>>> andreas.veithen@gmail.com> wrote:
>>>>
>>>>> I also created a proof-of-concept [1] that shows the feasibility of
>>>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>>>> implements a custom deployer that is based on ServiceDeployer, but
>>>>> replaces the code that builds the initial AxisService object from the
>>>>> WSDL by code that uses
>>>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>>>> introduces massive code duplication and is thus only valid as a
>>>>> proof-of-concept.
>>>>
>>>> Apart from this I think when we introduce a new deployer then we need to
>>>> have a different folder to
>>>> deploy files and a different extension.
>>>>
>>>>
>>>>
>>>>> To do this properly, it would be necessary to modify
>>>>> ServiceDeployer to create some sort of extension point that allows
>>>>> JAX-WS to supply the initial AxisService description.
>>>>>
>>>>
>>>> I think your intention here is to let users to deploy JAX-WS services as
>>>> aar files which already
>>>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>>>> services. ie. jaxws jar files can have an optional service.xml file in the
>>>> META-INF.
>>>>
>>>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2
>>>> does not have the concept of custom deployers. So at that time (time when
>>>> JAX-WS started) every thing deployed as .aar files. But latter there were
>>>> problems with JAX-WS support in aar files and introduced thin new custom
>>>> deployer concept to address this issue. Therefore adding JAX-WS support to
>>>> .aar files may not be the best approach.
>>>>
>>>
>>> Another important use case is to support JAX-WS based WAR archive
>>> deployment , lot of people want to integrate web services as a part of their
>>> web applications by adding AxisServlet in the web.xml file , this works
>>> fine for native services.xml based web service deployment but AFAIK we can't
>>> use WAR deployment with JAX-WS ,
>>>
>>
>> I have not tried this but I think it is possible. if you deploy a .jar
>> file under WEB-INF/servicejars I think it is possible.
>>
>
>
> Nice to hear about such workaround for JAX-WS WAR deployment, I will try
> out too . But having a descriptor file or annotations based JAX-WS
> deployment approach will increase the 'ease of use ' of the project
> specially when some one use build tools like Maven.
>
> 1.) In my experience service.xml based WAR based deployment is very simple
> and fit well with build tools like Maven and Ant. Only requirement is to add
> a services.xml into the WEB-INF/services directory no need to care about
> location of the .calss files. we can use Maven/ant default behavior for
> .class file locations ( classes or lib) and packaging . But in the
> mentioned approach we have to place a JAR file inside the
> WEB-INF/servicejars directory this may require to modify build script little
> bit. It would be great if we can come up with a solution so that we only
> place meta data file in the WEB-INF or WEB-INF/servicejars directory and
> classes are loaded from default Classpath ( like in service.xml based WAR
> deployment).
>
>
> 2.) Most of the other Java web service frameworks support JAX-WS WAR
> deployment only by placing a meta data file in the WEB-INF directory, if
> we can support to similar approach it will help out for people who move in
> to Axis2 from other frameworks. If they have a existing JAX-WS service they
> only need to write a descriptor file in order to deploy on Axis2 container.
>
> Above scenarios can be specific for few use cases but IMO with the maturity
> level of Axis2 project now we have to think about those aspects too.
>
>
>
>>
>>
>>> It's going to be a valuable feature if we can support for this.
>>>
>>>
>>>>
>>>> These are the options I can think of adding axis2 specific
>>>> custermizations to JAX-WS.
>>>>
>>>> 1. Support optional services.xml file in META-INF
>>>> Services.xml file is a too generic file. So people may confuse
>>>> with some options with services.xml file.
>>>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>>>> May have to duplicate some exising code in ServiceBuilder
>>>> 3. Introduce axis2 specific anotations to JAX-WS
>>>> May have problems with writting annotations to set the
>>>> security polices.
>>>>
>>>
>>>
>>> Personally I like to have a descriptor file such as axis2-jaxws.xml or
>>> usual service.xml rather introducing another set of axis2 specific
>>> annotations.
>>>
>>
>> Think about a scenario like this. Lets say some one has wirten a jax ws
>> service already and they need to deploy it under 'transportSession' in that
>> case isn't it easy to just add an anotation to existing jax ws web service
>> class instead of writtng a new services.xml file?
>>
>> Infact there can be instances where services.xml is useful and annotations
>> useful.
>>
>
> I can agree with your ideas, each of this approaches have their own
> specific usages, as an example sometimes people want to change some settings
> when they deploy the application without recompiling source codes having a
> descriptor file is a ideal for such use case. what about to support both
> options ?
>
+1.
I think that is the best way. For an example if we take a user who have
deployed a jax-ws jar in a standalone server like WSO2 WSAS then they may
not interested going for a web app or .aar file, but want to just put a
services.xml file inside the .jar file itself or add some annotaions.
On the other hand as you and Andreas has pointed out there are senarios
where .aar support is important as well.
thanks,
Amila.
>
> Thanks,
>
>
>
>>
>> thanks,
>> Amila.
>>
>>
>>> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
>>> great if we can utilize same JAR file with WAR deployment only adding a
>>> descriptor file into the WEB-INF directory.
>>>
>>> Thanks,
>>>
>>>
>>>>
>>>> Thanks,
>>>> Amila.
>>>>
>>>>>
>>>>> Andreas
>>>>>
>>>>> [1]
>>>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>>>
>>>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>>>> wrote:
>>>>> > Hi all,
>>>>> >
>>>>> > Andreas has already reported an issue [1] regarding the inability to
>>>>> > configure JAX-WS services. That is because we've removed support for
>>>>> a
>>>>> > services.xml. But there are many use cases where the user should be
>>>>> able to
>>>>> > configure the service according to his requirements. Following are
>>>>> some of
>>>>> > the very common examples.
>>>>> >
>>>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>>>> > application etc.)
>>>>> > [2] Ability to set ServiceTCCL
>>>>> > [3] Ability to specify service parameters
>>>>> >
>>>>> > In order to support these use cases, we have to support service
>>>>> > customizations somehow. If allowing a services.xml file is not a
>>>>> proper
>>>>> > solution, I think defining Axis2 specific annotations whould be a
>>>>> good
>>>>> > solution for this issue.
>>>>> >
>>>>> > WDYT?..
>>>>> >
>>>>> > Thanks,
>>>>> > ~Isuru
>>>>> >
>>>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>>>> >
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Amila Suriarachchi
>>>> WSO2 Inc.
>>>> blog: http://amilachinthaka.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Sagara Gunathunga
>>>
>>> Blog - http://ssagara.blogspot.com
>>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>>>
>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Amila Suriarachchi <am...@gmail.com>.
On Tue, Mar 9, 2010 at 8:01 PM, Sagara Gunathunga <
sagara.gunathunga@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 6:37 PM, Amila Suriarachchi <
> amilasuriarachchi@gmail.com> wrote:
>
>>
>>
>> On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
>> sagara.gunathunga@gmail.com> wrote:
>>
>>>
>>>
>>> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
>>> amilasuriarachchi@gmail.com> wrote:
>>>
>>>>
>>>>
>>>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>>>> andreas.veithen@gmail.com> wrote:
>>>>
>>>>> I also created a proof-of-concept [1] that shows the feasibility of
>>>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>>>> implements a custom deployer that is based on ServiceDeployer, but
>>>>> replaces the code that builds the initial AxisService object from the
>>>>> WSDL by code that uses
>>>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>>>> introduces massive code duplication and is thus only valid as a
>>>>> proof-of-concept.
>>>>
>>>> Apart from this I think when we introduce a new deployer then we need to
>>>> have a different folder to
>>>> deploy files and a different extension.
>>>>
>>>>
>>>>
>>>>> To do this properly, it would be necessary to modify
>>>>> ServiceDeployer to create some sort of extension point that allows
>>>>> JAX-WS to supply the initial AxisService description.
>>>>>
>>>>
>>>> I think your intention here is to let users to deploy JAX-WS services as
>>>> aar files which already
>>>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>>>> services. ie. jaxws jar files can have an optional service.xml file in the
>>>> META-INF.
>>>>
>>>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2
>>>> does not have the concept of custom deployers. So at that time (time when
>>>> JAX-WS started) every thing deployed as .aar files. But latter there were
>>>> problems with JAX-WS support in aar files and introduced thin new custom
>>>> deployer concept to address this issue. Therefore adding JAX-WS support to
>>>> .aar files may not be the best approach.
>>>>
>>>
>>> Another important use case is to support JAX-WS based WAR archive
>>> deployment , lot of people want to integrate web services as a part of their
>>> web applications by adding AxisServlet in the web.xml file , this works
>>> fine for native services.xml based web service deployment but AFAIK we can't
>>> use WAR deployment with JAX-WS ,
>>>
>>
>> I have not tried this but I think it is possible. if you deploy a .jar
>> file under WEB-INF/servicejars I think it is possible.
>>
>
>
> Nice to hear about such workaround for JAX-WS WAR deployment, I will try
> out too . But having a descriptor file or annotations based JAX-WS
> deployment approach will increase the 'ease of use ' of the project
> specially when some one use build tools like Maven.
>
> 1.) In my experience service.xml based WAR based deployment is very simple
> and fit well with build tools like Maven and Ant. Only requirement is to add
> a services.xml into the WEB-INF/services directory no need to care about
> location of the .calss files. we can use Maven/ant default behavior for
> .class file locations ( classes or lib) and packaging . But in the
> mentioned approach we have to place a JAR file inside the
> WEB-INF/servicejars directory this may require to modify build script little
> bit. It would be great if we can come up with a solution so that we only
> place meta data file in the WEB-INF or WEB-INF/servicejars directory and
> classes are loaded from default Classpath ( like in service.xml based WAR
> deployment).
>
>
> 2.) Most of the other Java web service frameworks support JAX-WS WAR
> deployment only by placing a meta data file in the WEB-INF directory, if
> we can support to similar approach it will help out for people who move in
> to Axis2 from other frameworks. If they have a existing JAX-WS service they
> only need to write a descriptor file in order to deploy on Axis2 container.
>
> Above scenarios can be specific for few use cases but IMO with the maturity
> level of Axis2 project now we have to think about those aspects too.
>
>
>
>>
>>
>>> It's going to be a valuable feature if we can support for this.
>>>
>>>
>>>>
>>>> These are the options I can think of adding axis2 specific
>>>> custermizations to JAX-WS.
>>>>
>>>> 1. Support optional services.xml file in META-INF
>>>> Services.xml file is a too generic file. So people may confuse
>>>> with some options with services.xml file.
>>>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>>>> May have to duplicate some exising code in ServiceBuilder
>>>> 3. Introduce axis2 specific anotations to JAX-WS
>>>> May have problems with writting annotations to set the
>>>> security polices.
>>>>
>>>
>>>
>>> Personally I like to have a descriptor file such as axis2-jaxws.xml or
>>> usual service.xml rather introducing another set of axis2 specific
>>> annotations.
>>>
>>
>> Think about a scenario like this. Lets say some one has wirten a jax ws
>> service already and they need to deploy it under 'transportSession' in that
>> case isn't it easy to just add an anotation to existing jax ws web service
>> class instead of writtng a new services.xml file?
>>
>> Infact there can be instances where services.xml is useful and annotations
>> useful.
>>
>
> I can agree with your ideas, each of this approaches have their own
> specific usages, as an example sometimes people want to change some settings
> when they deploy the application without recompiling source codes having a
> descriptor file is a ideal for such use case. what about to support both
> options ?
>
+1.
I think that is the best way. For an example if we take a user who have
deployed a jax-ws jar in a standalone server like WSO2 WSAS then they may
not interested going for a web app or .aar file, but want to just put a
services.xml file inside the .jar file itself or add some annotaions.
On the other hand as you and Andreas has pointed out there are senarios
where .aar support is important as well.
thanks,
Amila.
>
> Thanks,
>
>
>
>>
>> thanks,
>> Amila.
>>
>>
>>> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
>>> great if we can utilize same JAR file with WAR deployment only adding a
>>> descriptor file into the WEB-INF directory.
>>>
>>> Thanks,
>>>
>>>
>>>>
>>>> Thanks,
>>>> Amila.
>>>>
>>>>>
>>>>> Andreas
>>>>>
>>>>> [1]
>>>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>>>
>>>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>>>> wrote:
>>>>> > Hi all,
>>>>> >
>>>>> > Andreas has already reported an issue [1] regarding the inability to
>>>>> > configure JAX-WS services. That is because we've removed support for
>>>>> a
>>>>> > services.xml. But there are many use cases where the user should be
>>>>> able to
>>>>> > configure the service according to his requirements. Following are
>>>>> some of
>>>>> > the very common examples.
>>>>> >
>>>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>>>> > application etc.)
>>>>> > [2] Ability to set ServiceTCCL
>>>>> > [3] Ability to specify service parameters
>>>>> >
>>>>> > In order to support these use cases, we have to support service
>>>>> > customizations somehow. If allowing a services.xml file is not a
>>>>> proper
>>>>> > solution, I think defining Axis2 specific annotations whould be a
>>>>> good
>>>>> > solution for this issue.
>>>>> >
>>>>> > WDYT?..
>>>>> >
>>>>> > Thanks,
>>>>> > ~Isuru
>>>>> >
>>>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>>>> >
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Amila Suriarachchi
>>>> WSO2 Inc.
>>>> blog: http://amilachinthaka.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Sagara Gunathunga
>>>
>>> Blog - http://ssagara.blogspot.com
>>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>>>
>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Sagara Gunathunga <sa...@gmail.com>.
On Tue, Mar 9, 2010 at 6:37 PM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
> sagara.gunathunga@gmail.com> wrote:
>
>>
>>
>> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
>> amilasuriarachchi@gmail.com> wrote:
>>
>>>
>>>
>>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com> wrote:
>>>
>>>> I also created a proof-of-concept [1] that shows the feasibility of
>>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>>> implements a custom deployer that is based on ServiceDeployer, but
>>>> replaces the code that builds the initial AxisService object from the
>>>> WSDL by code that uses
>>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>>> introduces massive code duplication and is thus only valid as a
>>>> proof-of-concept.
>>>
>>> Apart from this I think when we introduce a new deployer then we need to
>>> have a different folder to
>>> deploy files and a different extension.
>>>
>>>
>>>
>>>> To do this properly, it would be necessary to modify
>>>> ServiceDeployer to create some sort of extension point that allows
>>>> JAX-WS to supply the initial AxisService description.
>>>>
>>>
>>> I think your intention here is to let users to deploy JAX-WS services as
>>> aar files which already
>>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>>> services. ie. jaxws jar files can have an optional service.xml file in the
>>> META-INF.
>>>
>>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>>> not have the concept of custom deployers. So at that time (time when JAX-WS
>>> started) every thing deployed as .aar files. But latter there were problems
>>> with JAX-WS support in aar files and introduced thin new custom deployer
>>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>>> may not be the best approach.
>>>
>>
>> Another important use case is to support JAX-WS based WAR archive
>> deployment , lot of people want to integrate web services as a part of their
>> web applications by adding AxisServlet in the web.xml file , this works
>> fine for native services.xml based web service deployment but AFAIK we can't
>> use WAR deployment with JAX-WS ,
>>
>
> I have not tried this but I think it is possible. if you deploy a .jar file
> under WEB-INF/servicejars I think it is possible.
>
Nice to hear about such workaround for JAX-WS WAR deployment, I will try out
too . But having a descriptor file or annotations based JAX-WS deployment
approach will increase the 'ease of use ' of the project specially when some
one use build tools like Maven.
1.) In my experience service.xml based WAR based deployment is very simple
and fit well with build tools like Maven and Ant. Only requirement is to add
a services.xml into the WEB-INF/services directory no need to care about
location of the .calss files. we can use Maven/ant default behavior for
.class file locations ( classes or lib) and packaging . But in the
mentioned approach we have to place a JAR file inside the
WEB-INF/servicejars directory this may require to modify build script little
bit. It would be great if we can come up with a solution so that we only
place meta data file in the WEB-INF or WEB-INF/servicejars directory and
classes are loaded from default Classpath ( like in service.xml based WAR
deployment).
2.) Most of the other Java web service frameworks support JAX-WS WAR
deployment only by placing a meta data file in the WEB-INF directory, if
we can support to similar approach it will help out for people who move in
to Axis2 from other frameworks. If they have a existing JAX-WS service they
only need to write a descriptor file in order to deploy on Axis2 container.
Above scenarios can be specific for few use cases but IMO with the maturity
level of Axis2 project now we have to think about those aspects too.
>
>
>> It's going to be a valuable feature if we can support for this.
>>
>>
>>>
>>> These are the options I can think of adding axis2 specific
>>> custermizations to JAX-WS.
>>>
>>> 1. Support optional services.xml file in META-INF
>>> Services.xml file is a too generic file. So people may confuse
>>> with some options with services.xml file.
>>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>>> May have to duplicate some exising code in ServiceBuilder
>>> 3. Introduce axis2 specific anotations to JAX-WS
>>> May have problems with writting annotations to set the
>>> security polices.
>>>
>>
>>
>> Personally I like to have a descriptor file such as axis2-jaxws.xml or
>> usual service.xml rather introducing another set of axis2 specific
>> annotations.
>>
>
> Think about a scenario like this. Lets say some one has wirten a jax ws
> service already and they need to deploy it under 'transportSession' in that
> case isn't it easy to just add an anotation to existing jax ws web service
> class instead of writtng a new services.xml file?
>
> Infact there can be instances where services.xml is useful and annotations
> useful.
>
I can agree with your ideas, each of this approaches have their own
specific usages, as an example sometimes people want to change some settings
when they deploy the application without recompiling source codes having a
descriptor file is a ideal for such use case. what about to support both
options ?
Thanks,
>
> thanks,
> Amila.
>
>
>> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
>> great if we can utilize same JAR file with WAR deployment only adding a
>> descriptor file into the WEB-INF directory.
>>
>> Thanks,
>>
>>
>>>
>>> Thanks,
>>> Amila.
>>>
>>>>
>>>> Andreas
>>>>
>>>> [1]
>>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>>
>>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>>> wrote:
>>>> > Hi all,
>>>> >
>>>> > Andreas has already reported an issue [1] regarding the inability to
>>>> > configure JAX-WS services. That is because we've removed support for a
>>>> > services.xml. But there are many use cases where the user should be
>>>> able to
>>>> > configure the service according to his requirements. Following are
>>>> some of
>>>> > the very common examples.
>>>> >
>>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>>> > application etc.)
>>>> > [2] Ability to set ServiceTCCL
>>>> > [3] Ability to specify service parameters
>>>> >
>>>> > In order to support these use cases, we have to support service
>>>> > customizations somehow. If allowing a services.xml file is not a
>>>> proper
>>>> > solution, I think defining Axis2 specific annotations whould be a good
>>>> > solution for this issue.
>>>> >
>>>> > WDYT?..
>>>> >
>>>> > Thanks,
>>>> > ~Isuru
>>>> >
>>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>>> >
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Amila Suriarachchi
>>> WSO2 Inc.
>>> blog: http://amilachinthaka.blogspot.com/
>>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Sagara Gunathunga <sa...@gmail.com>.
On Tue, Mar 9, 2010 at 6:37 PM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
> sagara.gunathunga@gmail.com> wrote:
>
>>
>>
>> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
>> amilasuriarachchi@gmail.com> wrote:
>>
>>>
>>>
>>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com> wrote:
>>>
>>>> I also created a proof-of-concept [1] that shows the feasibility of
>>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>>> implements a custom deployer that is based on ServiceDeployer, but
>>>> replaces the code that builds the initial AxisService object from the
>>>> WSDL by code that uses
>>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>>> introduces massive code duplication and is thus only valid as a
>>>> proof-of-concept.
>>>
>>> Apart from this I think when we introduce a new deployer then we need to
>>> have a different folder to
>>> deploy files and a different extension.
>>>
>>>
>>>
>>>> To do this properly, it would be necessary to modify
>>>> ServiceDeployer to create some sort of extension point that allows
>>>> JAX-WS to supply the initial AxisService description.
>>>>
>>>
>>> I think your intention here is to let users to deploy JAX-WS services as
>>> aar files which already
>>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>>> services. ie. jaxws jar files can have an optional service.xml file in the
>>> META-INF.
>>>
>>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>>> not have the concept of custom deployers. So at that time (time when JAX-WS
>>> started) every thing deployed as .aar files. But latter there were problems
>>> with JAX-WS support in aar files and introduced thin new custom deployer
>>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>>> may not be the best approach.
>>>
>>
>> Another important use case is to support JAX-WS based WAR archive
>> deployment , lot of people want to integrate web services as a part of their
>> web applications by adding AxisServlet in the web.xml file , this works
>> fine for native services.xml based web service deployment but AFAIK we can't
>> use WAR deployment with JAX-WS ,
>>
>
> I have not tried this but I think it is possible. if you deploy a .jar file
> under WEB-INF/servicejars I think it is possible.
>
Nice to hear about such workaround for JAX-WS WAR deployment, I will try out
too . But having a descriptor file or annotations based JAX-WS deployment
approach will increase the 'ease of use ' of the project specially when some
one use build tools like Maven.
1.) In my experience service.xml based WAR based deployment is very simple
and fit well with build tools like Maven and Ant. Only requirement is to add
a services.xml into the WEB-INF/services directory no need to care about
location of the .calss files. we can use Maven/ant default behavior for
.class file locations ( classes or lib) and packaging . But in the
mentioned approach we have to place a JAR file inside the
WEB-INF/servicejars directory this may require to modify build script little
bit. It would be great if we can come up with a solution so that we only
place meta data file in the WEB-INF or WEB-INF/servicejars directory and
classes are loaded from default Classpath ( like in service.xml based WAR
deployment).
2.) Most of the other Java web service frameworks support JAX-WS WAR
deployment only by placing a meta data file in the WEB-INF directory, if
we can support to similar approach it will help out for people who move in
to Axis2 from other frameworks. If they have a existing JAX-WS service they
only need to write a descriptor file in order to deploy on Axis2 container.
Above scenarios can be specific for few use cases but IMO with the maturity
level of Axis2 project now we have to think about those aspects too.
>
>
>> It's going to be a valuable feature if we can support for this.
>>
>>
>>>
>>> These are the options I can think of adding axis2 specific
>>> custermizations to JAX-WS.
>>>
>>> 1. Support optional services.xml file in META-INF
>>> Services.xml file is a too generic file. So people may confuse
>>> with some options with services.xml file.
>>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>>> May have to duplicate some exising code in ServiceBuilder
>>> 3. Introduce axis2 specific anotations to JAX-WS
>>> May have problems with writting annotations to set the
>>> security polices.
>>>
>>
>>
>> Personally I like to have a descriptor file such as axis2-jaxws.xml or
>> usual service.xml rather introducing another set of axis2 specific
>> annotations.
>>
>
> Think about a scenario like this. Lets say some one has wirten a jax ws
> service already and they need to deploy it under 'transportSession' in that
> case isn't it easy to just add an anotation to existing jax ws web service
> class instead of writtng a new services.xml file?
>
> Infact there can be instances where services.xml is useful and annotations
> useful.
>
I can agree with your ideas, each of this approaches have their own
specific usages, as an example sometimes people want to change some settings
when they deploy the application without recompiling source codes having a
descriptor file is a ideal for such use case. what about to support both
options ?
Thanks,
>
> thanks,
> Amila.
>
>
>> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
>> great if we can utilize same JAR file with WAR deployment only adding a
>> descriptor file into the WEB-INF directory.
>>
>> Thanks,
>>
>>
>>>
>>> Thanks,
>>> Amila.
>>>
>>>>
>>>> Andreas
>>>>
>>>> [1]
>>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>>
>>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>>> wrote:
>>>> > Hi all,
>>>> >
>>>> > Andreas has already reported an issue [1] regarding the inability to
>>>> > configure JAX-WS services. That is because we've removed support for a
>>>> > services.xml. But there are many use cases where the user should be
>>>> able to
>>>> > configure the service according to his requirements. Following are
>>>> some of
>>>> > the very common examples.
>>>> >
>>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>>> > application etc.)
>>>> > [2] Ability to set ServiceTCCL
>>>> > [3] Ability to specify service parameters
>>>> >
>>>> > In order to support these use cases, we have to support service
>>>> > customizations somehow. If allowing a services.xml file is not a
>>>> proper
>>>> > solution, I think defining Axis2 specific annotations whould be a good
>>>> > solution for this issue.
>>>> >
>>>> > WDYT?..
>>>> >
>>>> > Thanks,
>>>> > ~Isuru
>>>> >
>>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>>> >
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Amila Suriarachchi
>>> WSO2 Inc.
>>> blog: http://amilachinthaka.blogspot.com/
>>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by chris roberts <ca...@gmail.com>.
can somebody help me unsubscribe? The unsubscribe link doesn't work and my
inbox is filling up with axis emails every day. I never registered for axis
in the firs place so I'm wondering if some changes have happened recently,
meaning that one mailing list has merged with another.
Thanks for any help,
Chris
On 9 March 2010 13:07, Amila Suriarachchi <am...@gmail.com>wrote:
>
>
> On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
> sagara.gunathunga@gmail.com> wrote:
>
>>
>>
>> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
>> amilasuriarachchi@gmail.com> wrote:
>>
>>>
>>>
>>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com> wrote:
>>>
>>>> I also created a proof-of-concept [1] that shows the feasibility of
>>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>>> implements a custom deployer that is based on ServiceDeployer, but
>>>> replaces the code that builds the initial AxisService object from the
>>>> WSDL by code that uses
>>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>>> introduces massive code duplication and is thus only valid as a
>>>> proof-of-concept.
>>>
>>> Apart from this I think when we introduce a new deployer then we need to
>>> have a different folder to
>>> deploy files and a different extension.
>>>
>>>
>>>
>>>> To do this properly, it would be necessary to modify
>>>> ServiceDeployer to create some sort of extension point that allows
>>>> JAX-WS to supply the initial AxisService description.
>>>>
>>>
>>> I think your intention here is to let users to deploy JAX-WS services as
>>> aar files which already
>>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>>> services. ie. jaxws jar files can have an optional service.xml file in the
>>> META-INF.
>>>
>>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>>> not have the concept of custom deployers. So at that time (time when JAX-WS
>>> started) every thing deployed as .aar files. But latter there were problems
>>> with JAX-WS support in aar files and introduced thin new custom deployer
>>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>>> may not be the best approach.
>>>
>>
>> Another important use case is to support JAX-WS based WAR archive
>> deployment , lot of people want to integrate web services as a part of their
>> web applications by adding AxisServlet in the web.xml file , this works
>> fine for native services.xml based web service deployment but AFAIK we can't
>> use WAR deployment with JAX-WS ,
>>
>
> I have not tried this but I think it is possible. if you deploy a .jar file
> under WEB-INF/servicejars I think it is possible.
>
>
>> It's going to be a valuable feature if we can support for this.
>>
>>
>>>
>>> These are the options I can think of adding axis2 specific
>>> custermizations to JAX-WS.
>>>
>>> 1. Support optional services.xml file in META-INF
>>> Services.xml file is a too generic file. So people may confuse
>>> with some options with services.xml file.
>>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>>> May have to duplicate some exising code in ServiceBuilder
>>> 3. Introduce axis2 specific anotations to JAX-WS
>>> May have problems with writting annotations to set the
>>> security polices.
>>>
>>
>>
>> Personally I like to have a descriptor file such as axis2-jaxws.xml or
>> usual service.xml rather introducing another set of axis2 specific
>> annotations.
>>
>
> Think about a scenario like this. Lets say some one has wirten a jax ws
> service already and they need to deploy it under 'transportSession' in that
> case isn't it easy to just add an anotation to existing jax ws web service
> class instead of writtng a new services.xml file?
>
> Infact there can be instances where services.xml is useful and annotations
> useful.
>
> thanks,
> Amila.
>
>
>> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
>> great if we can utilize same JAR file with WAR deployment only adding a
>> descriptor file into the WEB-INF directory.
>>
>> Thanks,
>>
>>
>>>
>>> Thanks,
>>> Amila.
>>>
>>>>
>>>> Andreas
>>>>
>>>> [1]
>>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>>
>>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>>> wrote:
>>>> > Hi all,
>>>> >
>>>> > Andreas has already reported an issue [1] regarding the inability to
>>>> > configure JAX-WS services. That is because we've removed support for a
>>>> > services.xml. But there are many use cases where the user should be
>>>> able to
>>>> > configure the service according to his requirements. Following are
>>>> some of
>>>> > the very common examples.
>>>> >
>>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>>> > application etc.)
>>>> > [2] Ability to set ServiceTCCL
>>>> > [3] Ability to specify service parameters
>>>> >
>>>> > In order to support these use cases, we have to support service
>>>> > customizations somehow. If allowing a services.xml file is not a
>>>> proper
>>>> > solution, I think defining Axis2 specific annotations whould be a good
>>>> > solution for this issue.
>>>> >
>>>> > WDYT?..
>>>> >
>>>> > Thanks,
>>>> > ~Isuru
>>>> >
>>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>>> >
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Amila Suriarachchi
>>> WSO2 Inc.
>>> blog: http://amilachinthaka.blogspot.com/
>>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by chris roberts <ca...@gmail.com>.
can somebody help me unsubscribe? The unsubscribe link doesn't work and my
inbox is filling up with axis emails every day. I never registered for axis
in the firs place so I'm wondering if some changes have happened recently,
meaning that one mailing list has merged with another.
Thanks for any help,
Chris
On 9 March 2010 13:07, Amila Suriarachchi <am...@gmail.com>wrote:
>
>
> On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
> sagara.gunathunga@gmail.com> wrote:
>
>>
>>
>> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
>> amilasuriarachchi@gmail.com> wrote:
>>
>>>
>>>
>>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com> wrote:
>>>
>>>> I also created a proof-of-concept [1] that shows the feasibility of
>>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>>> implements a custom deployer that is based on ServiceDeployer, but
>>>> replaces the code that builds the initial AxisService object from the
>>>> WSDL by code that uses
>>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>>> introduces massive code duplication and is thus only valid as a
>>>> proof-of-concept.
>>>
>>> Apart from this I think when we introduce a new deployer then we need to
>>> have a different folder to
>>> deploy files and a different extension.
>>>
>>>
>>>
>>>> To do this properly, it would be necessary to modify
>>>> ServiceDeployer to create some sort of extension point that allows
>>>> JAX-WS to supply the initial AxisService description.
>>>>
>>>
>>> I think your intention here is to let users to deploy JAX-WS services as
>>> aar files which already
>>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>>> services. ie. jaxws jar files can have an optional service.xml file in the
>>> META-INF.
>>>
>>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>>> not have the concept of custom deployers. So at that time (time when JAX-WS
>>> started) every thing deployed as .aar files. But latter there were problems
>>> with JAX-WS support in aar files and introduced thin new custom deployer
>>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>>> may not be the best approach.
>>>
>>
>> Another important use case is to support JAX-WS based WAR archive
>> deployment , lot of people want to integrate web services as a part of their
>> web applications by adding AxisServlet in the web.xml file , this works
>> fine for native services.xml based web service deployment but AFAIK we can't
>> use WAR deployment with JAX-WS ,
>>
>
> I have not tried this but I think it is possible. if you deploy a .jar file
> under WEB-INF/servicejars I think it is possible.
>
>
>> It's going to be a valuable feature if we can support for this.
>>
>>
>>>
>>> These are the options I can think of adding axis2 specific
>>> custermizations to JAX-WS.
>>>
>>> 1. Support optional services.xml file in META-INF
>>> Services.xml file is a too generic file. So people may confuse
>>> with some options with services.xml file.
>>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>>> May have to duplicate some exising code in ServiceBuilder
>>> 3. Introduce axis2 specific anotations to JAX-WS
>>> May have problems with writting annotations to set the
>>> security polices.
>>>
>>
>>
>> Personally I like to have a descriptor file such as axis2-jaxws.xml or
>> usual service.xml rather introducing another set of axis2 specific
>> annotations.
>>
>
> Think about a scenario like this. Lets say some one has wirten a jax ws
> service already and they need to deploy it under 'transportSession' in that
> case isn't it easy to just add an anotation to existing jax ws web service
> class instead of writtng a new services.xml file?
>
> Infact there can be instances where services.xml is useful and annotations
> useful.
>
> thanks,
> Amila.
>
>
>> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
>> great if we can utilize same JAR file with WAR deployment only adding a
>> descriptor file into the WEB-INF directory.
>>
>> Thanks,
>>
>>
>>>
>>> Thanks,
>>> Amila.
>>>
>>>>
>>>> Andreas
>>>>
>>>> [1]
>>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>>
>>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>>> wrote:
>>>> > Hi all,
>>>> >
>>>> > Andreas has already reported an issue [1] regarding the inability to
>>>> > configure JAX-WS services. That is because we've removed support for a
>>>> > services.xml. But there are many use cases where the user should be
>>>> able to
>>>> > configure the service according to his requirements. Following are
>>>> some of
>>>> > the very common examples.
>>>> >
>>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>>> > application etc.)
>>>> > [2] Ability to set ServiceTCCL
>>>> > [3] Ability to specify service parameters
>>>> >
>>>> > In order to support these use cases, we have to support service
>>>> > customizations somehow. If allowing a services.xml file is not a
>>>> proper
>>>> > solution, I think defining Axis2 specific annotations whould be a good
>>>> > solution for this issue.
>>>> >
>>>> > WDYT?..
>>>> >
>>>> > Thanks,
>>>> > ~Isuru
>>>> >
>>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>>> >
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Amila Suriarachchi
>>> WSO2 Inc.
>>> blog: http://amilachinthaka.blogspot.com/
>>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Sagara Gunathunga <sa...@gmail.com>.
On Tue, Mar 9, 2010 at 6:37 PM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
> sagara.gunathunga@gmail.com> wrote:
>
>>
>>
>> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
>> amilasuriarachchi@gmail.com> wrote:
>>
>>>
>>>
>>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com> wrote:
>>>
>>>> I also created a proof-of-concept [1] that shows the feasibility of
>>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>>> implements a custom deployer that is based on ServiceDeployer, but
>>>> replaces the code that builds the initial AxisService object from the
>>>> WSDL by code that uses
>>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>>> introduces massive code duplication and is thus only valid as a
>>>> proof-of-concept.
>>>
>>> Apart from this I think when we introduce a new deployer then we need to
>>> have a different folder to
>>> deploy files and a different extension.
>>>
>>>
>>>
>>>> To do this properly, it would be necessary to modify
>>>> ServiceDeployer to create some sort of extension point that allows
>>>> JAX-WS to supply the initial AxisService description.
>>>>
>>>
>>> I think your intention here is to let users to deploy JAX-WS services as
>>> aar files which already
>>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>>> services. ie. jaxws jar files can have an optional service.xml file in the
>>> META-INF.
>>>
>>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>>> not have the concept of custom deployers. So at that time (time when JAX-WS
>>> started) every thing deployed as .aar files. But latter there were problems
>>> with JAX-WS support in aar files and introduced thin new custom deployer
>>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>>> may not be the best approach.
>>>
>>
>> Another important use case is to support JAX-WS based WAR archive
>> deployment , lot of people want to integrate web services as a part of their
>> web applications by adding AxisServlet in the web.xml file , this works
>> fine for native services.xml based web service deployment but AFAIK we can't
>> use WAR deployment with JAX-WS ,
>>
>
> I have not tried this but I think it is possible. if you deploy a .jar file
> under WEB-INF/servicejars I think it is possible.
>
Nice to hear about such workaround for JAX-WS WAR deployment, I will try out
too . But having a descriptor file or annotations based JAX-WS deployment
approach will increase the 'ease of use ' of the project specially when some
one use build tools like Maven.
1.) In my experience service.xml based WAR based deployment is very simple
and fit well with build tools like Maven and Ant. Only requirement is to add
a services.xml into the WEB-INF/services directory no need to care about
location of the .calss files. we can use Maven/ant default behavior for
.class file locations ( classes or lib) and packaging . But in the
mentioned approach we have to place a JAR file inside the
WEB-INF/servicejars directory this may require to modify build script little
bit. It would be great if we can come up with a solution so that we only
place meta data file in the WEB-INF or WEB-INF/servicejars directory and
classes are loaded from default Classpath ( like in service.xml based WAR
deployment).
2.) Most of the other Java web service frameworks support JAX-WS WAR
deployment only by placing a meta data file in the WEB-INF directory, if
we can support to similar approach it will help out for people who move in
to Axis2 from other frameworks. If they have a existing JAX-WS service they
only need to write a descriptor file in order to deploy on Axis2 container.
Above scenarios can be specific for few use cases but IMO with the maturity
level of Axis2 project now we have to think about those aspects too.
>
>
>> It's going to be a valuable feature if we can support for this.
>>
>>
>>>
>>> These are the options I can think of adding axis2 specific
>>> custermizations to JAX-WS.
>>>
>>> 1. Support optional services.xml file in META-INF
>>> Services.xml file is a too generic file. So people may confuse
>>> with some options with services.xml file.
>>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>>> May have to duplicate some exising code in ServiceBuilder
>>> 3. Introduce axis2 specific anotations to JAX-WS
>>> May have problems with writting annotations to set the
>>> security polices.
>>>
>>
>>
>> Personally I like to have a descriptor file such as axis2-jaxws.xml or
>> usual service.xml rather introducing another set of axis2 specific
>> annotations.
>>
>
> Think about a scenario like this. Lets say some one has wirten a jax ws
> service already and they need to deploy it under 'transportSession' in that
> case isn't it easy to just add an anotation to existing jax ws web service
> class instead of writtng a new services.xml file?
>
> Infact there can be instances where services.xml is useful and annotations
> useful.
>
I can agree with your ideas, each of this approaches have their own
specific usages, as an example sometimes people want to change some settings
when they deploy the application without recompiling source codes having a
descriptor file is a ideal for such use case. what about to support both
options ?
Thanks,
>
> thanks,
> Amila.
>
>
>> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
>> great if we can utilize same JAR file with WAR deployment only adding a
>> descriptor file into the WEB-INF directory.
>>
>> Thanks,
>>
>>
>>>
>>> Thanks,
>>> Amila.
>>>
>>>>
>>>> Andreas
>>>>
>>>> [1]
>>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>>
>>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>>> wrote:
>>>> > Hi all,
>>>> >
>>>> > Andreas has already reported an issue [1] regarding the inability to
>>>> > configure JAX-WS services. That is because we've removed support for a
>>>> > services.xml. But there are many use cases where the user should be
>>>> able to
>>>> > configure the service according to his requirements. Following are
>>>> some of
>>>> > the very common examples.
>>>> >
>>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>>> > application etc.)
>>>> > [2] Ability to set ServiceTCCL
>>>> > [3] Ability to specify service parameters
>>>> >
>>>> > In order to support these use cases, we have to support service
>>>> > customizations somehow. If allowing a services.xml file is not a
>>>> proper
>>>> > solution, I think defining Axis2 specific annotations whould be a good
>>>> > solution for this issue.
>>>> >
>>>> > WDYT?..
>>>> >
>>>> > Thanks,
>>>> > ~Isuru
>>>> >
>>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>>> >
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Amila Suriarachchi
>>> WSO2 Inc.
>>> blog: http://amilachinthaka.blogspot.com/
>>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by chris roberts <ca...@gmail.com>.
can somebody help me unsubscribe? The unsubscribe link doesn't work and my
inbox is filling up with axis emails every day. I never registered for axis
in the firs place so I'm wondering if some changes have happened recently,
meaning that one mailing list has merged with another.
Thanks for any help,
Chris
On 9 March 2010 13:07, Amila Suriarachchi <am...@gmail.com>wrote:
>
>
> On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
> sagara.gunathunga@gmail.com> wrote:
>
>>
>>
>> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
>> amilasuriarachchi@gmail.com> wrote:
>>
>>>
>>>
>>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com> wrote:
>>>
>>>> I also created a proof-of-concept [1] that shows the feasibility of
>>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>>> implements a custom deployer that is based on ServiceDeployer, but
>>>> replaces the code that builds the initial AxisService object from the
>>>> WSDL by code that uses
>>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>>> introduces massive code duplication and is thus only valid as a
>>>> proof-of-concept.
>>>
>>> Apart from this I think when we introduce a new deployer then we need to
>>> have a different folder to
>>> deploy files and a different extension.
>>>
>>>
>>>
>>>> To do this properly, it would be necessary to modify
>>>> ServiceDeployer to create some sort of extension point that allows
>>>> JAX-WS to supply the initial AxisService description.
>>>>
>>>
>>> I think your intention here is to let users to deploy JAX-WS services as
>>> aar files which already
>>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>>> services. ie. jaxws jar files can have an optional service.xml file in the
>>> META-INF.
>>>
>>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>>> not have the concept of custom deployers. So at that time (time when JAX-WS
>>> started) every thing deployed as .aar files. But latter there were problems
>>> with JAX-WS support in aar files and introduced thin new custom deployer
>>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>>> may not be the best approach.
>>>
>>
>> Another important use case is to support JAX-WS based WAR archive
>> deployment , lot of people want to integrate web services as a part of their
>> web applications by adding AxisServlet in the web.xml file , this works
>> fine for native services.xml based web service deployment but AFAIK we can't
>> use WAR deployment with JAX-WS ,
>>
>
> I have not tried this but I think it is possible. if you deploy a .jar file
> under WEB-INF/servicejars I think it is possible.
>
>
>> It's going to be a valuable feature if we can support for this.
>>
>>
>>>
>>> These are the options I can think of adding axis2 specific
>>> custermizations to JAX-WS.
>>>
>>> 1. Support optional services.xml file in META-INF
>>> Services.xml file is a too generic file. So people may confuse
>>> with some options with services.xml file.
>>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>>> May have to duplicate some exising code in ServiceBuilder
>>> 3. Introduce axis2 specific anotations to JAX-WS
>>> May have problems with writting annotations to set the
>>> security polices.
>>>
>>
>>
>> Personally I like to have a descriptor file such as axis2-jaxws.xml or
>> usual service.xml rather introducing another set of axis2 specific
>> annotations.
>>
>
> Think about a scenario like this. Lets say some one has wirten a jax ws
> service already and they need to deploy it under 'transportSession' in that
> case isn't it easy to just add an anotation to existing jax ws web service
> class instead of writtng a new services.xml file?
>
> Infact there can be instances where services.xml is useful and annotations
> useful.
>
> thanks,
> Amila.
>
>
>> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
>> great if we can utilize same JAR file with WAR deployment only adding a
>> descriptor file into the WEB-INF directory.
>>
>> Thanks,
>>
>>
>>>
>>> Thanks,
>>> Amila.
>>>
>>>>
>>>> Andreas
>>>>
>>>> [1]
>>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>>
>>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>>> wrote:
>>>> > Hi all,
>>>> >
>>>> > Andreas has already reported an issue [1] regarding the inability to
>>>> > configure JAX-WS services. That is because we've removed support for a
>>>> > services.xml. But there are many use cases where the user should be
>>>> able to
>>>> > configure the service according to his requirements. Following are
>>>> some of
>>>> > the very common examples.
>>>> >
>>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>>> > application etc.)
>>>> > [2] Ability to set ServiceTCCL
>>>> > [3] Ability to specify service parameters
>>>> >
>>>> > In order to support these use cases, we have to support service
>>>> > customizations somehow. If allowing a services.xml file is not a
>>>> proper
>>>> > solution, I think defining Axis2 specific annotations whould be a good
>>>> > solution for this issue.
>>>> >
>>>> > WDYT?..
>>>> >
>>>> > Thanks,
>>>> > ~Isuru
>>>> >
>>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>>> >
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Amila Suriarachchi
>>> WSO2 Inc.
>>> blog: http://amilachinthaka.blogspot.com/
>>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Sagara Gunathunga <sa...@gmail.com>.
On Tue, Mar 9, 2010 at 6:37 PM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
> sagara.gunathunga@gmail.com> wrote:
>
>>
>>
>> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
>> amilasuriarachchi@gmail.com> wrote:
>>
>>>
>>>
>>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com> wrote:
>>>
>>>> I also created a proof-of-concept [1] that shows the feasibility of
>>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>>> implements a custom deployer that is based on ServiceDeployer, but
>>>> replaces the code that builds the initial AxisService object from the
>>>> WSDL by code that uses
>>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>>> introduces massive code duplication and is thus only valid as a
>>>> proof-of-concept.
>>>
>>> Apart from this I think when we introduce a new deployer then we need to
>>> have a different folder to
>>> deploy files and a different extension.
>>>
>>>
>>>
>>>> To do this properly, it would be necessary to modify
>>>> ServiceDeployer to create some sort of extension point that allows
>>>> JAX-WS to supply the initial AxisService description.
>>>>
>>>
>>> I think your intention here is to let users to deploy JAX-WS services as
>>> aar files which already
>>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>>> services. ie. jaxws jar files can have an optional service.xml file in the
>>> META-INF.
>>>
>>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>>> not have the concept of custom deployers. So at that time (time when JAX-WS
>>> started) every thing deployed as .aar files. But latter there were problems
>>> with JAX-WS support in aar files and introduced thin new custom deployer
>>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>>> may not be the best approach.
>>>
>>
>> Another important use case is to support JAX-WS based WAR archive
>> deployment , lot of people want to integrate web services as a part of their
>> web applications by adding AxisServlet in the web.xml file , this works
>> fine for native services.xml based web service deployment but AFAIK we can't
>> use WAR deployment with JAX-WS ,
>>
>
> I have not tried this but I think it is possible. if you deploy a .jar file
> under WEB-INF/servicejars I think it is possible.
>
Nice to hear about such workaround for JAX-WS WAR deployment, I will try out
too . But having a descriptor file or annotations based JAX-WS deployment
approach will increase the 'ease of use ' of the project specially when some
one use build tools like Maven.
1.) In my experience service.xml based WAR based deployment is very simple
and fit well with build tools like Maven and Ant. Only requirement is to add
a services.xml into the WEB-INF/services directory no need to care about
location of the .calss files. we can use Maven/ant default behavior for
.class file locations ( classes or lib) and packaging . But in the
mentioned approach we have to place a JAR file inside the
WEB-INF/servicejars directory this may require to modify build script little
bit. It would be great if we can come up with a solution so that we only
place meta data file in the WEB-INF or WEB-INF/servicejars directory and
classes are loaded from default Classpath ( like in service.xml based WAR
deployment).
2.) Most of the other Java web service frameworks support JAX-WS WAR
deployment only by placing a meta data file in the WEB-INF directory, if
we can support to similar approach it will help out for people who move in
to Axis2 from other frameworks. If they have a existing JAX-WS service they
only need to write a descriptor file in order to deploy on Axis2 container.
Above scenarios can be specific for few use cases but IMO with the maturity
level of Axis2 project now we have to think about those aspects too.
>
>
>> It's going to be a valuable feature if we can support for this.
>>
>>
>>>
>>> These are the options I can think of adding axis2 specific
>>> custermizations to JAX-WS.
>>>
>>> 1. Support optional services.xml file in META-INF
>>> Services.xml file is a too generic file. So people may confuse
>>> with some options with services.xml file.
>>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>>> May have to duplicate some exising code in ServiceBuilder
>>> 3. Introduce axis2 specific anotations to JAX-WS
>>> May have problems with writting annotations to set the
>>> security polices.
>>>
>>
>>
>> Personally I like to have a descriptor file such as axis2-jaxws.xml or
>> usual service.xml rather introducing another set of axis2 specific
>> annotations.
>>
>
> Think about a scenario like this. Lets say some one has wirten a jax ws
> service already and they need to deploy it under 'transportSession' in that
> case isn't it easy to just add an anotation to existing jax ws web service
> class instead of writtng a new services.xml file?
>
> Infact there can be instances where services.xml is useful and annotations
> useful.
>
I can agree with your ideas, each of this approaches have their own
specific usages, as an example sometimes people want to change some settings
when they deploy the application without recompiling source codes having a
descriptor file is a ideal for such use case. what about to support both
options ?
Thanks,
>
> thanks,
> Amila.
>
>
>> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
>> great if we can utilize same JAR file with WAR deployment only adding a
>> descriptor file into the WEB-INF directory.
>>
>> Thanks,
>>
>>
>>>
>>> Thanks,
>>> Amila.
>>>
>>>>
>>>> Andreas
>>>>
>>>> [1]
>>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>>
>>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>>> wrote:
>>>> > Hi all,
>>>> >
>>>> > Andreas has already reported an issue [1] regarding the inability to
>>>> > configure JAX-WS services. That is because we've removed support for a
>>>> > services.xml. But there are many use cases where the user should be
>>>> able to
>>>> > configure the service according to his requirements. Following are
>>>> some of
>>>> > the very common examples.
>>>> >
>>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>>> > application etc.)
>>>> > [2] Ability to set ServiceTCCL
>>>> > [3] Ability to specify service parameters
>>>> >
>>>> > In order to support these use cases, we have to support service
>>>> > customizations somehow. If allowing a services.xml file is not a
>>>> proper
>>>> > solution, I think defining Axis2 specific annotations whould be a good
>>>> > solution for this issue.
>>>> >
>>>> > WDYT?..
>>>> >
>>>> > Thanks,
>>>> > ~Isuru
>>>> >
>>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>>> >
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Amila Suriarachchi
>>> WSO2 Inc.
>>> blog: http://amilachinthaka.blogspot.com/
>>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Sagara Gunathunga <sa...@gmail.com>.
On Tue, Mar 9, 2010 at 6:37 PM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
> sagara.gunathunga@gmail.com> wrote:
>
>>
>>
>> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
>> amilasuriarachchi@gmail.com> wrote:
>>
>>>
>>>
>>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com> wrote:
>>>
>>>> I also created a proof-of-concept [1] that shows the feasibility of
>>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>>> implements a custom deployer that is based on ServiceDeployer, but
>>>> replaces the code that builds the initial AxisService object from the
>>>> WSDL by code that uses
>>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>>> introduces massive code duplication and is thus only valid as a
>>>> proof-of-concept.
>>>
>>> Apart from this I think when we introduce a new deployer then we need to
>>> have a different folder to
>>> deploy files and a different extension.
>>>
>>>
>>>
>>>> To do this properly, it would be necessary to modify
>>>> ServiceDeployer to create some sort of extension point that allows
>>>> JAX-WS to supply the initial AxisService description.
>>>>
>>>
>>> I think your intention here is to let users to deploy JAX-WS services as
>>> aar files which already
>>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>>> services. ie. jaxws jar files can have an optional service.xml file in the
>>> META-INF.
>>>
>>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>>> not have the concept of custom deployers. So at that time (time when JAX-WS
>>> started) every thing deployed as .aar files. But latter there were problems
>>> with JAX-WS support in aar files and introduced thin new custom deployer
>>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>>> may not be the best approach.
>>>
>>
>> Another important use case is to support JAX-WS based WAR archive
>> deployment , lot of people want to integrate web services as a part of their
>> web applications by adding AxisServlet in the web.xml file , this works
>> fine for native services.xml based web service deployment but AFAIK we can't
>> use WAR deployment with JAX-WS ,
>>
>
> I have not tried this but I think it is possible. if you deploy a .jar file
> under WEB-INF/servicejars I think it is possible.
>
Nice to hear about such workaround for JAX-WS WAR deployment, I will try out
too . But having a descriptor file or annotations based JAX-WS deployment
approach will increase the 'ease of use ' of the project specially when some
one use build tools like Maven.
1.) In my experience service.xml based WAR based deployment is very simple
and fit well with build tools like Maven and Ant. Only requirement is to add
a services.xml into the WEB-INF/services directory no need to care about
location of the .calss files. we can use Maven/ant default behavior for
.class file locations ( classes or lib) and packaging . But in the
mentioned approach we have to place a JAR file inside the
WEB-INF/servicejars directory this may require to modify build script little
bit. It would be great if we can come up with a solution so that we only
place meta data file in the WEB-INF or WEB-INF/servicejars directory and
classes are loaded from default Classpath ( like in service.xml based WAR
deployment).
2.) Most of the other Java web service frameworks support JAX-WS WAR
deployment only by placing a meta data file in the WEB-INF directory, if
we can support to similar approach it will help out for people who move in
to Axis2 from other frameworks. If they have a existing JAX-WS service they
only need to write a descriptor file in order to deploy on Axis2 container.
Above scenarios can be specific for few use cases but IMO with the maturity
level of Axis2 project now we have to think about those aspects too.
>
>
>> It's going to be a valuable feature if we can support for this.
>>
>>
>>>
>>> These are the options I can think of adding axis2 specific
>>> custermizations to JAX-WS.
>>>
>>> 1. Support optional services.xml file in META-INF
>>> Services.xml file is a too generic file. So people may confuse
>>> with some options with services.xml file.
>>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>>> May have to duplicate some exising code in ServiceBuilder
>>> 3. Introduce axis2 specific anotations to JAX-WS
>>> May have problems with writting annotations to set the
>>> security polices.
>>>
>>
>>
>> Personally I like to have a descriptor file such as axis2-jaxws.xml or
>> usual service.xml rather introducing another set of axis2 specific
>> annotations.
>>
>
> Think about a scenario like this. Lets say some one has wirten a jax ws
> service already and they need to deploy it under 'transportSession' in that
> case isn't it easy to just add an anotation to existing jax ws web service
> class instead of writtng a new services.xml file?
>
> Infact there can be instances where services.xml is useful and annotations
> useful.
>
I can agree with your ideas, each of this approaches have their own
specific usages, as an example sometimes people want to change some settings
when they deploy the application without recompiling source codes having a
descriptor file is a ideal for such use case. what about to support both
options ?
Thanks,
>
> thanks,
> Amila.
>
>
>> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
>> great if we can utilize same JAR file with WAR deployment only adding a
>> descriptor file into the WEB-INF directory.
>>
>> Thanks,
>>
>>
>>>
>>> Thanks,
>>> Amila.
>>>
>>>>
>>>> Andreas
>>>>
>>>> [1]
>>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>>
>>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>>> wrote:
>>>> > Hi all,
>>>> >
>>>> > Andreas has already reported an issue [1] regarding the inability to
>>>> > configure JAX-WS services. That is because we've removed support for a
>>>> > services.xml. But there are many use cases where the user should be
>>>> able to
>>>> > configure the service according to his requirements. Following are
>>>> some of
>>>> > the very common examples.
>>>> >
>>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>>> > application etc.)
>>>> > [2] Ability to set ServiceTCCL
>>>> > [3] Ability to specify service parameters
>>>> >
>>>> > In order to support these use cases, we have to support service
>>>> > customizations somehow. If allowing a services.xml file is not a
>>>> proper
>>>> > solution, I think defining Axis2 specific annotations whould be a good
>>>> > solution for this issue.
>>>> >
>>>> > WDYT?..
>>>> >
>>>> > Thanks,
>>>> > ~Isuru
>>>> >
>>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>>> >
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Amila Suriarachchi
>>> WSO2 Inc.
>>> blog: http://amilachinthaka.blogspot.com/
>>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by chris roberts <ca...@gmail.com>.
can somebody help me unsubscribe? The unsubscribe link doesn't work and my
inbox is filling up with axis emails every day. I never registered for axis
in the firs place so I'm wondering if some changes have happened recently,
meaning that one mailing list has merged with another.
Thanks for any help,
Chris
On 9 March 2010 13:07, Amila Suriarachchi <am...@gmail.com>wrote:
>
>
> On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
> sagara.gunathunga@gmail.com> wrote:
>
>>
>>
>> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
>> amilasuriarachchi@gmail.com> wrote:
>>
>>>
>>>
>>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>>> andreas.veithen@gmail.com> wrote:
>>>
>>>> I also created a proof-of-concept [1] that shows the feasibility of
>>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>>> implements a custom deployer that is based on ServiceDeployer, but
>>>> replaces the code that builds the initial AxisService object from the
>>>> WSDL by code that uses
>>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>>> introduces massive code duplication and is thus only valid as a
>>>> proof-of-concept.
>>>
>>> Apart from this I think when we introduce a new deployer then we need to
>>> have a different folder to
>>> deploy files and a different extension.
>>>
>>>
>>>
>>>> To do this properly, it would be necessary to modify
>>>> ServiceDeployer to create some sort of extension point that allows
>>>> JAX-WS to supply the initial AxisService description.
>>>>
>>>
>>> I think your intention here is to let users to deploy JAX-WS services as
>>> aar files which already
>>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>>> services. ie. jaxws jar files can have an optional service.xml file in the
>>> META-INF.
>>>
>>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>>> not have the concept of custom deployers. So at that time (time when JAX-WS
>>> started) every thing deployed as .aar files. But latter there were problems
>>> with JAX-WS support in aar files and introduced thin new custom deployer
>>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>>> may not be the best approach.
>>>
>>
>> Another important use case is to support JAX-WS based WAR archive
>> deployment , lot of people want to integrate web services as a part of their
>> web applications by adding AxisServlet in the web.xml file , this works
>> fine for native services.xml based web service deployment but AFAIK we can't
>> use WAR deployment with JAX-WS ,
>>
>
> I have not tried this but I think it is possible. if you deploy a .jar file
> under WEB-INF/servicejars I think it is possible.
>
>
>> It's going to be a valuable feature if we can support for this.
>>
>>
>>>
>>> These are the options I can think of adding axis2 specific
>>> custermizations to JAX-WS.
>>>
>>> 1. Support optional services.xml file in META-INF
>>> Services.xml file is a too generic file. So people may confuse
>>> with some options with services.xml file.
>>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>>> May have to duplicate some exising code in ServiceBuilder
>>> 3. Introduce axis2 specific anotations to JAX-WS
>>> May have problems with writting annotations to set the
>>> security polices.
>>>
>>
>>
>> Personally I like to have a descriptor file such as axis2-jaxws.xml or
>> usual service.xml rather introducing another set of axis2 specific
>> annotations.
>>
>
> Think about a scenario like this. Lets say some one has wirten a jax ws
> service already and they need to deploy it under 'transportSession' in that
> case isn't it easy to just add an anotation to existing jax ws web service
> class instead of writtng a new services.xml file?
>
> Infact there can be instances where services.xml is useful and annotations
> useful.
>
> thanks,
> Amila.
>
>
>> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
>> great if we can utilize same JAR file with WAR deployment only adding a
>> descriptor file into the WEB-INF directory.
>>
>> Thanks,
>>
>>
>>>
>>> Thanks,
>>> Amila.
>>>
>>>>
>>>> Andreas
>>>>
>>>> [1]
>>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>>
>>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>>> wrote:
>>>> > Hi all,
>>>> >
>>>> > Andreas has already reported an issue [1] regarding the inability to
>>>> > configure JAX-WS services. That is because we've removed support for a
>>>> > services.xml. But there are many use cases where the user should be
>>>> able to
>>>> > configure the service according to his requirements. Following are
>>>> some of
>>>> > the very common examples.
>>>> >
>>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>>> > application etc.)
>>>> > [2] Ability to set ServiceTCCL
>>>> > [3] Ability to specify service parameters
>>>> >
>>>> > In order to support these use cases, we have to support service
>>>> > customizations somehow. If allowing a services.xml file is not a
>>>> proper
>>>> > solution, I think defining Axis2 specific annotations whould be a good
>>>> > solution for this issue.
>>>> >
>>>> > WDYT?..
>>>> >
>>>> > Thanks,
>>>> > ~Isuru
>>>> >
>>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>>> >
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Amila Suriarachchi
>>> WSO2 Inc.
>>> blog: http://amilachinthaka.blogspot.com/
>>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Amila Suriarachchi <am...@gmail.com>.
On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
sagara.gunathunga@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
> amilasuriarachchi@gmail.com> wrote:
>
>>
>>
>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> I also created a proof-of-concept [1] that shows the feasibility of
>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>> implements a custom deployer that is based on ServiceDeployer, but
>>> replaces the code that builds the initial AxisService object from the
>>> WSDL by code that uses
>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>> introduces massive code duplication and is thus only valid as a
>>> proof-of-concept.
>>
>> Apart from this I think when we introduce a new deployer then we need to
>> have a different folder to
>> deploy files and a different extension.
>>
>>
>>
>>> To do this properly, it would be necessary to modify
>>> ServiceDeployer to create some sort of extension point that allows
>>> JAX-WS to supply the initial AxisService description.
>>>
>>
>> I think your intention here is to let users to deploy JAX-WS services as
>> aar files which already
>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>> services. ie. jaxws jar files can have an optional service.xml file in the
>> META-INF.
>>
>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>> not have the concept of custom deployers. So at that time (time when JAX-WS
>> started) every thing deployed as .aar files. But latter there were problems
>> with JAX-WS support in aar files and introduced thin new custom deployer
>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>> may not be the best approach.
>>
>
> Another important use case is to support JAX-WS based WAR archive
> deployment , lot of people want to integrate web services as a part of their
> web applications by adding AxisServlet in the web.xml file , this works
> fine for native services.xml based web service deployment but AFAIK we can't
> use WAR deployment with JAX-WS ,
>
I have not tried this but I think it is possible. if you deploy a .jar file
under WEB-INF/servicejars I think it is possible.
> It's going to be a valuable feature if we can support for this.
>
>
>>
>> These are the options I can think of adding axis2 specific custermizations
>> to JAX-WS.
>>
>> 1. Support optional services.xml file in META-INF
>> Services.xml file is a too generic file. So people may confuse
>> with some options with services.xml file.
>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>> May have to duplicate some exising code in ServiceBuilder
>> 3. Introduce axis2 specific anotations to JAX-WS
>> May have problems with writting annotations to set the security
>> polices.
>>
>
>
> Personally I like to have a descriptor file such as axis2-jaxws.xml or
> usual service.xml rather introducing another set of axis2 specific
> annotations.
>
Think about a scenario like this. Lets say some one has wirten a jax ws
service already and they need to deploy it under 'transportSession' in that
case isn't it easy to just add an anotation to existing jax ws web service
class instead of writtng a new services.xml file?
Infact there can be instances where services.xml is useful and annotations
useful.
thanks,
Amila.
> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
> great if we can utilize same JAR file with WAR deployment only adding a
> descriptor file into the WEB-INF directory.
>
> Thanks,
>
>
>>
>> Thanks,
>> Amila.
>>
>>>
>>> Andreas
>>>
>>> [1]
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>
>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>> wrote:
>>> > Hi all,
>>> >
>>> > Andreas has already reported an issue [1] regarding the inability to
>>> > configure JAX-WS services. That is because we've removed support for a
>>> > services.xml. But there are many use cases where the user should be
>>> able to
>>> > configure the service according to his requirements. Following are some
>>> of
>>> > the very common examples.
>>> >
>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>> > application etc.)
>>> > [2] Ability to set ServiceTCCL
>>> > [3] Ability to specify service parameters
>>> >
>>> > In order to support these use cases, we have to support service
>>> > customizations somehow. If allowing a services.xml file is not a proper
>>> > solution, I think defining Axis2 specific annotations whould be a good
>>> > solution for this issue.
>>> >
>>> > WDYT?..
>>> >
>>> > Thanks,
>>> > ~Isuru
>>> >
>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Andreas Veithen <an...@gmail.com>.
My proposal (to add an extension point to ServiceDeployer to allow
JAX-WS to inject AxisService descriptions built from JAX-WS
annotations) has the following advantages:
* The familiar services.xml syntax applies. No new descriptor formats
or annotations are necessary.
* No need for a new deployer; JAX-WS services can be deployed from an AAR.
* JAX-WS services can benefit from the other advantages of AAR files
(e.g. embedded JARs).
* Works with WARs (i.e. with an exploded AAR bundled inside the WAR).
* Restores compatibility with earlier Axis2 versions (and with what is
promised in the Axis2 documentation).
* Possibility to mix JAX-WS services with other types of services in a
single AAR.
* Relatively easy to implement and not much new code required.
However, it will require a refactoring of ServiceDeployer to introduce
a new API (which could be useful for other purposes in the future).
Andreas
On Tue, Mar 9, 2010 at 11:15, Sagara Gunathunga
<sa...@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi
> <am...@gmail.com> wrote:
>>
>>
>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen
>> <an...@gmail.com> wrote:
>>>
>>> I also created a proof-of-concept [1] that shows the feasibility of
>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>> implements a custom deployer that is based on ServiceDeployer, but
>>> replaces the code that builds the initial AxisService object from the
>>> WSDL by code that uses
>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>> introduces massive code duplication and is thus only valid as a
>>> proof-of-concept.
>>
>> Apart from this I think when we introduce a new deployer then we need to
>> have a different folder to
>> deploy files and a different extension.
>>
>>
>>>
>>> To do this properly, it would be necessary to modify
>>> ServiceDeployer to create some sort of extension point that allows
>>> JAX-WS to supply the initial AxisService description.
>>
>> I think your intention here is to let users to deploy JAX-WS services as
>> aar files which already
>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>> services. ie. jaxws jar files can have an optional service.xml file in the
>> META-INF.
>>
>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>> not have the concept of custom deployers. So at that time (time when JAX-WS
>> started) every thing deployed as .aar files. But latter there were problems
>> with JAX-WS support in aar files and introduced thin new custom deployer
>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>> may not be the best approach.
>
> Another important use case is to support JAX-WS based WAR archive deployment
> , lot of people want to integrate web services as a part of their web
> applications by adding AxisServlet in the web.xml file , this works fine
> for native services.xml based web service deployment but AFAIK we can't use
> WAR deployment with JAX-WS , It's going to be a valuable feature if we can
> support for this.
>
>>
>> These are the options I can think of adding axis2 specific custermizations
>> to JAX-WS.
>>
>> 1. Support optional services.xml file in META-INF
>> Services.xml file is a too generic file. So people may confuse
>> with some options with services.xml file.
>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>> May have to duplicate some exising code in ServiceBuilder
>> 3. Introduce axis2 specific anotations to JAX-WS
>> May have problems with writting annotations to set the security
>> polices.
>
>
> Personally I like to have a descriptor file such as axis2-jaxws.xml or usual
> service.xml rather introducing another set of axis2 specific annotations.
> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
> great if we can utilize same JAR file with WAR deployment only adding a
> descriptor file into the WEB-INF directory.
>
> Thanks,
>
>>
>> Thanks,
>> Amila.
>>>
>>> Andreas
>>>
>>> [1]
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>
>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>> wrote:
>>> > Hi all,
>>> >
>>> > Andreas has already reported an issue [1] regarding the inability to
>>> > configure JAX-WS services. That is because we've removed support for a
>>> > services.xml. But there are many use cases where the user should be
>>> > able to
>>> > configure the service according to his requirements. Following are some
>>> > of
>>> > the very common examples.
>>> >
>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>> > application etc.)
>>> > [2] Ability to set ServiceTCCL
>>> > [3] Ability to specify service parameters
>>> >
>>> > In order to support these use cases, we have to support service
>>> > customizations somehow. If allowing a services.xml file is not a proper
>>> > solution, I think defining Axis2 specific annotations whould be a good
>>> > solution for this issue.
>>> >
>>> > WDYT?..
>>> >
>>> > Thanks,
>>> > ~Isuru
>>> >
>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Andreas Veithen <an...@gmail.com>.
My proposal (to add an extension point to ServiceDeployer to allow
JAX-WS to inject AxisService descriptions built from JAX-WS
annotations) has the following advantages:
* The familiar services.xml syntax applies. No new descriptor formats
or annotations are necessary.
* No need for a new deployer; JAX-WS services can be deployed from an AAR.
* JAX-WS services can benefit from the other advantages of AAR files
(e.g. embedded JARs).
* Works with WARs (i.e. with an exploded AAR bundled inside the WAR).
* Restores compatibility with earlier Axis2 versions (and with what is
promised in the Axis2 documentation).
* Possibility to mix JAX-WS services with other types of services in a
single AAR.
* Relatively easy to implement and not much new code required.
However, it will require a refactoring of ServiceDeployer to introduce
a new API (which could be useful for other purposes in the future).
Andreas
On Tue, Mar 9, 2010 at 11:15, Sagara Gunathunga
<sa...@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi
> <am...@gmail.com> wrote:
>>
>>
>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen
>> <an...@gmail.com> wrote:
>>>
>>> I also created a proof-of-concept [1] that shows the feasibility of
>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>> implements a custom deployer that is based on ServiceDeployer, but
>>> replaces the code that builds the initial AxisService object from the
>>> WSDL by code that uses
>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>> introduces massive code duplication and is thus only valid as a
>>> proof-of-concept.
>>
>> Apart from this I think when we introduce a new deployer then we need to
>> have a different folder to
>> deploy files and a different extension.
>>
>>
>>>
>>> To do this properly, it would be necessary to modify
>>> ServiceDeployer to create some sort of extension point that allows
>>> JAX-WS to supply the initial AxisService description.
>>
>> I think your intention here is to let users to deploy JAX-WS services as
>> aar files which already
>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>> services. ie. jaxws jar files can have an optional service.xml file in the
>> META-INF.
>>
>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>> not have the concept of custom deployers. So at that time (time when JAX-WS
>> started) every thing deployed as .aar files. But latter there were problems
>> with JAX-WS support in aar files and introduced thin new custom deployer
>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>> may not be the best approach.
>
> Another important use case is to support JAX-WS based WAR archive deployment
> , lot of people want to integrate web services as a part of their web
> applications by adding AxisServlet in the web.xml file , this works fine
> for native services.xml based web service deployment but AFAIK we can't use
> WAR deployment with JAX-WS , It's going to be a valuable feature if we can
> support for this.
>
>>
>> These are the options I can think of adding axis2 specific custermizations
>> to JAX-WS.
>>
>> 1. Support optional services.xml file in META-INF
>> Services.xml file is a too generic file. So people may confuse
>> with some options with services.xml file.
>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>> May have to duplicate some exising code in ServiceBuilder
>> 3. Introduce axis2 specific anotations to JAX-WS
>> May have problems with writting annotations to set the security
>> polices.
>
>
> Personally I like to have a descriptor file such as axis2-jaxws.xml or usual
> service.xml rather introducing another set of axis2 specific annotations.
> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
> great if we can utilize same JAR file with WAR deployment only adding a
> descriptor file into the WEB-INF directory.
>
> Thanks,
>
>>
>> Thanks,
>> Amila.
>>>
>>> Andreas
>>>
>>> [1]
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>
>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>> wrote:
>>> > Hi all,
>>> >
>>> > Andreas has already reported an issue [1] regarding the inability to
>>> > configure JAX-WS services. That is because we've removed support for a
>>> > services.xml. But there are many use cases where the user should be
>>> > able to
>>> > configure the service according to his requirements. Following are some
>>> > of
>>> > the very common examples.
>>> >
>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>> > application etc.)
>>> > [2] Ability to set ServiceTCCL
>>> > [3] Ability to specify service parameters
>>> >
>>> > In order to support these use cases, we have to support service
>>> > customizations somehow. If allowing a services.xml file is not a proper
>>> > solution, I think defining Axis2 specific annotations whould be a good
>>> > solution for this issue.
>>> >
>>> > WDYT?..
>>> >
>>> > Thanks,
>>> > ~Isuru
>>> >
>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Andreas Veithen <an...@gmail.com>.
My proposal (to add an extension point to ServiceDeployer to allow
JAX-WS to inject AxisService descriptions built from JAX-WS
annotations) has the following advantages:
* The familiar services.xml syntax applies. No new descriptor formats
or annotations are necessary.
* No need for a new deployer; JAX-WS services can be deployed from an AAR.
* JAX-WS services can benefit from the other advantages of AAR files
(e.g. embedded JARs).
* Works with WARs (i.e. with an exploded AAR bundled inside the WAR).
* Restores compatibility with earlier Axis2 versions (and with what is
promised in the Axis2 documentation).
* Possibility to mix JAX-WS services with other types of services in a
single AAR.
* Relatively easy to implement and not much new code required.
However, it will require a refactoring of ServiceDeployer to introduce
a new API (which could be useful for other purposes in the future).
Andreas
On Tue, Mar 9, 2010 at 11:15, Sagara Gunathunga
<sa...@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi
> <am...@gmail.com> wrote:
>>
>>
>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen
>> <an...@gmail.com> wrote:
>>>
>>> I also created a proof-of-concept [1] that shows the feasibility of
>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>> implements a custom deployer that is based on ServiceDeployer, but
>>> replaces the code that builds the initial AxisService object from the
>>> WSDL by code that uses
>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>> introduces massive code duplication and is thus only valid as a
>>> proof-of-concept.
>>
>> Apart from this I think when we introduce a new deployer then we need to
>> have a different folder to
>> deploy files and a different extension.
>>
>>
>>>
>>> To do this properly, it would be necessary to modify
>>> ServiceDeployer to create some sort of extension point that allows
>>> JAX-WS to supply the initial AxisService description.
>>
>> I think your intention here is to let users to deploy JAX-WS services as
>> aar files which already
>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>> services. ie. jaxws jar files can have an optional service.xml file in the
>> META-INF.
>>
>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>> not have the concept of custom deployers. So at that time (time when JAX-WS
>> started) every thing deployed as .aar files. But latter there were problems
>> with JAX-WS support in aar files and introduced thin new custom deployer
>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>> may not be the best approach.
>
> Another important use case is to support JAX-WS based WAR archive deployment
> , lot of people want to integrate web services as a part of their web
> applications by adding AxisServlet in the web.xml file , this works fine
> for native services.xml based web service deployment but AFAIK we can't use
> WAR deployment with JAX-WS , It's going to be a valuable feature if we can
> support for this.
>
>>
>> These are the options I can think of adding axis2 specific custermizations
>> to JAX-WS.
>>
>> 1. Support optional services.xml file in META-INF
>> Services.xml file is a too generic file. So people may confuse
>> with some options with services.xml file.
>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>> May have to duplicate some exising code in ServiceBuilder
>> 3. Introduce axis2 specific anotations to JAX-WS
>> May have problems with writting annotations to set the security
>> polices.
>
>
> Personally I like to have a descriptor file such as axis2-jaxws.xml or usual
> service.xml rather introducing another set of axis2 specific annotations.
> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
> great if we can utilize same JAR file with WAR deployment only adding a
> descriptor file into the WEB-INF directory.
>
> Thanks,
>
>>
>> Thanks,
>> Amila.
>>>
>>> Andreas
>>>
>>> [1]
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>
>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>> wrote:
>>> > Hi all,
>>> >
>>> > Andreas has already reported an issue [1] regarding the inability to
>>> > configure JAX-WS services. That is because we've removed support for a
>>> > services.xml. But there are many use cases where the user should be
>>> > able to
>>> > configure the service according to his requirements. Following are some
>>> > of
>>> > the very common examples.
>>> >
>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>> > application etc.)
>>> > [2] Ability to set ServiceTCCL
>>> > [3] Ability to specify service parameters
>>> >
>>> > In order to support these use cases, we have to support service
>>> > customizations somehow. If allowing a services.xml file is not a proper
>>> > solution, I think defining Axis2 specific annotations whould be a good
>>> > solution for this issue.
>>> >
>>> > WDYT?..
>>> >
>>> > Thanks,
>>> > ~Isuru
>>> >
>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Amila Suriarachchi <am...@gmail.com>.
On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
sagara.gunathunga@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
> amilasuriarachchi@gmail.com> wrote:
>
>>
>>
>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> I also created a proof-of-concept [1] that shows the feasibility of
>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>> implements a custom deployer that is based on ServiceDeployer, but
>>> replaces the code that builds the initial AxisService object from the
>>> WSDL by code that uses
>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>> introduces massive code duplication and is thus only valid as a
>>> proof-of-concept.
>>
>> Apart from this I think when we introduce a new deployer then we need to
>> have a different folder to
>> deploy files and a different extension.
>>
>>
>>
>>> To do this properly, it would be necessary to modify
>>> ServiceDeployer to create some sort of extension point that allows
>>> JAX-WS to supply the initial AxisService description.
>>>
>>
>> I think your intention here is to let users to deploy JAX-WS services as
>> aar files which already
>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>> services. ie. jaxws jar files can have an optional service.xml file in the
>> META-INF.
>>
>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>> not have the concept of custom deployers. So at that time (time when JAX-WS
>> started) every thing deployed as .aar files. But latter there were problems
>> with JAX-WS support in aar files and introduced thin new custom deployer
>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>> may not be the best approach.
>>
>
> Another important use case is to support JAX-WS based WAR archive
> deployment , lot of people want to integrate web services as a part of their
> web applications by adding AxisServlet in the web.xml file , this works
> fine for native services.xml based web service deployment but AFAIK we can't
> use WAR deployment with JAX-WS ,
>
I have not tried this but I think it is possible. if you deploy a .jar file
under WEB-INF/servicejars I think it is possible.
> It's going to be a valuable feature if we can support for this.
>
>
>>
>> These are the options I can think of adding axis2 specific custermizations
>> to JAX-WS.
>>
>> 1. Support optional services.xml file in META-INF
>> Services.xml file is a too generic file. So people may confuse
>> with some options with services.xml file.
>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>> May have to duplicate some exising code in ServiceBuilder
>> 3. Introduce axis2 specific anotations to JAX-WS
>> May have problems with writting annotations to set the security
>> polices.
>>
>
>
> Personally I like to have a descriptor file such as axis2-jaxws.xml or
> usual service.xml rather introducing another set of axis2 specific
> annotations.
>
Think about a scenario like this. Lets say some one has wirten a jax ws
service already and they need to deploy it under 'transportSession' in that
case isn't it easy to just add an anotation to existing jax ws web service
class instead of writtng a new services.xml file?
Infact there can be instances where services.xml is useful and annotations
useful.
thanks,
Amila.
> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
> great if we can utilize same JAR file with WAR deployment only adding a
> descriptor file into the WEB-INF directory.
>
> Thanks,
>
>
>>
>> Thanks,
>> Amila.
>>
>>>
>>> Andreas
>>>
>>> [1]
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>
>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>> wrote:
>>> > Hi all,
>>> >
>>> > Andreas has already reported an issue [1] regarding the inability to
>>> > configure JAX-WS services. That is because we've removed support for a
>>> > services.xml. But there are many use cases where the user should be
>>> able to
>>> > configure the service according to his requirements. Following are some
>>> of
>>> > the very common examples.
>>> >
>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>> > application etc.)
>>> > [2] Ability to set ServiceTCCL
>>> > [3] Ability to specify service parameters
>>> >
>>> > In order to support these use cases, we have to support service
>>> > customizations somehow. If allowing a services.xml file is not a proper
>>> > solution, I think defining Axis2 specific annotations whould be a good
>>> > solution for this issue.
>>> >
>>> > WDYT?..
>>> >
>>> > Thanks,
>>> > ~Isuru
>>> >
>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Amila Suriarachchi <am...@gmail.com>.
On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
sagara.gunathunga@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
> amilasuriarachchi@gmail.com> wrote:
>
>>
>>
>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> I also created a proof-of-concept [1] that shows the feasibility of
>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>> implements a custom deployer that is based on ServiceDeployer, but
>>> replaces the code that builds the initial AxisService object from the
>>> WSDL by code that uses
>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>> introduces massive code duplication and is thus only valid as a
>>> proof-of-concept.
>>
>> Apart from this I think when we introduce a new deployer then we need to
>> have a different folder to
>> deploy files and a different extension.
>>
>>
>>
>>> To do this properly, it would be necessary to modify
>>> ServiceDeployer to create some sort of extension point that allows
>>> JAX-WS to supply the initial AxisService description.
>>>
>>
>> I think your intention here is to let users to deploy JAX-WS services as
>> aar files which already
>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>> services. ie. jaxws jar files can have an optional service.xml file in the
>> META-INF.
>>
>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>> not have the concept of custom deployers. So at that time (time when JAX-WS
>> started) every thing deployed as .aar files. But latter there were problems
>> with JAX-WS support in aar files and introduced thin new custom deployer
>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>> may not be the best approach.
>>
>
> Another important use case is to support JAX-WS based WAR archive
> deployment , lot of people want to integrate web services as a part of their
> web applications by adding AxisServlet in the web.xml file , this works
> fine for native services.xml based web service deployment but AFAIK we can't
> use WAR deployment with JAX-WS ,
>
I have not tried this but I think it is possible. if you deploy a .jar file
under WEB-INF/servicejars I think it is possible.
> It's going to be a valuable feature if we can support for this.
>
>
>>
>> These are the options I can think of adding axis2 specific custermizations
>> to JAX-WS.
>>
>> 1. Support optional services.xml file in META-INF
>> Services.xml file is a too generic file. So people may confuse
>> with some options with services.xml file.
>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>> May have to duplicate some exising code in ServiceBuilder
>> 3. Introduce axis2 specific anotations to JAX-WS
>> May have problems with writting annotations to set the security
>> polices.
>>
>
>
> Personally I like to have a descriptor file such as axis2-jaxws.xml or
> usual service.xml rather introducing another set of axis2 specific
> annotations.
>
Think about a scenario like this. Lets say some one has wirten a jax ws
service already and they need to deploy it under 'transportSession' in that
case isn't it easy to just add an anotation to existing jax ws web service
class instead of writtng a new services.xml file?
Infact there can be instances where services.xml is useful and annotations
useful.
thanks,
Amila.
> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
> great if we can utilize same JAR file with WAR deployment only adding a
> descriptor file into the WEB-INF directory.
>
> Thanks,
>
>
>>
>> Thanks,
>> Amila.
>>
>>>
>>> Andreas
>>>
>>> [1]
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>
>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>> wrote:
>>> > Hi all,
>>> >
>>> > Andreas has already reported an issue [1] regarding the inability to
>>> > configure JAX-WS services. That is because we've removed support for a
>>> > services.xml. But there are many use cases where the user should be
>>> able to
>>> > configure the service according to his requirements. Following are some
>>> of
>>> > the very common examples.
>>> >
>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>> > application etc.)
>>> > [2] Ability to set ServiceTCCL
>>> > [3] Ability to specify service parameters
>>> >
>>> > In order to support these use cases, we have to support service
>>> > customizations somehow. If allowing a services.xml file is not a proper
>>> > solution, I think defining Axis2 specific annotations whould be a good
>>> > solution for this issue.
>>> >
>>> > WDYT?..
>>> >
>>> > Thanks,
>>> > ~Isuru
>>> >
>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Amila Suriarachchi <am...@gmail.com>.
On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
sagara.gunathunga@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
> amilasuriarachchi@gmail.com> wrote:
>
>>
>>
>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> I also created a proof-of-concept [1] that shows the feasibility of
>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>> implements a custom deployer that is based on ServiceDeployer, but
>>> replaces the code that builds the initial AxisService object from the
>>> WSDL by code that uses
>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>> introduces massive code duplication and is thus only valid as a
>>> proof-of-concept.
>>
>> Apart from this I think when we introduce a new deployer then we need to
>> have a different folder to
>> deploy files and a different extension.
>>
>>
>>
>>> To do this properly, it would be necessary to modify
>>> ServiceDeployer to create some sort of extension point that allows
>>> JAX-WS to supply the initial AxisService description.
>>>
>>
>> I think your intention here is to let users to deploy JAX-WS services as
>> aar files which already
>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>> services. ie. jaxws jar files can have an optional service.xml file in the
>> META-INF.
>>
>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>> not have the concept of custom deployers. So at that time (time when JAX-WS
>> started) every thing deployed as .aar files. But latter there were problems
>> with JAX-WS support in aar files and introduced thin new custom deployer
>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>> may not be the best approach.
>>
>
> Another important use case is to support JAX-WS based WAR archive
> deployment , lot of people want to integrate web services as a part of their
> web applications by adding AxisServlet in the web.xml file , this works
> fine for native services.xml based web service deployment but AFAIK we can't
> use WAR deployment with JAX-WS ,
>
I have not tried this but I think it is possible. if you deploy a .jar file
under WEB-INF/servicejars I think it is possible.
> It's going to be a valuable feature if we can support for this.
>
>
>>
>> These are the options I can think of adding axis2 specific custermizations
>> to JAX-WS.
>>
>> 1. Support optional services.xml file in META-INF
>> Services.xml file is a too generic file. So people may confuse
>> with some options with services.xml file.
>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>> May have to duplicate some exising code in ServiceBuilder
>> 3. Introduce axis2 specific anotations to JAX-WS
>> May have problems with writting annotations to set the security
>> polices.
>>
>
>
> Personally I like to have a descriptor file such as axis2-jaxws.xml or
> usual service.xml rather introducing another set of axis2 specific
> annotations.
>
Think about a scenario like this. Lets say some one has wirten a jax ws
service already and they need to deploy it under 'transportSession' in that
case isn't it easy to just add an anotation to existing jax ws web service
class instead of writtng a new services.xml file?
Infact there can be instances where services.xml is useful and annotations
useful.
thanks,
Amila.
> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
> great if we can utilize same JAR file with WAR deployment only adding a
> descriptor file into the WEB-INF directory.
>
> Thanks,
>
>
>>
>> Thanks,
>> Amila.
>>
>>>
>>> Andreas
>>>
>>> [1]
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>
>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>> wrote:
>>> > Hi all,
>>> >
>>> > Andreas has already reported an issue [1] regarding the inability to
>>> > configure JAX-WS services. That is because we've removed support for a
>>> > services.xml. But there are many use cases where the user should be
>>> able to
>>> > configure the service according to his requirements. Following are some
>>> of
>>> > the very common examples.
>>> >
>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>> > application etc.)
>>> > [2] Ability to set ServiceTCCL
>>> > [3] Ability to specify service parameters
>>> >
>>> > In order to support these use cases, we have to support service
>>> > customizations somehow. If allowing a services.xml file is not a proper
>>> > solution, I think defining Axis2 specific annotations whould be a good
>>> > solution for this issue.
>>> >
>>> > WDYT?..
>>> >
>>> > Thanks,
>>> > ~Isuru
>>> >
>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Amila Suriarachchi <am...@gmail.com>.
On Tue, Mar 9, 2010 at 3:45 PM, Sagara Gunathunga <
sagara.gunathunga@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
> amilasuriarachchi@gmail.com> wrote:
>
>>
>>
>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> I also created a proof-of-concept [1] that shows the feasibility of
>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>> implements a custom deployer that is based on ServiceDeployer, but
>>> replaces the code that builds the initial AxisService object from the
>>> WSDL by code that uses
>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>> introduces massive code duplication and is thus only valid as a
>>> proof-of-concept.
>>
>> Apart from this I think when we introduce a new deployer then we need to
>> have a different folder to
>> deploy files and a different extension.
>>
>>
>>
>>> To do this properly, it would be necessary to modify
>>> ServiceDeployer to create some sort of extension point that allows
>>> JAX-WS to supply the initial AxisService description.
>>>
>>
>> I think your intention here is to let users to deploy JAX-WS services as
>> aar files which already
>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>> services. ie. jaxws jar files can have an optional service.xml file in the
>> META-INF.
>>
>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>> not have the concept of custom deployers. So at that time (time when JAX-WS
>> started) every thing deployed as .aar files. But latter there were problems
>> with JAX-WS support in aar files and introduced thin new custom deployer
>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>> may not be the best approach.
>>
>
> Another important use case is to support JAX-WS based WAR archive
> deployment , lot of people want to integrate web services as a part of their
> web applications by adding AxisServlet in the web.xml file , this works
> fine for native services.xml based web service deployment but AFAIK we can't
> use WAR deployment with JAX-WS ,
>
I have not tried this but I think it is possible. if you deploy a .jar file
under WEB-INF/servicejars I think it is possible.
> It's going to be a valuable feature if we can support for this.
>
>
>>
>> These are the options I can think of adding axis2 specific custermizations
>> to JAX-WS.
>>
>> 1. Support optional services.xml file in META-INF
>> Services.xml file is a too generic file. So people may confuse
>> with some options with services.xml file.
>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>> May have to duplicate some exising code in ServiceBuilder
>> 3. Introduce axis2 specific anotations to JAX-WS
>> May have problems with writting annotations to set the security
>> polices.
>>
>
>
> Personally I like to have a descriptor file such as axis2-jaxws.xml or
> usual service.xml rather introducing another set of axis2 specific
> annotations.
>
Think about a scenario like this. Lets say some one has wirten a jax ws
service already and they need to deploy it under 'transportSession' in that
case isn't it easy to just add an anotation to existing jax ws web service
class instead of writtng a new services.xml file?
Infact there can be instances where services.xml is useful and annotations
useful.
thanks,
Amila.
> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
> great if we can utilize same JAR file with WAR deployment only adding a
> descriptor file into the WEB-INF directory.
>
> Thanks,
>
>
>>
>> Thanks,
>> Amila.
>>
>>>
>>> Andreas
>>>
>>> [1]
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>
>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>> wrote:
>>> > Hi all,
>>> >
>>> > Andreas has already reported an issue [1] regarding the inability to
>>> > configure JAX-WS services. That is because we've removed support for a
>>> > services.xml. But there are many use cases where the user should be
>>> able to
>>> > configure the service according to his requirements. Following are some
>>> of
>>> > the very common examples.
>>> >
>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>> > application etc.)
>>> > [2] Ability to set ServiceTCCL
>>> > [3] Ability to specify service parameters
>>> >
>>> > In order to support these use cases, we have to support service
>>> > customizations somehow. If allowing a services.xml file is not a proper
>>> > solution, I think defining Axis2 specific annotations whould be a good
>>> > solution for this issue.
>>> >
>>> > WDYT?..
>>> >
>>> > Thanks,
>>> > ~Isuru
>>> >
>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Andreas Veithen <an...@gmail.com>.
My proposal (to add an extension point to ServiceDeployer to allow
JAX-WS to inject AxisService descriptions built from JAX-WS
annotations) has the following advantages:
* The familiar services.xml syntax applies. No new descriptor formats
or annotations are necessary.
* No need for a new deployer; JAX-WS services can be deployed from an AAR.
* JAX-WS services can benefit from the other advantages of AAR files
(e.g. embedded JARs).
* Works with WARs (i.e. with an exploded AAR bundled inside the WAR).
* Restores compatibility with earlier Axis2 versions (and with what is
promised in the Axis2 documentation).
* Possibility to mix JAX-WS services with other types of services in a
single AAR.
* Relatively easy to implement and not much new code required.
However, it will require a refactoring of ServiceDeployer to introduce
a new API (which could be useful for other purposes in the future).
Andreas
On Tue, Mar 9, 2010 at 11:15, Sagara Gunathunga
<sa...@gmail.com> wrote:
>
>
> On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi
> <am...@gmail.com> wrote:
>>
>>
>> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen
>> <an...@gmail.com> wrote:
>>>
>>> I also created a proof-of-concept [1] that shows the feasibility of
>>> the services.xml based approach that I suggested in AXIS2-4611. It
>>> implements a custom deployer that is based on ServiceDeployer, but
>>> replaces the code that builds the initial AxisService object from the
>>> WSDL by code that uses
>>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>>> introduces massive code duplication and is thus only valid as a
>>> proof-of-concept.
>>
>> Apart from this I think when we introduce a new deployer then we need to
>> have a different folder to
>> deploy files and a different extension.
>>
>>
>>>
>>> To do this properly, it would be necessary to modify
>>> ServiceDeployer to create some sort of extension point that allows
>>> JAX-WS to supply the initial AxisService description.
>>
>> I think your intention here is to let users to deploy JAX-WS services as
>> aar files which already
>> have the service.xml. IMHO we need to add service.xml support to JAX-WS
>> services. ie. jaxws jar files can have an optional service.xml file in the
>> META-INF.
>>
>> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
>> not have the concept of custom deployers. So at that time (time when JAX-WS
>> started) every thing deployed as .aar files. But latter there were problems
>> with JAX-WS support in aar files and introduced thin new custom deployer
>> concept to address this issue. Therefore adding JAX-WS support to .aar files
>> may not be the best approach.
>
> Another important use case is to support JAX-WS based WAR archive deployment
> , lot of people want to integrate web services as a part of their web
> applications by adding AxisServlet in the web.xml file , this works fine
> for native services.xml based web service deployment but AFAIK we can't use
> WAR deployment with JAX-WS , It's going to be a valuable feature if we can
> support for this.
>
>>
>> These are the options I can think of adding axis2 specific custermizations
>> to JAX-WS.
>>
>> 1. Support optional services.xml file in META-INF
>> Services.xml file is a too generic file. So people may confuse
>> with some options with services.xml file.
>> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
>> May have to duplicate some exising code in ServiceBuilder
>> 3. Introduce axis2 specific anotations to JAX-WS
>> May have problems with writting annotations to set the security
>> polices.
>
>
> Personally I like to have a descriptor file such as axis2-jaxws.xml or usual
> service.xml rather introducing another set of axis2 specific annotations.
> Axis2 already supports to JAX-WS deployment as a JAR file , it would be
> great if we can utilize same JAR file with WAR deployment only adding a
> descriptor file into the WEB-INF directory.
>
> Thanks,
>
>>
>> Thanks,
>> Amila.
>>>
>>> Andreas
>>>
>>> [1]
>>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>>
>>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>>> wrote:
>>> > Hi all,
>>> >
>>> > Andreas has already reported an issue [1] regarding the inability to
>>> > configure JAX-WS services. That is because we've removed support for a
>>> > services.xml. But there are many use cases where the user should be
>>> > able to
>>> > configure the service according to his requirements. Following are some
>>> > of
>>> > the very common examples.
>>> >
>>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>>> > application etc.)
>>> > [2] Ability to set ServiceTCCL
>>> > [3] Ability to specify service parameters
>>> >
>>> > In order to support these use cases, we have to support service
>>> > customizations somehow. If allowing a services.xml file is not a proper
>>> > solution, I think defining Axis2 specific annotations whould be a good
>>> > solution for this issue.
>>> >
>>> > WDYT?..
>>> >
>>> > Thanks,
>>> > ~Isuru
>>> >
>>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Sagara Gunathunga <sa...@gmail.com>.
On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:
>
>
> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <andreas.veithen@gmail.com
> > wrote:
>
>> I also created a proof-of-concept [1] that shows the feasibility of
>> the services.xml based approach that I suggested in AXIS2-4611. It
>> implements a custom deployer that is based on ServiceDeployer, but
>> replaces the code that builds the initial AxisService object from the
>> WSDL by code that uses
>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>> introduces massive code duplication and is thus only valid as a
>> proof-of-concept.
>
> Apart from this I think when we introduce a new deployer then we need to
> have a different folder to
> deploy files and a different extension.
>
>
>
>> To do this properly, it would be necessary to modify
>> ServiceDeployer to create some sort of extension point that allows
>> JAX-WS to supply the initial AxisService description.
>>
>
> I think your intention here is to let users to deploy JAX-WS services as
> aar files which already
> have the service.xml. IMHO we need to add service.xml support to JAX-WS
> services. ie. jaxws jar files can have an optional service.xml file in the
> META-INF.
>
> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
> not have the concept of custom deployers. So at that time (time when JAX-WS
> started) every thing deployed as .aar files. But latter there were problems
> with JAX-WS support in aar files and introduced thin new custom deployer
> concept to address this issue. Therefore adding JAX-WS support to .aar files
> may not be the best approach.
>
Another important use case is to support JAX-WS based WAR archive deployment
, lot of people want to integrate web services as a part of their web
applications by adding AxisServlet in the web.xml file , this works fine
for native services.xml based web service deployment but AFAIK we can't use
WAR deployment with JAX-WS , It's going to be a valuable feature if we can
support for this.
>
> These are the options I can think of adding axis2 specific custermizations
> to JAX-WS.
>
> 1. Support optional services.xml file in META-INF
> Services.xml file is a too generic file. So people may confuse
> with some options with services.xml file.
> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
> May have to duplicate some exising code in ServiceBuilder
> 3. Introduce axis2 specific anotations to JAX-WS
> May have problems with writting annotations to set the security
> polices.
>
Personally I like to have a descriptor file such as axis2-jaxws.xml or usual
service.xml rather introducing another set of axis2 specific annotations.
Axis2 already supports to JAX-WS deployment as a JAR file , it would be
great if we can utilize same JAR file with WAR deployment only adding a
descriptor file into the WEB-INF directory.
Thanks,
>
> Thanks,
> Amila.
>
>>
>> Andreas
>>
>> [1]
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>
>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>> wrote:
>> > Hi all,
>> >
>> > Andreas has already reported an issue [1] regarding the inability to
>> > configure JAX-WS services. That is because we've removed support for a
>> > services.xml. But there are many use cases where the user should be able
>> to
>> > configure the service according to his requirements. Following are some
>> of
>> > the very common examples.
>> >
>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>> > application etc.)
>> > [2] Ability to set ServiceTCCL
>> > [3] Ability to specify service parameters
>> >
>> > In order to support these use cases, we have to support service
>> > customizations somehow. If allowing a services.xml file is not a proper
>> > solution, I think defining Axis2 specific annotations whould be a good
>> > solution for this issue.
>> >
>> > WDYT?..
>> >
>> > Thanks,
>> > ~Isuru
>> >
>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Sagara Gunathunga <sa...@gmail.com>.
On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:
>
>
> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <andreas.veithen@gmail.com
> > wrote:
>
>> I also created a proof-of-concept [1] that shows the feasibility of
>> the services.xml based approach that I suggested in AXIS2-4611. It
>> implements a custom deployer that is based on ServiceDeployer, but
>> replaces the code that builds the initial AxisService object from the
>> WSDL by code that uses
>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>> introduces massive code duplication and is thus only valid as a
>> proof-of-concept.
>
> Apart from this I think when we introduce a new deployer then we need to
> have a different folder to
> deploy files and a different extension.
>
>
>
>> To do this properly, it would be necessary to modify
>> ServiceDeployer to create some sort of extension point that allows
>> JAX-WS to supply the initial AxisService description.
>>
>
> I think your intention here is to let users to deploy JAX-WS services as
> aar files which already
> have the service.xml. IMHO we need to add service.xml support to JAX-WS
> services. ie. jaxws jar files can have an optional service.xml file in the
> META-INF.
>
> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
> not have the concept of custom deployers. So at that time (time when JAX-WS
> started) every thing deployed as .aar files. But latter there were problems
> with JAX-WS support in aar files and introduced thin new custom deployer
> concept to address this issue. Therefore adding JAX-WS support to .aar files
> may not be the best approach.
>
Another important use case is to support JAX-WS based WAR archive deployment
, lot of people want to integrate web services as a part of their web
applications by adding AxisServlet in the web.xml file , this works fine
for native services.xml based web service deployment but AFAIK we can't use
WAR deployment with JAX-WS , It's going to be a valuable feature if we can
support for this.
>
> These are the options I can think of adding axis2 specific custermizations
> to JAX-WS.
>
> 1. Support optional services.xml file in META-INF
> Services.xml file is a too generic file. So people may confuse
> with some options with services.xml file.
> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
> May have to duplicate some exising code in ServiceBuilder
> 3. Introduce axis2 specific anotations to JAX-WS
> May have problems with writting annotations to set the security
> polices.
>
Personally I like to have a descriptor file such as axis2-jaxws.xml or usual
service.xml rather introducing another set of axis2 specific annotations.
Axis2 already supports to JAX-WS deployment as a JAR file , it would be
great if we can utilize same JAR file with WAR deployment only adding a
descriptor file into the WEB-INF directory.
Thanks,
>
> Thanks,
> Amila.
>
>>
>> Andreas
>>
>> [1]
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>
>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>> wrote:
>> > Hi all,
>> >
>> > Andreas has already reported an issue [1] regarding the inability to
>> > configure JAX-WS services. That is because we've removed support for a
>> > services.xml. But there are many use cases where the user should be able
>> to
>> > configure the service according to his requirements. Following are some
>> of
>> > the very common examples.
>> >
>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>> > application etc.)
>> > [2] Ability to set ServiceTCCL
>> > [3] Ability to specify service parameters
>> >
>> > In order to support these use cases, we have to support service
>> > customizations somehow. If allowing a services.xml file is not a proper
>> > solution, I think defining Axis2 specific annotations whould be a good
>> > solution for this issue.
>> >
>> > WDYT?..
>> >
>> > Thanks,
>> > ~Isuru
>> >
>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Sagara Gunathunga <sa...@gmail.com>.
On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:
>
>
> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <andreas.veithen@gmail.com
> > wrote:
>
>> I also created a proof-of-concept [1] that shows the feasibility of
>> the services.xml based approach that I suggested in AXIS2-4611. It
>> implements a custom deployer that is based on ServiceDeployer, but
>> replaces the code that builds the initial AxisService object from the
>> WSDL by code that uses
>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>> introduces massive code duplication and is thus only valid as a
>> proof-of-concept.
>
> Apart from this I think when we introduce a new deployer then we need to
> have a different folder to
> deploy files and a different extension.
>
>
>
>> To do this properly, it would be necessary to modify
>> ServiceDeployer to create some sort of extension point that allows
>> JAX-WS to supply the initial AxisService description.
>>
>
> I think your intention here is to let users to deploy JAX-WS services as
> aar files which already
> have the service.xml. IMHO we need to add service.xml support to JAX-WS
> services. ie. jaxws jar files can have an optional service.xml file in the
> META-INF.
>
> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
> not have the concept of custom deployers. So at that time (time when JAX-WS
> started) every thing deployed as .aar files. But latter there were problems
> with JAX-WS support in aar files and introduced thin new custom deployer
> concept to address this issue. Therefore adding JAX-WS support to .aar files
> may not be the best approach.
>
Another important use case is to support JAX-WS based WAR archive deployment
, lot of people want to integrate web services as a part of their web
applications by adding AxisServlet in the web.xml file , this works fine
for native services.xml based web service deployment but AFAIK we can't use
WAR deployment with JAX-WS , It's going to be a valuable feature if we can
support for this.
>
> These are the options I can think of adding axis2 specific custermizations
> to JAX-WS.
>
> 1. Support optional services.xml file in META-INF
> Services.xml file is a too generic file. So people may confuse
> with some options with services.xml file.
> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
> May have to duplicate some exising code in ServiceBuilder
> 3. Introduce axis2 specific anotations to JAX-WS
> May have problems with writting annotations to set the security
> polices.
>
Personally I like to have a descriptor file such as axis2-jaxws.xml or usual
service.xml rather introducing another set of axis2 specific annotations.
Axis2 already supports to JAX-WS deployment as a JAR file , it would be
great if we can utilize same JAR file with WAR deployment only adding a
descriptor file into the WEB-INF directory.
Thanks,
>
> Thanks,
> Amila.
>
>>
>> Andreas
>>
>> [1]
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>
>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>> wrote:
>> > Hi all,
>> >
>> > Andreas has already reported an issue [1] regarding the inability to
>> > configure JAX-WS services. That is because we've removed support for a
>> > services.xml. But there are many use cases where the user should be able
>> to
>> > configure the service according to his requirements. Following are some
>> of
>> > the very common examples.
>> >
>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>> > application etc.)
>> > [2] Ability to set ServiceTCCL
>> > [3] Ability to specify service parameters
>> >
>> > In order to support these use cases, we have to support service
>> > customizations somehow. If allowing a services.xml file is not a proper
>> > solution, I think defining Axis2 specific annotations whould be a good
>> > solution for this issue.
>> >
>> > WDYT?..
>> >
>> > Thanks,
>> > ~Isuru
>> >
>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Sagara Gunathunga <sa...@gmail.com>.
On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:
>
>
> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <andreas.veithen@gmail.com
> > wrote:
>
>> I also created a proof-of-concept [1] that shows the feasibility of
>> the services.xml based approach that I suggested in AXIS2-4611. It
>> implements a custom deployer that is based on ServiceDeployer, but
>> replaces the code that builds the initial AxisService object from the
>> WSDL by code that uses
>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>> introduces massive code duplication and is thus only valid as a
>> proof-of-concept.
>
> Apart from this I think when we introduce a new deployer then we need to
> have a different folder to
> deploy files and a different extension.
>
>
>
>> To do this properly, it would be necessary to modify
>> ServiceDeployer to create some sort of extension point that allows
>> JAX-WS to supply the initial AxisService description.
>>
>
> I think your intention here is to let users to deploy JAX-WS services as
> aar files which already
> have the service.xml. IMHO we need to add service.xml support to JAX-WS
> services. ie. jaxws jar files can have an optional service.xml file in the
> META-INF.
>
> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
> not have the concept of custom deployers. So at that time (time when JAX-WS
> started) every thing deployed as .aar files. But latter there were problems
> with JAX-WS support in aar files and introduced thin new custom deployer
> concept to address this issue. Therefore adding JAX-WS support to .aar files
> may not be the best approach.
>
Another important use case is to support JAX-WS based WAR archive deployment
, lot of people want to integrate web services as a part of their web
applications by adding AxisServlet in the web.xml file , this works fine
for native services.xml based web service deployment but AFAIK we can't use
WAR deployment with JAX-WS , It's going to be a valuable feature if we can
support for this.
>
> These are the options I can think of adding axis2 specific custermizations
> to JAX-WS.
>
> 1. Support optional services.xml file in META-INF
> Services.xml file is a too generic file. So people may confuse
> with some options with services.xml file.
> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
> May have to duplicate some exising code in ServiceBuilder
> 3. Introduce axis2 specific anotations to JAX-WS
> May have problems with writting annotations to set the security
> polices.
>
Personally I like to have a descriptor file such as axis2-jaxws.xml or usual
service.xml rather introducing another set of axis2 specific annotations.
Axis2 already supports to JAX-WS deployment as a JAR file , it would be
great if we can utilize same JAR file with WAR deployment only adding a
descriptor file into the WEB-INF directory.
Thanks,
>
> Thanks,
> Amila.
>
>>
>> Andreas
>>
>> [1]
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>
>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>> wrote:
>> > Hi all,
>> >
>> > Andreas has already reported an issue [1] regarding the inability to
>> > configure JAX-WS services. That is because we've removed support for a
>> > services.xml. But there are many use cases where the user should be able
>> to
>> > configure the service according to his requirements. Following are some
>> of
>> > the very common examples.
>> >
>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>> > application etc.)
>> > [2] Ability to set ServiceTCCL
>> > [3] Ability to specify service parameters
>> >
>> > In order to support these use cases, we have to support service
>> > customizations somehow. If allowing a services.xml file is not a proper
>> > solution, I think defining Axis2 specific annotations whould be a good
>> > solution for this issue.
>> >
>> > WDYT?..
>> >
>> > Thanks,
>> > ~Isuru
>> >
>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Sagara Gunathunga <sa...@gmail.com>.
On Tue, Mar 9, 2010 at 10:23 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:
>
>
> On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen <andreas.veithen@gmail.com
> > wrote:
>
>> I also created a proof-of-concept [1] that shows the feasibility of
>> the services.xml based approach that I suggested in AXIS2-4611. It
>> implements a custom deployer that is based on ServiceDeployer, but
>> replaces the code that builds the initial AxisService object from the
>> WSDL by code that uses
>> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
>> introduces massive code duplication and is thus only valid as a
>> proof-of-concept.
>
> Apart from this I think when we introduce a new deployer then we need to
> have a different folder to
> deploy files and a different extension.
>
>
>
>> To do this properly, it would be necessary to modify
>> ServiceDeployer to create some sort of extension point that allows
>> JAX-WS to supply the initial AxisService description.
>>
>
> I think your intention here is to let users to deploy JAX-WS services as
> aar files which already
> have the service.xml. IMHO we need to add service.xml support to JAX-WS
> services. ie. jaxws jar files can have an optional service.xml file in the
> META-INF.
>
> AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
> not have the concept of custom deployers. So at that time (time when JAX-WS
> started) every thing deployed as .aar files. But latter there were problems
> with JAX-WS support in aar files and introduced thin new custom deployer
> concept to address this issue. Therefore adding JAX-WS support to .aar files
> may not be the best approach.
>
Another important use case is to support JAX-WS based WAR archive deployment
, lot of people want to integrate web services as a part of their web
applications by adding AxisServlet in the web.xml file , this works fine
for native services.xml based web service deployment but AFAIK we can't use
WAR deployment with JAX-WS , It's going to be a valuable feature if we can
support for this.
>
> These are the options I can think of adding axis2 specific custermizations
> to JAX-WS.
>
> 1. Support optional services.xml file in META-INF
> Services.xml file is a too generic file. So people may confuse
> with some options with services.xml file.
> 2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
> May have to duplicate some exising code in ServiceBuilder
> 3. Introduce axis2 specific anotations to JAX-WS
> May have problems with writting annotations to set the security
> polices.
>
Personally I like to have a descriptor file such as axis2-jaxws.xml or usual
service.xml rather introducing another set of axis2 specific annotations.
Axis2 already supports to JAX-WS deployment as a JAR file , it would be
great if we can utilize same JAR file with WAR deployment only adding a
descriptor file into the WEB-INF directory.
Thanks,
>
> Thanks,
> Amila.
>
>>
>> Andreas
>>
>> [1]
>> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>>
>> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
>> wrote:
>> > Hi all,
>> >
>> > Andreas has already reported an issue [1] regarding the inability to
>> > configure JAX-WS services. That is because we've removed support for a
>> > services.xml. But there are many use cases where the user should be able
>> to
>> > configure the service according to his requirements. Following are some
>> of
>> > the very common examples.
>> >
>> > [1] Ability to deploy JAX-WS services in different scopes (session,
>> > application etc.)
>> > [2] Ability to set ServiceTCCL
>> > [3] Ability to specify service parameters
>> >
>> > In order to support these use cases, we have to support service
>> > customizations somehow. If allowing a services.xml file is not a proper
>> > solution, I think defining Axis2 specific annotations whould be a good
>> > solution for this issue.
>> >
>> > WDYT?..
>> >
>> > Thanks,
>> > ~Isuru
>> >
>> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Amila Suriarachchi <am...@gmail.com>.
On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen
<an...@gmail.com>wrote:
> I also created a proof-of-concept [1] that shows the feasibility of
> the services.xml based approach that I suggested in AXIS2-4611. It
> implements a custom deployer that is based on ServiceDeployer, but
> replaces the code that builds the initial AxisService object from the
> WSDL by code that uses
> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
> introduces massive code duplication and is thus only valid as a
> proof-of-concept.
Apart from this I think when we introduce a new deployer then we need to
have a different folder to
deploy files and a different extension.
> To do this properly, it would be necessary to modify
> ServiceDeployer to create some sort of extension point that allows
> JAX-WS to supply the initial AxisService description.
>
I think your intention here is to let users to deploy JAX-WS services as aar
files which already
have the service.xml. IMHO we need to add service.xml support to JAX-WS
services. ie. jaxws jar files can have an optional service.xml file in the
META-INF.
AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
not have the concept of custom deployers. So at that time (time when JAX-WS
started) every thing deployed as .aar files. But latter there were problems
with JAX-WS support in aar files and introduced thin new custom deployer
concept to address this issue. Therefore adding JAX-WS support to .aar files
may not be the best approach.
These are the options I can think of adding axis2 specific custermizations
to JAX-WS.
1. Support optional services.xml file in META-INF
Services.xml file is a too generic file. So people may confuse with
some options with services.xml file.
2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
May have to duplicate some exising code in ServiceBuilder
3. Introduce axis2 specific anotations to JAX-WS
May have problems with writting annotations to set the security
polices.
Thanks,
Amila.
>
> Andreas
>
> [1]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>
> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
> wrote:
> > Hi all,
> >
> > Andreas has already reported an issue [1] regarding the inability to
> > configure JAX-WS services. That is because we've removed support for a
> > services.xml. But there are many use cases where the user should be able
> to
> > configure the service according to his requirements. Following are some
> of
> > the very common examples.
> >
> > [1] Ability to deploy JAX-WS services in different scopes (session,
> > application etc.)
> > [2] Ability to set ServiceTCCL
> > [3] Ability to specify service parameters
> >
> > In order to support these use cases, we have to support service
> > customizations somehow. If allowing a services.xml file is not a proper
> > solution, I think defining Axis2 specific annotations whould be a good
> > solution for this issue.
> >
> > WDYT?..
> >
> > Thanks,
> > ~Isuru
> >
> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Amila Suriarachchi <am...@gmail.com>.
On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen
<an...@gmail.com>wrote:
> I also created a proof-of-concept [1] that shows the feasibility of
> the services.xml based approach that I suggested in AXIS2-4611. It
> implements a custom deployer that is based on ServiceDeployer, but
> replaces the code that builds the initial AxisService object from the
> WSDL by code that uses
> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
> introduces massive code duplication and is thus only valid as a
> proof-of-concept.
Apart from this I think when we introduce a new deployer then we need to
have a different folder to
deploy files and a different extension.
> To do this properly, it would be necessary to modify
> ServiceDeployer to create some sort of extension point that allows
> JAX-WS to supply the initial AxisService description.
>
I think your intention here is to let users to deploy JAX-WS services as aar
files which already
have the service.xml. IMHO we need to add service.xml support to JAX-WS
services. ie. jaxws jar files can have an optional service.xml file in the
META-INF.
AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
not have the concept of custom deployers. So at that time (time when JAX-WS
started) every thing deployed as .aar files. But latter there were problems
with JAX-WS support in aar files and introduced thin new custom deployer
concept to address this issue. Therefore adding JAX-WS support to .aar files
may not be the best approach.
These are the options I can think of adding axis2 specific custermizations
to JAX-WS.
1. Support optional services.xml file in META-INF
Services.xml file is a too generic file. So people may confuse with
some options with services.xml file.
2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
May have to duplicate some exising code in ServiceBuilder
3. Introduce axis2 specific anotations to JAX-WS
May have problems with writting annotations to set the security
polices.
Thanks,
Amila.
>
> Andreas
>
> [1]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>
> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
> wrote:
> > Hi all,
> >
> > Andreas has already reported an issue [1] regarding the inability to
> > configure JAX-WS services. That is because we've removed support for a
> > services.xml. But there are many use cases where the user should be able
> to
> > configure the service according to his requirements. Following are some
> of
> > the very common examples.
> >
> > [1] Ability to deploy JAX-WS services in different scopes (session,
> > application etc.)
> > [2] Ability to set ServiceTCCL
> > [3] Ability to specify service parameters
> >
> > In order to support these use cases, we have to support service
> > customizations somehow. If allowing a services.xml file is not a proper
> > solution, I think defining Axis2 specific annotations whould be a good
> > solution for this issue.
> >
> > WDYT?..
> >
> > Thanks,
> > ~Isuru
> >
> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Amila Suriarachchi <am...@gmail.com>.
On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen
<an...@gmail.com>wrote:
> I also created a proof-of-concept [1] that shows the feasibility of
> the services.xml based approach that I suggested in AXIS2-4611. It
> implements a custom deployer that is based on ServiceDeployer, but
> replaces the code that builds the initial AxisService object from the
> WSDL by code that uses
> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
> introduces massive code duplication and is thus only valid as a
> proof-of-concept.
Apart from this I think when we introduce a new deployer then we need to
have a different folder to
deploy files and a different extension.
> To do this properly, it would be necessary to modify
> ServiceDeployer to create some sort of extension point that allows
> JAX-WS to supply the initial AxisService description.
>
I think your intention here is to let users to deploy JAX-WS services as aar
files which already
have the service.xml. IMHO we need to add service.xml support to JAX-WS
services. ie. jaxws jar files can have an optional service.xml file in the
META-INF.
AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
not have the concept of custom deployers. So at that time (time when JAX-WS
started) every thing deployed as .aar files. But latter there were problems
with JAX-WS support in aar files and introduced thin new custom deployer
concept to address this issue. Therefore adding JAX-WS support to .aar files
may not be the best approach.
These are the options I can think of adding axis2 specific custermizations
to JAX-WS.
1. Support optional services.xml file in META-INF
Services.xml file is a too generic file. So people may confuse with
some options with services.xml file.
2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
May have to duplicate some exising code in ServiceBuilder
3. Introduce axis2 specific anotations to JAX-WS
May have problems with writting annotations to set the security
polices.
Thanks,
Amila.
>
> Andreas
>
> [1]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>
> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
> wrote:
> > Hi all,
> >
> > Andreas has already reported an issue [1] regarding the inability to
> > configure JAX-WS services. That is because we've removed support for a
> > services.xml. But there are many use cases where the user should be able
> to
> > configure the service according to his requirements. Following are some
> of
> > the very common examples.
> >
> > [1] Ability to deploy JAX-WS services in different scopes (session,
> > application etc.)
> > [2] Ability to set ServiceTCCL
> > [3] Ability to specify service parameters
> >
> > In order to support these use cases, we have to support service
> > customizations somehow. If allowing a services.xml file is not a proper
> > solution, I think defining Axis2 specific annotations whould be a good
> > solution for this issue.
> >
> > WDYT?..
> >
> > Thanks,
> > ~Isuru
> >
> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Amila Suriarachchi <am...@gmail.com>.
On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen
<an...@gmail.com>wrote:
> I also created a proof-of-concept [1] that shows the feasibility of
> the services.xml based approach that I suggested in AXIS2-4611. It
> implements a custom deployer that is based on ServiceDeployer, but
> replaces the code that builds the initial AxisService object from the
> WSDL by code that uses
> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
> introduces massive code duplication and is thus only valid as a
> proof-of-concept.
Apart from this I think when we introduce a new deployer then we need to
have a different folder to
deploy files and a different extension.
> To do this properly, it would be necessary to modify
> ServiceDeployer to create some sort of extension point that allows
> JAX-WS to supply the initial AxisService description.
>
I think your intention here is to let users to deploy JAX-WS services as aar
files which already
have the service.xml. IMHO we need to add service.xml support to JAX-WS
services. ie. jaxws jar files can have an optional service.xml file in the
META-INF.
AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
not have the concept of custom deployers. So at that time (time when JAX-WS
started) every thing deployed as .aar files. But latter there were problems
with JAX-WS support in aar files and introduced thin new custom deployer
concept to address this issue. Therefore adding JAX-WS support to .aar files
may not be the best approach.
These are the options I can think of adding axis2 specific custermizations
to JAX-WS.
1. Support optional services.xml file in META-INF
Services.xml file is a too generic file. So people may confuse with
some options with services.xml file.
2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
May have to duplicate some exising code in ServiceBuilder
3. Introduce axis2 specific anotations to JAX-WS
May have problems with writting annotations to set the security
polices.
Thanks,
Amila.
>
> Andreas
>
> [1]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>
> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
> wrote:
> > Hi all,
> >
> > Andreas has already reported an issue [1] regarding the inability to
> > configure JAX-WS services. That is because we've removed support for a
> > services.xml. But there are many use cases where the user should be able
> to
> > configure the service according to his requirements. Following are some
> of
> > the very common examples.
> >
> > [1] Ability to deploy JAX-WS services in different scopes (session,
> > application etc.)
> > [2] Ability to set ServiceTCCL
> > [3] Ability to specify service parameters
> >
> > In order to support these use cases, we have to support service
> > customizations somehow. If allowing a services.xml file is not a proper
> > solution, I think defining Axis2 specific annotations whould be a good
> > solution for this issue.
> >
> > WDYT?..
> >
> > Thanks,
> > ~Isuru
> >
> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Amila Suriarachchi <am...@gmail.com>.
On Mon, Mar 8, 2010 at 5:39 PM, Andreas Veithen
<an...@gmail.com>wrote:
> I also created a proof-of-concept [1] that shows the feasibility of
> the services.xml based approach that I suggested in AXIS2-4611. It
> implements a custom deployer that is based on ServiceDeployer, but
> replaces the code that builds the initial AxisService object from the
> WSDL by code that uses
> org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
> introduces massive code duplication and is thus only valid as a
> proof-of-concept.
Apart from this I think when we introduce a new deployer then we need to
have a different folder to
deploy files and a different extension.
> To do this properly, it would be necessary to modify
> ServiceDeployer to create some sort of extension point that allows
> JAX-WS to supply the initial AxisService description.
>
I think your intention here is to let users to deploy JAX-WS services as aar
files which already
have the service.xml. IMHO we need to add service.xml support to JAX-WS
services. ie. jaxws jar files can have an optional service.xml file in the
META-INF.
AFAIK(please correct me if I wrong :)), at the initial statges Axis2 does
not have the concept of custom deployers. So at that time (time when JAX-WS
started) every thing deployed as .aar files. But latter there were problems
with JAX-WS support in aar files and introduced thin new custom deployer
concept to address this issue. Therefore adding JAX-WS support to .aar files
may not be the best approach.
These are the options I can think of adding axis2 specific custermizations
to JAX-WS.
1. Support optional services.xml file in META-INF
Services.xml file is a too generic file. So people may confuse with
some options with services.xml file.
2. Introduce new optional config file in META-INF (eg axis2-jaxws.xml)
May have to duplicate some exising code in ServiceBuilder
3. Introduce axis2 specific anotations to JAX-WS
May have problems with writting annotations to set the security
polices.
Thanks,
Amila.
>
> Andreas
>
> [1]
> https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
>
> On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com>
> wrote:
> > Hi all,
> >
> > Andreas has already reported an issue [1] regarding the inability to
> > configure JAX-WS services. That is because we've removed support for a
> > services.xml. But there are many use cases where the user should be able
> to
> > configure the service according to his requirements. Following are some
> of
> > the very common examples.
> >
> > [1] Ability to deploy JAX-WS services in different scopes (session,
> > application etc.)
> > [2] Ability to set ServiceTCCL
> > [3] Ability to specify service parameters
> >
> > In order to support these use cases, we have to support service
> > customizations somehow. If allowing a services.xml file is not a proper
> > solution, I think defining Axis2 specific annotations whould be a good
> > solution for this issue.
> >
> > WDYT?..
> >
> > Thanks,
> > ~Isuru
> >
> > [1] https://issues.apache.org/jira/browse/AXIS2-4611
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Andreas Veithen <an...@gmail.com>.
I also created a proof-of-concept [1] that shows the feasibility of
the services.xml based approach that I suggested in AXIS2-4611. It
implements a custom deployer that is based on ServiceDeployer, but
replaces the code that builds the initial AxisService object from the
WSDL by code that uses
org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
introduces massive code duplication and is thus only valid as a
proof-of-concept. To do this properly, it would be necessary to modify
ServiceDeployer to create some sort of extension point that allows
JAX-WS to supply the initial AxisService description.
Andreas
[1] https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com> wrote:
> Hi all,
>
> Andreas has already reported an issue [1] regarding the inability to
> configure JAX-WS services. That is because we've removed support for a
> services.xml. But there are many use cases where the user should be able to
> configure the service according to his requirements. Following are some of
> the very common examples.
>
> [1] Ability to deploy JAX-WS services in different scopes (session,
> application etc.)
> [2] Ability to set ServiceTCCL
> [3] Ability to specify service parameters
>
> In order to support these use cases, we have to support service
> customizations somehow. If allowing a services.xml file is not a proper
> solution, I think defining Axis2 specific annotations whould be a good
> solution for this issue.
>
> WDYT?..
>
> Thanks,
> ~Isuru
>
> [1] https://issues.apache.org/jira/browse/AXIS2-4611
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Andreas Veithen <an...@gmail.com>.
I also created a proof-of-concept [1] that shows the feasibility of
the services.xml based approach that I suggested in AXIS2-4611. It
implements a custom deployer that is based on ServiceDeployer, but
replaces the code that builds the initial AxisService object from the
WSDL by code that uses
org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
introduces massive code duplication and is thus only valid as a
proof-of-concept. To do this properly, it would be necessary to modify
ServiceDeployer to create some sort of extension point that allows
JAX-WS to supply the initial AxisService description.
Andreas
[1] https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com> wrote:
> Hi all,
>
> Andreas has already reported an issue [1] regarding the inability to
> configure JAX-WS services. That is because we've removed support for a
> services.xml. But there are many use cases where the user should be able to
> configure the service according to his requirements. Following are some of
> the very common examples.
>
> [1] Ability to deploy JAX-WS services in different scopes (session,
> application etc.)
> [2] Ability to set ServiceTCCL
> [3] Ability to specify service parameters
>
> In order to support these use cases, we have to support service
> customizations somehow. If allowing a services.xml file is not a proper
> solution, I think defining Axis2 specific annotations whould be a good
> solution for this issue.
>
> WDYT?..
>
> Thanks,
> ~Isuru
>
> [1] https://issues.apache.org/jira/browse/AXIS2-4611
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Andreas Veithen <an...@gmail.com>.
I also created a proof-of-concept [1] that shows the feasibility of
the services.xml based approach that I suggested in AXIS2-4611. It
implements a custom deployer that is based on ServiceDeployer, but
replaces the code that builds the initial AxisService object from the
WSDL by code that uses
org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
introduces massive code duplication and is thus only valid as a
proof-of-concept. To do this properly, it would be necessary to modify
ServiceDeployer to create some sort of extension point that allows
JAX-WS to supply the initial AxisService description.
Andreas
[1] https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com> wrote:
> Hi all,
>
> Andreas has already reported an issue [1] regarding the inability to
> configure JAX-WS services. That is because we've removed support for a
> services.xml. But there are many use cases where the user should be able to
> configure the service according to his requirements. Following are some of
> the very common examples.
>
> [1] Ability to deploy JAX-WS services in different scopes (session,
> application etc.)
> [2] Ability to set ServiceTCCL
> [3] Ability to specify service parameters
>
> In order to support these use cases, we have to support service
> customizations somehow. If allowing a services.xml file is not a proper
> solution, I think defining Axis2 specific annotations whould be a good
> solution for this issue.
>
> WDYT?..
>
> Thanks,
> ~Isuru
>
> [1] https://issues.apache.org/jira/browse/AXIS2-4611
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Andreas Veithen <an...@gmail.com>.
I also created a proof-of-concept [1] that shows the feasibility of
the services.xml based approach that I suggested in AXIS2-4611. It
implements a custom deployer that is based on ServiceDeployer, but
replaces the code that builds the initial AxisService object from the
WSDL by code that uses
org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
introduces massive code duplication and is thus only valid as a
proof-of-concept. To do this properly, it would be necessary to modify
ServiceDeployer to create some sort of extension point that allows
JAX-WS to supply the initial AxisService description.
Andreas
[1] https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com> wrote:
> Hi all,
>
> Andreas has already reported an issue [1] regarding the inability to
> configure JAX-WS services. That is because we've removed support for a
> services.xml. But there are many use cases where the user should be able to
> configure the service according to his requirements. Following are some of
> the very common examples.
>
> [1] Ability to deploy JAX-WS services in different scopes (session,
> application etc.)
> [2] Ability to set ServiceTCCL
> [3] Ability to specify service parameters
>
> In order to support these use cases, we have to support service
> customizations somehow. If allowing a services.xml file is not a proper
> solution, I think defining Axis2 specific annotations whould be a good
> solution for this issue.
>
> WDYT?..
>
> Thanks,
> ~Isuru
>
> [1] https://issues.apache.org/jira/browse/AXIS2-4611
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Making JAX-WS services configurable (with a services.xml or Axis2
specific annotations)
Posted by Andreas Veithen <an...@gmail.com>.
I also created a proof-of-concept [1] that shows the feasibility of
the services.xml based approach that I suggested in AXIS2-4611. It
implements a custom deployer that is based on ServiceDeployer, but
replaces the code that builds the initial AxisService object from the
WSDL by code that uses
org.apache.axis2.jaxws.description.DescriptionFactory. Of course this
introduces massive code duplication and is thus only valid as a
proof-of-concept. To do this properly, it would be necessary to modify
ServiceDeployer to create some sort of extension point that allows
JAX-WS to supply the initial AxisService description.
Andreas
[1] https://svn.apache.org/repos/asf/axis/axis2/java/core/scratch/java/veithen/AXIS2-4611/
On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <is...@gmail.com> wrote:
> Hi all,
>
> Andreas has already reported an issue [1] regarding the inability to
> configure JAX-WS services. That is because we've removed support for a
> services.xml. But there are many use cases where the user should be able to
> configure the service according to his requirements. Following are some of
> the very common examples.
>
> [1] Ability to deploy JAX-WS services in different scopes (session,
> application etc.)
> [2] Ability to set ServiceTCCL
> [3] Ability to specify service parameters
>
> In order to support these use cases, we have to support service
> customizations somehow. If allowing a services.xml file is not a proper
> solution, I think defining Axis2 specific annotations whould be a good
> solution for this issue.
>
> WDYT?..
>
> Thanks,
> ~Isuru
>
> [1] https://issues.apache.org/jira/browse/AXIS2-4611
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org