Sorry I don't get you. Can you provide more detail? Which Axiom fix are you talking about?
Thanks, Mary Hu _____ From: Amila Suriarachchi [mailto:amilasuriarach...@gmail.com] Sent: Wednesday, August 26, 2009 12:30 AM To: axis-user@ws.apache.org Subject: Re: imcompatible issue between axis2 and weblogic 10 On Wed, Aug 26, 2009 at 2:43 AM, Andreas Veithen <andreas.veit...@gmail.com> wrote: Since I recently worked on improving the interoperability of Axiom with various StAX parser, I can give you a precise answer. The short answer is: none (with Axiom 1.2.8). The long answer is: - Sun's parser (when used with Axiom up to version 1.2.8) causes a concurrency issue; see WSCOMMONS-489. - Axiom 1.2.8 makes the assumption that all parsers except Woodstox, Sun and Weblogic are broken. This is wrong because only the one from IBM is broken [1]. This means that any parser other than Woodstox, Sun, Weblogic Sometimes back I tested the Axis2 with web logic. Then I had problems with the weblogic parser and when I put the that weblogic entry to Axiom it worked fine. So if you picked an Axis2 version with this Axiom fix it should work with weblogic parser. thanks, Amila. and XLXP (IBM) will not work with Axiom 1.2.8. This excludes BEA's reference implementation (which will work fine with Axiom 1.2.9). - Finally, the one from IBM (which should work with any Axiom version) is not freely available. Andreas [1] http://svn.apache.org/viewvc?rev=800141&view=rev On Tue, Aug 25, 2009 at 22:40, Hu, Mary - ITG<mary...@jpmorgan.com> wrote: > No, Weblogic parser doesn't work for axis2. I'm wondering, beside wstx stream parser, what other parser could possibly work for axiom from axix2. > > Mary Hu > > -----Original Message----- > From: Andreas Veithen [mailto:andreas.veit...@gmail.com] > Sent: Tuesday, August 25, 2009 3:53 PM > To: axis-user@ws.apache.org > Subject: Re: imcompatible issue between axis2 and weblogic 10 > > The probable reason for this error is that the TLD file has a DOCTYPE > declaration referencing a network location. Woodstox insists on > loading the referenced DTD, while for the same configuration > Weblogic's parser wouldn't load the DTD. This is due to an ambiguity > in the StAX specs. > > Assuming that this explanation is correct, you have two options: > > 1) Also remove Woodstox and cross fingers that Axis2 works correctly > with Weblogic's parser. Chances are high, but it is not guaranteed. > I'm not a Weblogic user, but maybe somebody on the list can share his > experience. > > 2) Hack the TLDs so that they don't have a DOCTYPE declaration with a > system ID referencing a network location. Not sure what Weblogic's > expectations are. Maybe you can just remove the DOCTYPE declaration > entirely, maybe only the system ID or maybe you need to add the DTD to > the JAR and change the system ID from an absolute URL to a relative > one. > > Andreas > > On Mon, Aug 24, 2009 at 23:32, Hu, Mary - ITG<mary...@jpmorgan.com> wrote: >> After removed this jar, weblogic can't parse TLD anymore: >> >> Error while parsing the Tag Library Descriptor at "c: ... >> \war\WEB-INF\lib\struts-1.2.9-lib.jar!/META-INF/tlds/struts-tiles.tld". >> com.ctc.wstx.exc.WstxIOException: java.sun.com >> at >> com.ctc.wstx.sr.StreamScanner.throwFromIOE(StreamScanner.java:683) >> at >> com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1086) >> at >> weblogic.servlet.internal.TldCacheHelper$TldIOHelper.parseXML(TldCacheHe >> lper.java:134) >> >> Mary Hu >> Int: 8.226.2620 >> Ext: 973.793.2620 >> >> -----Original Message----- >> From: Andreas Veithen [mailto:andreas.veit...@gmail.com] >> Sent: Monday, August 24, 2009 4:54 PM >> To: axis-user@ws.apache.org >> Subject: Re: imcompatible issue between axis2 and weblogic 10 >> >> Try removing geronimo-stax-api_1.0_spec-1.0.1.jar from WEB-INF/lib. >> >> Andreas >> >> On Mon, Aug 24, 2009 at 22:28, Hu, Mary - ITG<mary...@jpmorgan.com> >> wrote: >>> >>> In axis2 - Application Server Specific Configuration Guide, it >> mentions >>> how to deploy axis2 into weblogic. However, I have seen an issue that >> is >>> blocking me. I wonder anyone has a solution for it: >>> >>> 1. I have a WAR containing axis2 jars. >>> >>> 2. My application requires prefer-web-inf-classes to be set as "true" >> in >>> weblogic.xml. >>> >>> 3. I got below exception: >>> >>> java.lang.ClassCastException: com.ctc.wstx.stax.WstxInputFactory >> cannot >>> be cast >>> to javax.xml.stream.XMLInputFactory >>> at >> javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:137 >>> ) >>> at >> weblogic.servlet.internal.TldCacheHelper$TldIOHelper.parseXML(TldCach >>> eHelper.java:124) >>> >>> >>> I know it is because weblogic can't use Woodstock stream parser. But >> how >>> to instruct weblogic to use Woodstock beside wrap the app into an EAR >>> (It doesn't apply me case)? >>> >>> Appreciate any help. >>> >>> >>> Mary Hu >>> >>> This email is confidential and subject to important disclaimers and >>> conditions including on offers for the purchase or sale of >>> securities, accuracy and completeness of information, viruses, >>> confidentiality, legal privilege, and legal entity disclaimers, >>> available at http://www.jpmorgan.com/pages/disclosures/email. >>> >> >> >> This email is confidential and subject to important disclaimers and >> conditions including on offers for the purchase or sale of >> securities, accuracy and completeness of information, viruses, >> confidentiality, legal privilege, and legal entity disclaimers, >> available at http://www.jpmorgan.com/pages/disclosures/email. >> > > > This email is confidential and subject to important disclaimers and > conditions including on offers for the purchase or sale of > securities, accuracy and completeness of information, viruses, > confidentiality, legal privilege, and legal entity disclaimers, > available at http://www.jpmorgan.com/pages/disclosures/email. > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/ This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email.
