[#PETALSSEBPEL-2] JDOM to DOM conversion generate double namespace in AXIOM at marshal time - Petals Link JIRA

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: 1.0.4
Fix Version/s: 1.0.4
Component/s: None
Security Level: Public

Description:

Hide

JDOM to DOM conversion generates DOM Documents which are not namespace aware ; no way to work around this in JDOM.

At time 1.0.3 was released, a quick and dirty patch has been added to bc-soap to prevent generation of these double namespaces (bc-soap, commit r15184).

Remember to recheck this test case newt time Prosodie test cases will be run, to reproduce the problem and fix it properly by removing jdom DOMOutputter in se-bpel, and replacing it with an XMLOutputter, which should fix properly the problem.

Remove related hack in bc-soap.

Show
JDOM to DOM conversion generates DOM Documents which are not namespace aware ; no way to work around this in JDOM. At time 1.0.3 was released, a quick and dirty patch has been added to bc-soap to prevent generation of these double namespaces (bc-soap, commit r15184). Remember to recheck this test case newt time Prosodie test cases will be run, to reproduce the problem and fix it properly by removing jdom DOMOutputter in se-bpel, and replacing it with an XMLOutputter, which should fix properly the problem. Remove related hack in bc-soap.

Environment:

petals 3.1
bc-soap 4.0.3

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

mjambert added a comment - Tue, 13 Jul 2010 - 17:16:15 +0200

Moreover, hack in bc-soap is partial : we can still have a double "default" namespace.

Sample :
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">soap:Server</faultcode>
<faultstring>A fault occurs during the petals treatment</faultstring>
<detail>
<removeClientOperationIllegalArgumentFault xmlns="http://contract.prosodie.com/DeliveredServiceService/1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://contract.prosodie.com/DeliveredServiceService/1/"
xmlns:fault="http://document.prosodie.com/Fault/1/" xsi:type="fault:IllegalArgumentFault">
<tns:message xmlns:tns="http://document.prosodie.com/Fault/1/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:type="xs:string">
RemoveClientOperation Error.
</tns:message>
</removeClientOperationIllegalArgumentFault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>

Show

mjambert added a comment - Tue, 13 Jul 2010 - 17:16:15 +0200 Moreover, hack in bc-soap is partial : we can still have a double "default" namespace. Sample : <?xml version='1.0' encoding='UTF-8'?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <soapenv:Fault> <faultcode xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">soap:Server</faultcode> <faultstring>A fault occurs during the petals treatment</faultstring> <detail> <removeClientOperationIllegalArgumentFault xmlns="http://contract.prosodie.com/DeliveredServiceService/1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://contract.prosodie.com/DeliveredServiceService/1/" xmlns:fault="http://document.prosodie.com/Fault/1/" xsi:type="fault:IllegalArgumentFault"> <tns:message xmlns:tns="http://document.prosodie.com/Fault/1/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:type="xs:string"> RemoveClientOperation Error. </tns:message> </removeClientOperationIllegalArgumentFault> </detail> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope>

People

Assignee:

mjambert

Reporter:

mjambert
Watchers:

0

Dates

Created:

Wed, 7 Jul 2010 - 15:26:08 +0200

Updated:

Tue, 12 Oct 2010 - 17:53:09 +0200

Resolved:

Tue, 12 Oct 2010 - 17:53:04 +0200

Petals SE BPEL

JDOM to DOM conversion generate double namespace in AXIOM at marshal time

Details

Activity

People

Dates