On Monday, June 20, 2011 9:54:52 AM Anthony Webster wrote: > OK well that's the assumption I've been working under so at least all those > wrappers weren't a waste of time :)
TECHNICALLY, as long as they don't have an XmlRootElement annotation so they are only a type, you could potentially be OK. I think CXF would be OK with it at runtime (not 100% sure though). HOWEVER, the jaxws spec specifically says the wrapper classnames have to be unique for the javafirst cases. If you run the java2ws tool on it, I think it would pick up the issue and throw an exception. Dan > > Thanks > > On 20 June 2011 05:36, Glen Mazza <[email protected]> wrote: > > I don't think so: WS-I Basic Profile compliance (R2710 of here: > > http://www.ws-i.org/profiles/**basicprofile-1.1.html#** > > Operation_Signatures<http://www.ws-i.org/profiles/basicprofile-1.1.html# > > Operation_Signatures>) requires unique signatures for each operation due > > to the fact that frequently the signature is used to determine the web > > service operation being called. > > > > Glen > > > > On 06/18/2011 02:36 PM, Anthony Webster wrote: > >> Hi there, > >> > >> Quick question. When developping jax-ws services using code-first, if > >> there > >> are multiple methods which contain the same parameters I can reuse the > >> same > >> RequestWrapper object right? > >> > >> Thanks > >> > >> Anthony > > > > -- > > Glen Mazza > > Application Integration Division > > Talend (http://www.talend.com/ai) > > blog: http://www.jroller.com/gmazza -- Daniel Kulp [email protected] http://dankulp.com/blog Talend - http://www.talend.com
