[ http://issues.apache.org/jira/browse/MUSE-108?page=comments#action_12435257 ] Andrew Eberbach commented on MUSE-108: --------------------------------------
I'd like to do this for the next point release. The thing I want to introduce is a pluggable error handler so that the interface can decide what to do with these kinds of errors. On the command line this would just be printing a warning message (or an error message). In eclipse tooling this could be decorating the offending operation. > Implementation forces WSDL Operation name choice > ------------------------------------------------ > > Key: MUSE-108 > URL: http://issues.apache.org/jira/browse/MUSE-108 > Project: Muse > Issue Type: Bug > Components: WSDM MUWS Core ManageabilityCapability API > Affects Versions: 2.0.0 > Reporter: Steve Jerman > Assigned To: Dan Jemiolo > > My test model contains an operation 'shutdown'. The generated code: > public class SystemOperationsImplImpl extends AbstractCapability implements > SystemOperationsImpl > { > public Element shutdown() throws Exception { > //TODO implement > throw new RuntimeException("Unimplemented Method"); > > Doesn't compile since AbstractCapabilty contains a 'shutdown'. > The documentation needs to explain what operation names are legal. Better > still put a _ in front of the operation names to avoid clashes. -- 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]
