Thanks Glen, this jaxb binding customization solution already spared me lot of time!
-----Original Message----- From: Glen Mazza [mailto:[email protected]] Sent: Tuesday, August 02, 2011 3:14 PM To: [email protected] Subject: Re: Client stub generation question In [1], under part 2: *Using a binding customization file*, the "jaxb:schemaBindings" is possibly what you're looking for. But that's a cumbersome way of doing things, I don't know if there's anything better. Glen [1] http://www.jroller.com/gmazza/entry/customizing_jaxb_artifacts On 08/02/2011 08:57 AM, Liter András (SCTR) wrote: > Hello Glen, > > thanks for the quick reply, you just exactly pointed at my problem :) > > My WSDLs are generated by JBossAS for JAX-WS annotated service > implementations. Is there a way to tell the CXF runtime at the "JAX-WS > annotation" level that I would like to have a separate targetNamespace for my > schema objects? // I tried @WebParam(targetNamespace=..) and > @WebResult(targetNamespace=..), but in the generated WSDL the XSD:Schema > namespace is still inherited from the service's namespace. > > Thank you very much, sincerely yours > András > > -----Original Message----- > From: Glen Mazza [mailto:[email protected]] > Sent: Tuesday, August 02, 2011 2:09 PM > To: [email protected] > Subject: RE: Client stub generation question > > You might be making the mistake in thinking that the schema objects need to > have the same namespace as your WSDL operations. Not true, see the > "targetNamespace" attached to the XSD:Schema element here: > http://www.jroller.com/gmazza/entry/web_service_tutorial#WFstep4 -- it > ensures the namespace is separate. Your problem should go away if you keep > the same namespace for your schema objects (your optional next step would be > then to factor the schema XML elements out to a common place and > import/include them into your WSDLs). Furthermore, check the wsdl2java > command on the CXF website -- I believe there's options to suppress > generation of the Java artifacts for the XSD schema elements which you may > want to do if you've already generated them and placed them into a JAR > someplace. > > HTH, > Glen > ________________________________________ > From: Liter András (SCTR) [[email protected]] > Sent: Tuesday, August 02, 2011 5:40 AM > To: [email protected] > Subject: Client stub generation question > > Dear user support, > > I have a question about generating webservice client code with wsdl2java. > > In my scenario I have more WSDLs, which work on the same set of entities on > the server side. When I generate the client code for these WSDLs I have the > same entities multiple times in different packages according to the > namespaces of my webservices. Since I want to use more services on the client > side, I bump into the problem of these multiple entities, and therefore after > every interface change I have to refactor the generated client code to work > with a simple set of generated entities/business objects (I move them to a > different package, delete the duplicates and refactor the other classes to > use the moved entities). > > I hope my I declared my problem clearly. Do you know some workaround to avoid > this refactoring overhead? Maybe some parameter for wsdl2java? Or some kind > of other approach? > > Thanks in advance! > > Best regards, > > Liter András > IT szakértő > E-mail: [email protected]<mailto:[email protected]> > Mobil: +36-20-515-0556 > > [cid:[email protected]] > > > GREPTON Informatikai Zrt. > H-1116 Budapest, Kondorfa u. 10. > Tel.: +36-1-204-7730 > Fax: +36-1-204-7731 > www.grepton.hu<http://www.grepton.hu/> > > Gondoljon környezetére, mielőtt kinyomtatja! > Ezen üzenet és annak bármely csatolt anyaga bizalmas, jogi védelem alatt áll, > a nyilvános közléstől védett. Kérjük látogassa meg honlapunk Adatvédelmi > nyilatkozat menüpontját a levéllel kapcsolatos további információért. > -- Glen Mazza Talend (http://www.talend.com/ai) blog: http://www.jroller.com/gmazza
