[
https://issues.apache.org/jira/browse/ODE-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthieu Riou resolved ODE-290.
-------------------------------
Resolution: Fixed
Assignee: Matthieu Riou
Even if it's maybe not ideal yet, I believe this has been greatly improved by
recent changes. Therefore closing the issue until something more specific
emerges.
> Excessive AXIS Namespace Prefix generation
> -------------------------------------------
>
> Key: ODE-290
> URL: https://issues.apache.org/jira/browse/ODE-290
> Project: ODE
> Issue Type: Bug
> Components: Axis2 Integration
> Affects Versions: 1.1.1
> Environment: Java6u6, Tomcat 6.0.16
> Reporter: Ciaran Jessup
> Assignee: Matthieu Riou
> Priority: Minor
> Fix For: 1.2
>
>
> The AXIS SOAP responses I'm getting back from ODE within soapui show a
> worrying proliferation of namespace prefixes. The same namespace is
> receiving a new prefix everytime it is referenced in the response document,
> an example document showing a mock-up of web service result follows:
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> <soapenv:Body>
> <axis2ns4756:ExecuteWorkflowResponse
> xmlns:axis2ns4756="http://mynsworkflow"; xmlns="http://mynsworkflow";
> xmlns:saw="http://mynsworkflow";>
> <ExecuteWorkflowResult version="48" xmlns:ns2="http://mynswsdl";>
> <axis2ns4757:type xmlns:axis2ns4757="http://mynsmsg";
> xmlns="http://mynsmsg";>1</axis2ns4757:type>
> <axis2ns4758:status xmlns:axis2ns4758="http://mynsmsg";
> xmlns="http://mynsmsg";>1</axis2ns4758:status>
> <axis2ns4759:channel xmlns:axis2ns4759="http://mynsmsg";
> xmlns="http://mynsmsg";>0</axis2ns4759:channel>
> <axis2ns4760:outcome xmlns:axis2ns4760="http://mynsmsg";
> xmlns="http://mynsmsg";>bece5689-a575-4531-86b6-15176d827c08</axis2ns4760:outcome>
> <axis2ns4761:state xmlns:axis2ns4761="http://mynsmsg";
> xmlns="http://mynsmsg";>53f123fc-9a27-4559-8fd2-86a6f9dc598e</axis2ns4761:state>
> <axis2ns4762:creationTime xmlns:axis2ns4762="http://mynsmsg";
> xmlns="http://mynsmsg";>0001-01-03T00:00:00+00:00</axis2ns4762:creationTime>
> <axis2ns4763:changeTime xmlns:axis2ns4763="http://mynsmsg";
> xmlns="http://mynsmsg";>0001-01-03T00:00:00+00:00</axis2ns4763:changeTime>
> <axis2ns4764:createdBy xmlns:axis2ns4764="http://mynsmsg";
> xmlns="http://mynsmsg";>bece5689-a575-4531-86b6-15176d827c08</axis2ns4764:createdBy>
> </ExecuteWorkflowResult>
> </axis2ns4756:ExecuteWorkflowResponse>
> </soapenv:Body>
> </soapenv:Envelope>
> As one can see the same namespace is repeated for every element (the XSD
> specifies that the element's default form is qualified), each element
> receiving a new prefix, where each prefix is a unique value.
> Now semantically speaking of course this doesn't matter, but I worry about
> the possible overhead of this (both in terms of having to create new
> namespace prefixes that are *globally* unique to the app server as far as I
> can tell, there must be some synchronisation there? and in terms of
> un-neccessary traffic over the wire as the XML is much 'fatter' than
> neccessary)
> I *think* this is an issue with the relationship between ODE and AXIS2,
> rather than woodstox as I use that in a different portion of my app?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
