Dims/Lahiru,

I like this solution as well.  After talking with Roy some yesterday, it
sounded like the POJODeployer wasn't quite the right fit for what's needed
here.

Cheers,

-Nick




                                                                       
             Davanum Srinivas                                          
             <[EMAIL PROTECTED]                                         
             m>                                                         To
                                       axis-dev@ws.apache.org          
             02/07/2008 07:30                                           cc
             AM                                                        
                                                                   Subject
                                       Re: [Axis2] Generating WSDL for 
             Please respond to         JAXWS artifacts                 
             [EMAIL PROTECTED]                                         
                   e.org                                               
                                                                       
                                                                       
                                                                       
                                                                       




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

Lahiru,

Yes, that's what my latest thinking is as well...Writing a new JAXWS
deployer. need to figure out what it will look for
in the webapp.

thanks,
dims

Lahiru Sandakith wrote:
| Hi Dims,
| I am thinking of not extending the pojo deployer on this regard. Since
the
| forward set of deployable service artifact of the sun TCK are in the form
of
| war files and seems we are not allowed it to change them as we want. We
have
| to get our deployment mechanism to get them sorted out. How about using
our
| axis2 webapp and then have an extension to the deployment from plugable
| component as TCK suit and made the sun specific wars deployable and we
can
| have the services up on Axis2. Actually we can make this deployment
| extension as JAXWS Deployer in JAXWS module. This was my idea rather than
| going for the POJO Deployer on this. Thoughts ?
|
| Thanks
| Lahiru Sandakith
|
| On Feb 5, 2008 4:16 AM, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
|
| Deepal, Sandakith,
|
| Right now we pick up just a few of the annotations from a java class.
| Namely the ones in
| org.apache.axis2.description.java2wsdlAnnotationConstants. I believe we
| need to take into account *all* possible
| annotations in the spec to pass the TCK.
|
| ~    String WEB_SERVICE = "javax.jws.WebService";
| ~    String WEB_METHOD = "javax.jws.WebMethod";
| ~    String WEB_PARAM = "javax.jws.WebParam";
| ~    String WEB_RESULT = "javax.jws.WebResult";
| ~    String TARGETNAMESPACE = "targetNamespace";
| ~    String NAME = "name";
| ~    String SERVICE_NAME = "serviceName";
| ~    String EXCLUDE = "exclude";
| ~    String ACTION = "action";
| ~    String WSDL_LOCATION = "wsdlLocation";
| ~    String OPERATION_NAME ="operationName";
|
| One option that was taken by the Geronimo team was to use the JAXWS RI's
| wsgen tool programatically. We should probably
| start looking at the same as well.
|
| We need to figure out how to support user specified WSDL's as well in the
| PojoDeployer..Thoughts?
|
| thanks,
| dims
|>
- ---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
|>
|>

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

iD8DBQFHqwfsgNg6eWEDv1kRAvD0AKDm/63MtVEsmSAu0WDgf/v5hH3fegCggN0J
JUGqiWSP6UlHL81LQyhY5dI=
=1XYV
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

<<inline: graycol.gif>>

<<inline: pic02889.gif>>

<<inline: ecblank.gif>>

Reply via email to