ims, My understanding of what the TCK permits is the same as yours. You can remove the RI-specific DDs and can add your own vendor-specific DDs. However, anything that exists in the TCK application archive (such as classes, WSDL, etc) must remain as is. So, the classes couldn't be moved from WEB-INF/classes to some POJO-deployer-specific location. Another consideration is that a single TCK application archive, I believe, contains multiple services AND there may be multiple TCK application archive.
Is any of that going to cause problems for the POJO deployer? I talked with Roy Wood about this a bit, and I got the impression that having multiple archives and multiple services may be a problem that needs to be fixed in the POJO deployer. Also, that it would be possible to point the POJO deployer at a specific directory or archive, so it could be pointed to an "installed applications" directory and be able to find the services there. It seems to me that would work for the TCKs. Thoughts? Thanks, Jeff IBM Software Group - WebSphere Web Services Development Phone: 512-838-4587 or Tie Line 678-4587 Internet e-mail and Sametime ID: [EMAIL PROTECTED] Davanum Srinivas <[EMAIL PROTECTED]> 02/04/2008 04:45 PM Please respond to [email protected] To [email protected] cc Subject [Axis2] Re: PojoDeployer vs JAXWSMessageReceiver in services.xml -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Resending using [Axis2] since looks like no one looks at the emails otherwise :) Davanum Srinivas wrote: | One more observation: | | In PojoDeployer, we can't specify a custom wsdl (yet!) When one writes a | WebServiceProvider, typically they provide a | wsdl and the xsd's. | | -- dims | | Davanum Srinivas wrote: | | Sandakith, Roy, | | Looks like PojoDeployer picks up only the javax.jws.WebService | | annotation and not the javax.xml.ws.WebServiceProvider | | annotation. | | | | Sandakith, | | ~From what i know, we cannot modify WAR's shipped by the TCK. Only | | changes allowed are removing sun specific dd's and | | adding our own and maybe change the port #'s...This may have an effect | | on which way to lean using PojoDeployer vs | | JAXWSMessageReceiver in services.xml as we cannot modify the WAR's to | | suit the pojo deployer. Please note that all the | | existing services.xml in the modules\jaxws are handwritten :( | | | | thanks, | | dims -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFHp5WggNg6eWEDv1kRAklNAJ9aFfhVXLfwk5VREDsYU1aZNkhEkACg8oYm 4Xqu2zBji3JEaJDbYT1cXAo= =OCYq -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
