axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Poetter (JIRA)" <>
Subject [jira] Created: (AXIS2-4006) Request for support for configuring AXIS2 with XMLBeans to tune namespace output when writing XML data
Date Tue, 02 Sep 2008 09:58:46 GMT
Request for support for configuring AXIS2 with XMLBeans to tune namespace output when writing
XML data

                 Key: AXIS2-4006
             Project: Axis 2.0 (Axis2)
          Issue Type: Improvement
          Components: modules
    Affects Versions: 1.4
         Environment: WinXP SP3 GER with AXIS2 server,XMLBeans 2.3
            Reporter: Thomas Poetter

Normally, I use code like this to fine-tune my XMLBeans namespaces for textual output:

XmlOptions xmlOptions = new XmlOptions();
HashMap suggestedPrefixes = new HashMap();
suggestedPrefixes.put("", "xsi");
String xmlStr = doc.xmlText(xmlOptions);

The first difficulty I have is with explicit prefixes like "xmlns" in these combinations:
"xmlns:tns" or "xmlns:soap". They don't seem to be accepted as specification by XMLBeans and
lead to a guessed namespace abbreviation in output of XMLBeans. Omitting the "xmlns:" part
works for the suggestedPrefixes HashMap - but I require them also to be explicitly mentioned
with "xmlns:" prefix at least in the namespace definition section created by XMLBeans because
they will later be subject to XML signing where every bit counts. I cannot achieve this so

My main question is: How can I specify/control how AXIS2 calls XMLBeans/SOAP for outputting
the XML?

Keith Chapman commented in the WSO2 online forum:
"Axis2 allows you to pass in options to these various dataBinding frameworks by prefixing
the option with -E. But going through the XMLBeans integration code in axis2 I don't see us
taking note of the options you mention above. Perhaps you could raise this as a JIRA on the
axis2 list."

I found the XMLBeans integration code in this directory:
However, the class/constructor Axis2BindingConfig in file CodeGenerationUtility just seems
to configure the mapping of URIs to package names. What I need to tune are the settings when
writing the data wihtin an XMLBean to a file or stream, e.g. using XmlOptions as stated above.
How/where can this be added/configured/patched in AXIS2? With some hints, I might be able
to do the extension/patch in AXIS2 myself.

I need to create an XML that conforms exactly to a given specification in each and every bit
because it is subject to an XML signature. Since the mentioning of namespaces is not adjusted
perfectly by XML canonicalization, this is a serious issue.
Since the XML structures are stored in their own class structures (and not just as simple
text strings) in the SOAP libraries, I can't easily adapt/correct them.
Is there any point where I can easily add some project-specific patches to the SOAP or AXIS2
libraries to really adjust every bit of XML before signing?
The best spot for patches I can think about right now is the XML canonicalization (
which also requires some complex attribute handling. Does anybody have some other suggestions?
Are there any interfaces or interceptors foreseen for XML fine-tuning? Are there any easily
adaptable examples for using them in this scenario?
Does anybody have experience fine-tuning the XML for using XML signatures that have to be
exactly compatible with a 2 years old server using some other implementation for canonicalization
and XML binding?

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:
For additional commands, e-mail:

View raw message