axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Cauchon" <>
Subject RE: Axis2 service repository supports for hierarchy?
Date Fri, 25 Jan 2008 15:47:04 GMT
Did some more reading in the last days and it seams I won't be able to
simply extend Axis2 to add the functionality I'm looking for. Just so
everyone really understand what I meant in my previous emails, I think
Paul gave the easiest/simplest/clearest description possible :



From: Paul Fremantle [] 
Sent: Wednesday, January 23, 2008 3:51 AM
Subject: Re: Axis2 service repository supports for hierarchy?


So you mean you would like:






I think this would be a fantastic improvement. +1 from me.



Correct me if I'm wrong ...


*	The service deployment is handled internally by the kernel. I
could probably add a Deployer to the axis configuration the same way
POJO deployment is done, but it seams to be tightly bound to a specific
directory in the repository. This is not applicable as the services
would need to be dynamically deployed based on their path in the
repository, not on a static one defined in the configuration. 
	My actual state of mind (might possibly change as I'm still
learning the framework and basics) is that changes are required in the
kernel itself, basically because the configuration context needs to be
organized and processed differently.

	*	The actual binding between the service and its name need
to be extended so the path is part of the service's key. This way 2
services with the same name can co-exist in 2 different sub-directories.
	*	Here are the classes that would need to be modified: 

		*	org.apache.axis2.engine.AxisConfiguration
		*	org.apache.axis2.deployment.ServiceDeployer
		*	org.apache.axis2.deployment.DeploymentEngine

*	Dispatching a message from the inflow is different as it can be
handled in the execution flow itself. Routing a message to the correct
path (service) could be done by creating my own handlers and configure
the Dispatch phase to use the new set of Dispatchers.



Guillaume Cauchon | DataDirect Technologies inc.








From: Guillaume Cauchon 
Sent: Wednesday, January 23, 2008 9:30 AM
To: ''
Subject: RE: Axis2 service repository supports for hierarchy?


I read about configuring the deployers in the axis2.xml, but from what I
understood it basically filters based on the extension... The default
Axis2 configuration already deploy the POJO in a separate directory:




<deployer extension=".class" directory="pojo"




In fact what I would like to do is be able to organize my web services
in sub directories in the repository (services directory). The error I
paste in my first email was caused by deploying a service archive in the
"test" sub directory:



    |- services.list

    |- version-SNAPSHOT.aar

    |- \test

        |- STAFF.aar

    |- ...



Guillaume Cauchon | DataDirect Technologies inc.  


 -mobile:       418.952-7357 

 -work:         418.649-1551 


-----Original Message-----
From: Deepal Jayasinghe [] 
Sent: Wednesday, January 23, 2008 2:46 AM
Subject: Re: Axis2 service repository supports for hierarchy?



> I've been playing around with Axis2 in the last few days to see if it

> could fit the SOAP stack needs of the project I'm working on.




> One of the features I'm looking for is the possibility to organize my

> web services (archives, POJOs, etc...) under the services repository

> (i.e. sub directories), but this feature doesn't seams to be available

> yet...


You can do that

As I can understand you want to add service aar file and POJOs into the

same directory








However you have to configure the deployers in your axis2.xml.


> A simple test made with this morning SNAPSHOT:



>       *This Web axisService has deployment faults*


As I can see the error is due to you are trying to deploy an invalid

service , and that service does not have META-INF directory which is

essential to be a valid service.






>       **


> Error: org.apache.axis2.deployment.DeploymentException: Invalid

> service. META-INF directory not found. at


> at


> at


> at


> at


> at


> at


> at


> at


> at


> at


> at


> ...


> I need to evaluate the amount of work required to get this kind of

> feature available, keep in mind that I'm only beginning in the Axis2

> codebase so I still have a lot of things to learn about the

> architecture... My question now, other than extending

> org.apache.axis2.deployment.ServiceDeployer so that I can get the web

> services deployed, what would be required for this repository

> "hierarchy" to work with all of the other components of Axis :

> run-time, management, etc?






To unsubscribe, e-mail:

For additional commands, e-mail:


View raw message