axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicholas L Gallardo <nlgal...@us.ibm.com>
Subject Re: [Axis2] Writing custom deployer for JAXWS that picks classes from WEB-INF/classes
Date Thu, 14 Feb 2008 15:43:28 GMT

Dims,

So with Plan B, I'm assuming your directory structure would look like this?

$AXIS2_HOME/repository
|
|-------------> modules/
|
|-------------> services/
|
|-------------> jaxws-services/

Given that, then someone would come along and drop their WARs directly in
there?

-Nick




                                                                           
             Davanum Srinivas                                              
             <davanum@gmail.co                                             
             m>                                                         To 
                                       axis-dev@ws.apache.org              
             02/13/2008 04:13                                           cc 
             PM                                                            
                                                                   Subject 
                                       [Axis2] Writing custom deployer for 
             Please respond to         JAXWS that picks classes from       
             axis-dev@ws.apach         WEB-INF/classes                     
                   e.org                                                   
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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.

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?

thanks,
dims
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)

iD8DBQFHs2twgNg6eWEDv1kRAkxIAJ9gPVKAVCdbbOqQfN4Tiba865ktgACeP+iB
FBvU9GjSZHu3VGItGcV2kVA=
=ryHL
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message