Re: XMLBEANS-427 -- Namespace prefix in attribute value not resolved correctly
Robert, If a there is a patch provided and the review shows it's good, it gets checked in and will be available in the next release. We've been talking about another release, but unfortunately there weren't enough time resources from the committers. If anybody can help with it, I'll work with you and start the ball rolling for a new release. Cezar On Mon, 2011-08-22 at 11:37 -0400, Robert J. Liguori wrote: Dear XmlBeans Dev Team, Anyway we can get a fix for the following JIRA issue in the next build? Namespace prefix in attribute value not resolved correctly https://issues.apache.org/jira/browse/XMLBEANS-427 If so, timewise... when would this build be released? Thanks, Robert - To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org - To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
[jira] [Assigned] (XMLBEANS-427) Namespace prefix in attribute value not resolved correctly
[ https://issues.apache.org/jira/browse/XMLBEANS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cezar Andrei reassigned XMLBEANS-427: - Assignee: Cezar Andrei Namespace prefix in attribute value not resolved correctly -- Key: XMLBEANS-427 URL: https://issues.apache.org/jira/browse/XMLBEANS-427 Project: XMLBeans Issue Type: Bug Components: Binding Affects Versions: Version 2.4 Reporter: Lukas Krecan Assignee: Cezar Andrei Attachments: test-ws-1.0-SNAPSHOT-src.zip I have following SOAP request. soapenv:Envelope xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Header/ soapenv:Body ns:getRights ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn ns:msisdn420123456789/ns:msisdn /ns:customerCredential /ns:getRights /soapenv:Body /soapenv:Envelope I only need to bind the payload: ns:getRights ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn ns:msisdn420123456789/ns:msisdn /ns:customerCredential /ns:getRights Please note that namespace prefix ns is not defined. Usually this is not a problem since in DOM namespaces are already resolved. There is one exception - attribute value. When XmlBeans try to unmarshall the element, they are not able to resolve the namespace and do not work correctly. If following request is used (the only difference is position of ns prefix declaration) everything works fine soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Header/ soapenv:Body ns:getRights xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0; ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn ns:msisdn420123456789/ns:msisdn /ns:customerCredential /ns:getRights /soapenv:Body /soapenv:Envelope -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
[jira] [Resolved] (XMLBEANS-427) Namespace prefix in attribute value not resolved correctly
[ https://issues.apache.org/jira/browse/XMLBEANS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cezar Andrei resolved XMLBEANS-427. --- Resolution: Invalid Fix Version/s: Version 2.5 Please use the setLoadAdditionalNamespaces() XmlOption when loading the subtree, with all the namespaces in that contest. See following link for details: http://xmlbeans.apache.org/docs/2.4.0/reference/org/apache/xmlbeans/XmlOptions.html#setLoadAdditionalNamespaces%28java.util.Map%29 Namespace prefix in attribute value not resolved correctly -- Key: XMLBEANS-427 URL: https://issues.apache.org/jira/browse/XMLBEANS-427 Project: XMLBeans Issue Type: Bug Components: Binding Affects Versions: Version 2.4 Reporter: Lukas Krecan Assignee: Cezar Andrei Fix For: Version 2.5 Attachments: test-ws-1.0-SNAPSHOT-src.zip I have following SOAP request. soapenv:Envelope xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Header/ soapenv:Body ns:getRights ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn ns:msisdn420123456789/ns:msisdn /ns:customerCredential /ns:getRights /soapenv:Body /soapenv:Envelope I only need to bind the payload: ns:getRights ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn ns:msisdn420123456789/ns:msisdn /ns:customerCredential /ns:getRights Please note that namespace prefix ns is not defined. Usually this is not a problem since in DOM namespaces are already resolved. There is one exception - attribute value. When XmlBeans try to unmarshall the element, they are not able to resolve the namespace and do not work correctly. If following request is used (the only difference is position of ns prefix declaration) everything works fine soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Header/ soapenv:Body ns:getRights xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0; ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn ns:msisdn420123456789/ns:msisdn /ns:customerCredential /ns:getRights /soapenv:Body /soapenv:Envelope -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
Re: XMLBEANS-427 -- Namespace prefix in attribute value not resolved correctly
I looked at the Jira issue, it's actually not a bug it needs to provide the additional namespaces in that context at the time of XmlBeans parsing. Cezar On Fri, 2011-09-16 at 12:00 -0500, Cezar Andrei wrote: Robert, If a there is a patch provided and the review shows it's good, it gets checked in and will be available in the next release. We've been talking about another release, but unfortunately there weren't enough time resources from the committers. If anybody can help with it, I'll work with you and start the ball rolling for a new release. Cezar On Mon, 2011-08-22 at 11:37 -0400, Robert J. Liguori wrote: Dear XmlBeans Dev Team, Anyway we can get a fix for the following JIRA issue in the next build? Namespace prefix in attribute value not resolved correctly https://issues.apache.org/jira/browse/XMLBEANS-427 If so, timewise... when would this build be released? Thanks, Robert - To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org - To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org - To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
XMLBEANS-427 -- Namespace prefix in attribute value not resolved correctly
Dear XmlBeans Dev Team, Anyway we can get a fix for the following JIRA issue in the next build? Namespace prefix in attribute value not resolved correctly https://issues.apache.org/jira/browse/XMLBEANS-427 If so, timewise... when would this build be released? Thanks, Robert - To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
[jira] Created: (XMLBEANS-427) Namespace prefix in attribute value not resolved correctly
Namespace prefix in attribute value not resolved correctly -- Key: XMLBEANS-427 URL: https://issues.apache.org/jira/browse/XMLBEANS-427 Project: XMLBeans Issue Type: Bug Components: Binding Affects Versions: Version 2.4 Reporter: Lukas krecan I have following SOAP request. soapenv:Envelope xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Header/ soapenv:Body ns:getRights ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn ns:msisdn420123456789/ns:msisdn /ns:customerCredential /ns:getRights /soapenv:Body /soapenv:Envelope I only need to bind the payload: ns:getRights ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn ns:msisdn420123456789/ns:msisdn /ns:customerCredential /ns:getRights Please note that namespace prefix ns is not defined. Usually this is not a problem since in DOM namespaces are already resolved. There is one exception - attribute value. When XmlBeans try to unmarshall the element, they are not able to resolve the namespace and do not work correctly. If following request is used (the only difference is position of ns prefix declaration) everything works fine soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Header/ soapenv:Body ns:getRights xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0; ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn ns:msisdn420123456789/ns:msisdn /ns:customerCredential /ns:getRights /soapenv:Body /soapenv:Envelope -- 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: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
[jira] Updated: (XMLBEANS-427) Namespace prefix in attribute value not resolved correctly
[
https://issues.apache.org/jira/browse/XMLBEANS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas krecan updated XMLBEANS-427:
--
Description:
I have following SOAP request.
{code}
soapenv:Envelope xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0;
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
soapenv:Header/
soapenv:Body
ns:getRights
ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn
ns:msisdn420123456789/ns:msisdn
/ns:customerCredential
/ns:getRights
/soapenv:Body
/soapenv:Envelope
{code}
I only need to bind the payload:
{code}
ns:getRights
ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn
ns:msisdn420123456789/ns:msisdn
/ns:customerCredential
/ns:getRights
{code}
Please note that namespace prefix ns is not defined. Usually this is not a
problem since in DOM namespaces are already resolved. There is one exception -
attribute value. When XmlBeans try to unmarshall the element, they are not able
to resolve the namespace and do not work correctly.
If following request is used (the only difference is position of ns prefix
declaration) everything works fine
{code}
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
soapenv:Header/
soapenv:Body
ns:getRights xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0;
ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn
ns:msisdn420123456789/ns:msisdn
/ns:customerCredential
/ns:getRights
/soapenv:Body
/soapenv:Envelope
{code}
was:
I have following SOAP request.
{code:xml}
soapenv:Envelope xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0;
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
soapenv:Header/
soapenv:Body
ns:getRights
ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn
ns:msisdn420123456789/ns:msisdn
/ns:customerCredential
/ns:getRights
/soapenv:Body
/soapenv:Envelope
{code}
I only need to bind the payload:
{code:xml}
ns:getRights
ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn
ns:msisdn420123456789/ns:msisdn
/ns:customerCredential
/ns:getRights
{code}
Please note that namespace prefix ns is not defined. Usually this is not a
problem since in DOM namespaces are already resolved. There is one exception -
attribute value. When XmlBeans try to unmarshall the element, they are not able
to resolve the namespace and do not work correctly.
If following request is used (the only difference is position of ns prefix
declaration) everything works fine
{code:xml}
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
soapenv:Header/
soapenv:Body
ns:getRights xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0;
ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn
ns:msisdn420123456789/ns:msisdn
/ns:customerCredential
/ns:getRights
/soapenv:Body
/soapenv:Envelope
{code}
Namespace prefix in attribute value not resolved correctly
--
Key: XMLBEANS-427
URL: https://issues.apache.org/jira/browse/XMLBEANS-427
Project: XMLBeans
Issue Type: Bug
Components: Binding
Affects Versions: Version 2.4
Reporter: Lukas krecan
I have following SOAP request.
{code}
soapenv:Envelope xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0;
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
soapenv:Header/
soapenv:Body
ns:getRights
ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn
ns:msisdn420123456789/ns:msisdn
/ns:customerCredential
/ns:getRights
/soapenv:Body
/soapenv:Envelope
{code}
I only need to bind the payload:
{code}
ns:getRights
ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn
ns:msisdn420123456789/ns:msisdn
/ns:customerCredential
/ns:getRights
{code}
Please note that namespace prefix ns is not defined. Usually this is not a
problem since in DOM namespaces are already resolved. There is one exception
- attribute value. When XmlBeans try to unmarshall the element, they are not
able to resolve the namespace and do not work correctly.
If following request is used (the only difference is position of ns prefix
declaration) everything works fine
{code}
soapenv:Envelope
[jira] Updated: (XMLBEANS-427) Namespace prefix in attribute value not resolved correctly
[
https://issues.apache.org/jira/browse/XMLBEANS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas krecan updated XMLBEANS-427:
--
Description:
I have following SOAP request.
{code:xml}
soapenv:Envelope xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0;
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
soapenv:Header/
soapenv:Body
ns:getRights
ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn
ns:msisdn420123456789/ns:msisdn
/ns:customerCredential
/ns:getRights
/soapenv:Body
/soapenv:Envelope
{code}
I only need to bind the payload:
{code:xml}
ns:getRights
ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn
ns:msisdn420123456789/ns:msisdn
/ns:customerCredential
/ns:getRights
{code}
Please note that namespace prefix ns is not defined. Usually this is not a
problem since in DOM namespaces are already resolved. There is one exception -
attribute value. When XmlBeans try to unmarshall the element, they are not able
to resolve the namespace and do not work correctly.
If following request is used (the only difference is position of ns prefix
declaration) everything works fine
{code:xml}
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
soapenv:Header/
soapenv:Body
ns:getRights xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0;
ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn
ns:msisdn420123456789/ns:msisdn
/ns:customerCredential
/ns:getRights
/soapenv:Body
/soapenv:Envelope
{code}
was:
I have following SOAP request.
soapenv:Envelope xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0;
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
soapenv:Header/
soapenv:Body
ns:getRights
ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn
ns:msisdn420123456789/ns:msisdn
/ns:customerCredential
/ns:getRights
/soapenv:Body
/soapenv:Envelope
I only need to bind the payload:
ns:getRights
ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn
ns:msisdn420123456789/ns:msisdn
/ns:customerCredential
/ns:getRights
Please note that namespace prefix ns is not defined. Usually this is not a
problem since in DOM namespaces are already resolved. There is one exception -
attribute value. When XmlBeans try to unmarshall the element, they are not able
to resolve the namespace and do not work correctly.
If following request is used (the only difference is position of ns prefix
declaration) everything works fine
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
soapenv:Header/
soapenv:Body
ns:getRights xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0;
ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn
ns:msisdn420123456789/ns:msisdn
/ns:customerCredential
/ns:getRights
/soapenv:Body
/soapenv:Envelope
Namespace prefix in attribute value not resolved correctly
--
Key: XMLBEANS-427
URL: https://issues.apache.org/jira/browse/XMLBEANS-427
Project: XMLBeans
Issue Type: Bug
Components: Binding
Affects Versions: Version 2.4
Reporter: Lukas krecan
I have following SOAP request.
{code:xml}
soapenv:Envelope xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0;
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
soapenv:Header/
soapenv:Body
ns:getRights
ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn
ns:msisdn420123456789/ns:msisdn
/ns:customerCredential
/ns:getRights
/soapenv:Body
/soapenv:Envelope
{code}
I only need to bind the payload:
{code:xml}
ns:getRights
ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn
ns:msisdn420123456789/ns:msisdn
/ns:customerCredential
/ns:getRights
{code}
Please note that namespace prefix ns is not defined. Usually this is not a
problem since in DOM namespaces are already resolved. There is one exception
- attribute value. When XmlBeans try to unmarshall the element, they are not
able to resolve the namespace and do not work correctly.
If following request is used (the only difference is position of ns prefix
declaration) everything works fine
{code:xml}
soapenv:Envelope
[jira] Commented: (XMLBEANS-427) Namespace prefix in attribute value not resolved correctly
[ https://issues.apache.org/jira/browse/XMLBEANS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12796197#action_12796197 ] Lukas krecan commented on XMLBEANS-427: --- See original Spring WS issue http://jira.springframework.org/browse/SWS-523 Namespace prefix in attribute value not resolved correctly -- Key: XMLBEANS-427 URL: https://issues.apache.org/jira/browse/XMLBEANS-427 Project: XMLBeans Issue Type: Bug Components: Binding Affects Versions: Version 2.4 Reporter: Lukas krecan Attachments: test-ws-1.0-SNAPSHOT-src.zip I have following SOAP request. soapenv:Envelope xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Header/ soapenv:Body ns:getRights ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn ns:msisdn420123456789/ns:msisdn /ns:customerCredential /ns:getRights /soapenv:Body /soapenv:Envelope I only need to bind the payload: ns:getRights ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn ns:msisdn420123456789/ns:msisdn /ns:customerCredential /ns:getRights Please note that namespace prefix ns is not defined. Usually this is not a problem since in DOM namespaces are already resolved. There is one exception - attribute value. When XmlBeans try to unmarshall the element, they are not able to resolve the namespace and do not work correctly. If following request is used (the only difference is position of ns prefix declaration) everything works fine soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Header/ soapenv:Body ns:getRights xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0; ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn ns:msisdn420123456789/ns:msisdn /ns:customerCredential /ns:getRights /soapenv:Body /soapenv:Envelope -- 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: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
[jira] Updated: (XMLBEANS-427) Namespace prefix in attribute value not resolved correctly
[ https://issues.apache.org/jira/browse/XMLBEANS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas krecan updated XMLBEANS-427: -- Attachment: test-ws-1.0-SNAPSHOT-src.zip Test Namespace prefix in attribute value not resolved correctly -- Key: XMLBEANS-427 URL: https://issues.apache.org/jira/browse/XMLBEANS-427 Project: XMLBeans Issue Type: Bug Components: Binding Affects Versions: Version 2.4 Reporter: Lukas krecan Attachments: test-ws-1.0-SNAPSHOT-src.zip I have following SOAP request. soapenv:Envelope xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Header/ soapenv:Body ns:getRights ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn ns:msisdn420123456789/ns:msisdn /ns:customerCredential /ns:getRights /soapenv:Body /soapenv:Envelope I only need to bind the payload: ns:getRights ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn ns:msisdn420123456789/ns:msisdn /ns:customerCredential /ns:getRights Please note that namespace prefix ns is not defined. Usually this is not a problem since in DOM namespaces are already resolved. There is one exception - attribute value. When XmlBeans try to unmarshall the element, they are not able to resolve the namespace and do not work correctly. If following request is used (the only difference is position of ns prefix declaration) everything works fine soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Header/ soapenv:Body ns:getRights xmlns:ns=http://schemas.qqq.com/wsdl/spi/profile/1.0; ns:customerCredential xsi:type=ns:CustomerCredentialMsisdn ns:msisdn420123456789/ns:msisdn /ns:customerCredential /ns:getRights /soapenv:Body /soapenv:Envelope -- 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: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
