Hi Liter,

I could not understand how/where you define your entities - if you define them in separate xsd files instead of the wsdl definition, you should be able to use the same entities in all service/client implementations. But if you define the same entities in separate namespaces in each wsdl, which implies redundancy, then you'll have same entities in different namespaces and different packages. It would be good practice to keep all your entity definitions in one place and import them in the wsdl files as necessary. As far as I understood, your solution would be better organization. I can be more helpful through more detailed explanation of your approach.

Regards,
Kutsal

On 02.08.2011 12:40, Liter András (SCTR) wrote:

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



        Leírás: Description: Description: Description: Grepton-logo2010


*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 nyilatkozatmenüpontját a levéllel kapcsolatos további információért.


Reply via email to