ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Can we call SOAP 1.2 Webservice from HTTP Request Node

Post new topic  Reply to topic
 Can we call SOAP 1.2 Webservice from HTTP Request Node « View previous topic :: View next topic » 
Author Message
kartheek.sp
PostPosted: Fri Feb 28, 2014 2:41 am    Post subject: Can we call SOAP 1.2 Webservice from HTTP Request Node Reply with quote

Novice

Joined: 05 Apr 2011
Posts: 21
Location: Pune

I am calling a webservice which is of SOAP 1.2 from HTTP Request and getting error as Unsupported Media Type HTTP Code 415.

After searching the forum it is there as SOAP Request Node will support SOAP 1.2

As we have problem in creating a MessageSet with wsdl provided , we have used HTTP Request.

Can anyone let me know whether SOAP 1.2 will be called from HTTP Request Node or not.
_________________
Siva
***********
Back to top
View user's profile Send private message
Gralgrathor
PostPosted: Fri Feb 28, 2014 2:57 am    Post subject: Re: Can we call SOAP 1.2 Webservice from HTTP Request Node Reply with quote

Master

Joined: 23 Jul 2009
Posts: 297

kartheek.sp wrote:
problem in creating a MessageSet with wsdl provided


Have you tried tweaking the WSDL to get a valid contract that is still semantically equivalent to the WSDL provided? Can you discuss alterations in the WSDL with the party providing it?
_________________
A measure of wheat for a penny, and three measures of barley for a penny; and see thou hurt not the oil and the wine.
Back to top
View user's profile Send private message Send e-mail
kartheek.sp
PostPosted: Fri Feb 28, 2014 3:00 am    Post subject: Reply with quote

Novice

Joined: 05 Apr 2011
Posts: 21
Location: Pune

The Providing party is not ready to change the WSDL and they developed WSDL in JDeveloper.

And the same WSDL is compliant in SOAPUI also.
_________________
Siva
***********
Back to top
View user's profile Send private message
Gralgrathor
PostPosted: Fri Feb 28, 2014 3:19 am    Post subject: Reply with quote

Master

Joined: 23 Jul 2009
Posts: 297

kartheek.sp wrote:
And the same WSDL is compliant in SOAPUI


Okay, so no W3C issues, it's just the WMB Toolkit that can't deal with it?

What kind of issues does it have with the WSDL? Exceptions? Or does it simply not import correctly?
_________________
A measure of wheat for a penny, and three measures of barley for a penny; and see thou hurt not the oil and the wine.
Back to top
View user's profile Send private message Send e-mail
mqjeff
PostPosted: Fri Feb 28, 2014 5:36 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Different versions of IIB and MB provide different levels of support for SOAP standards.
Back to top
View user's profile Send private message
Armageddon123
PostPosted: Sat Mar 01, 2014 12:03 am    Post subject: Reply with quote

Acolyte

Joined: 11 Feb 2014
Posts: 61

my humble opinion

Why dont you use Gateway mode of the SoapRequest node?

Quote:
In Gateway mode, the SOAP nodes send SOAP 1.1 messages by default, although they also accept inbound SOAP 1.2 messages. To send an outbound SOAP 1.2 message, set the SOAP.Context field to indicate that SOAP 1.2 is required. For example, to set this field using ESQL:

SET OutputRoot.SOAP.Context.SOAP_Version = '1.2';

The outbound message then uses a SOAP 1.2 SOAP Envelope. You can also set the namespace prefix used by the SOAP Envelope. For example, by using ESQL:

DECLARE soapenc NAMESPACE 'http://www.w3.org/2003/05/soap-envelope';
SET OutputRoot.SOAP.Context.Namespace.(SOAP.NamespaceDecl)xmlns:soap12 = soapenc;
SET OutputRoot.SOAP.Context.SOAP_Version = '1.2';
Back to top
View user's profile Send private message
kartheek.sp
PostPosted: Tue Mar 04, 2014 9:22 am    Post subject: Reply with quote

Novice

Joined: 05 Apr 2011
Posts: 21
Location: Pune

Quote:
What kind of issues does it have with the WSDL? Exceptions? Or does it simply not import correctly?


It shows errors related to bindings and port type.

@Armageddon, As i have dont have a proper Messageset because of incorrect wsdl so i am trying to call the the webservice from HTTP Request Node and getting error as Unsupported Media Type HTTP Code 415.

And i am able to call this Webservice from our Datapower Box.
_________________
Siva
***********
Back to top
View user's profile Send private message
Armageddon123
PostPosted: Thu Mar 06, 2014 4:24 am    Post subject: Reply with quote

Acolyte

Joined: 11 Feb 2014
Posts: 61

In Gateway mode, you dont need a WSDL...
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Mar 06, 2014 6:07 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Fix the wsdl and give it a real target. Regenerate the bindings. Then import the wsdl again...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Can we call SOAP 1.2 Webservice from HTTP Request Node
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.