Skip to main content

Response package issues. Help please.

1 reply [Last post]
krasman
Offline
Joined: 2009-03-29
Points: 0

Hello,
Due to a port collision issue on our server I changed the default port to the glassfish server (was interfering with a JBoss appserver instance). Prior to the change in tests that didn't include the JBoss server, my Web Services services was working fine. Clients could reference the Wsdl and make calls, get responses as per normal. After this change something has gone wrong. Wsdl is published but calls are resulting in responses that now includes this:
Status Code: 200
Content Length : -1
Content Type: multipart/related;start="<rootpart*1a58d9a9-30e6-4304-9130-60c804507265@example.jaxws.sun.com>";type="application/xop+xml";boundary="uuid:1a58d9a9-30e6-4304-9130-60c804507265";start-info="text/xml"
Server: Sun GlassFish Enterprise Server v2.1
Status Description: OK

The content type has been changed as above and is resulting in unusable response data for many clients (php for 1) though my Java based testing client appears to be handling it fine.
Can anyone shed any light on this?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
krasman
Offline
Joined: 2009-03-29
Points: 0

As opposed to the previous header information that looks like this:
Status Code: 200
Content Length : -1
Content Type: text/xml;charset="utf-8"
Server: Sun GlassFish Enterprise Server v2.1.1
Status Description: OK