[jira] Commented: (CXF-1084) namespace control in aegis (with jaxws) don't work for the wsdl element, only for the schemas

["Benson Margulies (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CXF-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536547 ] 

Benson Margulies commented on CXF-1084:
---------------------------------------

Here's the story. ServiceWSDLBuilder knows about TNS, but it doesn't have any visibility of namespace maps. These live inside the namespace context of the xml schemata. 

Essentially, when a databinding, (e.g. Aegis) wants to supply a namespace map, that needs to be visible to ServiceWSDLBuilder, which needs to sort them out as a more complex version of what it already does with target namespace comparison. If two services disagree about the prefix map, then one of them has to be booted out into an import.

I wonder if there's a JAXB angle here related to @XmlNs. 

The question here is per-schema namespace maps versus per-service. The Aegis map is at the level of the entire databinding, so all the schema in a service (which share, of course, the Aegis databinding instance) will share a namespace map. In Aegis, the schemas all can end up with independent XmlNs. Those namespaces that end up at the JAX-WS level (and thus in the Service model), can they have @XmlNs? Should prefixes float up from schemas to the service level in JAXB? What if they conflict?


> namespace control in aegis (with jaxws) don't work for the wsdl element, only for the schemas
> ---------------------------------------------------------------------------------------------
>
>                 Key: CXF-1084
>                 URL: https://issues.apache.org/jira/browse/CXF-1084
>             Project: CXF
>          Issue Type: Bug
>          Components: Aegis Databinding
>    Affects Versions: 2.0.2
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>
> When aegis is used with the JaxWs front-end, the namespaceMap on the data binding has no effect on the prefixes used for the wsdl element, and thus for the parts and related bits.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.