[
https://jira.jboss.org/jira/browse/JBWS-3012?page=com.atlassian.jira.plug...
]
Tim Walsh updated JBWS-3012:
----------------------------
Description:
https://enterprise.redhat.com/issue-tracker/?module=issues&action=vie...
After upgrading from CP03 to CP07 we now get the following errors on our production
environment concerning JBossWS:
Caused by: javax.xml.bind.UnmarshalException: unrecognized type name: debitCardSO. Did you
mean {http://service.dienstcontract.services.snsbank.nl/}debitCardSO?
at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.handleEvent(UnmarshallingContext.java:603)
at com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:244)
at com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:239)
This problem did not occur on platforms with CP03, but was introduced after upgrading to
CP04 and CP07. It is blocking for our next release of services, so could you please supply
an estimated resolution time so we can adjust our release planning accordingly?
was:
https://enterprise.redhat.com/issue-tracker/?module=issues&action=vie...
After upgrading from CP03 to CP07 we now get the following errors on our production
environment concerning JBossWS:
Caused by: javax.xml.bind.UnmarshalException: unrecognized type name: debitCardSO. Did you
mean {http://service.dienstcontract.services.snsbank.nl/}debitCardSO?
at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.handleEvent(UnmarshallingContext.java:603)
at com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:244)
at com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:239)
The relevant input message part for this exception is:
<env:Body wsu:Id='element-17722-1268323678541-1923510807'
xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-ws...
<ns1:geefPaslimietenResponse
xmlns:ns1='http://service.dienstcontract.services.snsbank.nl/'
xmlns:ns2='http://service.dienstcontract.services.snsbank.nl/'>
<return>
<pas
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xsi:type='debitCardSO'>
<rekeningnummer>280102755</rekeningnummer>
The <pas> element (card in dutch) has the complexType "pasSO" which is not
abstract and used for most types of cards. For debit cards the "debitCardSO"
type is used which extends "pasSO".
It look like the xsi:type specifies the correct schema type, but misses a namespace prefix
which causes the UnmarshalException. It seems to me that the correct attribute would be:
xsi:type='ns1:debitCardSO'.
This problem did not occur on platforms with CP03, but was introduced after upgrading to
CP04 and CP07. It is blocking for our next release of services, so could you please supply
an estimated resolution time so we can adjust our release planning accordingly?
The JAXB build deployed with JBoss EAB 4.3 CP 07 throws a marshalling
exception
--------------------------------------------------------------------------------
Key: JBWS-3012
URL:
https://jira.jboss.org/jira/browse/JBWS-3012
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Environment: JBoss EAP 4.3 CP07
Reporter: Tim Walsh
https://enterprise.redhat.com/issue-tracker/?module=issues&action=vie...
After upgrading from CP03 to CP07 we now get the following errors on our production
environment concerning JBossWS:
Caused by: javax.xml.bind.UnmarshalException: unrecognized type name: debitCardSO. Did
you mean {http://service.dienstcontract.services.snsbank.nl/}debitCardSO?
at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.handleEvent(UnmarshallingContext.java:603)
at com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:244)
at com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:239)
This problem did not occur on platforms with CP03, but was introduced after upgrading to
CP04 and CP07. It is blocking for our next release of services, so could you please supply
an estimated resolution time so we can adjust our release planning accordingly?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira