tag:old.nabble.com,2006:forum-12117Nabble - codehaus - woodstox2009-12-16T09:51:42ZWoodstox is a fast Open Source StAX-compliant XML-processor written in Java. codehaus - woodstox home is <a href="http://woodstox.codehaus.org/" target="_top" rel="nofollow">here</a>.tag:old.nabble.com,2006:post-26815470Re: websphere 7 issues2009-12-16T09:51:42Z2009-12-16T09:51:42ZCowtowncoderOn Wed, Dec 16, 2009 at 6:23 AM, <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26815470&i=0" target="_top" rel="nofollow">simbo1905@...</a>> wrote:
<br>>
<br>> Hi,
<br>>
<br>> I am using jibx1.1.6a which has a dependency on wstx-asl 3.2.1. Things
<br>> work fine on Websphere6.1, jetty6.1.0 and tomcat6. When I move the
<br>> webapp onto Websphere7.0.0.7 I get the following issue:
<br><br>Ok. One thing I would recommend would be to upgrade to 3.2.9, but that
<br>is probably not the cause of your specific problems (which seem to be
<br>due to IBM stax implementation).
<br><br>Common way to specify implementation to use is to use system
<br>properties; from
<br>[<a href="http://java.sun.com/javaee/5/docs/tutorial/doc/bnbem.html" target="_top" rel="nofollow">http://java.sun.com/javaee/5/docs/tutorial/doc/bnbem.html</a>]:
<br><br>"Use the javax.xml.stream.XMLInputFactory system property" (and
<br>similarly for XMLOutputFactory and XMLEventFactory), so something
<br>like:
<br><br>System.setProperty("javax.xml.stream.XMLInputFactory",
<br>"com.ctc.wstx.stax.WstxInputFactory");
<br><br>which should override defaults. Websphere may have a minor bug, too
<br>(or IBM stax impl), since usually the default implementation should
<br>NOT set service descriptor. Sun JDK works as expected, such that
<br>explicitly added jars will work without additional system properties.
<br><br>I hope this helps,
<br><br>-+ Tatu +-
<br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-26811839websphere 7 issues2009-12-16T06:23:50Z2009-12-16T06:23:50ZSimon-2745<br>Hi,
<br><br>I am using jibx1.1.6a which has a dependency on wstx-asl 3.2.1. Things
<br>work fine on Websphere6.1, jetty6.1.0 and tomcat6. When I move the
<br>webapp onto Websphere7.0.0.7 I get the following issue:
<br><br>Caused by: java.lang.IllegalStateException: The current state is not
<br>START_DOCUMENT.
<br> at
<br> com.ibm.xml.xlxp2.api.stax.msg.StAXMessageProvider.throwIllegalStateException(StAXMessageProvider.java:49)
<br> at
<br> com.ibm.xml.xlxp2.api.stax.XMLStreamReaderImpl.getEncoding(XMLStreamReaderImpl.java:1420)
<br> at
<br> com.ibm.xml.xlxp2.api.stax.XMLInputFactoryImpl$XMLStreamReaderProxyImpl.getEncoding(XMLInputFactoryImpl.java:402)
<br> at
<br> com.ibm.xml.xlxp2.api.wssec.WSSXMLInputFactory$WSSStreamReaderProxy.getEncoding(WSSXMLInputFactory.java:55)
<br> at
<br> org.jibx.runtime.impl.StAXReaderWrapper.startTag(StAXReaderWrapper.java:110)
<br> at
<br> org.jibx.runtime.impl.StAXReaderWrapper.next(StAXReaderWrapper.java:239)
<br> at
<br> org.jibx.runtime.impl.UnmarshallingContext.toStart(UnmarshallingContext.java:508)
<br> at
<br> org.jibx.runtime.impl.UnmarshallingContext.unmarshalElement(UnmarshallingContext.java:2530)
<br> at
<br> org.jibx.runtime.impl.UnmarshallingContext.unmarshalDocument(UnmarshallingContext.java:2694)
<br><br>I can repeat the error on Jetty if I run it on the IBM JDK1.6 and take
<br>woodstox off of the classpath to force it to fall back to the com.ibm
<br>stax parser. This suggests that I should just be able to set "parent
<br>last" on websphere to get it to pick up the woodstox stax classes not
<br>the ibm ones. I cannot seem to get this to work deploying a WAR file on
<br>WAS7 with the following classloader settings:
<br><br>Application Servers server1 Server-specific Application Settings:
<br> Classloader policy: Single
<br> Class loading mode: Classes loaded with local class loader first
<br> (parent last)
<br>Enterprise Applications myApp.war Class Loader
<br> Class loader order: Classes loaded with local class loader first
<br> (parent last)
<br> War class loader policy: Class loader for each WAR file in application
<br><br>Does anyone know how to force the loading of wookstox on Websphere7
<br>avoiding this issue?
<br><br>Jibx can be told to use a XMLPull type of parser instead of a stax
<br>parser with the system property org.jibx.runtime.impl.parser to the
<br>value org.jibx.runtime.impl.XMLPullReaderFactory but it would be nice to
<br>know how to force the use of woodstox.
<br><br>thanks,
<br><br>Simon
<br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-26500552Re: StaxMate: NPE when using Sun Stax Parser2009-11-24T09:55:11Z2009-11-24T09:55:11ZCowtowncoderOn Tue, Nov 24, 2009 at 7:11 AM, Johannes Schneider
<br><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26500552&i=0" target="_top" rel="nofollow">mailings@...</a>> wrote:
<br>> Hi,
<br>>
<br>> if I am using the default stax parser provided by java 6, I run into the
<br>> following NPE.
<br>> When using Woodstox, everything works as expected.
<br>>
<br>> Any ideas, hints?
<br><br>Which version? I think I did fix a problem like this for 1.3. At least
<br>I fixed some issues wrt. compatibility.
<br><br>Or, alternatively... hmmh. Maybe I supplied fix for Sjsxp (Sun parser)
<br>to address the underlying bug.
<br>If so, you could try downloading the latest sjsxp version.
<br><br>I can try digging up references to above, but it might be fastest to
<br>try out upgrading one or both. Sjsxp is tested and should work at any
<br>rate; both 1.3 and 2.0 (with Woodstox, you must use Woodstox-4.x for
<br>StaxMate-2.0; but regular sjsxp works ok with 2.0, as long as you get
<br>Stax2-api-3.0.1 jar)
<br><br>Hope this helps,
<br><br>-+ Tatu +-
<br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-26497587StaxMate: NPE when using Sun Stax Parser2009-11-24T07:11:32Z2009-11-24T07:11:32ZJohannes Schneider-5Hi,
<br><br>if I am using the default stax parser provided by java 6, I run into the
<br>following NPE.
<br>When using Woodstox, everything works as expected.
<br><br>Any ideas, hints?
<br><br><br>Thanks,
<br><br>Johannes
<br><br><br><br>java.lang.NullPointerException
<br> at
<br>com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.getProperty(XMLStreamWriterImpl.java:426)
<br> at
<br>org.codehaus.stax2.ri.Stax2WriterAdapter.<init>(Stax2WriterAdapter.java:77)
<br> at
<br>org.codehaus.stax2.ri.Stax2WriterAdapter.wrapIfNecessary(Stax2WriterAdapter.java:94)
<br> at
<br>org.codehaus.staxmate.SMOutputFactory.createStax2Writer(SMOutputFactory.java:316)
<br> at
<br>org.codehaus.staxmate.SMOutputFactory.createOutputDocument(SMOutputFactory.java:133)
<br> at
<br>com.cedarsoft.serialization.stax.AbstractStaxMateSerializer.serialize(AbstractStaxMateSerializer.java:28)
<br> at
<br>com.cedarsoft.serialization.AbstractSerializerTest.testSerializer(AbstractSerializerTest.java:28)
<br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-26185870Re: Checksum failure of wstx-asl-3.2.8.jar on maven central2009-11-03T12:15:19Z2009-11-03T12:15:19ZUlf LindbackOk, thanks for the promptly reply.<div>/Ulf</div><div><br><div class="gmail_quote">On Tue, Nov 3, 2009 at 19:40, Tatu Saloranta <span dir="ltr"><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26185870&i=0" target="_top" rel="nofollow">tsaloranta@...</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Tue, Nov 3, 2009 at 1:21 AM, Ulf Lindback <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26185870&i=1" target="_top" rel="nofollow">lindback@...</a>> wrote:<br>
> Hi!<br>
> When trying to download the wstx-asl-3.2.8.jar from maven central:<br>
> <a href="http://repo1.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar" target="_blank" rel="nofollow">http://repo1.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar</a><br>
> I get checksum errors (the md5 and sh1 files are the same as they are ath<br>
> <a href="http://repository.codehaus.org/org/codehaus/woodstox/wstx-asl/3.2.8" target="_blank" rel="nofollow">http://repository.codehaus.org/org/codehaus/woodstox/wstx-asl/3.2.8</a> so it<br>
> must<br>
> be the JAR that is corrupt at the central (size 523825 at central and size<br>
> 522787 at codehaus).<br>
<br>
</div>This could be because earlier Maven pushes were done manually (just uploading).<br>
In this case there must have been something wrong with the initial jar<br>
version, which was replaced, but not before broken version was<br>
propagated. Unfortunately Maven does not seem to be able to resolve<br>
such cases.<br>
<div class="im"><br>
> Is it possible to somehow push out a correct version to the central<br>
> repository?<br>
> (No I cannot use a newer version, since I use it indirectly through cxf<br>
> which depends on wstx-asl:jar:3.2.8 and I can download a correct version,<br>
> but we have<br>
> a local artifactory which cannot get it due to the invalid checksum)<br>
<br>
</div>Maven's artifact distribution system is problematic, since it seems<br>
that once a version has been propagated it is very difficult to<br>
replace it. :-/<br>
I do have access to Codehaus repository, but unfortunately not to<br>
central Maven repository. If anyone knows who might be able to help, I<br>
could contact that person to see if it was possible to delete current<br>
version and let fixed version be synced from Codehaus repository.<br>
<br>
Another possibility would be try to convince CXF folks either upgrade<br>
to 3.2.9 (patch versions are very safe in this direction), or make<br>
dependency less strict (using [3.2.0,3.3.0), or whatever notation is<br>
to basically allow 3.2.x).<br>
<br>
Apologies for the mess up -- current deployments should work better<br>
with Ant Maven tasks, so this should not recur. But that was not yet<br>
the case for 3.2.8.<br>
<br>
-+ Tatu +-<br>
<br>
---------------------------------------------------------------------<br>
To unsubscribe from this list, please visit:<br>
<br>
<a href="http://xircles.codehaus.org/manage_email" target="_blank" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br>
<br>
<br>
</blockquote></div><br></div>
<p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-26184461Re: Checksum failure of wstx-asl-3.2.8.jar on maven central2009-11-03T10:40:21Z2009-11-03T10:40:21ZCowtowncoderOn Tue, Nov 3, 2009 at 1:21 AM, Ulf Lindback <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26184461&i=0" target="_top" rel="nofollow">lindback@...</a>> wrote:
<br>> Hi!
<br>> When trying to download the wstx-asl-3.2.8.jar from maven central:
<br>> <a href="http://repo1.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar" target="_top" rel="nofollow">http://repo1.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar</a><br>> I get checksum errors (the md5 and sh1 files are the same as they are ath
<br>> <a href="http://repository.codehaus.org/org/codehaus/woodstox/wstx-asl/3.2.8" target="_top" rel="nofollow">http://repository.codehaus.org/org/codehaus/woodstox/wstx-asl/3.2.8</a> so it
<br>> must
<br>> be the JAR that is corrupt at the central (size 523825 at central and size
<br>> 522787 at codehaus).
<br><br>This could be because earlier Maven pushes were done manually (just uploading).
<br>In this case there must have been something wrong with the initial jar
<br>version, which was replaced, but not before broken version was
<br>propagated. Unfortunately Maven does not seem to be able to resolve
<br>such cases.
<br><br>> Is it possible to somehow push out a correct version to the central
<br>> repository?
<br>> (No I cannot use a newer version, since I use it indirectly through cxf
<br>> which depends on wstx-asl:jar:3.2.8 and I can download a correct version,
<br>> but we have
<br>> a local artifactory which cannot get it due to the invalid checksum)
<br><br>Maven's artifact distribution system is problematic, since it seems
<br>that once a version has been propagated it is very difficult to
<br>replace it. :-/
<br>I do have access to Codehaus repository, but unfortunately not to
<br>central Maven repository. If anyone knows who might be able to help, I
<br>could contact that person to see if it was possible to delete current
<br>version and let fixed version be synced from Codehaus repository.
<br><br>Another possibility would be try to convince CXF folks either upgrade
<br>to 3.2.9 (patch versions are very safe in this direction), or make
<br>dependency less strict (using [3.2.0,3.3.0), or whatever notation is
<br>to basically allow 3.2.x).
<br><br>Apologies for the mess up -- current deployments should work better
<br>with Ant Maven tasks, so this should not recur. But that was not yet
<br>the case for 3.2.8.
<br><br>-+ Tatu +-
<br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-26176975Checksum failure of wstx-asl-3.2.8.jar on maven central2009-11-03T01:21:32Z2009-11-03T01:21:32ZUlf LindbackHi!<br>When trying to download the wstx-asl-3.2.8.jar from maven central: <a href="http://repo1.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar" target="_top" rel="nofollow">http://repo1.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar</a> <br>
I get checksum errors (the md5 and sh1 files are the same as they are ath <a href="http://repository.codehaus.org/org/codehaus/woodstox/wstx-asl/3.2.8" target="_top" rel="nofollow">http://repository.codehaus.org/org/codehaus/woodstox/wstx-asl/3.2.8</a> so it must <br>
be the JAR that is corrupt at the central (size 523825 at central and size 522787 at codehaus).<br><br>Is it possible to somehow push out a correct version to the central repository?<br> (No I cannot use a newer version, since I use it indirectly through cxf which depends on wstx-asl:jar:3.2.8 and I can download a correct version, but we have<br>
a local artifactory which cannot get it due to the invalid checksum)<br><br>Regards<br>/Ulf Lindback<br><br><br>
<p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-26134105Re: XML Declaration2009-10-30T10:34:15Z2009-10-30T10:34:15ZJohannes Schneider-5As I have written I don't need this feature anymore for my unit tests. I
<br>have switched to XmlUnit (and I think this has been a good decision).
<br>And of course the produced xml is completely valid. This is just a minor
<br>case of "might-be-nice-to-be-configurable".
<br><br><br>Sincerly,
<br><br>Johannes
<br><br>Michael Kay wrote:
<div class='shrinkable-quote'><br>>> But on the other side I think the type of quotes should
<br>>> really be configurable.
<br>>
<br>> Well, as a data point, in the W3C serialization spec we have options to
<br>> control quite a few aspects of serialization, and there has never been any
<br>> demand to add this. Recipients of the document shouldn't care. If you want
<br>> XML that can be compared byte-by-byte, serialize the output and then
<br>> canonicalize.
<br>>
<br>> Regards,
<br>>
<br>> Michael Kay
<br>> <a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br>> <a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a>
<br>>
<br>>
<br>> ---------------------------------------------------------------------
<br>> To unsubscribe from this list, please visit:
<br>>
<br>> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br>>
<br>>
</div><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-26127171RE: XML Declaration2009-10-30T02:31:32Z2009-10-30T02:31:32ZMichael Kay> But on the other side I think the type of quotes should
<br>> really be configurable.
<br><br>Well, as a data point, in the W3C serialization spec we have options to
<br>control quite a few aspects of serialization, and there has never been any
<br>demand to add this. Recipients of the document shouldn't care. If you want
<br>XML that can be compared byte-by-byte, serialize the output and then
<br>canonicalize.
<br><br>Regards,
<br><br>Michael Kay
<br><a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br><a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a>
<br><br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-26126577Re: XML Declaration2009-10-30T01:35:20Z2009-10-30T01:35:20ZJohannes Schneider-5Hi,
<br><br>thanks for your fast replys. Of course you are right - I have to modify
<br>my tests (will switch to XmlUnit).
<br>But on the other side I think the type of quotes should really be
<br>configurable.
<br><br>Maybe one might discuss about the default settings (I know several XML
<br>tools and nearly everyone uses " as quote) but at least it should be
<br>configurable.
<br><br><br>Sincerly,
<br><br>Johannes
<br><br>Tatu Saloranta wrote:
<div class='shrinkable-quote'><br>> On Thu, Oct 29, 2009 at 10:37 AM, Johannes Schneider
<br>> <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26126577&i=0" target="_top" rel="nofollow">mailings@...</a>> wrote:
<br>>> Hi guys,
<br>>>
<br>>> at the moment I am thinking about switchting from JDOM to woodstox and
<br>>> staxmate:
<br>>> The first tests look very promising.
<br>>>
<br>>> But I have on small problem when writing the XML Declaration.
<br>>>
<br>>> JDom creates that line:
<br>>> <?xml version="1.0" encoding="UTF-8"?>
<br>>>
<br>>> but Woodstock creates:
<br>>> <?xml version='1.0' encoding='UTF-8'?>
<br>>>
<br>>> Since I have many, many unit tests that contain that line I'd like to
<br>>> reconfigure Woodstock to output the format I am used to.
<br>>> Is there anything I can do about?
<br>>>
<br>>> I debugged a bit and found that method:
<br>>> com.ctc.wstx.sw.BufferingXmlWriter#writeXmlDeclaration
<br>>>
<br>>> But that doesn't seem to be configurable....
<br>>
<br>> There is nothing in API to really configure this, and like Michael
<br>> pointed out, this (type of quotes) is not something that tests should
<br>> assume is one way or the other. Same applies to attribute value
<br>> quoting, and amount of white space. I have had to fix quite a few unit
<br>> tests myself (for projects I have worked on) not to count on specific
<br>> formatting that is not defined by xml specification.
<br>>
<br>> Still, if you absolutely do want to control this, your best bet is to
<br>> use method "writeRaw" on XMLStreamWriter2. All Woodstox
<br>> XMLStreamWriter implementations actually implement
<br>> org.codehaus.stax2.XMLStreamWriter2 (part of Stax2 extension API). It
<br>> will embed textual content as-is without any processing and can be
<br>> used to output what amounts to XML declaration. Also, you should not
<br>> call writeStartDocument (which would try to write declaration again).
<br>>
<br>> -+ Tatu +-
<br>>
<br>> ---------------------------------------------------------------------
<br>> To unsubscribe from this list, please visit:
<br>>
<br>> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br>>
<br>>
</div><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-26125698Re: XML Declaration2009-10-29T23:46:48Z2009-10-29T23:46:48ZCowtowncoderOn Thu, Oct 29, 2009 at 10:37 AM, Johannes Schneider
<br><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26125698&i=0" target="_top" rel="nofollow">mailings@...</a>> wrote:
<div class='shrinkable-quote'><br>> Hi guys,
<br>>
<br>> at the moment I am thinking about switchting from JDOM to woodstox and
<br>> staxmate:
<br>> The first tests look very promising.
<br>>
<br>> But I have on small problem when writing the XML Declaration.
<br>>
<br>> JDom creates that line:
<br>> <?xml version="1.0" encoding="UTF-8"?>
<br>>
<br>> but Woodstock creates:
<br>> <?xml version='1.0' encoding='UTF-8'?>
<br>>
<br>> Since I have many, many unit tests that contain that line I'd like to
<br>> reconfigure Woodstock to output the format I am used to.
<br>> Is there anything I can do about?
<br>>
<br>> I debugged a bit and found that method:
<br>> com.ctc.wstx.sw.BufferingXmlWriter#writeXmlDeclaration
<br>>
<br>> But that doesn't seem to be configurable....
</div><br>There is nothing in API to really configure this, and like Michael
<br>pointed out, this (type of quotes) is not something that tests should
<br>assume is one way or the other. Same applies to attribute value
<br>quoting, and amount of white space. I have had to fix quite a few unit
<br>tests myself (for projects I have worked on) not to count on specific
<br>formatting that is not defined by xml specification.
<br><br>Still, if you absolutely do want to control this, your best bet is to
<br>use method "writeRaw" on XMLStreamWriter2. All Woodstox
<br>XMLStreamWriter implementations actually implement
<br>org.codehaus.stax2.XMLStreamWriter2 (part of Stax2 extension API). It
<br>will embed textual content as-is without any processing and can be
<br>used to output what amounts to XML declaration. Also, you should not
<br>call writeStartDocument (which would try to write declaration again).
<br><br>-+ Tatu +-
<br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-26117769RE: XML Declaration2009-10-29T10:51:47Z2009-10-29T10:51:47ZMichael Kay>
<br>> Since I have many, many unit tests that contain that line I'd
<br>> like to reconfigure Woodstock to output the format I am used to.
<br>> Is there anything I can do about?
<br><br>Rewrite the unit tests. It's always a mistake to make tests depend on things
<br>that aren't essential to correct functioning. When you're testing XML, you
<br>should always canonicalize the XML before comparing with expected results:
<br>otherwise, as you have found, your tests lock you into technology choices
<br>and reduce the potential for change in the system.
<br><br>It's a problem, as it happens, which is faced by a project I'm helping with
<br>at the moment that has invested very heavily in creating a large battery of
<br>test material.
<br><br>Regards,
<br><br>Michael Kay
<br><a href="http://www.saxonica.com/" target="_top" rel="nofollow">http://www.saxonica.com/</a><br><a href="http://twitter.com/michaelhkay" target="_top" rel="nofollow">http://twitter.com/michaelhkay</a>
<br><br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-26117560XML Declaration2009-10-29T10:37:30Z2009-10-29T10:37:30ZJohannes Schneider-5Hi guys,
<br><br>at the moment I am thinking about switchting from JDOM to woodstox and
<br>staxmate:
<br>The first tests look very promising.
<br><br><br>But I have on small problem when writing the XML Declaration.
<br><br>JDom creates that line:
<br><?xml version="1.0" encoding="UTF-8"?>
<br><br>but Woodstock creates:
<br><?xml version='1.0' encoding='UTF-8'?>
<br><br>Since I have many, many unit tests that contain that line I'd like to
<br>reconfigure Woodstock to output the format I am used to.
<br>Is there anything I can do about?
<br><br>I debugged a bit and found that method:
<br>com.ctc.wstx.sw.BufferingXmlWriter#writeXmlDeclaration
<br><br>But that doesn't seem to be configurable....
<br><br><br><br>Thanks,
<br><br>Johannes
<br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-25778900Re: InternCache - intern() method causing thread synchronization issue2009-10-06T17:20:06Z2009-10-06T17:20:06ZCowtowncoder2009/10/6 Holger Hoffstätte <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=25778900&i=0" target="_top" rel="nofollow">holger.hoffstaette@...</a>>:
<div class='shrinkable-quote'><br>> vadheraju1 wrote:
<br>>> We are using AXIS and Xfire as our soap stacks which internally use
<br>>> woodstox. and In a load test, we see thread are waiting on InternCache
<br>>> object - due to the fact that intern() method is Synchronized.
<br>>> We changed the code it seems to be fixed the issue; we need someone from
<br>>> woodstox team to confirm our change.
<br>>>
<br>>> New implementation:
<br>>> public String intern(String input) {
<br>>> String result = (String) get(input);
<br>>> if (result == null) {
<br>>> result = putInCache(input);
<br>>> }
<br>>> return result;
<br>>> }
<br>>> public synchronized String putInCache(String input) {
<br>>> String result = input.intern();
<br>>> put(result, result);
<br>>> return result;
<br>>> }
<br>>>
<br>>
<br>> I'm not the woodstox team, but that change is wrong as get()s are now
<br>> unsynchronized, which can lead to all sorts of bugs. It is not enough to
<br>> synchronize the put().
</div><br>Right: I did mention this in the Jira issue.
<br>It is actually ok to separately sync on get and put(), because of
<br>intervening intern() call guaranteeing that instance is canonical.
<br>More interestingly though, that will just move the bottleneck within
<br>intern() method, which is all but guaranteed to also synchronize with
<br>a global/singleton lock. So in the end I am not quite sure it will be
<br>a net win.
<br>It definitely is not ok to leave sync out of get part, for
<br>unsynchronized containers like HashMap.
<br><br>> Unless you need to run on JDK 1.4 it is probably easiest to just use a
<br>> ConcurrentMap with proper putIfAbsent(). If you put your InternCache
<br>> implementation on the start of the classpath, Woodstox should pick it up.
<br><br>Woodstox is 1.4+ for version 4.0, so Concurrent map can not yet be
<br>used, but for 5.0 and above it can be used.
<br>There are quite a few things that JDK 1.5 will add, including
<br>StringBuilder() (unsynced wrt StringBuffer()); and 1.6 would have
<br>nifty array resize/realloc methods.
<br><br>-+ Tatu +-
<br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-25777972RE: InternCache - intern() method causing thread synchronization issue2009-10-06T16:03:42Z2009-10-06T16:03:42ZMichael KayAs a general rule, when you read shared data and then update it, the whole
<br>operation should be done under a synchronization lock: it's not safe to only
<br>get the lock if an update is needed. Having said that, however, an awful lot
<br>of software gets away with it nearly all the time. Certainly, Saxon does! In
<br>practice it depends a little on the design of the data structures that you
<br>use: although it's always unsafe in theory, it's often safe in practice
<br>(i.e. given the design of current JVMs).
<br><br>Michael Kay
<br>Saxonica
<br><div class='shrinkable-quote'><br>> -----Original Message-----
<br>> From: vadheraju1 [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=25777972&i=0" target="_top" rel="nofollow">Rajeswar.Rao@...</a>]
<br>> Sent: 06 October 2009 20:31
<br>> To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=25777972&i=1" target="_top" rel="nofollow">user@...</a>
<br>> Subject: [woodstox-user] InternCache - intern() method
<br>> causing thread synchronization issue
<br>>
<br>>
<br>> We are using AXIS and Xfire as our soap stacks which
<br>> internally use woodstox. and In a load test, we see thread
<br>> are waiting on InternCache object - due to the fact that
<br>> intern() method is Synchronized.
<br>> We changed the code it seems to be fixed the issue; we need
<br>> someone from woodstox team to confirm our change.
<br>>
<br>> Jar : wstx-asl-3.0.1
<br>> Stack Trace:
<br>> at com.ctc.wstx.util.InternCache.intern(InternCache.java:40)
<br>> - waiting to lock [0x942373a0] (a com.ctc.wstx.util.InternCache) at
<br>> com.ctc.wstx.sr.NsInputElementStack.resolveAndValidateElement(
<br>> NsInputElementStack.java:305)
<br>> at
<br>> com.ctc.wstx.sr.BasicStreamReader.handleStartElem(BasicStreamR
<br>> eader.java:2826)
<br>> at
<br>> com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamRead
<br>> er.java:2737)
<br>> at
<br>> com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1004) at
<br>> org.codehaus.xfire.util.stax.DepthXMLStreamReader.next(DepthXM
<br>> LStreamReader.java:252)
<br>> at
<br>> org.codehaus.xfire.util.stax.FragmentStreamReader.next(Fragmen
<br>> tStreamReader.java:79)
<br>> at
<br>> org.codehaus.xfire.util.jdom.StaxBuilder.buildTree(StaxBuilder
<br>> .java:466)
<br>> at
<br>> org.codehaus.xfire.util.jdom.StaxBuilder.build(StaxBuilder.jav
<br>> a:215) at
<br>> org.codehaus.xfire.soap.handler.ReadHeadersHandler.readHeaders
<br>> (ReadHeadersHandler.java:134)
<br>> at
<br>> org.codehaus.xfire.soap.handler.ReadHeadersHandler.invoke(Read
<br>> HeadersHandler.java:59)
<br>> at
<br>> org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipel
<br>> ine.java:131)
<br>> at org.codehaus.xfire.client.Client.onReceive(Client.java:406) at
<br>> org.codehaus.xfire.transport.http.HttpChannel.sendViaClient(Ht
<br>> tpChannel.java:139)
<br>> at
<br>> org.codehaus.xfire.transport.http.HttpChannel.send(HttpChannel
<br>> .java:48)
<br>> at
<br>> org.codehaus.xfire.handler.OutMessageSender.invoke(OutMessageS
<br>> ender.java:26)
<br>> at
<br>> org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipel
<br>> ine.java:131)
<br>> at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:79) at
<br>> org.codehaus.xfire.client.Invocation.invoke(Invocation.java:114) at
<br>> org.codehaus.xfire.client.Client.invoke(Client.java:336) at
<br>> org.codehaus.xfire.client.XFireProxy.handleRequest(XFireProxy.
<br>> java:77) at
<br>> org.codehaus.xfire.client.XFireProxy.invoke(XFireProxy.java:57
<br>> ) at $Proxy2.doCompleteAndTrackForms(Unknown Source) at
<br>> com.metavante.eds.deposit_origination.common.DoBusSvcsDao.invo
<br>> keBusService(DoBusSvcsDao.java:104)
<br>> at
<br>> com.metavante.eds.common.pages.print_forms.PrintFormsSH.doNavi
<br>> gateOff(PrintFormsSH.java:873)
<br>>
<br>> Class Name and Method Name:
<br>> com.ctc.wstx.util.InternCache.intern
<br>>
<br>> Current Implementation:
<br>> public synchronized String intern(String input) {
<br>> String result = (String) get(input);
<br>> if (result == null) {
<br>> result = input.intern();
<br>> put(result, result);
<br>> }
<br>> return result;
<br>> }
<br>>
<br>> New implementation:
<br>> public String intern(String input) {
<br>> String result = (String) get(input);
<br>> if (result == null) {
<br>> result = putInCache(input);
<br>> }
<br>> return result;
<br>> }
<br>> public synchronized String putInCache(String input) {
<br>> String result = input.intern();
<br>> put(result, result);
<br>> return result;
<br>> }
<br>>
<br>> --
<br>> View this message in context:
<br>> <a href="http://www.nabble.com/InternCache---intern%28%29-method-causin" target="_top">http://www.nabble.com/InternCache---intern%28%29-method-causin</a><br>> g-thread-synchronization-issue-tp25775169p25775169.html
<br>> Sent from the woodstox - user mailing list archive at Nabble.com.
<br>>
<br>>
<br>> ---------------------------------------------------------------------
<br>> To unsubscribe from this list, please visit:
<br>>
<br>> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br>>
<br>>
</div><br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-25777937Re: InternCache - intern() method causing thread synchronization issue2009-10-06T16:00:10Z2009-10-06T16:00:10ZHolger Hoffstätte-4vadheraju1 wrote:
<div class='shrinkable-quote'><br>> We are using AXIS and Xfire as our soap stacks which internally use
<br>> woodstox. and In a load test, we see thread are waiting on InternCache
<br>> object - due to the fact that intern() method is Synchronized.
<br>> We changed the code it seems to be fixed the issue; we need someone from
<br>> woodstox team to confirm our change.
<br>>
<br>> New implementation:
<br>> public String intern(String input) {
<br>> String result = (String) get(input);
<br>> if (result == null) {
<br>> result = putInCache(input);
<br>> }
<br>> return result;
<br>> }
<br>> public synchronized String putInCache(String input) {
<br>> String result = input.intern();
<br>> put(result, result);
<br>> return result;
<br>> }
<br>>
</div><br>I'm not the woodstox team, but that change is wrong as get()s are now
<br>unsynchronized, which can lead to all sorts of bugs. It is not enough to
<br>synchronize the put().
<br>Unless you need to run on JDK 1.4 it is probably easiest to just use a
<br>ConcurrentMap with proper putIfAbsent(). If you put your InternCache
<br>implementation on the start of the classpath, Woodstox should pick it up.
<br><br>However, as Tatu has already answered - it is not entirely clear *why*
<br>this method is a bottleneck in your case. Chances are very good that you
<br>will see other (much more severe) bottlenecks come up after this "fix",
<br>especially in Axis (which is horribly broken in itself) and XFire (long
<br>unmaintained).
<br><br>-h
<br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-25777842Re: [woodstox-user] InternCache - intern() method causing thread synchronization issue2009-10-06T15:24:20Z2009-10-06T15:24:20ZCowtowncoderOn Tue, Oct 6, 2009 at 12:30 PM, vadheraju1 <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=25777842&i=0" target="_top" rel="nofollow">Rajeswar.Rao@...</a>> wrote:
<br>>
<br>> We are using AXIS and Xfire as our soap stacks which internally use
<br>> woodstox. and In a load test, we see thread are waiting on InternCache
<br>> object - due to the fact that intern() method is Synchronized.
<br>> We changed the code it seems to be fixed the issue; we need someone from
<br>> woodstox team to confirm our change.
<br>>
<br>> Jar : wstx-asl-3.0.1
<br>...
<br><br>First of all, thank you for your suggestion. It is always possible
<br>that implementation could be improved.
<br>I'll have a look at proposed change (first create a Jira issue for it.
<br><br>I have some questions regarding the change. First: version 3.0.1 is
<br>rather old, and although I don't think there have been drastic
<br>changes, it would be good if the performance aspects could be verified
<br>with a more recent version. 3.2.9 should be fully backwards
<br>compatible, so if you could re-check findings using that version it'd
<br>be great.
<br><br>Also: I am somewhat surprised that this method could be heavily
<br>contested; and that suggests that perhaps your application is not
<br>reusing XMLInputFactory instances as expected. The reason for this is
<br>that intern()ing only occurs if symbol is not found from symbol table;
<br>and symbol table gets populated and recycled on per-input-factory
<br>basis. Which means that fairly quickly such cache misses should be
<br>very rare.
<br>Put another way: this could indicate sub-optimal behavior within
<br>service itself, whereas symbol tables are not being reused. So you may
<br>want to see how reuse is implemented -- it has significant performance
<br>benefits, especially for small to medium size documents.
<br><br>-+ Tatu +-
<br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---dev-f12119.html" embed="fixTarget[12119]" target="_top" >woodstox - dev</a></p>tag:old.nabble.com,2006:post-25777844Re: InternCache - intern() method causing thread synchronization issue2009-10-06T15:24:20Z2009-10-06T15:24:20ZCowtowncoderOn Tue, Oct 6, 2009 at 12:30 PM, vadheraju1 <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=25777844&i=0" target="_top" rel="nofollow">Rajeswar.Rao@...</a>> wrote:
<br>>
<br>> We are using AXIS and Xfire as our soap stacks which internally use
<br>> woodstox. and In a load test, we see thread are waiting on InternCache
<br>> object - due to the fact that intern() method is Synchronized.
<br>> We changed the code it seems to be fixed the issue; we need someone from
<br>> woodstox team to confirm our change.
<br>>
<br>> Jar : wstx-asl-3.0.1
<br>...
<br><br>First of all, thank you for your suggestion. It is always possible
<br>that implementation could be improved.
<br>I'll have a look at proposed change (first create a Jira issue for it.
<br><br>I have some questions regarding the change. First: version 3.0.1 is
<br>rather old, and although I don't think there have been drastic
<br>changes, it would be good if the performance aspects could be verified
<br>with a more recent version. 3.2.9 should be fully backwards
<br>compatible, so if you could re-check findings using that version it'd
<br>be great.
<br><br>Also: I am somewhat surprised that this method could be heavily
<br>contested; and that suggests that perhaps your application is not
<br>reusing XMLInputFactory instances as expected. The reason for this is
<br>that intern()ing only occurs if symbol is not found from symbol table;
<br>and symbol table gets populated and recycled on per-input-factory
<br>basis. Which means that fairly quickly such cache misses should be
<br>very rare.
<br>Put another way: this could indicate sub-optimal behavior within
<br>service itself, whereas symbol tables are not being reused. So you may
<br>want to see how reuse is implemented -- it has significant performance
<br>benefits, especially for small to medium size documents.
<br><br>-+ Tatu +-
<br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-25775170InternCache - intern() method causing thread synchronization issue2009-10-06T12:32:48Z2009-10-06T12:32:48Zvadheraju1We are using AXIS and Xfire as our soap stacks which internally use woodstox. and In a load test, we see thread are waiting on InternCache object - due to the fact that intern() method is Synchronized.
<br>We changed the code it seems to be fixed the issue; we need someone from woodstox team to confirm our change.
<br><br><b>Jar</b> : wstx-asl-3.0.1
<br><b>Stack Trace</b>:
<br>at com.ctc.wstx.util.InternCache.intern(InternCache.java:40) - waiting to lock [0x942373a0] (a com.ctc.wstx.util.InternCache) at com.ctc.wstx.sr.NsInputElementStack.resolveAndValidateElement(NsInputElementStack.java:305) at com.ctc.wstx.sr.BasicStreamReader.handleStartElem(BasicStreamReader.java:2826) at com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2737) at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1004) at org.codehaus.xfire.util.stax.DepthXMLStreamReader.next(DepthXMLStreamReader.java:252) at org.codehaus.xfire.util.stax.FragmentStreamReader.next(FragmentStreamReader.java:79) at org.codehaus.xfire.util.jdom.StaxBuilder.buildTree(StaxBuilder.java:466) at org.codehaus.xfire.util.jdom.StaxBuilder.build(StaxBuilder.java:215) at org.codehaus.xfire.soap.handler.ReadHeadersHandler.readHeaders(ReadHeadersHandler.java:134) at org.codehaus.xfire.soap.handler.ReadHeadersHandler.invoke(ReadHeadersHandler.java:59) at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131) at org.codehaus.xfire.client.Client.onReceive(Client.java:406) at org.codehaus.xfire.transport.http.HttpChannel.sendViaClient(HttpChannel.java:139) at org.codehaus.xfire.transport.http.HttpChannel.send(HttpChannel.java:48) at org.codehaus.xfire.handler.OutMessageSender.invoke(OutMessageSender.java:26) at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131) at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:79) at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:114) at org.codehaus.xfire.client.Client.invoke(Client.java:336) at org.codehaus.xfire.client.XFireProxy.handleRequest(XFireProxy.java:77) at org.codehaus.xfire.client.XFireProxy.invoke(XFireProxy.java:57) at $Proxy2.doCompleteAndTrackForms(Unknown Source) at com.metavante.eds.deposit_origination.common.DoBusSvcsDao.invokeBusService(DoBusSvcsDao.java:104) at com.metavante.eds.common.pages.print_forms.PrintFormsSH.doNavigateOff(PrintFormsSH.java:873)
<br><br><b>Class Name and Method Name</b>:
<br>com.ctc.wstx.util.InternCache.intern
<br><br><b>Current Implementation</b>:
<br>public synchronized String intern(String input) {
<br> String result = (String) get(input);
<br> if (result == null) {
<br> result = input.intern();
<br> put(result, result);
<br> }
<br> return result;
<br> }
<br><br><b>New implementation</b>:
<br>public String intern(String input) {
<br> String result = (String) get(input);
<br> if (result == null) {
<br> result = putInCache(input);
<br> }
<br> return result;
<br> }
<br>public synchronized String putInCache(String input) {
<br> String result = input.intern();
<br> put(result, result);
<br> return result;
<br> }
<br><br><p>From forum: <a href="http://old.nabble.com/woodstox---dev-f12119.html" embed="fixTarget[12119]" target="_top" >woodstox - dev</a></p>tag:old.nabble.com,2006:post-25775169InternCache - intern() method causing thread synchronization issue2009-10-06T12:30:43Z2009-10-06T20:30:32Zvadheraju1We are using AXIS and Xfire as our soap stacks which internally use woodstox. and In a load test, we see thread are waiting on InternCache object - due to the fact that intern() method is Synchronized.
<br>We changed the code it seems to be fixed the issue; we need someone from woodstox team to confirm our change.
<br><br><b>Jar</b> : wstx-asl-3.0.1
<br><b>Stack Trace:</b><br>at com.ctc.wstx.util.InternCache.intern(InternCache.java:40) - waiting to lock [0x942373a0] (a com.ctc.wstx.util.InternCache) at com.ctc.wstx.sr.NsInputElementStack.resolveAndValidateElement(NsInputElementStack.java:305) at com.ctc.wstx.sr.BasicStreamReader.handleStartElem(BasicStreamReader.java:2826) at com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2737) at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1004) at org.codehaus.xfire.util.stax.DepthXMLStreamReader.next(DepthXMLStreamReader.java:252) at org.codehaus.xfire.util.stax.FragmentStreamReader.next(FragmentStreamReader.java:79) at org.codehaus.xfire.util.jdom.StaxBuilder.buildTree(StaxBuilder.java:466) at org.codehaus.xfire.util.jdom.StaxBuilder.build(StaxBuilder.java:215) at org.codehaus.xfire.soap.handler.ReadHeadersHandler.readHeaders(ReadHeadersHandler.java:134) at org.codehaus.xfire.soap.handler.ReadHeadersHandler.invoke(ReadHeadersHandler.java:59) at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131) at org.codehaus.xfire.client.Client.onReceive(Client.java:406) at org.codehaus.xfire.transport.http.HttpChannel.sendViaClient(HttpChannel.java:139) at org.codehaus.xfire.transport.http.HttpChannel.send(HttpChannel.java:48) at org.codehaus.xfire.handler.OutMessageSender.invoke(OutMessageSender.java:26) at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131) at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:79) at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:114) at org.codehaus.xfire.client.Client.invoke(Client.java:336) at org.codehaus.xfire.client.XFireProxy.handleRequest(XFireProxy.java:77) at org.codehaus.xfire.client.XFireProxy.invoke(XFireProxy.java:57)
<br><br><b>Class Name and Method Name:</b><br>com.ctc.wstx.util.InternCache.intern
<br><br><b>Current Implementation:</b><br>public synchronized String intern(String input) {
<br> String result = (String) get(input);
<br> if (result == null) {
<br> result = input.intern();
<br> put(result, result);
<br> }
<br> return result;
<br> }
<br><br><b>New implementation:</b><br>public String intern(String input) {
<br> String result = (String) get(input);
<br> if (result == null) {
<br> result = putInCache(input);
<br> }
<br> return result;
<br> }
<br>public synchronized String putInCache(String input) {
<br> String result = input.intern();
<br> put(result, result);
<br> return result;
<br> }
<br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-25710264[woodstox-announce] Woodstox 4.0.6 released: upgrade from 4.0.x recommended2009-10-01T21:11:33Z2009-10-01T21:11:33ZCowtowncoderI decided to go ahead and release patch/maintenance version 4.0.6,
<br>even though there is just one bug fix.
<br>However, that's an important one (see
<br>[<a href="http://jira.codehaus.org/browse/WSTX-211" target="_top" rel="nofollow">http://jira.codehaus.org/browse/WSTX-211</a>] for details), related to
<br>handling of CDATA sections when read using
<br>XMLStreamReader.getElementText().
<br>Because of this, upgrade from earlier 4.0.x is strongly recommended.
<br><br>Also: thanks to Olivier's suggestion (see
<br>[<a href="http://jira.codehaus.org/browse/WSTX-218" target="_top" rel="nofollow">http://jira.codehaus.org/browse/WSTX-218</a>]), I added "legacy" Maven
<br>pom entries that should make it easier to upgrade from 3.2. Problem
<br>being addressed is that of artifactId having changed between 3.2 and
<br>4.0 (from "wstx-asl" to "woodstox-core-asl"). I hope this makes pain
<br>with transitive dependency handling bit more tolerable.
<br><br>As usual, please let me know if you find any problems,
<br><br>-+ Tatu +-
<br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-25605714Re: tied myself in prezel with validation name namespaces2009-09-24T19:29:38Z2009-09-24T19:29:38ZbimarguliesI updated the old JIRA on this subject. I'll cook at test case and attach it.<br><br><div class="gmail_quote">On Thu, Sep 24, 2009 at 3:59 PM, Tatu Saloranta <span dir="ltr"><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=25605714&i=0" target="_top" rel="nofollow">tsaloranta@...</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Thu, Sep 24, 2009 at 9:35 AM, Benson Margulies <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=25605714&i=1" target="_top" rel="nofollow">bimargulies@...</a>> wrote:<br>
> I'm writing a document with a document element like:<br>
><br>
> <foo xmlns="urn:my-namespace"><br>
><br>
> I do this by writing the start and then setting the default namespace.<br>
<br>
</div>Which should be correct...<br>
<div class="im"><br>
> Well, this causes validation to reject on the grounds that the element has<br>
> the wrong namespace.<br>
><br>
> I can't find any way to get this right without assigning a prefix, which I<br>
> don't really want.<br>
<br>
</div>Just to clarify: your writeStartElement() does get correct namespace<br>
URI, and null or empty String as prefix?<br>
Is this in namespace-repairing mode or not? And validating against W3C<br>
Schema? (not dtd, dtds still rely on prefixes, alas)<br>
Do you have line number for exception where validation problem is reported?<br>
<br>
-+ Tatu +-<br>
<br>
---------------------------------------------------------------------<br>
To unsubscribe from this list, please visit:<br>
<br>
<a href="http://xircles.codehaus.org/manage_email" target="_blank" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br>
<br>
<br>
</blockquote></div><br>
<p>From forum: <a href="http://old.nabble.com/woodstox---dev-f12119.html" embed="fixTarget[12119]" target="_top" >woodstox - dev</a></p>tag:old.nabble.com,2006:post-25601679Re: tied myself in prezel with validation name namespaces2009-09-24T12:59:34Z2009-09-24T12:59:34ZCowtowncoderOn Thu, Sep 24, 2009 at 9:35 AM, Benson Margulies <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=25601679&i=0" target="_top" rel="nofollow">bimargulies@...</a>> wrote:
<br>> I'm writing a document with a document element like:
<br>>
<br>> <foo xmlns="urn:my-namespace">
<br>>
<br>> I do this by writing the start and then setting the default namespace.
<br><br>Which should be correct...
<br><br>> Well, this causes validation to reject on the grounds that the element has
<br>> the wrong namespace.
<br>>
<br>> I can't find any way to get this right without assigning a prefix, which I
<br>> don't really want.
<br><br>Just to clarify: your writeStartElement() does get correct namespace
<br>URI, and null or empty String as prefix?
<br>Is this in namespace-repairing mode or not? And validating against W3C
<br>Schema? (not dtd, dtds still rely on prefixes, alas)
<br>Do you have line number for exception where validation problem is reported?
<br><br>-+ Tatu +-
<br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---dev-f12119.html" embed="fixTarget[12119]" target="_top" >woodstox - dev</a></p>tag:old.nabble.com,2006:post-25598485tied myself in prezel with validation name namespaces2009-09-24T09:35:02Z2009-09-24T09:35:02ZbimarguliesI'm writing a document with a document element like:<br><br><foo xmlns="urn:my-namespace"><br><br>I do this by writing the start and then setting the default namespace.<br><br>Well, this causes validation to reject on the grounds that the element has the wrong namespace.<br>
<br>I can't find any way to get this right without assigning a prefix, which I don't really want.<br><br>
<p>From forum: <a href="http://old.nabble.com/woodstox---dev-f12119.html" embed="fixTarget[12119]" target="_top" >woodstox - dev</a></p>tag:old.nabble.com,2006:post-25546505Re: StAX from source2009-09-21T09:05:43Z2009-09-21T09:05:43ZCowtowncoderOn Mon, Sep 21, 2009 at 3:58 AM, Chris Faulkner
<br><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=25546505&i=0" target="_top" rel="nofollow">chris.faulkner@...</a>> wrote:
<br>> Hi
<br>>
<br>> Having previously been a user of various SAX libraries, DOM (and JDOM), I
<br>> was very happy to have found StAX and Woodstox ! It feels a lot more natural
<br>> to me, even after quite a long time with those other implementations.
<br><br>Thanks!
<br><br>> Anyway, I am at the point where I have a need to strip out extraneous
<br>> characters (linefeeds, long sections of repeating whitespace and tabs, etc)
<br>> from within some of my elements. I had hoped to understand how do this (if
<br><br>Makes sense, yes.
<br><br>> possible) by downloading the source jars and begining to debug in Eclipse by
<br>> attaching source in the normal way in there. I have been through some of the
<br>> javadoc and documentation but I can't see how I might do this with the
<br>> existing implementations.
<br><br>There are no options directly doing this, unless you have a DTD that
<br>defines what whitespace is "ignorable".
<br>XML by default assumes no textual content is meaningless, so it is
<br>reported as regular CHARACTERS.
<br>However, DTD can define content model for elements which does not
<br>include any CDATA; if so, any white space included must then be
<br>ignorable white space (for indentation); if so, it will be reported as
<br>SPACE. So filtering these out would be one way to achieve this goal,
<br>iff there's a DTD to use. Or theoretically Schema/RNG; but I don't
<br>remember whethere that has been tested to work this way (both can
<br>declare element-only content, but whether that gets properly
<br>propagated through validation API).
<br><br>> 1. Is there a way of doing what I need in terms of stripping those
<br>> extraneous characters ? For most of my elements, I am iterating through
<br>> elements with nextTag() and getElementText / getElementAs... and I am not
<br><br>One way to trim leading/trailing space would be to just do trim() on
<br>results of getElementText()?
<br>One problem is that getElementText() only works for text-only content.
<br><br>For what it's worth, I personally use StaxMate for much of my XML
<br>processing; it builds on Stax API, implements fully streaming
<br>extensions that allow somewhat more convenient access. And features
<br>like "advanced" white space processing would fit nicely within that
<br>framework (no such functionality yet exists in StaxMate either tho).
<br><br>> doing anything within the elements. Even if there is, I'd like to get my
<br>> source build working - I may be able to provide help and input back to the
<br>> project.
<br><br>Yes, source build should work. And help is always appreciated! So:
<br><br>> 2. How do you build woodstox AND the stax2-3.0-api.jar from source ? I
<br>> downloaded the woodstox source and tried "ant dist -f build.xml" but I get
<br>> errors because it tries to import some other build files (for osgi) which
<br>> aren't there.
<br>>
<br>> 3. I can't find all of the source for the stax2-3.0-api.jar - this contains
<br>> classes in org.codehaus.stax2 namespace. The org.codehaus.stax2.ri code is
<br>> in the woodstox source download but not the rest of the stuff in that jar
<br>> (evt, io, etc).
<br><br>Is this from trunk or one of branches? All sources should of course be
<br>included, so there may be an error in build setup, probably due to
<br>refactoring done to split jars (core vs others). :-/
<br><br>One known problem is that the OSGi build task is bit tricky to get
<br>working; I just couldn't get it working without adding task jar in my
<br>local Ant lib dir (so any help to make that work would be well
<br>appreciated!). Jar in question is under lib/osgi/, and its declared in
<br>and invoked from build-osgi.xml.
<br>I am not aware of other problems; but it is of course possible
<br>something might be missing from source package. Perhaps you could
<br>download sources from svn repo to see what is missing?
<br><br>-+ Tatu +-
<br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-25541984StAX from source2009-09-21T03:58:32Z2009-09-21T03:58:32ZChris FaulknerHi<br><br>Having previously been a user of various SAX libraries, DOM
(and JDOM), I was very happy to have found StAX and Woodstox ! It feels
a lot more natural to me, even after quite a long time with those other
implementations.<br>
<br>Anyway, I am at the point where I have a need to strip out
extraneous characters (linefeeds, long sections of repeating whitespace
and tabs, etc) from within some of my elements. I had hoped to
understand how do this (if possible) by downloading the source jars and
begining to debug in Eclipse by attaching source in the normal way in
there. I have been through some of the javadoc and documentation but I
can't see how I might do this with the existing implementations. <br>
<br>1. Is there a way of doing what I need in terms of stripping those
extraneous characters ? For most of my elements, I am iterating
through elements with nextTag() and getElementText / getElementAs...
and I am not doing anything within the elements. Even if there is, I'd
like to get my source build working - I may be able to provide help and
input back to the project.<br>
<br>2. How do you build woodstox AND the stax2-3.0-api.jar from source
? I downloaded the woodstox source and tried "ant dist -f build.xml"
but I get errors because it tries to import some other build files (for
osgi) which aren't there. <br>
<br>3. I can't find all of the source for the stax2-3.0-api.jar - this contains classes in org.<span class="il">codehaus</span>.stax2 namespace. The org.<span class="il">codehaus</span>.stax2.ri code is in the woodstox source download but not the rest of the stuff in that jar (evt, io, etc).<br>
<br>Thanks all<br><font color="#888888"><br></font>
<p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-25519058Finally wrote the last part of "using typed access API" blog series -> [http://www.cowtowncoder.com/blog/blog.html]2009-09-18T23:35:32Z2009-09-18T23:35:32ZCowtowncoderJust thought this might be useful for Woodstox 4.0 users: I wrote the
<br>third part of "Typed Access API" blog entries at Cowtown blog
<br>(<a href="http://www.cowtowncoder.com/blog/blog.html);" target="_top" rel="nofollow">http://www.cowtowncoder.com/blog/blog.html);</a> this one covering how to
<br>read/write Base64-encoded binary data.
<br><br>If anyone has used base64 encoding functionality so far, please let me
<br>know -- I am very interested in feedback.
<br>And I hope to find time to do some benchmarking; implementation is
<br>designed to be very competitive for transferring binary data, relative
<br>to other XML-related approaches (such as using attachments for SOAP
<br>etc); and definitely "efficient enough" for most common use cases.
<br><br>-+ Tatu +-
<br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-25372894Re: Error in retrived XML in Chucks using the getText()2009-09-09T13:48:36Z2009-09-09T13:48:36ZCowtowncoderOn Wed, Sep 9, 2009 at 12:05 AM, Tanveer
<br>Virani<<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=25372894&i=0" target="_top" rel="nofollow">TanveerVirani@...</a>> wrote:
<br>>
<br>> When I upgraded to Tomcat 6.0.20 from Tomcat 5.5.26, the problem when away.
<br>> I'm thinking that it may have to do with Tomcat and the Velocity engine
<br>> (1.6.2). I tryed writing the stream directly to a temp with using any XML
<br><br>Ok, I can google to see if there's anything indicating problems with
<br>streams that can return 0 bytes/chars per read -- that would explain
<br>problems Woodstox has. That is not the only possibility, just most
<br>obvious.
<br><br>> parsing, and still wound up with only k.
<br><br>Interesting. I think what I will do is keep this in mind; and if I can
<br>not reproduce this (I will add couple of unit tests for specific kinds
<br>of constrainted streams, ones that only produce 1 byte/char per read),
<br>wait to see if anyone else hits the same problem. I need to be able to
<br>reproduce it before it can be fixed.
<br><br>-+ Tatu +-
<br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-25359697Re: Error in retrived XML in Chucks using the getText()2009-09-09T00:05:14Z2009-09-09T00:05:14ZTanveer ViraniWhen I upgraded to Tomcat 6.0.20 from Tomcat 5.5.26, the problem when away. I'm thinking that it may have to do with Tomcat and the Velocity engine (1.6.2). I tryed writing the stream directly to a temp with using any XML parsing, and still wound up with only k.
<br><br><blockquote class="quote light-black dark-border-color"><div class="quote light-border-color">
<div class="quote-author" style="font-weight: bold;">Cowtowncoder wrote:</div>
<div class="quote-message shrinkable-quote">On Fri, Sep 4, 2009 at 9:45 PM, Tanveer
<br>Virani<TanveerVirani@elluminate.com> wrote:
<br>>
<br>> Dropped the new jar in, and reran.
<br>>
<br>> Here's the stack trace:
<br>> com.ctc.wstx.exc.WstxException: Reader (of type
<br>> com.ctc.wstx.io.MergedReader) returned 0 characters, even when asked to read
<br>> up to 4000
<br>> at [row,col {unknown-source}]: [1,1]
<br>> at com.ctc.wstx.io.ReaderSource.readInto(Unknown Source)
<br>> at com.ctc.wstx.io.BranchingReaderSource.readInto(Unknown Source)
<br>> at com.ctc.wstx.sr.StreamScanner.loadMore(Unknown Source)
<br>> at com.ctc.wstx.sr.StreamScanner.loadMore(Unknown Source)
<br>> at com.ctc.wstx.sr.StreamScanner.getNextChar(Unknown Source)
<br>> at com.ctc.wstx.sr.BasicStreamReader.readAndWriteText(Unknown Source)
<br>> at com.ctc.wstx.sr.BasicStreamReader.getText(Unknown Source)
<br>> at
<br>> com.elluminate.service.proxy.impl.WebServiceProxy.processStreamValue(WebServiceProxy.java:649)
<br><br>Strange. I wonder if this could be due to merged reader getting
<br>initialized with empty contents.
<br>That could explain it... I'll need to figure out a test case for
<br>reproducing the problem.
<br><br>-+ Tatu +-
<br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br></div>
</div></blockquote>
<p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-25359438Re: Error in retrived XML in Chucks using the getText()2009-09-08T23:40:49Z2009-09-08T23:40:49ZCowtowncoderOn Fri, Sep 4, 2009 at 9:45 PM, Tanveer
<br>Virani<<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=25359438&i=0" target="_top" rel="nofollow">TanveerVirani@...</a>> wrote:
<div class='shrinkable-quote'><br>>
<br>> Dropped the new jar in, and reran.
<br>>
<br>> Here's the stack trace:
<br>> com.ctc.wstx.exc.WstxException: Reader (of type
<br>> com.ctc.wstx.io.MergedReader) returned 0 characters, even when asked to read
<br>> up to 4000
<br>> at [row,col {unknown-source}]: [1,1]
<br>> at com.ctc.wstx.io.ReaderSource.readInto(Unknown Source)
<br>> at com.ctc.wstx.io.BranchingReaderSource.readInto(Unknown Source)
<br>> at com.ctc.wstx.sr.StreamScanner.loadMore(Unknown Source)
<br>> at com.ctc.wstx.sr.StreamScanner.loadMore(Unknown Source)
<br>> at com.ctc.wstx.sr.StreamScanner.getNextChar(Unknown Source)
<br>> at com.ctc.wstx.sr.BasicStreamReader.readAndWriteText(Unknown Source)
<br>> at com.ctc.wstx.sr.BasicStreamReader.getText(Unknown Source)
<br>> at
<br>> com.elluminate.service.proxy.impl.WebServiceProxy.processStreamValue(WebServiceProxy.java:649)
</div><br>Strange. I wonder if this could be due to merged reader getting
<br>initialized with empty contents.
<br>That could explain it... I'll need to figure out a test case for
<br>reproducing the problem.
<br><br>-+ Tatu +-
<br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-25305082Re: Error in retrived XML in Chucks using the getText()2009-09-04T21:45:39Z2009-09-04T21:45:39ZTanveer ViraniDropped the new jar in, and reran.
<br><br>Here's the stack trace:
<br>com.ctc.wstx.exc.WstxException: Reader (of type com.ctc.wstx.io.MergedReader) returned 0 characters, even when asked to read up to 4000
<br> at [row,col {unknown-source}]: [1,1]
<br> at com.ctc.wstx.io.ReaderSource.readInto(Unknown Source)
<br> at com.ctc.wstx.io.BranchingReaderSource.readInto(Unknown Source)
<br> at com.ctc.wstx.sr.StreamScanner.loadMore(Unknown Source)
<br> at com.ctc.wstx.sr.StreamScanner.loadMore(Unknown Source)
<br> at com.ctc.wstx.sr.StreamScanner.getNextChar(Unknown Source)
<br> at com.ctc.wstx.sr.BasicStreamReader.readAndWriteText(Unknown Source)
<br> at com.ctc.wstx.sr.BasicStreamReader.getText(Unknown Source)
<br> at com.elluminate.service.proxy.impl.WebServiceProxy.processStreamValue(WebServiceProxy.java:649)
<br><br>thanks,
<br>Tanveer
<br><br><blockquote class="quote light-black dark-border-color"><div class="quote light-border-color">
<div class="quote-author" style="font-weight: bold;">Cowtowncoder wrote:</div>
<div class="quote-message shrinkable-quote">Ok. I don't know what exactly is the problem, but I did add bit more
<br>debug info (class name of Reader being invoked) in sources (4.0 and
<br>4.1 branches, trunk), which might help in figuring out what is
<br>happening.
<br>Would it be possible to try out jar included -- the only change from
<br>4.0.5 is the change in exception being thrown (it's also
<br>XMLStreamException directly, instead of being wrapped, which more
<br>clearly shows the location)?
<br><br>-+ Tatu +-
<br><br>ps. Had to strip out debug info from jar (codehaus mailing list size
<br>limitations...); might lose line numbers... but it's quite easy to see
<br>which line throws the exception anyway
<br><br>On Fri, Sep 4, 2009 at 2:43 PM, Tanveer
<br>Virani<TanveerVirani@elluminate.com> wrote:
<br>>
<br>> The connection is passed straight through from a tomcat webapp.
<br>>
<br>> We do all processing internally for the SOAP request and envelope.
<br>>
<br>> Tanveer
<br>>
<br>>
<br>> Tanveer Virani wrote:
<br>>>
<br>>> When using the getTExt from the BasicStreamReader, I get the following
<br>>> error:
<br>>>
<br>>> com.ctc.wstx.exc.WstxIOException: Reader returned 0 characters, even when
<br>>> asked to read up to 4000
<br>>> at com.ctc.wstx.sr.StreamScanner.constructFromIOE(StreamScanner.java:599)
<br>>> at com.ctc.wstx.sr.StreamScanner.loadMore(StreamScanner.java:967)
<br>>> at com.ctc.wstx.sr.StreamScanner.loadMore(StreamScanner.java:1006)
<br>>> at com.ctc.wstx.sr.StreamScanner.getNextChar(StreamScanner.java:758)
<br>>> at
<br>>> com.ctc.wstx.sr.BasicStreamReader.readAndWriteText(BasicStreamReader.java:4993)
<br>>> at com.ctc.wstx.sr.BasicStreamReader.getText(BasicStreamReader.java:1344)
<br>>> at
<br>>> com.elluminate.service.proxy.impl.WebServiceProxy.processStreamValue(WebServiceProxy.java:614)
<br>>>
<br>>> Calling code snippet:
<br>>> XMLInputFactory factory = XMLInputFactory.newInstance();
<br>>> factory.setProperty(XMLInputFactory.SUPPORT_DTD, Boolean.FALSE);
<br>>> factory.setProperty(XMLInputFactory.IS_VALIDATING, Boolean.FALSE);
<br>>> factory.setProperty(XMLInputFactory.IS_NAMESPACE_AWARE, Boolean.TRUE);
<br>>> BasicStreamReader reader = (BasicStreamReader)
<br>>> factory.createXMLStreamReader(input);
<br>>> ...
<br>>> hexPrinter = new HexPrintWriter(temporaryFile);
<br>>> reader.getText(hexPrinter, false);
<br>>> hexPrinter.flush();
<br>>>
<br>>>
<br>>> I get the first 8000 characters, but after that it breaks. The stream
<br>>> length is 1.4Mb.
<br>>>
<br>>> Any help would be appreciated.
<br>>>
<br>>> Tanveer
<br>>>
<br>>
<br>> --
<br>> View this message in context: <a href="http://www.nabble.com/Error-in-retrived-XML-in-Chucks-using-the-getText%28%29-tp25301114p25302455.html" target="_top">http://www.nabble.com/Error-in-retrived-XML-in-Chucks-using-the-getText%28%29-tp25301114p25302455.html</a><br>> Sent from the woodstox - user mailing list archive at Nabble.com.
<br>>
<br>>
<br>> ---------------------------------------------------------------------
<br>> To unsubscribe from this list, please visit:
<br>>
<br>> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br>>
<br>>
<br>>
<br><br>
<br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a></div>
</div></blockquote>
<p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-25303653Re: Error in retrived XML in Chucks using the getText()2009-09-04T16:59:32Z2009-09-04T16:59:32ZCowtowncoderOk. I don't know what exactly is the problem, but I did add bit more
<br>debug info (class name of Reader being invoked) in sources (4.0 and
<br>4.1 branches, trunk), which might help in figuring out what is
<br>happening.
<br>Would it be possible to try out jar included -- the only change from
<br>4.0.5 is the change in exception being thrown (it's also
<br>XMLStreamException directly, instead of being wrapped, which more
<br>clearly shows the location)?
<br><br>-+ Tatu +-
<br><br>ps. Had to strip out debug info from jar (codehaus mailing list size
<br>limitations...); might lose line numbers... but it's quite easy to see
<br>which line throws the exception anyway
<br><br>On Fri, Sep 4, 2009 at 2:43 PM, Tanveer
<br>Virani<<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=25303653&i=0" target="_top" rel="nofollow">TanveerVirani@...</a>> wrote:
<div class='shrinkable-quote'><div class='shrinkable-quote'><br>>
<br>> The connection is passed straight through from a tomcat webapp.
<br>>
<br>> We do all processing internally for the SOAP request and envelope.
<br>>
<br>> Tanveer
<br>>
<br>>
<br>> Tanveer Virani wrote:
<br>>>
<br>>> When using the getTExt from the BasicStreamReader, I get the following
<br>>> error:
<br>>>
<br>>> com.ctc.wstx.exc.WstxIOException: Reader returned 0 characters, even when
<br>>> asked to read up to 4000
<br>>> at com.ctc.wstx.sr.StreamScanner.constructFromIOE(StreamScanner.java:599)
<br>>> at com.ctc.wstx.sr.StreamScanner.loadMore(StreamScanner.java:967)
<br>>> at com.ctc.wstx.sr.StreamScanner.loadMore(StreamScanner.java:1006)
<br>>> at com.ctc.wstx.sr.StreamScanner.getNextChar(StreamScanner.java:758)
<br>>> at
<br>>> com.ctc.wstx.sr.BasicStreamReader.readAndWriteText(BasicStreamReader.java:4993)
<br>>> at com.ctc.wstx.sr.BasicStreamReader.getText(BasicStreamReader.java:1344)
<br>>> at
<br>>> com.elluminate.service.proxy.impl.WebServiceProxy.processStreamValue(WebServiceProxy.java:614)
<br>>>
<br>>> Calling code snippet:
<br>>> XMLInputFactory factory = XMLInputFactory.newInstance();
<br>>> factory.setProperty(XMLInputFactory.SUPPORT_DTD, Boolean.FALSE);
<br>>> factory.setProperty(XMLInputFactory.IS_VALIDATING, Boolean.FALSE);
<br>>> factory.setProperty(XMLInputFactory.IS_NAMESPACE_AWARE, Boolean.TRUE);
<br>>> BasicStreamReader reader = (BasicStreamReader)
<br>>> factory.createXMLStreamReader(input);
<br>>> ...
<br>>> hexPrinter = new HexPrintWriter(temporaryFile);
<br>>> reader.getText(hexPrinter, false);
<br>>> hexPrinter.flush();
<br>>>
<br>>>
<br>>> I get the first 8000 characters, but after that it breaks. The stream
<br>>> length is 1.4Mb.
<br>>>
<br>>> Any help would be appreciated.
<br>>>
<br>>> Tanveer
<br>>>
<br>>
<br>> --
<br>> View this message in context: <a href="http://www.nabble.com/Error-in-retrived-XML-in-Chucks-using-the-getText%28%29-tp25301114p25302455.html" target="_top">http://www.nabble.com/Error-in-retrived-XML-in-Chucks-using-the-getText%28%29-tp25301114p25302455.html</a><br>> Sent from the woodstox - user mailing list archive at Nabble.com.
<br>>
<br>>
<br>> ---------------------------------------------------------------------
<br>> To unsubscribe from this list, please visit:
<br>>
<br>> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br>>
<br>>
<br>>
</div></div><br /> <br />---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>woodstox-core-asl-4.0.6.jar</strong> (461K) <a href="http://old.nabble.com/attachment/25303653/0/woodstox-core-asl-4.0.6.jar" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-25302455Re: Error in retrived XML in Chucks using the getText()2009-09-04T14:43:01Z2009-09-04T14:43:01ZTanveer ViraniThe connection is passed straight through from a tomcat webapp.
<br><br>We do all processing internally for the SOAP request and envelope.
<br><br>Tanveer
<br><br><blockquote class="quote light-black dark-border-color"><div class="quote light-border-color">
<div class="quote-author" style="font-weight: bold;">Tanveer Virani wrote:</div>
<div class="quote-message shrinkable-quote">When using the getTExt from the BasicStreamReader, I get the following error:
<br><br>com.ctc.wstx.exc.WstxIOException: Reader returned 0 characters, even when asked to read up to 4000
<br> at com.ctc.wstx.sr.StreamScanner.constructFromIOE(StreamScanner.java:599)
<br> at com.ctc.wstx.sr.StreamScanner.loadMore(StreamScanner.java:967)
<br> at com.ctc.wstx.sr.StreamScanner.loadMore(StreamScanner.java:1006)
<br> at com.ctc.wstx.sr.StreamScanner.getNextChar(StreamScanner.java:758)
<br> at com.ctc.wstx.sr.BasicStreamReader.readAndWriteText(BasicStreamReader.java:4993)
<br> at com.ctc.wstx.sr.BasicStreamReader.getText(BasicStreamReader.java:1344)
<br> at com.elluminate.service.proxy.impl.WebServiceProxy.processStreamValue(WebServiceProxy.java:614)
<br><br>Calling code snippet:
<br> XMLInputFactory factory = XMLInputFactory.newInstance();
<br> factory.setProperty(XMLInputFactory.SUPPORT_DTD, Boolean.FALSE);
<br> factory.setProperty(XMLInputFactory.IS_VALIDATING, Boolean.FALSE);
<br> factory.setProperty(XMLInputFactory.IS_NAMESPACE_AWARE, Boolean.TRUE);
<br> BasicStreamReader reader = (BasicStreamReader) factory.createXMLStreamReader(input);
<br>...
<br> hexPrinter = new HexPrintWriter(temporaryFile);
<br> reader.getText(hexPrinter, false);
<br> hexPrinter.flush();
<br><br><br>I get the first 8000 characters, but after that it breaks. The stream length is 1.4Mb.
<br><br>Any help would be appreciated.
<br><br>Tanveer
</div>
</div></blockquote>
<p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-25302388Re: Error in retrived XML in Chucks using the getText()2009-09-04T14:37:32Z2009-09-04T14:37:32ZCowtowncoderOn Fri, Sep 4, 2009 at 2:16 PM, Tanveer
<br>Virani<<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=25302388&i=0" target="_top" rel="nofollow">TanveerVirani@...</a>> wrote:
<br>>
<br>> The stream is coming from the network (Soap Service).
<br><br>Ok. Do you know if it might be using Jakarta httpclient (3.1 or 4.0),
<br>or JDK HttpURLConnection?
<br>(might not make a big difference).
<br>Or maybe some client library that wraps network connection.
<br><br>> I'm using version 4.0.5 with the 1.6.12 JRE.
<br><br>Thanks! I will try to see what could possibly cause InputStream.read()
<br>to return 0, when non-zero number of bytes were requested (assuming
<br>that is the problem, as suggested by error message).
<br>This could be due to a broken input stream wrapper -- InputStream
<br>javadocs clearly state that a stream has to try to read at least one
<br>byte (or if not yet available, block). But it could just be a side
<br>effect of some kind.
<br><br>-+ Tatu +-
<br><br>---------------------------------------------------------------------
<br>To unsubscribe from this list, please visit:
<br><br> <a href="http://xircles.codehaus.org/manage_email" target="_top" rel="nofollow">http://xircles.codehaus.org/manage_email</a><br><br><br><p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>tag:old.nabble.com,2006:post-25302114Re: Error in retrived XML in Chucks using the getText()2009-09-04T14:16:14Z2009-09-04T14:16:14ZTanveer ViraniThe stream is coming from the network (Soap Service).
<br><br>I'm using version 4.0.5 with the 1.6.12 JRE.
<br><br>Tanveer
<br><br><blockquote class="quote light-black dark-border-color"><div class="quote light-border-color">
<div class="quote-author" style="font-weight: bold;">Tanveer Virani wrote:</div>
<div class="quote-message shrinkable-quote">When using the getTExt from the BasicStreamReader, I get the following error:
<br><br>com.ctc.wstx.exc.WstxIOException: Reader returned 0 characters, even when asked to read up to 4000
<br> at com.ctc.wstx.sr.StreamScanner.constructFromIOE(StreamScanner.java:599)
<br> at com.ctc.wstx.sr.StreamScanner.loadMore(StreamScanner.java:967)
<br> at com.ctc.wstx.sr.StreamScanner.loadMore(StreamScanner.java:1006)
<br> at com.ctc.wstx.sr.StreamScanner.getNextChar(StreamScanner.java:758)
<br> at com.ctc.wstx.sr.BasicStreamReader.readAndWriteText(BasicStreamReader.java:4993)
<br> at com.ctc.wstx.sr.BasicStreamReader.getText(BasicStreamReader.java:1344)
<br> at com.elluminate.service.proxy.impl.WebServiceProxy.processStreamValue(WebServiceProxy.java:614)
<br><br>Calling code snippet:
<br> XMLInputFactory factory = XMLInputFactory.newInstance();
<br> factory.setProperty(XMLInputFactory.SUPPORT_DTD, Boolean.FALSE);
<br> factory.setProperty(XMLInputFactory.IS_VALIDATING, Boolean.FALSE);
<br> factory.setProperty(XMLInputFactory.IS_NAMESPACE_AWARE, Boolean.TRUE);
<br> BasicStreamReader reader = (BasicStreamReader) factory.createXMLStreamReader(input);
<br>...
<br> hexPrinter = new HexPrintWriter(temporaryFile);
<br> reader.getText(hexPrinter, false);
<br> hexPrinter.flush();
<br><br><br>I get the first 8000 characters, but after that it breaks. The stream length is 1.4Mb.
<br><br>Any help would be appreciated.
<br><br>Tanveer
</div>
</div></blockquote>
<p>From forum: <a href="http://old.nabble.com/woodstox---user-f12118.html" embed="fixTarget[12118]" target="_top" >woodstox - user</a></p>