Sorry, I'm a little confused here. How does Jboss integrate with AXIS? If I delete the SAR will AXIS work? Currently the AXIS service URL doesn't work if I upgrade the version of AXIS in Jboss 3.0.
Kev -----Original Message----- From: Jung , Dr. Christoph [mailto:[EMAIL PROTECTED]] Sent: 17 January 2003 14:03 To: '[EMAIL PROTECTED]' Subject: AW: [JBoss-dev] Axis/Jboss bug parsing soap calls using Oracle XDK9? If you do not use jboss-net, simply delete the sar. CGJ -----Ursprüngliche Nachricht----- Von: Kevin Roast [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 17. Januar 2003 14:44 An: [EMAIL PROTECTED] Betreff: RE: [JBoss-dev] Axis/Jboss bug parsing soap calls using Oracle XDK9? Hi, Thanks for your reply. Unfortuntely simply upgrading the JAR does not work :( My investigation leads me to believe that parts of the Jboss3.0 AXIS integration (in jboss-net.sar?) would need to be re-compiled against the newew AXIS jar to work. For instance, I get this exception when starting Jboss: 13:34:48,166 ERROR [URLDeploymentScanner] Failed to deploy: org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL@45bb4fb6{ url=file:/C:/jboss-3.0.4/server/all/deploy/jbossweb.sar/, deployedLastModified=0 } org.jboss.deployment.DeploymentException: Could not create deployment: file:/C:/jboss-3.0.4/server/all/deploy/jbossweb.sar/; - nested throwable: (java.lang.IllegalAccessError: try to access field org.apache.axis.configuration.FileProvider.myInputStream from class org.jboss.net.axis.XMLResourceProvider) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:827) I'll take a look at 3.2RC1 and see if it fixes the problem... Kev -----Original Message----- From: Jung , Dr. Christoph [mailto:[EMAIL PROTECTED]] Sent: 17 January 2003 10:34 To: '[EMAIL PROTECTED]' Subject: AW: [JBoss-dev] Axis/Jboss bug parsing soap calls using Oracle XDK9? The axis version in the 3.0 branch is a beta. >From 3.2 on, we have axis release 1 (it is no more located in the system lib >directory, but an integral part of the jboss.net sar) In head, we have axis 1.1beta integrated. Since you seem not to use jboss.net, why don´t you simply update the jar in your 3.0 distro? If you want the nice deployment/security features of jboss.net, however, I recommend obtaining 3.2RCwhatever. CGJ -----Ursprüngliche Nachricht----- Von: Kevin Roast [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 17. Januar 2003 10:55 An: [EMAIL PROTECTED] Betreff: [JBoss-dev] Axis/Jboss bug parsing soap calls using Oracle XDK9? Hi, I am interested to know if the following is a known Jboss+AXIS bug: We are testing a system using Jboss3.0.4 using the standard embedded version of AXIS. We are using SOAP calls for our web services which AXIS is parsing using the system XML parser. By default this is Xerces which is fine. However, if I change the parser factory to use Oracle XDK 9 parser then I receive an error from the AXIS SAX parsing thus: java.lang.StringIndexOutOfBoundsException: String index out of range: 323 at java.lang.String.<init>(String.java:245) at org.apache.axis.message.SymbolTable.addSymbol(SymbolTable.java:121) at org.apache.axis.message.SAX2EventRecorder.characters(SAX2EventRecorder.j ava:137) at org.apache.axis.encoding.DeserializationContextImpl.characters(Deseriali zationContextImpl.java:771) at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java: 213) at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.j ava:578) at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:207) at org.apache.axis.message.RPCElement.getParams(RPCElement.java:231) at org.apache.axis.client.Call.invoke(Call.java:1605) I have inspected the SOAP being parsed and SAX parsed it myself using both Xerces and Oracle XDK and it parses fine. This leads me to believe that AXIS is doing something naughty in the SAX "characters()" event method i.e. maybe not respecting the start/len parameters? (I'm guessing here from the error) Anyone have any thoughts on this, or I am in completely the wrong ball park? Also - can anyone confirm which version of AXIS is built into Jboss? As I posted this bug to the AXIS-Bug list and they said this particular method no longer exists in the current source line. If possible, I am happy to upgrade the version of AXIS in Jboss - can this be done? Thanks for your time, Kevin ------------------------------------------------------- This SF.NET email is sponsored by: Thawte.com Understand how to protect your customers personal information by implementing SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ ------------------------------------------------------- This SF.NET email is sponsored by: Thawte.com Understand how to protect your customers personal information by implementing SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ------------------------------------------------------- This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will allow you to extend the highest allowed 128 bit encryption to all your clients even if they use browsers that are limited to 40 bit encryption. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
