axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deepal Jayasinghe <>
Subject Re: [Axis2] Writing custom deployer for JAXWS that picks classes from WEB-INF/classes
Date Thu, 14 Feb 2008 04:45:47 GMT

> Deepal, Roy, Sandakith, Jeff,
> Currently, when one writes a deployer, it needs to have a directory 
> and a file extension for it. The deployment engine
> scans all the directories and if it finds a file with that extension 
> it will invoke it.
Hmm , what actually happen is it will scan all the directories specified 
by deployers and scan those directories.  For example if we have added a 
deployer with "foo" directory and "bar" extension then Axis2 will scan 
foo directory for bar extension.
> Problem is in the TCK case, all we have are classes in WEB-INF/classes 
> with the package names dictating the directory
> structure under it (and the class files deep somewhere inside)
> Plan A: Is there to write a new deployer that can traverse the file 
> system by itself (NOT by the deployment engine)?
> Plan B: Just create a directory called jaxws-services and drop a text 
> file or xml file with enough information (just the
> class name is enough). then we can use the current way deployment 
> engine works...
> Thoughts please?
If I were you , I would go for PlanB.


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

View raw message