[
https://issues.apache.org/jira/browse/MUSE-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kam K. Yee updated MUSE-102:
----------------------------
Attachment: muse-102.patch
To address ALL of the messages for muse-tools will require a throrough code
scan.
However, attached is a patch that fixes the "immediate" problem reported (that
of the projectizer not providing a useful error message). This was due to the
fact that exception or runtime exceptions without a message description were
being thrown. I have added the appropriate messages to those instances.
During my scan of the code I also noticed that the logger being created is
actually being associated with the ConsoleHandler so the output is routed to
the CLI console as expected:
...
ConsoleHandler handler = new ConsoleHandler();
handler.setFormatter(new SimpleLogFormatter());
...
> Error messages from wsdl2java need work
> ---------------------------------------
>
> Key: MUSE-102
> URL: https://issues.apache.org/jira/browse/MUSE-102
> Project: Muse
> Issue Type: Bug
> Components: Tooling - Code Generation
> Affects Versions: 2.0.0
> Reporter: Steve Jerman
> Assignee: Andrew Eberbach
> Fix For: 2.3.0
>
> Attachments: muse-102.patch
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
