We have an issue when trying to run our application on the new JBoss-4.0.4.CR2 
release instead of previous releases (including 4.0.4RC1).

We have a special Servlet that makes heavy use of SAAJ and the resulting SOAP 
messages are quite different between the old AXIS based implementation and 
JBossWS. The new behaviour brakes all of our clients that are using our 
applicaiton and renders it useless right now.

The following is the response to a message from a client in JBossWS:

HTTP/1.1 200 OK
  | Server: Apache-Coyote/1.1
  | X-Powered-By: Servlet 2.4; JBoss-4.0.4.CR2 (build: CVSTag=JBoss_4_0_4_CR2 
date=200603311500)/Tomcat-5.5
  | Set-Cookie: JSESSIONID=D350AFBEA98D4CA4FFFB96D9296DAE05; Path=/
  | Content-Type: text/xml
  | Transfer-Encoding: chunked
  | Date: Wed, 26 Apr 2006 16:45:47 GMT
  | 
  | 78
  | <env:Envelope xmlns:cwmp='urn:dslforum-org:cwmp-1-0' 
xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Header/>
  | 2e
  | <env:Body><cwmp:InformResponse><MaxEnvelopes>1
  | f
  | </MaxEnvelopes>
  | 16
  | </cwmp:InformResponse>
  | b
  | </env:Body>
  | f
  | </env:Envelope>
  | 0
  | 

While the following is the response from the previous AXIS implementation:

HTTP/1.1 200 OK
  | Server: Apache-Coyote/1.1
  | X-Powered-By: Servlet 2.4; JBoss-4.0.3SP1 (build: CVSTag=JBoss_4_0_3_SP1 
date=200510231054)/Tomcat-5.5
  | Set-Cookie: JSESSIONID=2C247BFB4C83A6E00E607ABF99793713; Path=/
  | Transfer-Encoding: chunked
  | Date: Wed, 26 Apr 2006 16:53:08 GMT
  | 
  | 1c7
  | <soapenv:Envelope 
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; 
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"; 
xmlns:cwmp="urn:dslforum-org:cwmp-1-0">
  |  <soapenv:Body>
  |   <cwmp:InformResponse xmlns:cwmp="urn:dslforum-org:cwmp-1-0">
  |    <MaxEnvelopes>1</MaxEnvelopes>
  |   </cwmp:InformResponse>
  |  </soapenv:Body>
  | </soapenv:Envelope>
  | 0
  | 
  | 

The way the SOAP message is structured causes the client parsers (that we have 
no influence on) to break. Is there a way to achieve the same output as with 
the AXIS implementation that I'm missing?

We've chosen JAAS to have a higher degree of control over the message 
parsing/generation that is required for our application and can't change that 
aspect.

Thanks in advance for any advice,
Reiner

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3939597#3939597

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3939597


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to