2 Replies Latest reply on Jun 20, 2005 8:34 AM by thomas.diesler

4.0.2 breaks Axis

dpocock Jun 19, 2005 9:11 AM

I have an application that I developed last year, while the WS4EE code was still quite primitive. It uses the regular Axis distribution - Axis' JAR files are bundled into a servlet WAR file, which is then bundled into my application's EAR file.

When the application is deployed on JBoss 4.0.0RC1, it works fine.

When deployed on JBoss 4.0.2, there are problems with functions that return arrays of complex types. When I send a SOAP request by hand, the XML output looks very different. When invoked within the client application, the endpoint (based on Axis 1.2.1 client library) returns an array of nulls instead of an array of complex types.

Is it possible that something in the JBoss classpath is messing things up? Has anyone else had this problem?

I've tried removing ws4ee completely from the `deploy' directory (and restarting), that didn't help. Are there any other JARs that should be removed if I am using regular Axis?

1. Re: 4.0.2 breaks Axis

dpocock Jun 19, 2005 9:26 AM (in response to dpocock)

Here is some SOAP output that is accepted by the client application (generated by Axis running with JBoss 4.0.0RC1):

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<ns1:getCustomersResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://www.uecommerce.com/telacct">
<getCustomersReturn xsi:type="soapenc:Array" soapenc:arrayType="ns1:CustomerDetails[8]" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">

Here is the output from the same Axis based application when runningin within JBoss 4.0.2, notice that soapenc:arrayType now equals `ArrayOfCustomerDetails[8]' rather than `CustomerDetails[8]'.:

<?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<ns1:getCustomersResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://www.uecommerce.com/telacct">
<getCustomersReturn soapenc:arrayType="ns1:ArrayOfCustomerDetails[8]" xsi:type="soapenc:Array" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
Actions
2. Re: 4.0.2 breaks Axis

thomas.diesler Jun 20, 2005 8:34 AM (in response to dpocock)

Note, that soap encoding is prohibited by the BasicProfile-1.0 and will no longer be supported by jbossws. Please use literal encoding.

Axis standalone deployed on jboss is also not supported.

It is unlikely that jboss interfers with axis since we moved org.apache.axis to org.jboss.axis. Starting from jboss-4.0.2 there are no longer any org.apache.axis classes in the jboss distribution.
Actions

Go to original post