geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <>
Subject [jira] Resolved: (GERONIMO-3828) Provide jaxws-tools stack traces to the server.log
Date Wed, 27 Feb 2008 19:11:51 GMT


Jarek Gawor resolved GERONIMO-3828.

       Resolution: Fixed
    Fix Version/s: 2.2

I modified the code so that when wsgen is forked the stdout/stderr of the process will be
logged. In most cases when wsgen fails, the wsgen output will be logged as an error. Otherwise,
the output is logged as a debug message. It is possible for wsgen to fail and not indicate
so. In such cases debugging must be explicitly enabled to see the wsgen output. To enable
debugging for wsgen add the following to file:

The wsgen output will appear in the geronimo.log file.

Committed the changes to trunk (revision 631679) and branches/2.1 (revision 631680).

> Provide jaxws-tools stack traces to the server.log
> --------------------------------------------------
>                 Key: GERONIMO-3828
>                 URL:
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: webservices, Wish List
>    Affects Versions: 2.0.x, 2.1.1, 2.2
>            Reporter: Cedric Hurst
>            Assignee: Jarek Gawor
>             Fix For: 2.1.1, 2.2
> Even with the logging level set to DEBUG, if jaxws-tools throws an Exception, it does
not seem to show up in the server log or console output.  This seems to be the case even if
"-Dorg.apache.geronimo.jaxws.wsgen.fork=false" is set.  Logging the output of wsgen is critical
to debug issues with @WebService classes.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message