[
https://issues.apache.org/jira/browse/MUSE-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482882
]
Jose Antonio commented on MUSE-214:
-----------------------------------
The problem is that sometimes you cannot modify certain elements. For example,
I'm trying to integrate WSDM with WS-CAF so, for some operations, messages have
to be compliant with WS-CAF specification. It happens that this specification
has two elements with the same name in different namespaces and I have to
expect that elements exactly as they are in the xsd files. I can regenerate the
WSDL as it's not normative, but not the xsd files because they define the
messages format. That could be even applicable to specifications in that you
cannot modify even the wsdl involved. So for that strange cases there could be
a method to specifiy a route from a message to an operation, it doesn't matter
if it's more or less complicated as it's going to be more the exception than
the norm, but having a convention could lead to Muse not being integrable with
other WS-* specifications even if they can interact with WSDM perfectly.
> XML element name could lead to invalid operation generation.
> ------------------------------------------------------------
>
> Key: MUSE-214
> URL: https://issues.apache.org/jira/browse/MUSE-214
> Project: Muse
> Issue Type: Bug
> Components: Tooling - Code Generation
> Affects Versions: 2.2.0
> Environment: Ubuntu Edgy 6.10, JDK 1.5.0
> Reporter: Jose Antonio
> Assigned To: Dan Jemiolo
> Priority: Minor
> Fix For: 2.3.0
>
>
> Some valid elements named as <element name="this-is-valid"> could lead to the
> generation of invalid function names like
> public void this-is-valid() throws Exception
> Which is not a valid java function name. When dealing with such names, upper
> dashes should be substituted with lower dashes so it generates a valid name:
> public void this_is_valid()
> I've found this while dealing with a wsdl that I have no control over it, so
> I cannot change the element's format because it's from a server that's
> deployed and is going to invoke me with that message.
--
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]
