NB 6.5 and Tomcat Web Service: Error starting wsgen

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

NB 6.5 and Tomcat Web Service: Error starting wsgen

borrellic@tiscali.it
One of the problemas with wsgen in NB 6.5 is the absence of a "verbose" description of the cause. In NB 6.1 a really verbose exception stack is sent to the Outoput Console. With NB 6.5 You cannot understand that classes are generated but WSDL is not.



However, another main problem with understanding the "Error starting wsgen", that could remain difficult to check is that the "parameter objects" that You use in the @WebMethod or int Session Bean, or in Your DAO layer are, or contain, references to non-java.io.Serializable Java objects.



Example: You use a bad java.sql.Date, instead of correctly using java.util.Date.



Bye bye,



borrellic




Reply | Threaded
Open this post in threaded view
|

Re: NB 6.5 and Tomcat Web Service: Error starting wsgen

mkuchtiak
Thank You for this useful observation.
wsgen: verbose="true" was put back for Nb6.7.

There is another important improvement: wsgen is not called
automatically in project's Build action.
There is actually no need for that as (e.g. in Tomcat case) there is a
JAX-WS WSServletContextListener that generates wsdl file based on
@WebService annotation.
Nevertheless, there is a "Generate and Copy WSDL" action that can be
called by user on service node. This action actually calls the wsgen ant
task.

Another improvement is that "wsgen-service-compile",
"wsimport-client-compile" and "wsimport-service-compile" targets (these
targets were compiling generated sources) were removed from build script
as  generated sources are now compiled by the compiler  setup  in
project properties (in the same way as other sources).
Even more - generated sources are now visible in project's view.

Milan

[hidden email] wrote:

> One of the problemas with wsgen in NB 6.5 is the absence of a "verbose" description of the cause. In NB 6.1 a really verbose exception stack is sent to the Outoput Console. With NB 6.5 You cannot understand that classes are generated but WSDL is not.
>
>
>
> However, another main problem with understanding the "Error starting wsgen", that could remain difficult to check is that the "parameter objects" that You use in the @WebMethod or int Session Bean, or in Your DAO layer are, or contain, references to non-java.io.Serializable Java objects.
>
>
>
> Example: You use a bad java.sql.Date, instead of correctly using java.util.Date.
>
>
>
> Bye bye,
>
>
>
> borrellic
>
>
>
>
>