Yes, I think attaching the AxisService after the fact is too late. All of the metadata code that is doing the annotation processing for jaxws should be what builds up the AxisService hierachy.
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] Nicholas L Gallardo/Austin/[EMAIL PROTECTED] 03/20/2008 10:07 AM Please respond to [email protected] To [email protected] cc Subject Re: [Axis2] Removing deprecated jaxws/metadata method DescriptionFactory.createServiceDescriptionFromServiceImpl(Class, AxisService) Dims, So will the new deployment code not run if someone has that pattern? i.e., the JAXWSDeployer will only work in the case where there's no srevices.xml specified? What if we were to call the builder method that just takes a class and then attach the AxisService after that? Is that too late? I agree with Jeff in that I'd like to see it go. I've struggled with the different paths that exist in the building of ServiceDescription objects and this would help clear some of that up. -Nick Davanum Srinivas <[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) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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] | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFH4nhxgNg6eWEDv1kRAtPrAJ9wHhaPOJa4wqkQ6N1UpkdVhoOc3gCfebYf +GS10YA8wH2yH1QheH60hzk= =ZRJS -----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]
