[ http://issues.apache.org/jira/browse/BEEHIVE-705?page=all ]

Chad Schoettger updated BEEHIVE-705:
------------------------------------

    Attachment: BEEHIVE-705.txt

Added patch for this bug and BEEHIVE-703.

Fix for 705:
* Added method to XmlBeanWSDLProcessor to build a Map of 
namespaces->elementFormDefault setting
* Updated service control impl to use the map when building a Call object and 
to do the right thing with the parameter namespaces base on the 
elementFormDefault setting.

Fix for 703:
Updated XmlBeanDeserializer to be aware of the element form qualifed setting 
when parsing an axis response.  The response from axis is always fully 
qualified (elementFormDefault="qualified") which causes problems for XML beans 
when the WSDL does not specify the element form qualified setting.  If this 
situation is detected use XmlOptions during the XML bean parse to correctly 
load the response into an xml bean.


> Service Contorl needs to be aware of the elementFormDefault attribute in 
> registeing types.
> ------------------------------------------------------------------------------------------
>
>          Key: BEEHIVE-705
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-705
>      Project: Beehive
>         Type: Bug
>   Components: System Controls
>     Reporter: daryoush mehrtash
>     Assignee: Chad Schoettger
>      Fix For: TBD
>  Attachments: BEEHIVE-705.txt
>
> This issue has been imported from controlhaus
> At this time all names are registered as qualifed with their namespaces. This 
> should only be the case if elementFormDefault="qualified" otherwise the 
> namespaces should be left as blank.

-- 
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

Reply via email to