Omkar Vinit Joshi created JCLOUDS-665:
-----------------------------------------

             Summary: xml parser for S3 doesn't take namespace into 
consideration.
                 Key: JCLOUDS-665
                 URL: https://issues.apache.org/jira/browse/JCLOUDS-665
             Project: jclouds
          Issue Type: Bug
            Reporter: Omkar Vinit Joshi


Jclouds by default assumes that the response will be in default namespace which 
may not the case always. It should respect the namespace in given xml.
For S3.
xml which will get parsed correctly.
<Error xmlns="http://s3.amazonaws.com/doc/2006-03-01/";>   
        <Code>InternalError</Code>
        <Message>
                We encountered an internal error. Please try again.             
                             
        </Message>
        <Resource>req123</Resource>
        <RequestId>1407808787722531</RequestId>
</Error>

what will not work is below xml string parsing...

<ns0:Error xmlns:ns0="http://s3.amazonaws.com/doc/2006-03-01/";>   
        <ns0:Code>InternalError</ns0:Code>
        <ns0:Message>
                We encountered an internal error. Please try again.             
                             
        </ns0:Message>
        <ns0:Resource>req123</ns0:Resource
        <ns0:RequestId>1407808787722531</ns0:RequestId>
</ns0:Error>



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to