-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jeff,
We shipped a jaxws-calculator sample in Axis2 1.3 that shows how to use JAXWS MR inside a services.xml. I've seen a couple of people use it. Removing this piece of code and throwing an exception is the right way to force them to move up...i guess. thanks, dims Jeff Barrett wrote: | Dims, | | Are you saying it was being used outside of the jaxws/test code? The code | path it was going down was very minimalistc, just enough to keep test | scaffolding running. I think it might do more harm than good to leave it | in. I doubt anyone using JAXWS successfully is using that method (for | example, Geronimo). | | 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]> | 03/20/2008 09:45 AM | Please respond to | [email protected] | | | To | [email protected] | cc | | Subject | Re: [Axis2] Removing deprecated jaxws/metadata method | DescriptionFactory.createServiceDescriptionFromServiceImpl(Class, | AxisService) | | | | | | | Jeff, | | I'd prefer that we leave it in as deprecated for at least 1.4 release | before cleaning it up. It's used to support the | older 1.3's case of the JAXWS MR specified inside a services.xml. | | thanks, | dims | | Jeff Barrett wrote: | | All, | | | | A few of us have been discussing whether the deprecated method | | | org.apache.axis2.jaxws.description.DescriptionFactory.createServiceDescriptionFromServiceImpl(Class, | | AxisService) can and/or should be removed. | | | | I think that it can and should be removed. I has been deprecated for a | | long, long time, and with the changes that Dims and Roy did to integrate | | the JAXWS deployment into Axis2 recently, that method should no longer | be | | used. It goes down code paths that are very, very obsolete and the | method | | was only there to support the legacy testcases which have since been | moved | | to the new deployment model. | | | | With the integration into the deployement code, I think the code path in | | JAXWSMessageReceiver that is calling the deprecated method should be | | throwing an exception instead indicating that the endpoint was not | | correctly deployed. | | | | 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] | | | | --------------------------------------------------------------------- | | 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] - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFH4zIbgNg6eWEDv1kRAnIjAKDdwCaX5bYnyu7EgyUqg/d5Vp5daACgn8sr k61pDq1wbvwzsglObu0QNtk= =CUsw -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
