subject:"RE\: retrieving MTOM in a client"

RE: retrieving MTOM in a client

2008-02-19 Thread Etches, Adam (GE Infra, Energy)

Hi,

The server I'm running on is JBOSS 4.0.3SP1. Here is the complete HTTP response.

Adam


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
Content-Type: application/xml;charset=UTF-8
Transfer-Encoding: chunked
Date: Mon, 18 Feb 2008 11:37:15 GMT
 
494
--MIMEBoundaryurn_uuid_4DDAF973E789AF02831203334635830
Content-Type: application/xop+xml; charset=UTF-8; type=application/soap+xml
Content-Transfer-Encoding: binary
Content-ID: 0.urn:uuid:[EMAIL PROTECTED]
 
ns:mapResponse 
xmlns:ns=http://samples.webservice.gss/xsd;ns:returnns:mapns:map_return_typens:display_style_nameAuto/ns:display_style_name
ns:crsuk_british_national_grid_mm/ns:crsns:centre283355000.00,542605000.00/ns:centrens:image_layers{sw_map=com.gesmallworld.gss.ser
[EMAIL 
PROTECTED]/ns:image_layersns:unitsmm/ns:unitsns:style_groupdefault/ns:style_groupns:options{}/ns:optionsns:view
_scale9846153.846153846/ns:view_scalens:rotation0.0/ns:rotationns:map_element_keyswrefVdisplay_styleVidZ0Q1/ns:map_element_keyns:worldswr
efVworldVdatasetZgisVuniverseZ0VworldZ0/ns:worldns:ace_namedefault/ns:ace_namens:namesw_default/ns:namens:map_imagexop:Include
 href=cid:
1.urn:uuid:[EMAIL PROTECTED] xmlns:xop=http://www.w3.org/2004/08/xop/include; 
//ns:map_image/ns:map_return_type/ns:ma
p/ns:return/ns:mapResponse
38
 
--MIMEBoundaryurn_uuid_4DDAF973E789AF02831203334635830
59d
 
Content-Type: image/jpeg
Content-Transfer-Encoding: binary
Content-ID: 1.urn:uuid:[EMAIL PROTECTED]
 
►JFIFC
 ♠
 
 
 

↔§▬#▼%$▼!+7/)4)!0A149;%.DICH7=;C☺


.REMOVED REST OF BINARY FILE...


 

-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED] 
Sent: 19 February 2008 02:54
To: axis-user@ws.apache.org
Subject: Re: retrieving MTOM in a client

Hi,
the content type should be as follows..
Content-Type: Multipart/Related;boundary=your_MIME_boundary;
type=application/xop+xml;start=...

Looks like Axis2 does not recognize your message as a MTOM message..It should 
print the binary payload in base64 encoding if it does, not the xop:Include 
element..

What is your server.. Can you post the full HTTP Headers...

thanks,
Thilina


On Feb 18, 2008 10:50 AM, Etches, Adam (GE Infra, Energy) [EMAIL PROTECTED] 
wrote:




 Hi,

 The http headers have the content-type set to application/xop+xml, this 
 seems incorrect should it be multipart? Below is the system print of the 
 mapImage element:

 ns:map_image 
 xmlns:ns=http://samples.webservice.gss/xsd;xop:Include 
 xmlns:xop=http://www.w3.org/2004/08/xop/include; 
 href=cid:1.urn:uuid:[EMAIL PROTECTED] 
 //ns:map_image

 thanks for the help.

 Adam

 
 From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
 Sent: 16 February 2008 13:49



 To: axis-user@ws.apache.org
 Subject: Re: retrieving MTOM in a client





 Hi,
 The SOAP Message looks fine...

 Can you also look at the HTTPHeaders.. Specially the content-type header and 
 see whether it has multipart/related and type=application/xop+xml I 
 doubt whether something is wrong in the content type and Axis2 cannot 
 recognize it as a MTOM message..

 Also try printing the content of the mapImage element using 
 mapImage.toString()...

 thanks,
 Thilina


 On Feb 13, 2008 11:31 AM, Etches, Adam (GE Infra, Energy) [EMAIL PROTECTED] 
 wrote:

  Thanks Thilina, the SOAP message is below: I'm sure the client 
  worked once but then stopped?  The client code extract is:
 
 
 OMText binaryNode = (OMText) mapImage.getFirstOMChild();
 
 DataHandler actualDH = (DataHandler) 
  binaryNode.getDataHandler();
 
  soapenv:Envelope
  xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
soapenv:Body
   ns:mapResponse xmlns:ns=http://samples.webservice.gss/xsd;
  ns:return
 ns:map
ns:map_return_type
   ns:display_style_nameRegion/ns:display_style_name
   ns:crsuk_british_national_grid_mm/ns:crs
 
  ns:centre546307392.00,258873636.00/ns:centre
 
  ns:image_layers{sw_map=com.gesmallworld.gss.services.map.MapLayerR
  espo
  [EMAIL PROTECTED]/ns:image_layers
   ns:unitsmm/ns:units
   ns:style_groupdefault/ns:style_group
   ns:options{}/ns:options
   ns:view_scale127020.02565384615/ns:view_scale
   ns:rotation0.0/ns:rotation
 
  ns:map_element_keyswrefVdisplay_styleVidZ0Q6/ns:map_element_key
 
  ns:worldswrefVworldVdatasetZgisVuniverseZ0VworldZ0/ns:world
   ns:ace_namedefault/ns:ace_name
   ns:nametest/ns:name
   ns:map_image
  xop:Include
  href=cid:1.urn:uuid:[EMAIL PROTECTED]
  xmlns:xop=http://www.w3.org/2004/08/xop/include/
   /ns:map_image
/ns:map_return_type
 /ns:map
  /ns:return
   /ns:mapResponse
/soapenv:Body

Re: retrieving MTOM in a client

2008-02-19 Thread Thilina Gunarathne

Hi,
As I expected, the content-type http header is incorrect.. See here[1]
for an example from the spec..

 Content-Type: application/xml;charset=UTF-8
This should be as follows,

Content-Type: Multipart/Related;
boundary=MIMEBoundaryurn_uuid_4DDAF973E789AF02831203334635830;type=application/xop+xml;start=...;

What surprises me is the fact that, Axis2 extracted the SOAP message
without knowing the Mime Boundary :).

thanks,
Thilina

[1] http://www.w3.org/TR/2004/PR-xop10-20041116/#xop_package_svg_sample

 Transfer-Encoding: chunked
 Date: Mon, 18 Feb 2008 11:37:15 GMT

 494
 --MIMEBoundaryurn_uuid_4DDAF973E789AF02831203334635830
 Content-Type: application/xop+xml; charset=UTF-8; type=application/soap+xml
 Content-Transfer-Encoding: binary
 Content-ID: 0.urn:uuid:[EMAIL PROTECTED]

 ns:mapResponse 
 xmlns:ns=http://samples.webservice.gss/xsd;ns:returnns:mapns:map_return_typens:display_style_nameAuto/ns:display_style_name
 ns:crsuk_british_national_grid_mm/ns:crsns:centre283355000.00,542605000.00/ns:centrens:image_layers{sw_map=com.gesmallworld.gss.ser
 [EMAIL 
 PROTECTED]/ns:image_layersns:unitsmm/ns:unitsns:style_groupdefault/ns:style_groupns:options{}/ns:optionsns:view
 _scale9846153.846153846/ns:view_scalens:rotation0.0/ns:rotationns:map_element_keyswrefVdisplay_styleVidZ0Q1/ns:map_element_keyns:worldswr
 efVworldVdatasetZgisVuniverseZ0VworldZ0/ns:worldns:ace_namedefault/ns:ace_namens:namesw_default/ns:namens:map_imagexop:Include
  href=cid:
 1.urn:uuid:[EMAIL PROTECTED] 
 xmlns:xop=http://www.w3.org/2004/08/xop/include; 
 //ns:map_image/ns:map_return_type/ns:ma
 p/ns:return/ns:mapResponse
 38

 --MIMEBoundaryurn_uuid_4DDAF973E789AF02831203334635830
 59d

 Content-Type: image/jpeg
 Content-Transfer-Encoding: binary
 Content-ID: 1.urn:uuid:[EMAIL PROTECTED]

 ►JFIFC
  ♠




 ↔§▬#▼%$▼!+7/)4)!0A149;%.DICH7=;C☺


 .REMOVED REST OF BINARY FILE...




 -Original Message-
 From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]

 Sent: 19 February 2008 02:54
 To: axis-user@ws.apache.org
 Subject: Re: retrieving MTOM in a client

 Hi,
 the content type should be as follows..
 Content-Type: Multipart/Related;boundary=your_MIME_boundary;
 type=application/xop+xml;start=...

 Looks like Axis2 does not recognize your message as a MTOM message..It should 
 print the binary payload in base64 encoding if it does, not the xop:Include 
 element..

 What is your server.. Can you post the full HTTP Headers...

 thanks,
 Thilina


 On Feb 18, 2008 10:50 AM, Etches, Adam (GE Infra, Energy) [EMAIL PROTECTED] 
 wrote:
 
 
 
 
  Hi,
 
  The http headers have the content-type set to application/xop+xml, this 
  seems incorrect should it be multipart? Below is the system print of the 
  mapImage element:
 
  ns:map_image
  xmlns:ns=http://samples.webservice.gss/xsd;xop:Include
  xmlns:xop=http://www.w3.org/2004/08/xop/include;
  href=cid:1.urn:uuid:[EMAIL PROTECTED]
  //ns:map_image
 
  thanks for the help.
 
  Adam
 
  
  From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
  Sent: 16 February 2008 13:49
 
 
 
  To: axis-user@ws.apache.org
  Subject: Re: retrieving MTOM in a client
 
 
 
 
 
  Hi,
  The SOAP Message looks fine...
 
  Can you also look at the HTTPHeaders.. Specially the content-type header 
  and see whether it has multipart/related and 
  type=application/xop+xml I doubt whether something is wrong in the 
  content type and Axis2 cannot recognize it as a MTOM message..
 
  Also try printing the content of the mapImage element using 
  mapImage.toString()...
 
  thanks,
  Thilina
 
 
  On Feb 13, 2008 11:31 AM, Etches, Adam (GE Infra, Energy) [EMAIL 
  PROTECTED] wrote:
 
   Thanks Thilina, the SOAP message is below: I'm sure the client
   worked once but then stopped?  The client code extract is:
  
  
  OMText binaryNode = (OMText) mapImage.getFirstOMChild();
  
  DataHandler actualDH = (DataHandler)
   binaryNode.getDataHandler();
  
   soapenv:Envelope
   xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
 soapenv:Body
ns:mapResponse xmlns:ns=http://samples.webservice.gss/xsd;
   ns:return
  ns:map
 ns:map_return_type
ns:display_style_nameRegion/ns:display_style_name
ns:crsuk_british_national_grid_mm/ns:crs
  
   ns:centre546307392.00,258873636.00/ns:centre
  
   ns:image_layers{sw_map=com.gesmallworld.gss.services.map.MapLayerR
   espo
   [EMAIL PROTECTED]/ns:image_layers
ns:unitsmm/ns:units
ns:style_groupdefault/ns:style_group
ns:options{}/ns:options
ns:view_scale127020.02565384615/ns:view_scale
ns:rotation0.0/ns:rotation
  
   ns:map_element_keyswrefVdisplay_styleVidZ0Q6/ns:map_element_key
  
   ns:worldswrefVworldVdatasetZgisVuniverseZ0VworldZ0/ns:world
ns:ace_namedefault/ns:ace_name

RE: retrieving MTOM in a client

2008-02-19 Thread Etches, Adam (GE Infra, Energy)

Thanks, Any ideas where this is configured or set up?

Adam 

-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED] 
Sent: 19 February 2008 12:29
To: axis-user@ws.apache.org
Subject: Re: retrieving MTOM in a client

Hi,
As I expected, the content-type http header is incorrect.. See here[1] for an 
example from the spec..

 Content-Type: application/xml;charset=UTF-8
This should be as follows,

Content-Type: Multipart/Related;
boundary=MIMEBoundaryurn_uuid_4DDAF973E789AF02831203334635830;type=application/xop+xml;start=...;

What surprises me is the fact that, Axis2 extracted the SOAP message without 
knowing the Mime Boundary :).

thanks,
Thilina

[1] http://www.w3.org/TR/2004/PR-xop10-20041116/#xop_package_svg_sample

 Transfer-Encoding: chunked
 Date: Mon, 18 Feb 2008 11:37:15 GMT

 494
 --MIMEBoundaryurn_uuid_4DDAF973E789AF02831203334635830
 Content-Type: application/xop+xml; charset=UTF-8; type=application/soap+xml
 Content-Transfer-Encoding: binary
 Content-ID: 0.urn:uuid:[EMAIL PROTECTED]

 ns:mapResponse 
 xmlns:ns=http://samples.webservice.gss/xsd;ns:returnns:mapns:ma
 p_return_typens:display_style_nameAuto/ns:display_style_name
 ns:crsuk_british_national_grid_mm/ns:crsns:centre283355000.
 00,542605000.00/ns:centrens:image_layers{sw_map=com.gesmallwo
 rld.gss.ser
 [EMAIL PROTECTED]/ns:image_layersns:unitsmm/ns:u
 nitsns:style_groupdefault/ns:style_groupns:options{}/ns:option
 sns:view 
 _scale9846153.846153846/ns:view_scalens:rotation0.0/ns:rotation
 ns:map_element_keyswrefVdisplay_styleVidZ0Q1/ns:map_element_keyns
 :worldswr 
 efVworldVdatasetZgisVuniverseZ0VworldZ0/ns:worldns:ace_namedefault/ns:ace_namens:namesw_default/ns:namens:map_imagexop:Include
  href=cid:
 1.urn:uuid:[EMAIL PROTECTED] 
 xmlns:xop=http://www.w3.org/2004/08/xop/include; 
 //ns:map_image/ns:map_return_type/ns:ma
 p/ns:return/ns:mapResponse
 38

 --MIMEBoundaryurn_uuid_4DDAF973E789AF02831203334635830
 59d

 Content-Type: image/jpeg
 Content-Transfer-Encoding: binary
 Content-ID: 1.urn:uuid:[EMAIL PROTECTED]

 ►JFIFC
  ♠

 ↔§▬#▼%$▼!+7/)4)!0A149;%.DICH7=;C☺

 .REMOVED REST OF BINARY FILE...

 -Original Message-
 From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]

 Sent: 19 February 2008 02:54
 To: axis-user@ws.apache.org
 Subject: Re: retrieving MTOM in a client

 Hi,
 the content type should be as follows..
 Content-Type: Multipart/Related;boundary=your_MIME_boundary;
 type=application/xop+xml;start=...

 Looks like Axis2 does not recognize your message as a MTOM message..It should 
 print the binary payload in base64 encoding if it does, not the xop:Include 
 element..

 What is your server.. Can you post the full HTTP Headers...

 thanks,
 Thilina

 On Feb 18, 2008 10:50 AM, Etches, Adam (GE Infra, Energy) [EMAIL PROTECTED] 
 wrote:

  Hi,

  The http headers have the content-type set to application/xop+xml, this 
  seems incorrect should it be multipart? Below is the system print of the 
  mapImage element:

  ns:map_image
  xmlns:ns=http://samples.webservice.gss/xsd;xop:Include
  xmlns:xop=http://www.w3.org/2004/08/xop/include;
  href=cid:1.urn:uuid:[EMAIL PROTECTED]
  //ns:map_image

  thanks for the help.

  Adam

  From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
  Sent: 16 February 2008 13:49

  To: axis-user@ws.apache.org
  Subject: Re: retrieving MTOM in a client

  Hi,
  The SOAP Message looks fine...

  Can you also look at the HTTPHeaders.. Specially the content-type header 
  and see whether it has multipart/related and 
  type=application/xop+xml I doubt whether something is wrong in the 
  content type and Axis2 cannot recognize it as a MTOM message..

  Also try printing the content of the mapImage element using 
  mapImage.toString()...

  thanks,
  Thilina

  On Feb 13, 2008 11:31 AM, Etches, Adam (GE Infra, Energy) [EMAIL 
  PROTECTED] wrote:

   Thanks Thilina, the SOAP message is below: I'm sure the client 
   worked once but then stopped?  The client code extract is:

  OMText binaryNode = (OMText) mapImage.getFirstOMChild();

  DataHandler actualDH = (DataHandler) 
   binaryNode.getDataHandler();

   soapenv:Envelope
   xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
 soapenv:Body
ns:mapResponse xmlns:ns=http://samples.webservice.gss/xsd;
   ns:return
  ns:map
 ns:map_return_type
ns:display_style_nameRegion/ns:display_style_name
ns:crsuk_british_national_grid_mm/ns:crs

   ns:centre546307392.00,258873636.00/ns:centre

   ns:image_layers{sw_map=com.gesmallworld.gss.services.map.MapLaye
   rR
   espo
   [EMAIL PROTECTED]/ns:image_layers
ns:unitsmm/ns:units
ns:style_groupdefault/ns:style_group
ns:options{}/ns:options

Re: retrieving MTOM in a client

2008-02-19 Thread Thilina Gunarathne

It is the web service engine which host your web service. No idea
about how to do it in Jboss..

But it definitely looks like a huge bug to me, as the server sends out
a MIME/Multipart message, without putting the Mime/multipart content
type and the boundary in the http headers. It's virtually impossible
to process such a message correctly by any client..

~Thilina

On Feb 19, 2008 7:37 AM, Etches, Adam (GE Infra, Energy)
[EMAIL PROTECTED] wrote:
 Thanks, Any ideas where this is configured or set up?

 Adam

 -Original Message-
 From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
 Sent: 19 February 2008 12:29
 To: axis-user@ws.apache.org
 Subject: Re: retrieving MTOM in a client

 Hi,

 As I expected, the content-type http header is incorrect.. See here[1] for an 
 example from the spec..

  Content-Type: application/xml;charset=UTF-8
 This should be as follows,

 Content-Type: Multipart/Related;
 boundary=MIMEBoundaryurn_uuid_4DDAF973E789AF02831203334635830;type=application/xop+xml;start=...;

 What surprises me is the fact that, Axis2 extracted the SOAP message without 
 knowing the Mime Boundary :).

 thanks,
 Thilina

 [1] http://www.w3.org/TR/2004/PR-xop10-20041116/#xop_package_svg_sample

  Transfer-Encoding: chunked
  Date: Mon, 18 Feb 2008 11:37:15 GMT
 
  494
  --MIMEBoundaryurn_uuid_4DDAF973E789AF02831203334635830
  Content-Type: application/xop+xml; charset=UTF-8; 
  type=application/soap+xml
  Content-Transfer-Encoding: binary
  Content-ID: 0.urn:uuid:[EMAIL PROTECTED]
 
  ns:mapResponse
  xmlns:ns=http://samples.webservice.gss/xsd;ns:returnns:mapns:ma
  p_return_typens:display_style_nameAuto/ns:display_style_name
  ns:crsuk_british_national_grid_mm/ns:crsns:centre283355000.
  00,542605000.00/ns:centrens:image_layers{sw_map=com.gesmallwo
  rld.gss.ser
  [EMAIL PROTECTED]/ns:image_layersns:unitsmm/ns:u
  nitsns:style_groupdefault/ns:style_groupns:options{}/ns:option
  sns:view
  _scale9846153.846153846/ns:view_scalens:rotation0.0/ns:rotation
  ns:map_element_keyswrefVdisplay_styleVidZ0Q1/ns:map_element_keyns
  :worldswr
  efVworldVdatasetZgisVuniverseZ0VworldZ0/ns:worldns:ace_namedefault/ns:ace_namens:namesw_default/ns:namens:map_imagexop:Include
   href=cid:
  1.urn:uuid:[EMAIL PROTECTED]
  xmlns:xop=http://www.w3.org/2004/08/xop/include;
  //ns:map_image/ns:map_return_type/ns:ma
  p/ns:return/ns:mapResponse
  38
 
  --MIMEBoundaryurn_uuid_4DDAF973E789AF02831203334635830
  59d
 
  Content-Type: image/jpeg
  Content-Transfer-Encoding: binary
  Content-ID: 1.urn:uuid:[EMAIL PROTECTED]
 
  ►JFIFC
   ♠
 
 
 
 
  ↔§▬#▼%$▼!+7/)4)!0A149;%.DICH7=;C☺
 
 
  .REMOVED REST OF BINARY FILE...
 
 
 
 
  -Original Message-
  From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
 
  Sent: 19 February 2008 02:54
  To: axis-user@ws.apache.org
  Subject: Re: retrieving MTOM in a client
 
  Hi,
  the content type should be as follows..
  Content-Type: Multipart/Related;boundary=your_MIME_boundary;
  type=application/xop+xml;start=...
 
  Looks like Axis2 does not recognize your message as a MTOM message..It 
  should print the binary payload in base64 encoding if it does, not the 
  xop:Include element..
 
  What is your server.. Can you post the full HTTP Headers...
 
  thanks,
  Thilina
 
 
  On Feb 18, 2008 10:50 AM, Etches, Adam (GE Infra, Energy) [EMAIL 
  PROTECTED] wrote:
  
  
  
  
   Hi,
  
   The http headers have the content-type set to application/xop+xml, this 
   seems incorrect should it be multipart? Below is the system print of the 
   mapImage element:
  
   ns:map_image
   xmlns:ns=http://samples.webservice.gss/xsd;xop:Include
   xmlns:xop=http://www.w3.org/2004/08/xop/include;
   href=cid:1.urn:uuid:[EMAIL PROTECTED]
   //ns:map_image
  
   thanks for the help.
  
   Adam
  
   
   From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
   Sent: 16 February 2008 13:49
  
  
  
   To: axis-user@ws.apache.org
   Subject: Re: retrieving MTOM in a client
  
  
  
  
  
   Hi,
   The SOAP Message looks fine...
  
   Can you also look at the HTTPHeaders.. Specially the content-type header 
   and see whether it has multipart/related and 
   type=application/xop+xml I doubt whether something is wrong in the 
   content type and Axis2 cannot recognize it as a MTOM message..
  
   Also try printing the content of the mapImage element using 
   mapImage.toString()...
  
   thanks,
   Thilina
  
  
   On Feb 13, 2008 11:31 AM, Etches, Adam (GE Infra, Energy) [EMAIL 
   PROTECTED] wrote:
  
Thanks Thilina, the SOAP message is below: I'm sure the client
worked once but then stopped?  The client code extract is:
   
   
   OMText binaryNode = (OMText) mapImage.getFirstOMChild();
   
   DataHandler actualDH = (DataHandler)
binaryNode.getDataHandler();
   
soapenv:Envelope
xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
  soapenv:Body
 ns:mapResponse xmlns:ns=http

RE: retrieving MTOM in a client

2008-02-18 Thread Etches, Adam (GE Infra, Energy)

Hi, 

The http headers have the content-type set to application/xop+xml,
this seems incorrect should it be multipart? Below is the system print
of the mapImage element:

ns:map_image xmlns:ns=http://samples.webservice.gss/xsd;xop:Include
xmlns:xop=http://www.w3.org/2004/08/xop/include;
href=cid:1.urn:uuid:[EMAIL PROTECTED]
//ns:map_image

thanks for the help.

Adam



  _  

From: Thilina Gunarathne [mailto:[EMAIL PROTECTED] 
Sent: 16 February 2008 13:49
To: axis-user@ws.apache.org
Subject: Re: retrieving MTOM in a client


Hi,
The SOAP Message looks fine...  

Can you also look at the HTTPHeaders.. Specially the content-type header
and see whether it has multipart/related and
type=application/xop+xml I doubt whether something is wrong in the
content type and Axis2 cannot recognize it as a MTOM message..

Also try printing the content of the mapImage element using
mapImage.toString()...

thanks,
Thilina


On Feb 13, 2008 11:31 AM, Etches, Adam (GE Infra, Energy)
[EMAIL PROTECTED] wrote:


Thanks Thilina, the SOAP message is below: I'm sure the client
worked
once but then stopped?  The client code extract is:


   OMText binaryNode = (OMText) mapImage.getFirstOMChild();


   DataHandler actualDH = (DataHandler)
binaryNode.getDataHandler();

soapenv:Envelope
xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
  soapenv:Body
 ns:mapResponse
xmlns:ns=http://samples.webservice.gss/xsd;
ns:return
   ns:map
  ns:map_return_type

ns:display_style_nameRegion/ns:display_style_name
 ns:crsuk_british_national_grid_mm/ns:crs

ns:centre546307392.00,258873636.00/ns:centre


ns:image_layers{sw_map=com.gesmallworld.gss.services.map.MapLayerRespo
[EMAIL PROTECTED]/ns:image_layers
 ns:unitsmm/ns:units
 ns:style_groupdefault/ns:style_group
 ns:options{}/ns:options

ns:view_scale127020.02565384615/ns:view_scale
 ns:rotation0.0/ns:rotation


ns:map_element_keyswrefVdisplay_styleVidZ0Q6/ns:map_element_key

ns:worldswrefVworldVdatasetZgisVuniverseZ0VworldZ0/ns:world
 ns:ace_namedefault/ns:ace_name
 ns:nametest/ns:name
 ns:map_image
xop:Include
href=cid:1.urn:uuid:[EMAIL PROTECTED]
xmlns:xop=http://www.w3.org/2004/08/xop/include/
 /ns:map_image
  /ns:map_return_type
   /ns:map
/ns:return
 /ns:mapResponse
  /soapenv:Body
/soapenv:Envelope


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 13 February 2008 14:48
To: axis-user@ws.apache.org
Subject: Re: retrieving MTOM in a client

Hi Adam,
It would be helpfull if you post the SOAP message...

Thilina

On 2/12/08, Etches, Adam (GE Infra, Energy) [EMAIL PROTECTED]
wrote:


 I'm using MTOM in a java client but when I try to retrieve the
OMText
 at the client side i.e.:



 OMText binaryNode = (OMText) mapImage.getFirstOMChild();



 I get a class cast exception, since the response is returning
an
 OMElement and not OMText  anyone come across this before?



 I've checked the soap message and it does actually include the
binary
 data.



 Thanks in advance

 Adam






--
Thilina Gunarathne  - http://thilinag.blogspot.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






-- 
Thilina Gunarathne  - http://thilinag.blogspot.com

Re: retrieving MTOM in a client

2008-02-18 Thread Thilina Gunarathne

Hi,
the content type should be as follows..
Content-Type: Multipart/Related;boundary=your_MIME_boundary;
type=application/xop+xml;start=...

Looks like Axis2 does not recognize your message as a MTOM message..It
should print the binary payload in base64 encoding if it does, not the
xop:Include element..

What is your server.. Can you post the full HTTP Headers...

thanks,
Thilina


On Feb 18, 2008 10:50 AM, Etches, Adam (GE Infra, Energy)
[EMAIL PROTECTED] wrote:




 Hi,

 The http headers have the content-type set to application/xop+xml, this 
 seems incorrect should it be multipart? Below is the system print of the 
 mapImage element:

 ns:map_image xmlns:ns=http://samples.webservice.gss/xsd;xop:Include 
 xmlns:xop=http://www.w3.org/2004/08/xop/include; href=cid:1.urn:uuid:[EMAIL 
 PROTECTED] //ns:map_image

 thanks for the help.

 Adam

 
 From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
 Sent: 16 February 2008 13:49



 To: axis-user@ws.apache.org
 Subject: Re: retrieving MTOM in a client





 Hi,
 The SOAP Message looks fine...

 Can you also look at the HTTPHeaders.. Specially the content-type header and 
 see whether it has multipart/related and type=application/xop+xml I 
 doubt whether something is wrong in the content type and Axis2 cannot 
 recognize it as a MTOM message..

 Also try printing the content of the mapImage element using 
 mapImage.toString()...

 thanks,
 Thilina


 On Feb 13, 2008 11:31 AM, Etches, Adam (GE Infra, Energy) [EMAIL PROTECTED] 
 wrote:

  Thanks Thilina, the SOAP message is below: I'm sure the client worked
  once but then stopped?  The client code extract is:
 
 
 OMText binaryNode = (OMText) mapImage.getFirstOMChild();
 
 DataHandler actualDH = (DataHandler)
  binaryNode.getDataHandler();
 
  soapenv:Envelope
  xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
soapenv:Body
   ns:mapResponse xmlns:ns=http://samples.webservice.gss/xsd;
  ns:return
 ns:map
ns:map_return_type
   ns:display_style_nameRegion/ns:display_style_name
   ns:crsuk_british_national_grid_mm/ns:crs
 
  ns:centre546307392.00,258873636.00/ns:centre
 
  ns:image_layers{sw_map=com.gesmallworld.gss.services.map.MapLayerRespo
  [EMAIL PROTECTED]/ns:image_layers
   ns:unitsmm/ns:units
   ns:style_groupdefault/ns:style_group
   ns:options{}/ns:options
   ns:view_scale127020.02565384615/ns:view_scale
   ns:rotation0.0/ns:rotation
 
  ns:map_element_keyswrefVdisplay_styleVidZ0Q6/ns:map_element_key
 
  ns:worldswrefVworldVdatasetZgisVuniverseZ0VworldZ0/ns:world
   ns:ace_namedefault/ns:ace_name
   ns:nametest/ns:name
   ns:map_image
  xop:Include
  href=cid:1.urn:uuid:[EMAIL PROTECTED]
  xmlns:xop=http://www.w3.org/2004/08/xop/include/
   /ns:map_image
/ns:map_return_type
 /ns:map
  /ns:return
   /ns:mapResponse
/soapenv:Body
  /soapenv:Envelope
 
 
 
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
  Sent: 13 February 2008 14:48
  To: axis-user@ws.apache.org
  Subject: Re: retrieving MTOM in a client
 
  Hi Adam,
  It would be helpfull if you post the SOAP message...
 
  Thilina
 
  On 2/12/08, Etches, Adam (GE Infra, Energy) [EMAIL PROTECTED] wrote:
  
  
   I'm using MTOM in a java client but when I try to retrieve the OMText
   at the client side i.e.:
  
  
  
   OMText binaryNode = (OMText) mapImage.getFirstOMChild();
  
  
  
   I get a class cast exception, since the response is returning an
   OMElement and not OMText  anyone come across this before?
  
  
  
   I've checked the soap message and it does actually include the binary
   data.
  
  
  
   Thanks in advance
  
   Adam
  
  
  
  
 
 
  --
  Thilina Gunarathne  - http://thilinag.blogspot.com
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 



 --
 Thilina Gunarathne  - http://thilinag.blogspot.com



-- 
Thilina Gunarathne  - http://thilinag.blogspot.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: retrieving MTOM in a client

2008-02-16 Thread Thilina Gunarathne

Hi,
The SOAP Message looks fine...

Can you also look at the HTTPHeaders.. Specially the content-type header and
see whether it has multipart/related and type=application/xop+xml I
doubt whether something is wrong in the content type and Axis2 cannot
recognize it as a MTOM message..

Also try printing the content of the mapImage element using
mapImage.toString()...

thanks,
Thilina

On Feb 13, 2008 11:31 AM, Etches, Adam (GE Infra, Energy) 
[EMAIL PROTECTED] wrote:

 Thanks Thilina, the SOAP message is below: I'm sure the client worked
 once but then stopped?  The client code extract is:

OMText binaryNode = (OMText) mapImage.getFirstOMChild();

DataHandler actualDH = (DataHandler)
 binaryNode.getDataHandler();

 soapenv:Envelope
 xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
   soapenv:Body
  ns:mapResponse xmlns:ns=http://samples.webservice.gss/xsd;
 ns:return
ns:map
   ns:map_return_type
  ns:display_style_nameRegion/ns:display_style_name
  ns:crsuk_british_national_grid_mm/ns:crs

 ns:centre546307392.00,258873636.00/ns:centre

 ns:image_layers{sw_map=com.gesmallworld.gss.services.map.MapLayerRespo
 [EMAIL PROTECTED]/ns:image_layers
  ns:unitsmm/ns:units
  ns:style_groupdefault/ns:style_group
  ns:options{}/ns:options
  ns:view_scale127020.02565384615/ns:view_scale
  ns:rotation0.0/ns:rotation

 ns:map_element_keyswrefVdisplay_styleVidZ0Q6/ns:map_element_key

 ns:worldswrefVworldVdatasetZgisVuniverseZ0VworldZ0/ns:world
  ns:ace_namedefault/ns:ace_name
  ns:nametest/ns:name
  ns:map_image
 xop:Include
 href=cid:1.urn:uuid:[EMAIL PROTECTED]
 xmlns:xop=http://www.w3.org/2004/08/xop/include/
  /ns:map_image
   /ns:map_return_type
/ns:map
 /ns:return
  /ns:mapResponse
   /soapenv:Body
 /soapenv:Envelope

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Sent: 13 February 2008 14:48
 To: axis-user@ws.apache.org
 Subject: Re: retrieving MTOM in a client

 Hi Adam,
 It would be helpfull if you post the SOAP message...

 Thilina

 On 2/12/08, Etches, Adam (GE Infra, Energy) [EMAIL PROTECTED] wrote:
 
 
  I'm using MTOM in a java client but when I try to retrieve the OMText
  at the client side i.e.:
 
 
 
  OMText binaryNode = (OMText) mapImage.getFirstOMChild();
 
 
 
  I get a class cast exception, since the response is returning an
  OMElement and not OMText  anyone come across this before?
 
 
 
  I've checked the soap message and it does actually include the binary
  data.
 
 
 
  Thanks in advance
 
  Adam
 
 
 
 


 --
 Thilina Gunarathne  - http://thilinag.blogspot.com

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-- 
Thilina Gunarathne  - http://thilinag.blogspot.com

Re: retrieving MTOM in a client

2008-02-13 Thread csethil

Hi Adam,
It would be helpfull if you post the SOAP message...

Thilina

On 2/12/08, Etches, Adam (GE Infra, Energy) [EMAIL PROTECTED] wrote:


 I'm using MTOM in a java client but when I try to retrieve the OMText at
 the client side i.e.:



 OMText binaryNode = (OMText) mapImage.getFirstOMChild();



 I get a class cast exception, since the response is returning an
 OMElement and not OMText  anyone come across this before?



 I've checked the soap message and it does actually include the binary
 data.



 Thanks in advance

 Adam






-- 
Thilina Gunarathne  - http://thilinag.blogspot.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: retrieving MTOM in a client

2008-02-13 Thread Etches, Adam (GE Infra, Energy)

Thanks Thilina, the SOAP message is below: I'm sure the client worked
once but then stopped?  The client code extract is:

OMText binaryNode = (OMText) mapImage.getFirstOMChild();

DataHandler actualDH = (DataHandler)
binaryNode.getDataHandler();

soapenv:Envelope
xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
   soapenv:Body
  ns:mapResponse xmlns:ns=http://samples.webservice.gss/xsd;
 ns:return
ns:map
   ns:map_return_type
  ns:display_style_nameRegion/ns:display_style_name
  ns:crsuk_british_national_grid_mm/ns:crs
 
ns:centre546307392.00,258873636.00/ns:centre
 
ns:image_layers{sw_map=com.gesmallworld.gss.services.map.MapLayerRespo
[EMAIL PROTECTED]/ns:image_layers
  ns:unitsmm/ns:units
  ns:style_groupdefault/ns:style_group
  ns:options{}/ns:options
  ns:view_scale127020.02565384615/ns:view_scale
  ns:rotation0.0/ns:rotation
 
ns:map_element_keyswrefVdisplay_styleVidZ0Q6/ns:map_element_key
 
ns:worldswrefVworldVdatasetZgisVuniverseZ0VworldZ0/ns:world
  ns:ace_namedefault/ns:ace_name
  ns:nametest/ns:name
  ns:map_image
 xop:Include
href=cid:1.urn:uuid:[EMAIL PROTECTED]
xmlns:xop=http://www.w3.org/2004/08/xop/include/
  /ns:map_image
   /ns:map_return_type
/ns:map
 /ns:return
  /ns:mapResponse
   /soapenv:Body
/soapenv:Envelope 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: 13 February 2008 14:48
To: axis-user@ws.apache.org
Subject: Re: retrieving MTOM in a client

Hi Adam,
It would be helpfull if you post the SOAP message...

Thilina

On 2/12/08, Etches, Adam (GE Infra, Energy) [EMAIL PROTECTED] wrote:


 I'm using MTOM in a java client but when I try to retrieve the OMText 
 at the client side i.e.:



 OMText binaryNode = (OMText) mapImage.getFirstOMChild();



 I get a class cast exception, since the response is returning an 
 OMElement and not OMText  anyone come across this before?



 I've checked the soap message and it does actually include the binary 
 data.



 Thanks in advance

 Adam






--
Thilina Gunarathne  - http://thilinag.blogspot.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: retrieving MTOM in a client

Re: retrieving MTOM in a client

RE: retrieving MTOM in a client

Re: retrieving MTOM in a client

RE: retrieving MTOM in a client

Re: retrieving MTOM in a client

Re: retrieving MTOM in a client

Re: retrieving MTOM in a client

RE: retrieving MTOM in a client

9 matches

Site Navigation

Mail list logo

Footer information