javax.xml.stream.XMLStreamException: Underlying stream encoding problem

While examining apache axiom to basically create an XML document, a weird exception is raised from serialize method. Serializing to System.out streams is problem-free; on the other hand, serializing to xml file is not. Since, the project's "text file encoding" is Cp1254 and it conflicts with the defined character encoding defined in OMDocument. Change it as i did it in screenshot at bottom of this post.

Let me explain what below code is about. It creates and an instance of OMFactory to create other OM supported XML parts: elements, attributes, namespaces and document to build an XML file programmatically with AXIOM. Then, set some xml metadata attributes and serialize it to System.out and output.xml file.  


javax.xml.stream.XMLStreamException: Underlying stream encoding 'Cp1254' and input paramter for writeStartDocument() method 'UTF-8' do not match.
 at com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.writeStartDocument(Unknown Source)
 at org.apache.axiom.util.stax.wrapper.XMLStreamWriterWrapper.writeStartDocument(XMLStreamWriterWrapper.java:157)
 at org.apache.axiom.util.stax.dialect.SJSXPStreamWriterWrapper.writeStartDocument(SJSXPStreamWriterWrapper.java:36)
 at org.apache.axiom.om.impl.llom.OMDocumentImplUtil.internalSerialize(OMDocumentImplUtil.java:56)
 at org.apache.axiom.om.impl.llom.OMDocumentImpl.internalSerialize(OMDocumentImpl.java:327)
 at org.apache.axiom.om.impl.llom.OMDocumentImpl.internalSerialize(OMDocumentImpl.java:322)
 at org.apache.axiom.om.impl.llom.OMSerializableImpl.serialize(OMSerializableImpl.java:120)
 at org.apache.axiom.om.impl.llom.OMSerializableImpl.serialize(OMSerializableImpl.java:108)
 at org.apache.axiom.om.impl.llom.OMSerializableImpl.serialize(OMSerializableImpl.java:136)
 at com.oguzhan.blog.axis2.axiom.AxiomProgrammatically2.main(AxiomProgrammatically2.java:48)


Change text file encoding from Project>Properties>Resource

Thank you for reading!
Location: Yıldız Mh., Sinan Paşa Mescidi Sk 16, 34330 Beşiktaş/İstanbul, Türkiye

Comments

Post a Comment

Thx for reading! Comments are appreciated...

Popular posts from this blog

SoapUI 4.5.0 Project XML File Encoding Problem

Image
I' ve been already using SoapUI Pro 3.6.1 since license expires. Previous migrations to soapUI newer versions had not caused problems but when starting using SoapUI 4.5.0(free) version resulted destroying existing projects. I checked log file ("C:\...\SmartBear\soapUI-4.5.0\bin\soapui.log") and realised that something went wrong about encoding of soapUI project XMLs. Turkish language characters in wsdl files are located in soapUI project XMLs and they are violating cp1254 character convention and causes below exception log.  java.io.CharConversionException: Malformed UTF-8 character: 0xc5 0x3f at org.apache.xmlbeans.impl.piccolo.xml.UTF8XMLDecoder.decode(UTF8XMLDecoder.java:80) at org.apache.xmlbeans.impl.piccolo.xml.XMLStreamReader$FastStreamDecoder.read(XMLStreamReader.java:762) at org.apache.xmlbeans.impl.piccolo.xml.XMLStreamReader.read(XMLStreamReader.java:162) at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.yy_refill(PiccoloLexer.java:3474) at org.apac
Read more

COMRESET failed (errno=-32)

Early in the morning, I hit this issue because of putting my nose into boot options. I changed the option form AHCI to RAID then restart but what I see flood of "COMRESET failed (errno=-32)" errors. I immediately restart and rollback my action but this doesnt prevent me from falling into desperate flow of error logs in /var/log/syslog. To solve problem, I make my talisman: used screwdriver to remove dvdrom. Because some ubuntu forum posts mentioning the reason is poor SATA cable connection. In my laptop there is no cable but there is  a socket to easily remove dvdrom. Anyway after removing, start the system and EUREKA the problem logs are gone! I checked mounted disks and validate reading and writing data is ok with some consequent restarts. Then of course I didnt leave the dvdrom empty. I shutdown the system and stick it into place roughly. And now everyone is allright. The lesson do not touch (mess up with) anything if it is working.  :) Aug 10 08:25:09 msi kernel:
Read more

SoapUI - Dynamic Properties - Getting Current Time in DateTime Format

Image
SoapUI satisfies the need of testing service oriented applications with test suites that depends on client scenarios. SoapUI enhances its test suite facility with Groovy scripts to create dynamic properties that helps functional testing. The example in soapUI website demonstrates how to retrieve current date in xsd:date format (yyyy-MM-dd). I am not very keen on Groovy but after a bit effort, i implemented this code snippet that returns the current date in xsd:dateTime format. I hope it helps... def dateTimeFormat = "yyyy-MM-dd'T'hh:mm:ss'Z'" def timeZone = TimeZone.getTimeZone("Etc/GMT") def dateTimeFormatter = new java.text.SimpleDateFormat(dateTimeFormat) dateTimeFormatter.setTimeZone(timeZone) return dateTimeFormatter.format(new java.util.Date()) SoapUI DataGen Test Suite Facility SoapUI is not only sending-receiving soap messages, great testing environment tools and Groovy script support makes it valueble.Do not commit any implementation
Read more