axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Afkham Azeez <>
Subject Re: Supporting a services.xml for JAX-WS services
Date Tue, 18 Jan 2011 04:54:47 GMT
I think we need a generic way of associating services.xml file with any
service type. What I;ve been thinking is, we can have a post Axis service
creation in the deployment phase, where the AxisService object created by
the deployer is updated based on an associated services.xml file. Else, we
can give this option to the Deployer author, whereby, the author will call
this Util, and pass in the AxisService, and optionally the services.xml
File, and then this util will update the AxisService.

In WSO2 Data Services, the Data service deployer has its own way of getting
stuff from the services.xml file. So, it is better to have a unified way
of doing this instead of implementing it for each and every deployer


On Mon, Jan 17, 2011 at 10:52 PM, Isuru Suriarachchi <>wrote:

> Hi all,
> Andreas has provided a very good explanation on why we need to support
> services.xml file for JAX-WS services in [1]. I think we can support it as
> an optional feature. If someone wants stuff like session management, he can
> insert a services.xml. And also, as Azeez has proposed, we can provide a
> generic API using which a services.xml can be supported for any type of
> service.
> WDYT??
> Thanks,
> ~Isuru
> [1]
> --
> Technical Lead,
> WSO2 Inc.
> Blog :

*Afkham Azeez*
Senior Software Architect & Senior Manager; WSO2, Inc.;,
*Member; Apache Software Foundation;
email: *** <>* cell: +94 77 3320919
blog: *** <>*
twitter: ***<>
linked-in: ***
*Lean . Enterprise . Middleware*

View raw message