axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Veithen <>
Subject Re: Making JAX-WS services configurable (with a services.xml or Axis2 specific annotations)
Date Mon, 08 Mar 2010 12:09:58 GMT
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.



On Mon, Mar 8, 2010 at 12:04, Isuru Suriarachchi <> 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]

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message