[
https://issues.apache.org/jira/browse/GERONIMO-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved GERONIMO-3828.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.2
2.1.1
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 server-log4j.properties file:
log4j.logger.org.apache.geronimo.jaxws.builder=DEBUG
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: https://issues.apache.org/jira/browse/GERONIMO-3828
> 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.
