MQSeries.net :: View topic - SOAP requests + two wsdl file = deploy problem

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SOAP requests + two wsdl file = deploy problem

SOAP requests + two wsdl file = deploy problem

« View previous topic :: View next topic »

Author

Message

PiWer

Posted: Thu Aug 28, 2008 5:42 am Post subject: SOAP requests + two wsdl file = deploy problem

Newbie

Joined: 11 Jul 2008
Posts: 6

Situation:
- Message Broker 6.1
- One message set with two WSDL files, created with Spring WS 1.5.2, imported in the message set using: Message definition file from: WSDL file
- One flow with a SOAP request node that uses WSDL file 1.
- Second flow with a SOAP request node that uses WSDL file 2.

When I try to deploy the .bar file I have an error:

Code:

BIP4041E: Execution group 'a793-cargoweb2' received an invalid configuration message. See the following messages for details of the error.

BIP3734S: The message could not be found in resource bundle BIPv610. Inserts: cargowebwagons /var/mqsi/components/BRBA01T/0ea808ee-1a01-0000-0080-8fff11ab5618/config/XSD/CargoWeb2PocMessageSet/be/brail/cargoweb/wagons/ws/beans/services/processWagonMovementFromISR.wsdl http://be/brail/cargoweb/wagons/ws/beans/services {3} {4} {5}

BIP3736S: The message could not be found in resource bundle BIPv610. Inserts: processWagonMovementFromISR {1} {2} {3} {4} {5}

When I remove one WSDL out of the messageset, the deploy is OK. It looks like I can only have one WSDL in my message set :s

Please some help,
Pieter

fde

Posted: Thu Aug 28, 2008 6:14 am Post subject:

Acolyte

Joined: 05 Jul 2007
Posts: 65

You can use two different message sets. One for each wsdl file.
That would simplify the handling and understanding of the flow.

If you dont want to reaggregate the elements from both services into one service, there is no need to use a single message set imo.
And if you want to reagregate elements, I would recommend to use a third message set.
_________________
Global warming is an unintentional side effect of SOA's hotness.
-- http://soafacts.com/
a business integration methodology

fjb_saper

Posted: Thu Aug 28, 2008 2:18 pm Post subject: Re: SOAP requests + two wsdl file = deploy problem

Grand High Poobah

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

PiWer wrote:

Code:

When I remove one WSDL out of the messageset, the deploy is OK. It looks like I can only have one WSDL in my message set :s

Please some help,
Pieter

Seen that. The problem that you have is that you have exclusive overlap in the xsds for the 2 wsdl. I have currently 2 wslds in a message set without any problems. However the wsdl and xsds do not overlap (but for the ns1:commons.xsd...)
It is particularly annoying when you have multiple wsdls for the same service each with different operations. Usually you are going to find some overlap in the xsds used for the operations across the wsdls.

This is where one wsdl import is going to chase the other away...
If you want / need to keep it all in one msg set you will do better to import the xsds involved separately and hope that the wsdl do not define any msgs but reference them from the xsds.

Enjoy

_________________
MQ & Broker admin

sandeep9678

Posted: Fri Aug 29, 2008 12:39 am Post subject:

Apprentice

Joined: 04 Aug 2008
Posts: 41
Location: India

you can have two wsdls in one message set and that works without any issues. Make sure that they do not have any same kind of xsd in it. Also check on namespaces.
_________________
Cheers,
Sandeep

PiWer

Posted: Fri Aug 29, 2008 1:46 am Post subject:

Newbie

Joined: 11 Jul 2008
Posts: 6

Currently the two wsdl's are in the same namespace (http://be/brail/cargoweb/wagons/ws/beans/services), is that the error? I've attached the 2 wsdl's below.

And if two wsdl's can't use the same xsd's in the message broker but in fact they should, how can you solve this? Working with different message sets or group services together in function of the domain.

ProcessWagonMovementFromISR.wsdl

Code:

SearchWagonCycle.wsdl

Code:

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:sch="http://be/brail/cargoweb/wagons/ws/beans/services" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns1="http://be/brail/cargoweb/wagons/ws/beans/services" targetNamespace="http://be/brail/cargoweb/wagons/ws/beans/services">
<wsdl:types>
<xs:schema xmlns:services="http://be/brail/cargoweb/wagons/ws/beans/services" xmlns:wagon_cycle="http://be/brail/cargoweb/wagons/ws/beans/wagon_cycle" xmlns:xs="http://www.w3.org/2001/XMLSchema" attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://be/brail/cargoweb/wagons/ws/beans/services">

<xs:import namespace="http://be/brail/cargoweb/wagons/ws/beans/wagon_cycle" schemaLocation="WagonCycle.xsd"/>

<xs:element name="searchWagonCycleRequest">
   <xs:annotation>
      <xs:documentation>
         Request Object: Execute a search using the specified parameters.
      </xs:documentation>
   </xs:annotation>
   <xs:complexType>
      <xs:sequence>
         
         <xs:element name="wagonNumber" nillable="true" type="xs:string"/>
         <xs:element name="startDate" nillable="true" type="xs:date"/>
         <xs:element name="endDate" nillable="true" type="xs:date"/>
         <xs:element name="rcnNet" nillable="true" type="xs:string"/>
         <xs:element name="rcnUic" nillable="true" type="xs:string"/>
         <xs:element name="rcnSequence" nillable="true" type="xs:string"/>
         <xs:element name="originNet" nillable="true" type="xs:string"/>
         <xs:element name="originUic" nillable="true" type="xs:string"/>
         <xs:element name="destinationNet" nillable="true" type="xs:string"/>
         <xs:element name="destinationUic" nillable="true" type="xs:string"/>
      </xs:sequence>
   </xs:complexType>
</xs:element>

<xs:element name="searchWagonCycleResponse">
   <xs:annotation>
      <xs:documentation>
         Response Object: Return the search results.
      </xs:documentation>
   </xs:annotation>
   <xs:complexType>
      <xs:sequence>
         <xs:element maxOccurs="200" minOccurs="0" name="WagonCycleXML" type="wagon_cycle:WagonCycleXML"/>
      </xs:sequence>
   </xs:complexType>
</xs:element>

</xs:schema>
</wsdl:types>
<wsdl:message name="searchWagonCycleResponse">
<wsdl:part element="tns1:searchWagonCycleResponse" name="searchWagonCycleResponse">
</wsdl:part>
</wsdl:message>
<wsdl:message name="searchWagonCycleRequest">
<wsdl:part element="tns1:searchWagonCycleRequest" name="searchWagonCycleRequest">
</wsdl:part>
</wsdl:message>
<wsdl:portType name="cargowebwagons">
<wsdl:operation name="searchWagonCycle">
<wsdl:input message="tns1:searchWagonCycleRequest" name="searchWagonCycleRequest">
</wsdl:input>
<wsdl:output message="tns1:searchWagonCycleResponse" name="searchWagonCycleResponse">
</wsdl:output>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="cargowebwagonsSoap11" type="tns1:cargowebwagons">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="searchWagonCycle">
<soap:operation soapAction=""/>
<wsdl:input name="searchWagonCycleRequest">
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output name="searchWagonCycleResponse">
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="cargowebwagonsService">
<wsdl:port binding="tns1:cargowebwagonsSoap11" name="cargowebwagonsSoap11">
<soap:address location="http://localhost:8080/a793-services-war/ws/"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SOAP requests + two wsdl file = deploy problem

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