aspose file tools*
The moose likes Other Java Products and Servers and the fly likes Apache 2 , Jboss issues Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Products » Other Java Products and Servers
Bookmark "Apache 2 , Jboss issues" Watch "Apache 2 , Jboss issues" New topic
Author

Apache 2 , Jboss issues

Karthik Krishnamurthy
Ranch Hand

Joined: Feb 04, 2005
Posts: 118
Hi,
I wrote an Apache proxy to jboss recently to route webservice requests from our clients.
There has been some strange behavior. Whenever the clients contact the server through a Java based client (like SoapUI) they are getting a valid response back.
But when they use a .NET client, the response that goes back has some strange characters in the XML.
Ex:

1f40

<?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><SomeResponse xmlns="http://abc.com/ws/indicationsxsd">
"><SortS
c0
eqNbr>110


As you can see, there are some spurious characters (1f40 and c0) that are getting added to the response.
I checked the jboss logs and our own logging system of when the response gets built and these cahracters are not there, but when wee do a packet dump at the TCP level these are showing up.

I am at wits' end figuring out what is happening. Has anyone encountered this issue?

Any help appreciated
Thanks
Karthik
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Apache 2 , Jboss issues
 
Similar Threads
encoding in java
Namespace problem in xslt
Soap format
WSDL issues
Optional operation parameters (long types)