| Author |
Message
|
| PEPERO |
 Posted: Thu Sep 06, 2012 9:16 am Post subject: Multiple Message definition files |
 |
|
Disciple
Joined: 30 May 2011
Posts: 177
|
Hi ;
I've multiple message definition files with no naming clashes within the message model objects. When separating the message definitions accross multiple message sets, every thing is ok. But when i put ; say two of ; them (which have the same physical formats) into a single message set , the requested object could not be found.
So is it a neccessity to put each of the models in a separate URI within a message set or there may be another problem? |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Thu Sep 06, 2012 9:29 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Are you following the golden rule to never use the default package name? If these message definitions are ones you are creating (ie. you are not importing a WSDL or XSD), then you should also create unique package names.
When attending the WMB Dev I class, that golden rule is discussed on the first day.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| PEPERO |
| Posted: Thu Sep 06, 2012 9:53 am Post subject: |
|
|
Disciple
Joined: 30 May 2011
Posts: 177
|
| No they are not located within the default package name but under the same package name. So you mean they must be within the separate URIs. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Sep 06, 2012 9:59 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
No. They don't need to be located under different URIs.
But URIs is the wrong term to use.
You've not explained exactly which thing is producing the 'object not found' message. That might help explain the issue. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Sep 06, 2012 10:07 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| PEPERO |
| Posted: Thu Sep 06, 2012 10:16 am Post subject: |
|
|
Disciple
Joined: 30 May 2011
Posts: 177
|
There are two message definition files located under the http://abs.datamodel.com with in a message set named "ABS_Message_SET" in which the first one has two global elements named txn1_Input_Message, txn1_Output_Message and the second one has txn2_Input_Message, txn2_Output_Message.
There is a SOAPINPUT node at the start of a message flow which uses the ABS_Message_Set message type of txn1_Message_Input. When the message comes into the SOAP input node , an exception is thrown and when i see the service trace log, it shows that it searches for the txn1_Input_Message with in the txn2_In element. Since the txn1_Input_Message has been defined under the txn1_In xsd , it goes to make a fault envelop and the problem grows. |
|
| Back to top |
|
|
| PEPERO |
| Posted: Wed Sep 12, 2012 1:55 am Post subject: |
|
|
Disciple
Joined: 30 May 2011
Posts: 177
|
| Supose that we have two message definition files located in the same package. if we want to generate the two related web services using them, shall we put the output WSDL files in the separate packages or they could be within the same package? |
|
| Back to top |
|
|
|
|
