[ http://issues.apache.org/jira/browse/MUSE-102?page=all ]
Dan Jemiolo updated MUSE-102:
-----------------------------
Fix Version/s: 2.2.0
(was: 2.1.0)
I've added a printStackTrace() to help us get some more info when runtime
exceptions happen, but Andrew will still need to work on this for 2.2. I notice
there's a log (JDK Logger) recording messages, but I can't find where the log
file is. Not sure if the right outputter is hooked up or what. At any rate, all
messages should probably be going to the console, not a log file.
> Error messages from wsdl2java need work
> ---------------------------------------
>
> Key: MUSE-102
> URL: http://issues.apache.org/jira/browse/MUSE-102
> Project: Muse
> Issue Type: Bug
> Components: Tooling - Code Generation
> Affects Versions: 2.0.0
> Reporter: Steve Jerman
> Assigned To: Andrew Eberbach
> Fix For: 2.2.0
>
>
> More a moan that anything, but the error messages from wsdl2java need work.
> They are often very obscure. It would be good if each error had a suggestion
> for a fix. Also often lower level 'sensible' messages get caught and replaced
> with more obscure general messages.
> I will add examples to this Jira as I find them
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
