You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Oleg Kozlov <ol...@leadpoint.com> on 2010/02/22 21:50:10 UTC

illegal XML character 0x8 from a .Net SOAP service :(

Hello,
 
I have an Axis2 1.5.1 (Java) client, auto-generated by wsdl2java with
XmlBeans framework.
 
I'm integrating with a new vendor that has a SOAP web service written in
.Net. The service is basically a wrapper around a legacy telephony
switch. The service returns 1-9 binary numbers in its response in one of
the XML elements. I have to point out that I our (client) side we do not
even need to use that element at all, it just has some meaningless
data... Apparently our vendor's other clients are all using .Net and the
.Net framework does not care about inserting or parsing illegal
characters in the SOAP Body ...
 
So, I'm getting an exception (see below).
 
I tried solving this problem by writing a custom Axis2 client module
where I get access to the XML element that contains illegal characters
and either set it's text value to blank string, or detach and get rid of
the whole XML element altogether (since I don't need it). However, every
time I iterate to the bad XML element - the parser blows up with the
parsing error again inside my custom module. Also, due to the fact that
Axis is using pull parsing method - there is no way to jump over the
element with binary data, so I was not able to copy the entire XML DOM
into a new DOM document skipping over the bad element.
 
I could not find a way to get low level access to XML stream where I
could, for example, read from an input stream and write to an output
stream, and skip over the illegal character.
 
Can anyone recommend another solution?
 
==============================
org.apache.axis2.AxisFault: [com.ctc.wstx.exc.WstxLazyException] Illegal
character entity: expansion character (code 0x8) not a valid XML
character
 at [row,col {unknown-source}]: [1,13020]
 at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
 at
leadpoint.voice.service.paetec.callrecords.client.ServiceStub.fromOM(Ser
viceStub.java:3315)
 at
leadpoint.voice.service.paetec.callrecords.client.ServiceStub.getEnhance
dCDR(ServiceStub.java:1063)
 at
leadpoint.voice.service.paetec.callrecords.client.ServiceTest.testgetEnh
ancedCDR(ServiceTest.java:184)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
 at
com.intellij.junit3.JUnit3IdeaTestRunner.doRun(JUnit3IdeaTestRunner.java
:108)
 at
com.intellij.junit3.JUnit3IdeaTestRunner.startRunnerWithArgs(JUnit3IdeaT
estRunner.java:42)
 at
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUni
tStarter.java:165)
 at
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:60)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
 at com.intellij.rt.execution.application.AppMain.main(AppMain.java:110)
Caused by: [com.ctc.wstx.exc.WstxLazyException]
com.ctc.wstx.exc.WstxParsingException: Illegal character entity:
expansion character (code 0x8) not a valid XML character
 at [row,col {unknown-source}]: [1,13020]
 at
com.ctc.wstx.exc.WstxLazyException.throwLazily(WstxLazyException.java:45
)
 at com.ctc.wstx.sr.StreamScanner.throwLazyError(StreamScanner.java:704)
 at
com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java
:3657)
 at
com.ctc.wstx.sr.BasicStreamReader.getTextCharacters(BasicStreamReader.ja
va:830)
 at
javax.xml.stream.util.StreamReaderDelegate.getTextCharacters(StreamReade
rDelegate.java:158)
 at
org.apache.axiom.om.impl.builder.SafeXMLStreamReader.getTextCharacters(S
afeXMLStreamReader.java:113)
 at
org.apache.axiom.om.impl.llom.OMStAXWrapper.getTextCharacters(OMStAXWrap
per.java:418)
 at
org.apache.axiom.om.util.OMXMLStreamReaderValidator.getTextCharacters(OM
XMLStreamReaderValidator.java:239)
 at
org.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader(Locale.java:11
54)
 at
org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:843)
 at
org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826)
 at
org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoa
derBase.java:231)
 at
com.paetec.e800ws.xmlservices.GetEnhancedCDRResponseDocument$Factory.par
se(GetEnhancedCDRResponseDocument.java:165)
 at
leadpoint.voice.service.paetec.callrecords.client.ServiceStub.fromOM(Ser
viceStub.java:3226)
 ... 23 more
Caused by: com.ctc.wstx.exc.WstxParsingException: Illegal character
entity: expansion character (code 0x8) not a valid XML character
 at [row,col {unknown-source}]: [1,13020]
 at
com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:6
05)
 at
com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:461)
 at
com.ctc.wstx.sr.StreamScanner.reportIllegalChar(StreamScanner.java:2375)
 at
com.ctc.wstx.sr.StreamScanner.checkAndExpandChar(StreamScanner.java:2321
)
 at
com.ctc.wstx.sr.StreamScanner.resolveSimpleEntity(StreamScanner.java:118
0)
 at
com.ctc.wstx.sr.BasicStreamReader.readTextSecondary(BasicStreamReader.ja
va:4675)
 at
com.ctc.wstx.sr.BasicStreamReader.readCoalescedText(BasicStreamReader.ja
va:4124)
 at
com.ctc.wstx.sr.BasicStreamReader.finishToken(BasicStreamReader.java:369
9)
 at
com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java
:3647)
 ... 34 more
==============================
 
Thank you,
Oleg.

Re: PLEASE DO NOT SEND UNSUBSCRIBE MESSAGES TO MAILING LISTS. Thank you. :)

Posted by Bruno Simioni <br...@gmail.com>.
God, thank you guy!
A can't support this anymore!


On Mon, Feb 22, 2010 at 6:11 PM, Glen Daniels <gl...@thoughtcraft.com> wrote:
> All:
>
> If you wish to unsubscribe from any apache mailing list, the general pattern
> is to drop a mail to "<listname>-unsubscribe@<host>.apache.org".  So in this
> case if you wish to be removed from java-user@axis.apache.org, you would mail
> an empty message to "java-user-unsubscribe@axis.apache.org".  Make sure to do
> this from the address that is subscribed to the list.
>
> Please do not send "unsubscribe" notes to the list itself, as you are
> cluttering hundreds of peoples' mailboxes when you do.
>
> Thanks,
> --Glen
>

PLEASE DO NOT SEND UNSUBSCRIBE MESSAGES TO MAILING LISTS. Thank you. :)

Posted by Glen Daniels <gl...@thoughtcraft.com>.
All:

If you wish to unsubscribe from any apache mailing list, the general pattern
is to drop a mail to "<listname>-unsubscribe@<host>.apache.org".  So in this
case if you wish to be removed from java-user@axis.apache.org, you would mail
an empty message to "java-user-unsubscribe@axis.apache.org".  Make sure to do
this from the address that is subscribed to the list.

Please do not send "unsubscribe" notes to the list itself, as you are
cluttering hundreds of peoples' mailboxes when you do.

Thanks,
--Glen

unsubscribe

Posted by Krzysztof Adamczyk <kr...@gmail.com>.


unsubscribe

Posted by Andre Coelho <an...@gmail.com>.


unsubscribe

Posted by "Hernandez Morales V, Carlos Alberto" <ca...@intercall.com>.
From: Mohannad Hammadeh [mailto:Mohannad.Hammadeh@orionhealth.com]
Sent: Monday, February 22, 2010 4:22 PM
To: java-user@axis.apache.org
Subject: unsubscribe


----- Original Message -----
From: "Paul Grillo" <Pa...@trivininc.com>
To: java-user@axis.apache.org
Sent: Tuesday, February 23, 2010 10:06:48 AM
Subject: unsubscribe


________________________________
From: Oleg Kozlov [mailto:oleg.kozlov@leadpoint.com]
Sent: Monday, February 22, 2010 3:50 PM
To: java-user@axis.apache.org
Subject: illegal XML character 0x8 from a .Net SOAP service :(

Hello,

I have an Axis2 1.5.1 (Java) client, auto-generated by wsdl2java with XmlBeans framework.

I'm integrating with a new vendor that has a SOAP web service written in .Net. The service is basically a wrapper around a legacy telephony switch. The service returns 1-9 binary numbers in its response in one of the XML elements. I have to point out that I our (client) side we do not even need to use that element at all, it just has some meaningless data... Apparently our vendor's other clients are all using .Net and the .Net framework does not care about inserting or parsing illegal characters in the SOAP Body ...

So, I'm getting an exception (see below).

I tried solving this problem by writing a custom Axis2 client module where I get access to the XML element that contains illegal characters and either set it's text value to blank string, or detach and get rid of the whole XML element altogether (since I don't need it). However, every time I iterate to the bad XML element - the parser blows up with the parsing error again inside my custom module. Also, due to the fact that Axis is using pull parsing method - there is no way to jump over the element with binary data, so I was not able to copy the entire XML DOM into a new DOM document skipping over the bad element.

I could not find a way to get low level access to XML stream where I could, for example, read from an input stream and write to an output stream, and skip over the illegal character.

Can anyone recommend another solution?

==============================
org.apache.axis2.AxisFault: [com.ctc.wstx.exc.WstxLazyException] Illegal character entity: expansion character (code 0x8) not a valid XML character
 at [row,col {unknown-source}]: [1,13020]
 at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
 at leadpoint.voice.service.paetec.callrecords.client.ServiceStub.fromOM(ServiceStub.java:3315)
 at leadpoint.voice.service.paetec.callrecords.client.ServiceStub.getEnhancedCDR(ServiceStub.java:1063)
 at leadpoint.voice.service.paetec.callrecords.client.ServiceTest.testgetEnhancedCDR(ServiceTest.java:184)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at com.intellij.junit3.JUnit3IdeaTestRunner.doRun(JUnit3IdeaTestRunner.java:108)
 at com.intellij.junit3.JUnit3IdeaTestRunner.startRunnerWithArgs(JUnit3IdeaTestRunner.java:42)
 at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:165)
 at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:60)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at com.intellij.rt.execution.application.AppMain.main(AppMain.java:110)
Caused by: [com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxParsingException: Illegal character entity: expansion character (code 0x8) not a valid XML character
 at [row,col {unknown-source}]: [1,13020]
 at com.ctc.wstx.exc.WstxLazyException.throwLazily(WstxLazyException.java:45)
 at com.ctc.wstx.sr.StreamScanner.throwLazyError(StreamScanner.java:704)
 at com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java:3657)
 at com.ctc.wstx.sr.BasicStreamReader.getTextCharacters(BasicStreamReader.java:830)
 at javax.xml.stream.util.StreamReaderDelegate.getTextCharacters(StreamReaderDelegate.java:158)
 at org.apache.axiom.om.impl.builder.SafeXMLStreamReader.getTextCharacters(SafeXMLStreamReader.java:113)
 at org.apache.axiom.om.impl.llom.OMStAXWrapper.getTextCharacters(OMStAXWrapper.java:418)
 at org.apache.axiom.om.util.OMXMLStreamReaderValidator.getTextCharacters(OMXMLStreamReaderValidator.java:239)
 at org.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader(Locale.java:1154)
 at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:843)
 at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826)
 at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231)
 at com.paetec.e800ws.xmlservices.GetEnhancedCDRResponseDocument$Factory.parse(GetEnhancedCDRResponseDocument.java:165)
 at leadpoint.voice.service.paetec.callrecords.client.ServiceStub.fromOM(ServiceStub.java:3226)
 ... 23 more
Caused by: com.ctc.wstx.exc.WstxParsingException: Illegal character entity: expansion character (code 0x8) not a valid XML character
 at [row,col {unknown-source}]: [1,13020]
 at com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:605)
 at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:461)
 at com.ctc.wstx.sr.StreamScanner.reportIllegalChar(StreamScanner.java:2375)
 at com.ctc.wstx.sr.StreamScanner.checkAndExpandChar(StreamScanner.java:2321)
 at com.ctc.wstx.sr.StreamScanner.resolveSimpleEntity(StreamScanner.java:1180)
 at com.ctc.wstx.sr.BasicStreamReader.readTextSecondary(BasicStreamReader.java:4675)
 at com.ctc.wstx.sr.BasicStreamReader.readCoalescedText(BasicStreamReader.java:4124)
 at com.ctc.wstx.sr.BasicStreamReader.finishToken(BasicStreamReader.java:3699)
 at com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java:3647)
 ... 34 more
==============================

Thank you,
Oleg.
NOTICE: This e-mail message and any attachments are confidential. Dissemination of this information by any person, including the intended recipient, or use of this information by any person other than the intended recipient is unauthorized. If you are not the intended recipient: please notify me by return e-mail as soon as possible, do not open any attachment and delete this communication and any copies from your computer. Thank you.

--
Mohannad Hammadeh | Legacy Interface Developer | Orion Health

P: +64 9 638 0600 | M: +64 21 334 143
F: +64 9 638 0699 | skype: mohannad.hammadeh

Orion Health | www.orionhealth.com

2nd Floor, Orion House | Cnr Mary and Enfield St | Mount Eden | Auckland 1003 | New Zealand

This e-mail and any attachments are intended only for the person to whom it is addressed and may contain privileged, proprietary, or other data protected from disclosure under applicable law. If you are not the addressee or the person responsible for delivering this to the addressee you are hereby notified that reading, copying or distributing this transmission is prohibited. If you have received this e-mail in error, please telephone us immediately and remove all copies of it from your system. Thank you for your co-operation.





unsubscribe

Posted by Chris Tinning <ch...@mclarensoftware.com>.
 

 

From: Mohannad Hammadeh [mailto:Mohannad.Hammadeh@orionhealth.com] 
Sent: 22 February 2010 22:22
To: java-user@axis.apache.org
Subject: unsubscribe

 


----- Original Message -----
From: "Paul Grillo" <Pa...@trivininc.com>
To: java-user@axis.apache.org
Sent: Tuesday, February 23, 2010 10:06:48 AM
Subject: unsubscribe

 

 

________________________________

From: Oleg Kozlov [mailto:oleg.kozlov@leadpoint.com] 
Sent: Monday, February 22, 2010 3:50 PM
To: java-user@axis.apache.org
Subject: illegal XML character 0x8 from a .Net SOAP service :(

 

Hello,

 

I have an Axis2 1.5.1 (Java) client, auto-generated by wsdl2java with XmlBeans framework.

 

I'm integrating with a new vendor that has a SOAP web service written in .Net. The service is basically a wrapper around a legacy telephony switch. The service returns 1-9 binary numbers in its response in one of the XML elements. I have to point out that I our (client) side we do not even need to use that element at all, it just has some meaningless data... Apparently our vendor's other clients are all using .Net and the .Net framework does not care about inserting or parsing illegal characters in the SOAP Body ...

 

So, I'm getting an exception (see below).

 

I tried solving this problem by writing a custom Axis2 client module where I get access to the XML element that contains illegal characters and either set it's text value to blank string, or detach and get rid of the whole XML element altogether (since I don't need it). However, every time I iterate to the bad XML element - the parser blows up with the parsing error again inside my custom module. Also, due to the fact that Axis is using pull parsing method - there is no way to jump over the element with binary data, so I was not able to copy the entire XML DOM into a new DOM document skipping over the bad element.

 

I could not find a way to get low level access to XML stream where I could, for example, read from an input stream and write to an output stream, and skip over the illegal character.

 

Can anyone recommend another solution?

 

==============================

org.apache.axis2.AxisFault: [com.ctc.wstx.exc.WstxLazyException] Illegal character entity: expansion character (code 0x8) not a valid XML character
 at [row,col {unknown-source}]: [1,13020]
 at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
 at leadpoint.voice.service.paetec.callrecords.client.ServiceStub.fromOM(ServiceStub.java:3315)
 at leadpoint.voice.service.paetec.callrecords.client.ServiceStub.getEnhancedCDR(ServiceStub.java:1063)
 at leadpoint.voice.service.paetec.callrecords.client.ServiceTest.testgetEnhancedCDR(ServiceTest.java:184)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at com.intellij.junit3.JUnit3IdeaTestRunner.doRun(JUnit3IdeaTestRunner.java:108)
 at com.intellij.junit3.JUnit3IdeaTestRunner.startRunnerWithArgs(JUnit3IdeaTestRunner.java:42)
 at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:165)
 at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:60)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at com.intellij.rt.execution.application.AppMain.main(AppMain.java:110)
Caused by: [com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxParsingException: Illegal character entity: expansion character (code 0x8) not a valid XML character
 at [row,col {unknown-source}]: [1,13020]
 at com.ctc.wstx.exc.WstxLazyException.throwLazily(WstxLazyException.java:45)
 at com.ctc.wstx.sr.StreamScanner.throwLazyError(StreamScanner.java:704)
 at com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java:3657)
 at com.ctc.wstx.sr.BasicStreamReader.getTextCharacters(BasicStreamReader.java:830)
 at javax.xml.stream.util.StreamReaderDelegate.getTextCharacters(StreamReaderDelegate.java:158)
 at org.apache.axiom.om.impl.builder.SafeXMLStreamReader.getTextCharacters(SafeXMLStreamReader.java:113)
 at org.apache.axiom.om.impl.llom.OMStAXWrapper.getTextCharacters(OMStAXWrapper.java:418)
 at org.apache.axiom.om.util.OMXMLStreamReaderValidator.getTextCharacters(OMXMLStreamReaderValidator.java:239)
 at org.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader(Locale.java:1154)
 at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:843)
 at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826)
 at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231)
 at com.paetec.e800ws.xmlservices.GetEnhancedCDRResponseDocument$Factory.parse(GetEnhancedCDRResponseDocument.java:165)
 at leadpoint.voice.service.paetec.callrecords.client.ServiceStub.fromOM(ServiceStub.java:3226)
 ... 23 more
Caused by: com.ctc.wstx.exc.WstxParsingException: Illegal character entity: expansion character (code 0x8) not a valid XML character
 at [row,col {unknown-source}]: [1,13020]
 at com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:605)
 at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:461)
 at com.ctc.wstx.sr.StreamScanner.reportIllegalChar(StreamScanner.java:2375)
 at com.ctc.wstx.sr.StreamScanner.checkAndExpandChar(StreamScanner.java:2321)
 at com.ctc.wstx.sr.StreamScanner.resolveSimpleEntity(StreamScanner.java:1180)
 at com.ctc.wstx.sr.BasicStreamReader.readTextSecondary(BasicStreamReader.java:4675)
 at com.ctc.wstx.sr.BasicStreamReader.readCoalescedText(BasicStreamReader.java:4124)
 at com.ctc.wstx.sr.BasicStreamReader.finishToken(BasicStreamReader.java:3699)
 at com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java:3647)
 ... 34 more

==============================

 

Thank you,

Oleg.

NOTICE: This e-mail message and any attachments are confidential. Dissemination of this information by any person, including the intended recipient, or use of this information by any person other than the intended recipient is unauthorized. If you are not the intended recipient: please notify me by return e-mail as soon as possible, do not open any attachment and delete this communication and any copies from your computer. Thank you. 

-- 
Mohannad Hammadeh | Legacy Interface Developer | Orion Health

P: +64 9 638 0600 | M: +64 21 334 143
F: +64 9 638 0699 | skype: mohannad.hammadeh

Orion Health | www.orionhealth.com

2nd Floor, Orion House | Cnr Mary and Enfield St | Mount Eden | Auckland 1003 | New Zealand

This e-mail and any attachments are intended only for the person to whom it is addressed and may contain privileged, proprietary, or other data protected from disclosure under applicable law. If you are not the addressee or the person responsible for delivering this to the addressee you are hereby notified that reading, copying or distributing this transmission is prohibited. If you have received this e-mail in error, please telephone us immediately and remove all copies of it from your system. Thank you for your co-operation.

 


________________________________________________________________________
This e-mail has been scanned for viruses, however, No liability is accepted for any viruses contained in this message or any of its attachments and it is the recipient?s liability to scan this message and its attachment for the same.
________________________________________________________________________



unsubscribe

Posted by Slim Driss <dr...@gmail.com>.

Envoyé de mon iPhone

Le 22 févr. 2010 à 23:22, Mohannad Hammadeh <Mohannad.Hammadeh@orionhealth.c 
om> a écrit :

>
> ----- Original Message -----
> From: "Paul Grillo" <Pa...@trivininc.com>
> To: java-user@axis.apache.org
> Sent: Tuesday, February 23, 2010 10:06:48 AM
> Subject: unsubscribe
>
>
>
>
>
> From: Oleg Kozlov [mailto:oleg.kozlov@leadpoint.com]
> Sent: Monday, February 22, 2010 3:50 PM
> To: java-user@axis.apache.org
> Subject: illegal XML character 0x8 from a .Net SOAP service :(
>
>
>
> Hello,
>
>
>
> I have an Axis2 1.5.1 (Java) client, auto-generated by wsdl2java  
> with XmlBeans framework.
>
>
>
> I'm integrating with a new vendor that has a SOAP web service  
> written in .Net. The service is basically a wrapper around a legacy  
> telephony switch. The service returns 1-9 binary numbers in its  
> response in one of the XML elements. I have to point out that I our  
> (client) side we do not even need to use that element at all, it  
> just has some meaningless data... Apparently our vendor's other  
> clients are all using .Net and the .Net framework does not care  
> about inserting or parsing illegal characters in the SOAP Body ...
>
>
>
> So, I'm getting an exception (see below).
>
>
>
> I tried solving this problem by writing a custom Axis2 client module  
> where I get access to the XML element that contains illegal  
> characters and either set it's text value to blank string, or detach  
> and get rid of the whole XML element altogether (since I don't need  
> it). However, every time I iterate to the bad XML element - the  
> parser blows up with the parsing error again inside my custom  
> module. Also, due to the fact that Axis is using pull parsing method  
> - there is no way to jump over the element with binary data, so I  
> was not able to copy the entire XML DOM into a new DOM document  
> skipping over the bad element.
>
>
>
> I could not find a way to get low level access to XML stream where I  
> could, for example, read from an input stream and write to an output  
> stream, and skip over the illegal character.
>
>
>
> Can anyone recommend another solution?
>
>
>
> ==============================
>
> org.apache.axis2.AxisFault: [com.ctc.wstx.exc.WstxLazyException]  
> Illegal character entity: expansion character (code 0x8) not a valid  
> XML character
>  at [row,col {unknown-source}]: [1,13020]
>  at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
>  at  
> leadpoint.voice.service.paetec.callrecords.client.ServiceStub.fromOM 
> (ServiceStub.java:3315)
>  at  
> leadpoint.voice.service.paetec.callrecords.client.ServiceStub.getEnhancedCDR( 
> ServiceStub.java:1063)
>  at  
> leadpoint.voice.service.paetec.callrecords.client.ServiceTest.testgetEnhancedCDR( 
> ServiceTest.java:184)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at sun.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:39)
>  at sun.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:25)
>  at com.intellij.junit3.JUnit3IdeaTestRunner.doRun 
> (JUnit3IdeaTestRunner.java:108)
>  at com.intellij.junit3.JUnit3IdeaTestRunner.startRunnerWithArgs 
> (JUnit3IdeaTestRunner.java:42)
>  at  
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart 
> (JUnitStarter.java:165)
>  at com.intellij.rt.execution.junit.JUnitStarter.main 
> (JUnitStarter.java:60)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at sun.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:39)
>  at com.intellij.rt.execution.application.AppMain.main(AppMain.java: 
> 110)
> Caused by: [com.ctc.wstx.exc.WstxLazyException]  
> com.ctc.wstx.exc.WstxParsingException: Illegal character entity:  
> expansion character (code 0x8) not a valid XML character
>  at [row,col {unknown-source}]: [1,13020]
>  at com.ctc.wstx.exc.WstxLazyException.throwLazily 
> (WstxLazyException.java:45)
>  at com.ctc.wstx.sr.StreamScanner.throwLazyError(StreamScanner.java: 
> 704)
>  at com.ctc.wstx.sr.BasicStreamReader.safeFinishToken 
> (BasicStreamReader.java:3657)
>  at com.ctc.wstx.sr.BasicStreamReader.getTextCharacters 
> (BasicStreamReader.java:830)
>  at javax.xml.stream.util.StreamReaderDelegate.getTextCharacters 
> (StreamReaderDelegate.java:158)
>  at  
> org.apache.axiom.om.impl.builder.SafeXMLStreamReader.getTextCharacters( 
> SafeXMLStreamReader.java:113)
>  at org.apache.axiom.om.impl.llom.OMStAXWrapper.getTextCharacters 
> (OMStAXWrapper.java:418)
>  at  
> org.apache.axiom.om.util.OMXMLStreamReaderValidator.getTextCharacters 
> (OMXMLStreamReaderValidator.java:239)
>  at org.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader 
> (Locale.java:1154)
>  at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject 
> (Locale.java:843)
>  at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject 
> (Locale.java:826)
>  at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse 
> (SchemaTypeLoaderBase.java:231)
>  at com.paetec.e800ws.xmlservices.GetEnhancedCDRResponseDocument 
> $Factory.parse(GetEnhancedCDRResponseDocument.java:165)
>  at  
> leadpoint.voice.service.paetec.callrecords.client.ServiceStub.fromOM 
> (ServiceStub.java:3226)
>  ... 23 more
> Caused by: com.ctc.wstx.exc.WstxParsingException: Illegal character  
> entity: expansion character (code 0x8) not a valid XML character
>  at [row,col {unknown-source}]: [1,13020]
>  at com.ctc.wstx.sr.StreamScanner.constructWfcException 
> (StreamScanner.java:605)
>  at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java: 
> 461)
>  at com.ctc.wstx.sr.StreamScanner.reportIllegalChar 
> (StreamScanner.java:2375)
>  at com.ctc.wstx.sr.StreamScanner.checkAndExpandChar 
> (StreamScanner.java:2321)
>  at com.ctc.wstx.sr.StreamScanner.resolveSimpleEntity 
> (StreamScanner.java:1180)
>  at com.ctc.wstx.sr.BasicStreamReader.readTextSecondary 
> (BasicStreamReader.java:4675)
>  at com.ctc.wstx.sr.BasicStreamReader.readCoalescedText 
> (BasicStreamReader.java:4124)
>  at com.ctc.wstx.sr.BasicStreamReader.finishToken 
> (BasicStreamReader.java:3699)
>  at com.ctc.wstx.sr.BasicStreamReader.safeFinishToken 
> (BasicStreamReader.java:3647)
>  ... 34 more
>
> ==============================
>
>
>
> Thank you,
>
> Oleg.
>
> NOTICE: This e-mail message and any attachments are confidential.  
> Dissemination of this information by any person, including the  
> intended recipient, or use of this information by any person other  
> than the intended recipient is unauthorized. If you are not the  
> intended recipient: please notify me by return e-mail as soon as  
> possible, do not open any attachment and delete this communication  
> and any copies from your computer. Thank you.
>
> -- 
> Mohannad Hammadeh | Legacy Interface Developer | Orion Health
>
> P: +64 9 638 0600 | M: +64 21 334 143
> F: +64 9 638 0699 | skype: mohannad.hammadeh
>
> Orion Health | www.orionhealth.com
>
> 2nd Floor, Orion House | Cnr Mary and Enfield St | Mount Eden |  
> Auckland 1003 | New Zealand
>
> This e-mail and any attachments are intended only for the person to  
> whom it is addressed and may contain privileged, proprietary, or  
> other data protected from disclosure under applicable law. If you  
> are not the addressee or the person responsible for delivering this  
> to the addressee you are hereby notified that reading, copying or  
> distributing this transmission is prohibited. If you have received  
> this e-mail in error, please telephone us immediately and remove all  
> copies of it from your system. Thank you for your co-operation.
>
>



unsubscribe

Posted by Mohannad Hammadeh <Mo...@orionhealth.com>.
----- Original Message ----- 
From: "Paul Grillo" <Pa...@trivininc.com> 
To: java-user@axis.apache.org 
Sent: Tuesday, February 23, 2010 10:06:48 AM 
Subject: unsubscribe 











From: Oleg Kozlov [mailto:oleg.kozlov@leadpoint.com] 
Sent: Monday, February 22, 2010 3:50 PM 
To: java-user@axis.apache.org 
Subject: illegal XML character 0x8 from a .Net SOAP service :( 



Hello, 






I have an Axis2 1.5.1 (Java) client, auto-generated by wsdl2java with XmlBeans framework. 





I'm integrating with a new vendor that has a SOAP web service written in .Net. The service is basically a wrapper around a legacy telephony switch. The service returns 1-9 binary numbers in its response in one of the XML elements. I have to point out that I our (client) side we do not even need to use that element at all, it just has some meaningless data... Apparently our vendor's other clients are all using .Net and the .Net framework does not care about inserting or parsing illegal characters in the SOAP Body ... 





So, I'm getting an exception (see below). 





I tried solving this problem by writing a custom Axis2 client module where I get access to the XML element that contains illegal characters and either set it's text value to blank string, or detach and get rid of the whole XML element altogether (since I don't need it). However, every time I iterate to the bad XML element - the parser blows up with the parsing error again inside my custom module. Also, due to the fact that Axis is using pull parsing method - there is no way to jump over the element with binary data, so I was not able to copy the entire XML DOM into a new DOM document skipping over the bad element. 





I could not find a way to get low level access to XML stream where I could, for example, read from an input stream and write to an output stream, and skip over the illegal character. 





Can anyone recommend another solution? 





============================== 


org.apache.axis2.AxisFault: [com.ctc.wstx.exc.WstxLazyException] Illegal character entity: expansion character (code 0x8) not a valid XML character 
at [row,col {unknown-source}]: [1,13020] 
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) 
at leadpoint.voice.service.paetec.callrecords.client.ServiceStub.fromOM(ServiceStub.java:3315) 
at leadpoint.voice.service.paetec.callrecords.client.ServiceStub.getEnhancedCDR(ServiceStub.java:1063) 
at leadpoint.voice.service.paetec.callrecords.client.ServiceTest.testgetEnhancedCDR(ServiceTest.java:184) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
at com.intellij.junit3.JUnit3IdeaTestRunner.doRun(JUnit3IdeaTestRunner.java:108) 
at com.intellij.junit3.JUnit3IdeaTestRunner.startRunnerWithArgs(JUnit3IdeaTestRunner.java:42) 
at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:165) 
at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:60) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:110) 
Caused by: [com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxParsingException: Illegal character entity: expansion character (code 0x8) not a valid XML character 
at [row,col {unknown-source}]: [1,13020] 
at com.ctc.wstx.exc.WstxLazyException.throwLazily(WstxLazyException.java:45) 
at com.ctc.wstx.sr.StreamScanner.throwLazyError(StreamScanner.java:704) 
at com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java:3657) 
at com.ctc.wstx.sr.BasicStreamReader.getTextCharacters(BasicStreamReader.java:830) 
at javax.xml.stream.util.StreamReaderDelegate.getTextCharacters(StreamReaderDelegate.java:158) 
at org.apache.axiom.om.impl.builder.SafeXMLStreamReader.getTextCharacters(SafeXMLStreamReader.java:113) 
at org.apache.axiom.om.impl.llom.OMStAXWrapper.getTextCharacters(OMStAXWrapper.java:418) 
at org.apache.axiom.om.util.OMXMLStreamReaderValidator.getTextCharacters(OMXMLStreamReaderValidator.java:239) 
at org.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader(Locale.java:1154) 
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:843) 
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826) 
at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231) 
at com.paetec.e800ws.xmlservices.GetEnhancedCDRResponseDocument$Factory.parse(GetEnhancedCDRResponseDocument.java:165) 
at leadpoint.voice.service.paetec.callrecords.client.ServiceStub.fromOM(ServiceStub.java:3226) 
... 23 more 
Caused by: com.ctc.wstx.exc.WstxParsingException: Illegal character entity: expansion character (code 0x8) not a valid XML character 
at [row,col {unknown-source}]: [1,13020] 
at com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:605) 
at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:461) 
at com.ctc.wstx.sr.StreamScanner.reportIllegalChar(StreamScanner.java:2375) 
at com.ctc.wstx.sr.StreamScanner.checkAndExpandChar(StreamScanner.java:2321) 
at com.ctc.wstx.sr.StreamScanner.resolveSimpleEntity(StreamScanner.java:1180) 
at com.ctc.wstx.sr.BasicStreamReader.readTextSecondary(BasicStreamReader.java:4675) 
at com.ctc.wstx.sr.BasicStreamReader.readCoalescedText(BasicStreamReader.java:4124) 
at com.ctc.wstx.sr.BasicStreamReader.finishToken(BasicStreamReader.java:3699) 
at com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java:3647) 
... 34 more 


============================== 





Thank you, 


Oleg. NOTICE: This e-mail message and any attachments are confidential. Dissemination of this information by any person, including the intended recipient, or use of this information by any person other than the intended recipient is unauthorized. If you are not the intended recipient: please notify me by return e-mail as soon as possible, do not open any attachment and delete this communication and any copies from your computer. Thank you. 

-- 
Mohannad Hammadeh | Legacy Interface Developer | Orion Health 

P: +64 9 638 0600 | M: +64 21 334 143 
F: +64 9 638 0699 | skype: mohannad.hammadeh 

Orion Health | www.orionhealth.com 

2nd Floor, Orion House | Cnr Mary and Enfield St | Mount Eden | Auckland 1003 | New Zealand 

This e-mail and any attachments are intended only for the person to whom it is addressed and may contain privileged, proprietary, or other data protected from disclosure under applicable law. If you are not the addressee or the person responsible for delivering this to the addressee you are hereby notified that reading, copying or distributing this transmission is prohibited. If you have received this e-mail in error, please telephone us immediately and remove all copies of it from your system. Thank you for your co-operation. 





unsubscribe

Posted by Paul Grillo <Pa...@trivininc.com>.
 

 

________________________________

From: Oleg Kozlov [mailto:oleg.kozlov@leadpoint.com] 
Sent: Monday, February 22, 2010 3:50 PM
To: java-user@axis.apache.org
Subject: illegal XML character 0x8 from a .Net SOAP service :(

 

Hello,

 

I have an Axis2 1.5.1 (Java) client, auto-generated by wsdl2java with
XmlBeans framework.

 

I'm integrating with a new vendor that has a SOAP web service written in
.Net. The service is basically a wrapper around a legacy telephony
switch. The service returns 1-9 binary numbers in its response in one of
the XML elements. I have to point out that I our (client) side we do not
even need to use that element at all, it just has some meaningless
data... Apparently our vendor's other clients are all using .Net and the
.Net framework does not care about inserting or parsing illegal
characters in the SOAP Body ...

 

So, I'm getting an exception (see below).

 

I tried solving this problem by writing a custom Axis2 client module
where I get access to the XML element that contains illegal characters
and either set it's text value to blank string, or detach and get rid of
the whole XML element altogether (since I don't need it). However, every
time I iterate to the bad XML element - the parser blows up with the
parsing error again inside my custom module. Also, due to the fact that
Axis is using pull parsing method - there is no way to jump over the
element with binary data, so I was not able to copy the entire XML DOM
into a new DOM document skipping over the bad element.

 

I could not find a way to get low level access to XML stream where I
could, for example, read from an input stream and write to an output
stream, and skip over the illegal character.

 

Can anyone recommend another solution?

 

==============================

org.apache.axis2.AxisFault: [com.ctc.wstx.exc.WstxLazyException] Illegal
character entity: expansion character (code 0x8) not a valid XML
character
 at [row,col {unknown-source}]: [1,13020]
 at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
 at
leadpoint.voice.service.paetec.callrecords.client.ServiceStub.fromOM(Ser
viceStub.java:3315)
 at
leadpoint.voice.service.paetec.callrecords.client.ServiceStub.getEnhance
dCDR(ServiceStub.java:1063)
 at
leadpoint.voice.service.paetec.callrecords.client.ServiceTest.testgetEnh
ancedCDR(ServiceTest.java:184)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
 at
com.intellij.junit3.JUnit3IdeaTestRunner.doRun(JUnit3IdeaTestRunner.java
:108)
 at
com.intellij.junit3.JUnit3IdeaTestRunner.startRunnerWithArgs(JUnit3IdeaT
estRunner.java:42)
 at
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUni
tStarter.java:165)
 at
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:60)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
 at com.intellij.rt.execution.application.AppMain.main(AppMain.java:110)
Caused by: [com.ctc.wstx.exc.WstxLazyException]
com.ctc.wstx.exc.WstxParsingException: Illegal character entity:
expansion character (code 0x8) not a valid XML character
 at [row,col {unknown-source}]: [1,13020]
 at
com.ctc.wstx.exc.WstxLazyException.throwLazily(WstxLazyException.java:45
)
 at com.ctc.wstx.sr.StreamScanner.throwLazyError(StreamScanner.java:704)
 at
com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java
:3657)
 at
com.ctc.wstx.sr.BasicStreamReader.getTextCharacters(BasicStreamReader.ja
va:830)
 at
javax.xml.stream.util.StreamReaderDelegate.getTextCharacters(StreamReade
rDelegate.java:158)
 at
org.apache.axiom.om.impl.builder.SafeXMLStreamReader.getTextCharacters(S
afeXMLStreamReader.java:113)
 at
org.apache.axiom.om.impl.llom.OMStAXWrapper.getTextCharacters(OMStAXWrap
per.java:418)
 at
org.apache.axiom.om.util.OMXMLStreamReaderValidator.getTextCharacters(OM
XMLStreamReaderValidator.java:239)
 at
org.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader(Locale.java:11
54)
 at
org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:843)
 at
org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826)
 at
org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoa
derBase.java:231)
 at
com.paetec.e800ws.xmlservices.GetEnhancedCDRResponseDocument$Factory.par
se(GetEnhancedCDRResponseDocument.java:165)
 at
leadpoint.voice.service.paetec.callrecords.client.ServiceStub.fromOM(Ser
viceStub.java:3226)
 ... 23 more
Caused by: com.ctc.wstx.exc.WstxParsingException: Illegal character
entity: expansion character (code 0x8) not a valid XML character
 at [row,col {unknown-source}]: [1,13020]
 at
com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:6
05)
 at
com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:461)
 at
com.ctc.wstx.sr.StreamScanner.reportIllegalChar(StreamScanner.java:2375)
 at
com.ctc.wstx.sr.StreamScanner.checkAndExpandChar(StreamScanner.java:2321
)
 at
com.ctc.wstx.sr.StreamScanner.resolveSimpleEntity(StreamScanner.java:118
0)
 at
com.ctc.wstx.sr.BasicStreamReader.readTextSecondary(BasicStreamReader.ja
va:4675)
 at
com.ctc.wstx.sr.BasicStreamReader.readCoalescedText(BasicStreamReader.ja
va:4124)
 at
com.ctc.wstx.sr.BasicStreamReader.finishToken(BasicStreamReader.java:369
9)
 at
com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java
:3647)
 ... 34 more

==============================

 

Thank you,

Oleg.






unsubscribe

Posted by Ian Kettle <ia...@fmit.co.nz>.
On Tue, 23 Feb 2010 09:50:10 Oleg Kozlov wrote:
> Hello,
> 
> I have an Axis2 1.5.1 (Java) client, auto-generated by wsdl2java with
> XmlBeans framework.
> 
> I'm integrating with a new vendor that has a SOAP web service written in
> .Net. The service is basically a wrapper around a legacy telephony
> switch. The service returns 1-9 binary numbers in its response in one of
> the XML elements. I have to point out that I our (client) side we do not
> even need to use that element at all, it just has some meaningless
> data... Apparently our vendor's other clients are all using .Net and the
> .Net framework does not care about inserting or parsing illegal
> characters in the SOAP Body ...
> 
> So, I'm getting an exception (see below).
> 
> I tried solving this problem by writing a custom Axis2 client module
> where I get access to the XML element that contains illegal characters
> and either set it's text value to blank string, or detach and get rid of
> the whole XML element altogether (since I don't need it). However, every
> time I iterate to the bad XML element - the parser blows up with the
> parsing error again inside my custom module. Also, due to the fact that
> Axis is using pull parsing method - there is no way to jump over the
> element with binary data, so I was not able to copy the entire XML DOM
> into a new DOM document skipping over the bad element.
> 
> I could not find a way to get low level access to XML stream where I
> could, for example, read from an input stream and write to an output
> stream, and skip over the illegal character.
> 
> Can anyone recommend another solution?
> 
> ==============================
> org.apache.axis2.AxisFault: [com.ctc.wstx.exc.WstxLazyException] Illegal
> character entity: expansion character (code 0x8) not a valid XML
> character
>  at [row,col {unknown-source}]: [1,13020]
>  at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
>  at
> leadpoint.voice.service.paetec.callrecords.client.ServiceStub.fromOM(Ser
> viceStub.java:3315)
>  at
> leadpoint.voice.service.paetec.callrecords.client.ServiceStub.getEnhance
> dCDR(ServiceStub.java:1063)
>  at
> leadpoint.voice.service.paetec.callrecords.client.ServiceTest.testgetEnh
> ancedCDR(ServiceTest.java:184)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> a:39)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> Impl.java:25)
>  at
> com.intellij.junit3.JUnit3IdeaTestRunner.doRun(JUnit3IdeaTestRunner.java
> 
> :108)
> 
>  at
> com.intellij.junit3.JUnit3IdeaTestRunner.startRunnerWithArgs(JUnit3IdeaT
> estRunner.java:42)
>  at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUni
> tStarter.java:165)
>  at
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:60)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> a:39)
>  at com.intellij.rt.execution.application.AppMain.main(AppMain.java:110)
> Caused by: [com.ctc.wstx.exc.WstxLazyException]
> com.ctc.wstx.exc.WstxParsingException: Illegal character entity:
> expansion character (code 0x8) not a valid XML character
>  at [row,col {unknown-source}]: [1,13020]
>  at
> com.ctc.wstx.exc.WstxLazyException.throwLazily(WstxLazyException.java:45
> )
>  at com.ctc.wstx.sr.StreamScanner.throwLazyError(StreamScanner.java:704)
>  at
> com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java
> 
> :3657)
> 
>  at
> com.ctc.wstx.sr.BasicStreamReader.getTextCharacters(BasicStreamReader.ja
> va:830)
>  at
> javax.xml.stream.util.StreamReaderDelegate.getTextCharacters(StreamReade
> rDelegate.java:158)
>  at
> org.apache.axiom.om.impl.builder.SafeXMLStreamReader.getTextCharacters(S
> afeXMLStreamReader.java:113)
>  at
> org.apache.axiom.om.impl.llom.OMStAXWrapper.getTextCharacters(OMStAXWrap
> per.java:418)
>  at
> org.apache.axiom.om.util.OMXMLStreamReaderValidator.getTextCharacters(OM
> XMLStreamReaderValidator.java:239)
>  at
> org.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader(Locale.java:11
> 54)
>  at
> org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:843)
>  at
> org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826)
>  at
> org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoa
> derBase.java:231)
>  at
> com.paetec.e800ws.xmlservices.GetEnhancedCDRResponseDocument$Factory.par
> se(GetEnhancedCDRResponseDocument.java:165)
>  at
> leadpoint.voice.service.paetec.callrecords.client.ServiceStub.fromOM(Ser
> viceStub.java:3226)
>  ... 23 more
> Caused by: com.ctc.wstx.exc.WstxParsingException: Illegal character
> entity: expansion character (code 0x8) not a valid XML character
>  at [row,col {unknown-source}]: [1,13020]
>  at
> com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:6
> 05)
>  at
> com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:461)
>  at
> com.ctc.wstx.sr.StreamScanner.reportIllegalChar(StreamScanner.java:2375)
>  at
> com.ctc.wstx.sr.StreamScanner.checkAndExpandChar(StreamScanner.java:2321
> )
>  at
> com.ctc.wstx.sr.StreamScanner.resolveSimpleEntity(StreamScanner.java:118
> 0)
>  at
> com.ctc.wstx.sr.BasicStreamReader.readTextSecondary(BasicStreamReader.ja
> va:4675)
>  at
> com.ctc.wstx.sr.BasicStreamReader.readCoalescedText(BasicStreamReader.ja
> va:4124)
>  at
> com.ctc.wstx.sr.BasicStreamReader.finishToken(BasicStreamReader.java:369
> 9)
>  at
> com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java
> 
> :3647)
> 
>  ... 34 more
> ==============================
> 
> Thank you,
> Oleg.
> 

-- 
Ian Kettle - Software Engineer 
Mobile: +64 21 406 461  
Email: ian.kettle@fmit.co.nz | Web: www.fmit.co.nz 
Level 6, 92 Albert Street, Auckland, NZ



Re: unsubscribe

Posted by Rafael Barrera Oro <bo...@gmail.com>.
It as disturbing as it is annoying...

2010/2/23 Henrique Ordine <ho...@gmail.com>

> Why are so many people unsubscribing at the same time?
>
> On 23 February 2010 16:32, giris <sr...@yahoo.com> wrote:
>
>> This is the age of automation, and some people just don't get that fact
>> nor understand netiquette. Could the system filter out messages containing
>> the word 'Unsubscribe' in the subject line, and simply not blast it out to
>> all? Once it can do that, a further improvement could be for it to change
>> the destination email address  for everyone who wants to unsubscribe. Does
>> anyone have time for such stuff?
>>
>>
>> --- On *Tue, 2/23/10, Jipu Jiang <j....@nesc.gla.ac.uk>* wrote:
>>
>>
>> From: Jipu Jiang <j....@nesc.gla.ac.uk>
>> Subject: unsubscribe
>> To: java-user@axis.apache.org
>> Date: Tuesday, February 23, 2010, 4:15 AM
>>
>>
>>
>>
>
>
> --
> Henrique Ordine
>



Re: AW: unsubscribe

Posted by Glen Daniels <gl...@thoughtcraft.com>.
Unfortunately for all of us, it seems there actually are that many "dorks" on
this list. :S

Sigh.

Someone yesterday likely had it right - people probably had the old list
filtered to a mailbox, and forgot they were on it.  Once the list name
changes happened due to the new Top Level Project, they started receiving
these mails in their inboxes again.

Hopefully this will all calm down soon and we'll be left with a more focused
and functional community in any case. :)

Thanks,
--G

On 2/24/2010 4:58 AM, Amiri Arash OSF sIT wrote:
> 
> could it be that java-user-unsubscribe@axis.apache.org is forwarding emails to this list? 
> 
> i cant believe that there are so many "dorks" on this list...
> 
> -----Ursprüngliche Nachricht-----
> Von: Henrique Ordine [mailto:hordine@gmail.com] 
> Gesendet: Dienstag, 23. Februar 2010 21:29
> An: java-user@axis.apache.org
> Betreff: Re: unsubscribe [phishing][html-removed]
> Wichtigkeit: Niedrig
> 
> I'm really curious. I feel like I've missed something.
> 
> On 23 February 2010 17:08, David Hesson <dh...@rjlg.com> wrote:
> 
>> Is this a serious question?  Because if it is, it's the funniest email i've
>> seen come across this mailing list.
>>
>> ________________________________
>>
>> From: Henrique Ordine [mailto:hordine@gmail.com]
>> Sent: Tue 2/23/2010 2:36 PM
>> To: java-user@axis.apache.org
>> Subject: Re: unsubscribe
>>
>>
>> Why are so many people unsubscribing at the same time?
>>
>>
>> On 23 February 2010 16:32, giris <sr...@yahoo.com> wrote:
>>
>>
>> This is the age of automation, and some people just don't get that fact nor
>> understand netiquette. Could the system filter out messages containing the
>> word 'Unsubscribe' in the subject line, and simply not blast it out to all?
>> Once it can do that, a further improvement could be for it to change the
>> destination email address  for everyone who wants to unsubscribe. Does
>> anyone have time for such stuff?
>>
>>
>> --- On Tue, 2/23/10, Jipu Jiang <j....@nesc.gla.ac.uk> wrote:
>>
>>
>>
>>        From: Jipu Jiang <j....@nesc.gla.ac.uk>
>>        Subject: unsubscribe
>>        To: java-user@axis.apache.org
>>        Date: Tuesday, February 23, 2010, 4:15 AM
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> Henrique Ordine
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-user-help@axis.apache.org
>>
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org




Re: AW: unsubscribe

Posted by Mauro Molinari <ma...@cardinis.com>.
Il 24/02/2010 14.45, Tony Thompson ha scritto:
> I unsubscribed properly as a test and I didn't see my email come through
> the list (but I was the one unsubscribing).

The problem is that people are *not* unsubscribing properly: they simply 
think that it is sufficient to reply with "unsubribe" in the subject... 
they even don't care to look at the footer of any e-mail sent to the 
mailing list...

-- 
Mauro Molinari
Software Designer & Developer
E-mail: mauro.molinari@cardinis.com

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org




AW: unsubscribe

Posted by Amiri Arash OSF sIT <Ar...@s-itsolutions.at>.
could it be that java-user-unsubscribe@axis.apache.org is forwarding emails to this list? 

i cant believe that there are so many "dorks" on this list...

-----Ursprüngliche Nachricht-----
Von: Henrique Ordine [mailto:hordine@gmail.com] 
Gesendet: Dienstag, 23. Februar 2010 21:29
An: java-user@axis.apache.org
Betreff: Re: unsubscribe [phishing][html-removed]
Wichtigkeit: Niedrig

I'm really curious. I feel like I've missed something.

On 23 February 2010 17:08, David Hesson <dh...@rjlg.com> wrote:

> Is this a serious question?  Because if it is, it's the funniest email i've
> seen come across this mailing list.
>
> ________________________________
>
> From: Henrique Ordine [mailto:hordine@gmail.com]
> Sent: Tue 2/23/2010 2:36 PM
> To: java-user@axis.apache.org
> Subject: Re: unsubscribe
>
>
> Why are so many people unsubscribing at the same time?
>
>
> On 23 February 2010 16:32, giris <sr...@yahoo.com> wrote:
>
>
> This is the age of automation, and some people just don't get that fact nor
> understand netiquette. Could the system filter out messages containing the
> word 'Unsubscribe' in the subject line, and simply not blast it out to all?
> Once it can do that, a further improvement could be for it to change the
> destination email address  for everyone who wants to unsubscribe. Does
> anyone have time for such stuff?
>
>
> --- On Tue, 2/23/10, Jipu Jiang <j....@nesc.gla.ac.uk> wrote:
>
>
>
>        From: Jipu Jiang <j....@nesc.gla.ac.uk>
>        Subject: unsubscribe
>        To: java-user@axis.apache.org
>        Date: Tuesday, February 23, 2010, 4:15 AM
>
>
>
>
>
>
>
>
> --
> Henrique Ordine
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>



-- 
Henrique Ordine

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org




Re: unsubscribe

Posted by Henrique Ordine <ho...@gmail.com>.
I'm really curious. I feel like I've missed something.

On 23 February 2010 17:08, David Hesson <dh...@rjlg.com> wrote:

> Is this a serious question?  Because if it is, it's the funniest email i've
> seen come across this mailing list.
>
> ________________________________
>
> From: Henrique Ordine [mailto:hordine@gmail.com]
> Sent: Tue 2/23/2010 2:36 PM
> To: java-user@axis.apache.org
> Subject: Re: unsubscribe
>
>
> Why are so many people unsubscribing at the same time?
>
>
> On 23 February 2010 16:32, giris <sr...@yahoo.com> wrote:
>
>
> This is the age of automation, and some people just don't get that fact nor
> understand netiquette. Could the system filter out messages containing the
> word 'Unsubscribe' in the subject line, and simply not blast it out to all?
> Once it can do that, a further improvement could be for it to change the
> destination email address  for everyone who wants to unsubscribe. Does
> anyone have time for such stuff?
>
>
> --- On Tue, 2/23/10, Jipu Jiang <j....@nesc.gla.ac.uk> wrote:
>
>
>
>        From: Jipu Jiang <j....@nesc.gla.ac.uk>
>        Subject: unsubscribe
>        To: java-user@axis.apache.org
>        Date: Tuesday, February 23, 2010, 4:15 AM
>
>
>
>
>
>
>
>
> --
> Henrique Ordine
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>



-- 
Henrique Ordine



RE: unsubscribe

Posted by Jonathan Roberts <jr...@rjlg.com>.
It's probably because they just changed the from address on the mails
and broke everyone's filters.  Why was the email address changed anyway?

 

________________________________

From: David Hesson [mailto:dhesson@rjlg.com] 
Sent: Tuesday, February 23, 2010 3:09 PM
To: java-user@axis.apache.org
Subject: RE: unsubscribe

 

Is this a serious question?  Because if it is, it's the funniest email
i've seen come across this mailing list.  

 

________________________________

From: Henrique Ordine [mailto:hordine@gmail.com]
Sent: Tue 2/23/2010 2:36 PM
To: java-user@axis.apache.org
Subject: Re: unsubscribe

Why are so many people unsubscribing at the same time?

On 23 February 2010 16:32, giris <sr...@yahoo.com> wrote:

This is the age of automation, and some people just don't get that fact
nor understand netiquette. Could the system filter out messages
containing the word 'Unsubscribe' in the subject line, and simply not
blast it out to all? Once it can do that, a further improvement could be
for it to change the destination email address  for everyone who wants
to unsubscribe. Does anyone have time for such stuff?


--- On Tue, 2/23/10, Jipu Jiang <j....@nesc.gla.ac.uk> wrote:


From: Jipu Jiang <j....@nesc.gla.ac.uk>
Subject: unsubscribe
To: java-user@axis.apache.org
Date: Tuesday, February 23, 2010, 4:15 AM

 

 




-- 
Henrique Ordine




RE: unsubscribe

Posted by David Hesson <dh...@rjlg.com>.
Is this a serious question?  Because if it is, it's the funniest email i've seen come across this mailing list.  

________________________________

From: Henrique Ordine [mailto:hordine@gmail.com]
Sent: Tue 2/23/2010 2:36 PM
To: java-user@axis.apache.org
Subject: Re: unsubscribe


Why are so many people unsubscribing at the same time?


On 23 February 2010 16:32, giris <sr...@yahoo.com> wrote:


This is the age of automation, and some people just don't get that fact nor understand netiquette. Could the system filter out messages containing the word 'Unsubscribe' in the subject line, and simply not blast it out to all? Once it can do that, a further improvement could be for it to change the destination email address  for everyone who wants to unsubscribe. Does anyone have time for such stuff?


--- On Tue, 2/23/10, Jipu Jiang <j....@nesc.gla.ac.uk> wrote:



	From: Jipu Jiang <j....@nesc.gla.ac.uk>
	Subject: unsubscribe
	To: java-user@axis.apache.org
	Date: Tuesday, February 23, 2010, 4:15 AM
	
	






-- 
Henrique Ordine




Re: unsubscribe

Posted by Henrique Ordine <ho...@gmail.com>.
Why are so many people unsubscribing at the same time?

On 23 February 2010 16:32, giris <sr...@yahoo.com> wrote:

> This is the age of automation, and some people just don't get that fact nor
> understand netiquette. Could the system filter out messages containing the
> word 'Unsubscribe' in the subject line, and simply not blast it out to all?
> Once it can do that, a further improvement could be for it to change the
> destination email address  for everyone who wants to unsubscribe. Does
> anyone have time for such stuff?
>
>
> --- On *Tue, 2/23/10, Jipu Jiang <j....@nesc.gla.ac.uk>* wrote:
>
>
> From: Jipu Jiang <j....@nesc.gla.ac.uk>
> Subject: unsubscribe
> To: java-user@axis.apache.org
> Date: Tuesday, February 23, 2010, 4:15 AM
>
>
>
>


-- 
Henrique Ordine



Re: unsubscribe

Posted by Andreas Fritzler <an...@googlemail.com>.
LOL

On Tue, Feb 23, 2010 at 20:25, Mallik Soupati <ma...@gmail.com> wrote:

> unsubscribe
>
>
> On Wed, Feb 24, 2010 at 1:02 AM, giris <sr...@yahoo.com> wrote:
>
>> This is the age of automation, and some people just don't get that fact
>> nor understand netiquette. Could the system filter out messages containing
>> the word 'Unsubscribe' in the subject line, and simply not blast it out to
>> all? Once it can do that, a further improvement could be for it to change
>> the destination email address  for everyone who wants to unsubscribe. Does
>> anyone have time for such stuff?
>>
>>
>> --- On *Tue, 2/23/10, Jipu Jiang <j....@nesc.gla.ac.uk>* wrote:
>>
>>
>> From: Jipu Jiang <j....@nesc.gla.ac.uk>
>> Subject: unsubscribe
>> To: java-user@axis.apache.org
>> Date: Tuesday, February 23, 2010, 4:15 AM
>>
>>
>>
>>
>
>
> --
> How easy it is to mock the sun: The light by which it is caught is its own
> !
>



unsubscribe

Posted by Mallik Soupati <ma...@gmail.com>.
unsubscribe

On Wed, Feb 24, 2010 at 1:02 AM, giris <sr...@yahoo.com> wrote:

> This is the age of automation, and some people just don't get that fact nor
> understand netiquette. Could the system filter out messages containing the
> word 'Unsubscribe' in the subject line, and simply not blast it out to all?
> Once it can do that, a further improvement could be for it to change the
> destination email address  for everyone who wants to unsubscribe. Does
> anyone have time for such stuff?
>
>
> --- On *Tue, 2/23/10, Jipu Jiang <j....@nesc.gla.ac.uk>* wrote:
>
>
> From: Jipu Jiang <j....@nesc.gla.ac.uk>
> Subject: unsubscribe
> To: java-user@axis.apache.org
> Date: Tuesday, February 23, 2010, 4:15 AM
>
>
>
>


-- 
How easy it is to mock the sun: The light by which it is caught is its own !



Re: unsubscribe

Posted by giris <sr...@yahoo.com>.
This is the age of automation, and some people just don't get that fact nor understand netiquette. Could the system filter out messages containing the word 'Unsubscribe' in the subject line, and simply not blast it out to all? Once it can do that, a further improvement could be for it to change the destination email address  for everyone who wants to unsubscribe. Does anyone have time for such stuff?


--- On Tue, 2/23/10, Jipu Jiang <j....@nesc.gla.ac.uk> wrote:

From: Jipu Jiang <j....@nesc.gla.ac.uk>
Subject: unsubscribe
To: java-user@axis.apache.org
Date: Tuesday, February 23, 2010, 4:15 AM





      


unsubscribe 

Posted by Jipu Jiang <j....@nesc.gla.ac.uk>.


Re: illegal XML character 0x8 from a .Net SOAP service :(

Posted by Andreas Veithen <an...@gmail.com>.
Two comments here:

* The assertion that "Axis2 and Java World understands by default only
UTF-8 encoded character sets" is not correct. XML is based on the
Unicode character _set_ (and that has nothing to do with Axis2/Java).
Any XML parser is required to support at least UTF-8 and UTF-16 as
character _encodings_, but in addition Woodstox (the parser used by
Axis2) supports at least those encodings recognized by Java [1].

* Characters with code points in the range 0-31, except for 9, 10 and
13 are forbidden in XML, regardless of the character encoding. If .NET
doesn't enforce this restriction, then that is Microsoft's decision.
That being said, there may be an option in the Woodstox parser to
disable invalid character checks. Please consult the Woodstox
documentation.

Andreas

[1] http://java.sun.com/j2se/1.5.0/docs/guide/intl/encoding.doc.html

On Tue, Feb 23, 2010 at 09:24, Stadelmann Josef
<jo...@axa-winterthur.ch> wrote:
> Hi,
>
>
>
> I have a .NET WCF Client and Apache Axis2 Web Service. My client makes a
> custom binding enforcing HTTP Transport and UTF-8 encoding, this because
> Axis2 and Java World understands by default only UTF-8 encoded character
> sets. And well, recently I have run into a problem, that my VB/C# .NET WCF
> client has to send words (all in a SOAP/XML structure) to the server
> consisting of German Umlauts ‘ä’ ‘ö’ ‘ü’, which resulted in a crash
> somewhere in a web service routine. But again: my custom binding said truly
> to use UTF-8. Now I ask you: why does it sent a bad non UTF-8, a bad 8 bit
> character to the wire that my service crashes. Simple answer: because this
> custom binding with UTF-8 encoding forced does not work at all as it should.
> Also – I can prove it – because I have special behavior implemented as
> INTERCEPTORS for each outgoing and incoming message, client and server side.
> I reported it to Microsoft in one of this WCF Web Service .Net forums.
> Unfortunately nothing but warm air comes back. Then I decided to help
> myself. As I was unable to look deep into the code doing wrong (deep in some
> .NET assemblies), I wrote a routine to substitute all .NET characters to a
> UTF-8 encoding before I send the request to the stub. Since – my problem is
> gone. And off course – at my legacy server I have to turn UTF-8 double byte
> encoded chars like German Umlauts into DEC MULTINATIONAL CHARACTER SET a 8
> bit char set on input to legacy server as well before transfer back via
> AXIS2 to the wire. But that was already done before and for that I used some
> LIBXML routines IsoLatin2UTF8() and UTF82IsoLatin() written in ANSI C. Maybe
> if you enforce your .NET chars belonging to ISO Latin you can use this two
> routines too. The interesting thing is, that with my current binding, all
> UTF-8 encoded characters arriving as response from the AXIS2 Server are
> perfectly converted into what .NET WCF client and the VB.NET client needs to
> display them correct. So the problem I was faced with is on sending to the
> server.
>
>
>
> Maybe this helps you a bit.
>
> Josef.Stadelmann
>
> @axa-winterthur.ch
>
>
>
>
>
> Von: Oleg Kozlov [mailto:oleg.kozlov@leadpoint.com]
> Gesendet: Montag, 22. Februar 2010 21:50
> An: java-user@axis.apache.org
> Betreff: illegal XML character 0x8 from a .Net SOAP service :(
>
>
>
> Hello,
>
>
>
> I have an Axis2 1.5.1 (Java) client, auto-generated by wsdl2java with
> XmlBeans framework.
>
>
>
> I'm integrating with a new vendor that has a SOAP web service written in
> .Net. The service is basically a wrapper around a legacy telephony switch.
> The service returns 1-9 binary numbers in its response in one of the XML
> elements. I have to point out that I our (client) side we do not even need
> to use that element at all, it just has some meaningless data... Apparently
> our vendor's other clients are all using .Net and the .Net framework does
> not care about inserting or parsing illegal characters in the SOAP Body ...
>
>
>
> So, I'm getting an exception (see below).
>
>
>
> I tried solving this problem by writing a custom Axis2 client module where I
> get access to the XML element that contains illegal characters and either
> set it's text value to blank string, or detach and get rid of the whole XML
> element altogether (since I don't need it). However, every time I iterate to
> the bad XML element - the parser blows up with the parsing error again
> inside my custom module. Also, due to the fact that Axis is using pull
> parsing method - there is no way to jump over the element with binary data,
> so I was not able to copy the entire XML DOM into a new DOM document
> skipping over the bad element.
>
>
>
> I could not find a way to get low level access to XML stream where I could,
> for example, read from an input stream and write to an output stream, and
> skip over the illegal character.
>
>
>
> Can anyone recommend another solution?
>
>
>
> ==============================
>
> org.apache.axis2.AxisFault: [com.ctc.wstx.exc.WstxLazyException] Illegal
> character entity: expansion character (code 0x8) not a valid XML character
>  at [row,col {unknown-source}]: [1,13020]
>  at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
>  at
> leadpoint.voice.service.paetec.callrecords.client.ServiceStub.fromOM(ServiceStub.java:3315)
>  at
> leadpoint.voice.service.paetec.callrecords.client.ServiceStub.getEnhancedCDR(ServiceStub.java:1063)
>  at
> leadpoint.voice.service.paetec.callrecords.client.ServiceTest.testgetEnhancedCDR(ServiceTest.java:184)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>  at
> com.intellij.junit3.JUnit3IdeaTestRunner.doRun(JUnit3IdeaTestRunner.java:108)
>  at
> com.intellij.junit3.JUnit3IdeaTestRunner.startRunnerWithArgs(JUnit3IdeaTestRunner.java:42)
>  at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:165)
>  at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:60)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>  at com.intellij.rt.execution.application.AppMain.main(AppMain.java:110)
> Caused by: [com.ctc.wstx.exc.WstxLazyException]
> com.ctc.wstx.exc.WstxParsingException: Illegal character entity: expansion
> character (code 0x8) not a valid XML character
>  at [row,col {unknown-source}]: [1,13020]
>  at
> com.ctc.wstx.exc.WstxLazyException.throwLazily(WstxLazyException.java:45)
>  at com.ctc.wstx.sr.StreamScanner.throwLazyError(StreamScanner.java:704)
>  at
> com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java:3657)
>  at
> com.ctc.wstx.sr.BasicStreamReader.getTextCharacters(BasicStreamReader.java:830)
>  at
> javax.xml.stream.util.StreamReaderDelegate.getTextCharacters(StreamReaderDelegate.java:158)
>  at
> org.apache.axiom.om.impl.builder.SafeXMLStreamReader.getTextCharacters(SafeXMLStreamReader.java:113)
>  at
> org.apache.axiom.om.impl.llom.OMStAXWrapper.getTextCharacters(OMStAXWrapper.java:418)
>  at
> org.apache.axiom.om.util.OMXMLStreamReaderValidator.getTextCharacters(OMXMLStreamReaderValidator.java:239)
>  at
> org.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader(Locale.java:1154)
>  at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:843)
>  at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826)
>  at
> org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231)
>  at
> com.paetec.e800ws.xmlservices.GetEnhancedCDRResponseDocument$Factory.parse(GetEnhancedCDRResponseDocument.java:165)
>  at
> leadpoint.voice.service.paetec.callrecords.client.ServiceStub.fromOM(ServiceStub.java:3226)
>  ... 23 more
> Caused by: com.ctc.wstx.exc.WstxParsingException: Illegal character entity:
> expansion character (code 0x8) not a valid XML character
>  at [row,col {unknown-source}]: [1,13020]
>  at
> com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:605)
>  at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:461)
>  at com.ctc.wstx.sr.StreamScanner.reportIllegalChar(StreamScanner.java:2375)
>  at
> com.ctc.wstx.sr.StreamScanner.checkAndExpandChar(StreamScanner.java:2321)
>  at
> com.ctc.wstx.sr.StreamScanner.resolveSimpleEntity(StreamScanner.java:1180)
>  at
> com.ctc.wstx.sr.BasicStreamReader.readTextSecondary(BasicStreamReader.java:4675)
>  at
> com.ctc.wstx.sr.BasicStreamReader.readCoalescedText(BasicStreamReader.java:4124)
>  at
> com.ctc.wstx.sr.BasicStreamReader.finishToken(BasicStreamReader.java:3699)
>  at
> com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java:3647)
>  ... 34 more
>
> ==============================
>
>
>
> Thank you,
>
> Oleg.



AW: illegal XML character 0x8 from a .Net SOAP service :(

Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Hi,

 

I have a .NET WCF Client and Apache Axis2 Web Service. My client makes a custom binding enforcing HTTP Transport and UTF-8 encoding, this because Axis2 and Java World understands by default only UTF-8 encoded character sets. And well, recently I have run into a problem, that my VB/C# .NET WCF client has to send words (all in a SOAP/XML structure) to the server consisting of German Umlauts 'ä' 'ö' 'ü', which resulted in a crash somewhere in a web service routine. But again: my custom binding said truly to use UTF-8. Now I ask you: why does it sent a bad non UTF-8, a bad 8 bit character to the wire that my service crashes. Simple answer: because this custom binding with UTF-8 encoding forced does not work at all as it should. Also - I can prove it - because I have special behavior implemented as INTERCEPTORS for each outgoing and incoming message, client and server side. I reported it to Microsoft in one of this WCF Web Service .Net forums. Unfortunately nothing but warm air comes back. Then I decided to help myself. As I was unable to look deep into the code doing wrong (deep in some .NET assemblies), I wrote a routine to substitute all .NET characters to a UTF-8 encoding before I send the request to the stub. Since - my problem is gone. And off course - at my legacy server I have to turn UTF-8 double byte encoded chars like German Umlauts into DEC MULTINATIONAL CHARACTER SET a 8 bit char set on input to legacy server as well before transfer back via AXIS2 to the wire. But that was already done before and for that I used some LIBXML routines IsoLatin2UTF8() and UTF82IsoLatin() written in ANSI C. Maybe if you enforce your .NET chars belonging to ISO Latin you can use this two routines too. The interesting thing is, that with my current binding, all UTF-8 encoded characters arriving as response from the AXIS2 Server are perfectly converted into what .NET WCF client and the VB.NET client needs to display them correct. So the problem I was faced with is on sending to the server.

 

Maybe this helps you a bit.

Josef.Stadelmann

@axa-winterthur.ch

 

 

Von: Oleg Kozlov [mailto:oleg.kozlov@leadpoint.com] 
Gesendet: Montag, 22. Februar 2010 21:50
An: java-user@axis.apache.org
Betreff: illegal XML character 0x8 from a .Net SOAP service :(

 

Hello,

 

I have an Axis2 1.5.1 (Java) client, auto-generated by wsdl2java with XmlBeans framework.

 

I'm integrating with a new vendor that has a SOAP web service written in .Net. The service is basically a wrapper around a legacy telephony switch. The service returns 1-9 binary numbers in its response in one of the XML elements. I have to point out that I our (client) side we do not even need to use that element at all, it just has some meaningless data... Apparently our vendor's other clients are all using .Net and the .Net framework does not care about inserting or parsing illegal characters in the SOAP Body ...

 

So, I'm getting an exception (see below).

 

I tried solving this problem by writing a custom Axis2 client module where I get access to the XML element that contains illegal characters and either set it's text value to blank string, or detach and get rid of the whole XML element altogether (since I don't need it). However, every time I iterate to the bad XML element - the parser blows up with the parsing error again inside my custom module. Also, due to the fact that Axis is using pull parsing method - there is no way to jump over the element with binary data, so I was not able to copy the entire XML DOM into a new DOM document skipping over the bad element.

 

I could not find a way to get low level access to XML stream where I could, for example, read from an input stream and write to an output stream, and skip over the illegal character.

 

Can anyone recommend another solution?

 

==============================

org.apache.axis2.AxisFault: [com.ctc.wstx.exc.WstxLazyException] Illegal character entity: expansion character (code 0x8) not a valid XML character
 at [row,col {unknown-source}]: [1,13020]
 at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
 at leadpoint.voice.service.paetec.callrecords.client.ServiceStub.fromOM(ServiceStub.java:3315)
 at leadpoint.voice.service.paetec.callrecords.client.ServiceStub.getEnhancedCDR(ServiceStub.java:1063)
 at leadpoint.voice.service.paetec.callrecords.client.ServiceTest.testgetEnhancedCDR(ServiceTest.java:184)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at com.intellij.junit3.JUnit3IdeaTestRunner.doRun(JUnit3IdeaTestRunner.java:108)
 at com.intellij.junit3.JUnit3IdeaTestRunner.startRunnerWithArgs(JUnit3IdeaTestRunner.java:42)
 at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:165)
 at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:60)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at com.intellij.rt.execution.application.AppMain.main(AppMain.java:110)
Caused by: [com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxParsingException: Illegal character entity: expansion character (code 0x8) not a valid XML character
 at [row,col {unknown-source}]: [1,13020]
 at com.ctc.wstx.exc.WstxLazyException.throwLazily(WstxLazyException.java:45)
 at com.ctc.wstx.sr.StreamScanner.throwLazyError(StreamScanner.java:704)
 at com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java:3657)
 at com.ctc.wstx.sr.BasicStreamReader.getTextCharacters(BasicStreamReader.java:830)
 at javax.xml.stream.util.StreamReaderDelegate.getTextCharacters(StreamReaderDelegate.java:158)
 at org.apache.axiom.om.impl.builder.SafeXMLStreamReader.getTextCharacters(SafeXMLStreamReader.java:113)
 at org.apache.axiom.om.impl.llom.OMStAXWrapper.getTextCharacters(OMStAXWrapper.java:418)
 at org.apache.axiom.om.util.OMXMLStreamReaderValidator.getTextCharacters(OMXMLStreamReaderValidator.java:239)
 at org.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader(Locale.java:1154)
 at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:843)
 at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826)
 at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231)
 at com.paetec.e800ws.xmlservices.GetEnhancedCDRResponseDocument$Factory.parse(GetEnhancedCDRResponseDocument.java:165)
 at leadpoint.voice.service.paetec.callrecords.client.ServiceStub.fromOM(ServiceStub.java:3226)
 ... 23 more
Caused by: com.ctc.wstx.exc.WstxParsingException: Illegal character entity: expansion character (code 0x8) not a valid XML character
 at [row,col {unknown-source}]: [1,13020]
 at com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:605)
 at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:461)
 at com.ctc.wstx.sr.StreamScanner.reportIllegalChar(StreamScanner.java:2375)
 at com.ctc.wstx.sr.StreamScanner.checkAndExpandChar(StreamScanner.java:2321)
 at com.ctc.wstx.sr.StreamScanner.resolveSimpleEntity(StreamScanner.java:1180)
 at com.ctc.wstx.sr.BasicStreamReader.readTextSecondary(BasicStreamReader.java:4675)
 at com.ctc.wstx.sr.BasicStreamReader.readCoalescedText(BasicStreamReader.java:4124)
 at com.ctc.wstx.sr.BasicStreamReader.finishToken(BasicStreamReader.java:3699)
 at com.ctc.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java:3647)
 ... 34 more

==============================

 

Thank you,

Oleg.