| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Deployment issue with WSDL |
« View previous topic :: View next topic » |
| Author |
Message
|
| ANILK |
 Posted: Mon Jan 25, 2016 7:08 am Post subject: Deployment issue with WSDL |
 |
|
Acolyte
Joined: 01 May 2014
Posts: 61
|
HI Friends,
1) We are using IIB 9.0 Version , we are facing a deployment issue with a web-service interface. we have created a message set by using WSDL , on the time of message set creation there was no error , even on the time of BAR file creation no error. but on the deployment we got below mentioned error
"BIP5029E: Error 's4s-att-not-allowed: Attribute 'form' cannot appear in element 'element'.' was encountered at line '63' while preprocessing XML Schema file" 'ms_test' The XMLNSC parser is preprocessing the XML Schemas for the message set and it has encountered an error.
Check that the XML Schemas in the message set are valid.
The task was unsuccessful: The deployment was unsuccessful. Check error messages above for explanation."
I think the issue is with the WSDL , but i am able successfully validate this WSDL through soapui. i am expecting all of your valuable advice to find out the exact issue,
2) When we normally deploy a SOAP node, broker usually assign 7800 port for that specif service , and for HTTP node 7080 port
is it possible to allocate 7800 port for HTTP node by using mqsichageproperties command ? , or is it a bad idea ?
Kindly share your valuable advice.
Thanks & Regards,
Anil |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Jan 25, 2016 7:25 am Post subject: Re: Deployment issue with WSDL |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ANILK wrote: |
| 1) We are using IIB 9.0 Version , we are facing a deployment issue with a web-service interface. we have created a message set by using WSDL |
Why are you using a message set for anything in v9, especially an XML document?
| ANILK wrote: |
on the time of message set creation there was no error , even on the time of BAR file creation no error. but on the deployment we got below mentioned error
"BIP5029E: Error 's4s-att-not-allowed: Attribute 'form' cannot appear in element 'element'.' was encountered at line '63' while preprocessing XML Schema file" 'ms_test' The XMLNSC parser is preprocessing the XML Schemas for the message set and it has encountered an error.
Check that the XML Schemas in the message set are valid. |
So the run time does a more in-depth job of checking the WSDL than the Toolkit? Not a surprise.
| ANILK wrote: |
| I think the issue is with the WSDL |
I think you're right.
| ANILK wrote: |
| , but i am able successfully validate this WSDL through soapui. |
When did they build the ability to validate a WSDL into SoapUI? Last version I used it just built a web service from it.
| ANILK wrote: |
| i am expecting all of your valuable advice to find out the exact issue |
Use a tool that actually validates XML, like XMLSpy.
| ANILK wrote: |
| 2) When we normally deploy a SOAP node, broker usually assign 7800 port for that specif service , and for HTTP node 7080 port |
Because the two node types use different listeners.
| ANILK wrote: |
| is it possible to allocate 7800 port for HTTP node by using mqsichageproperties command ? , or is it a bad idea ? |
It's a horrible idea, as the listeners will fight for the port and you'll get unreliable results. It's much better to set both node types to use the same listener (which one is your choice) and set that to the desired port.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Jan 25, 2016 8:14 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
There are also a good few XML Schema and WSDL Validators on the internet.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| ANILK |
| Posted: Mon Jan 25, 2016 8:38 am Post subject: Deployment issue with WSDL |
|
|
Acolyte
Joined: 01 May 2014
Posts: 61
|
Thank you Mr.Vitor , the error got resolved , we have not done any changes in wsdl. but instead of creating message set we used Message modeling. and now we are able to deploy the code successfully.
Once again thank you for your valuable advice.
Anil |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
