when creating a webservice client with the wizard from an EJB3 SEI that is defined in another opened project, the
wizard call the wsimport tool to create all the artifacts needed.
The problem is that, because we created the wsdl from the SEI (EJB interface) and that interface references POJO
objects that belong to a third project, we want to use these objects also on the client side.
Thus, we don't want to use the classes generated by wsimport but the ones created by wsgen on both server and client
I think, for the case we create the web service client from an EJB, the wizard should ask if we don't prefer to use the
wsgen artifacts rather than directly calling wsimport.
The contract between web service provider and its consumer is defined by WSDL file, not by anything else and it is also
not guaranteed that classes generated from java (by wsgen) will be the same as classes generated from WSDL (by wsimport)...
I would rather say: it's almost guaranteed that classes generated from java (by wsgen) will be different than classes
generated from WSDL !
The problem is : J2EE 1.5 promise us POJO paradigm and more and more I dive into J2EE 1.5 and more and more I see that's
not true !
I have POJO domain model objects (if I can still call POJO objects classes full of JPA and xml binding
annotations...that's another story) wrapped into a jar file which is common to java swing client, ejb part and war part.
I just want to exchange these objects through webservice like I did when my session ejbs were using IIOP.
The solution I submitted work correctly, I'm just surprised to see neither netbeans nor any Sun tutorial talk about that.
And according to the number of people search the web for such solution I think that could be an improvement to have
netbeans propose this.
I agree that this could be a good improvement (=> enhancement).
What you can try now is to create some java library project, create a ws client there, go to project properties ->
sources -> includes/excludes, set there what you don't want to be packaged in the final jar of this library and on
places from where you want to call the ws use the client from the library instead of creating the client in the ie. web
moving opened issues where TM != dev to TM=TBD