Re: [ebxmlms-develop] SOAPException: Unable to internalize messag e (Invalid Content-Typ e:text/html)

[Patrick Y. <kc...@ce...>]

RE: [ebxmlms-develop] SOAPException: Unable to internalize messag e =
(Invalid Content-Typ e:text/html)Peter,

Please get CVS to work in your place. It worths. :-)

A. We change the class =
hk.hku.cecid.phoenix.message.transport.HttpServlet. When it is about to =
send the SOAP message out, we modify the content type header to make it =
a single line. Here is the trick: don't call saveChanges() to the SOAP =
message. Calling saveChanges() will make the library generate a wrapped =
header again.

B. Sorry my bad English sometimes causes misunderstanding. Deployment is =
OK. But according to our experiment, when Websphere receives a HTTP =
request with wrapper header, it will generate a 400 Bad Request response =
to the sender.

Regards, -Patrick

  ----- Original Message -----=20
  From: Mayne, Peter=20
  To: 'ebx...@li...'=20
  Sent: Friday, March 21, 2003 6:21 AM
  Subject: RE: [ebxmlms-develop] SOAPException: Unable to internalize =
messag e (Invalid Content-Typ e:text/html)


  Doh! :-)=20

  CVS? Used it a long time ago, can't remember how it works, and I =
probably couldn't get it through our firewall if I could.

  As a matter of interest,=20

  a) where did you make the change (not that it matters)=20
  b) why does producing a wrapped header stop deployment into WebSphere =
Application Server?=20

  PJDM=20
  --=20
  Peter Mayne=20
  Technology Consultant=20
  Spherion Technology Solutions=20
  Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602=20
  T: 61 2 62689727  F: 61 2 62689777=20

  -----Original Message-----=20
  From: Patrick Yee [mailto:kc...@ce...]=20
  Sent: Thursday, 20 March 2003 8:54 PM=20
  To: ebx...@li...=20
  Subject: Re: [ebxmlms-develop] SOAPException: Unable to internalize =
messag e (Invalid Content-Typ e:text/html)=20



  Peter,=20

  Thank you for your note.=20

  Please check out the latest CVS source tree and try again. We have =
committed the change to make the Content-Type not wrapped. What a =
coincident! We have made the change to get Hermes deployable in =
Websphere.

  Regards, -Patrick=20

The information contained in this email and any attachments to it:

(a) may be confidential and if you are not the intended recipient, any =
interference with,=20
use, disclosure or copying of this material is unauthorised and =
prohibited; and

(b) may contain personal information of the recipient and/or the sender =
as defined=20
under the Privacy Act 1988 (Cth). Consent is hereby given by the =
recipient(s) to=20
collect, hold and use such information and any personal information =
contained in a=20
response to this email, for any reasonable purpose in the ordinary =
course of=20
Spherion's=20
business, including forwarding this email internally or disclosing it to =
a third party. All=20
personal information collected by Spherion will be handled in accordance =
with=20
Spherion's Privacy Policy. If you have received this email in error, =
please notify the=20
sender and delete it.

(c) you agree not to employ or arrange employment for any candidate(s) =
supplied in=20
this email and any attachments without first entering into a contractual =
agreement with=20
Spherion. You further agree not to divulge any information contained in =
this document=20
to any person(s) or entities without the express permission of Spherion.