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 » BIP5029E: Error 's4s-elt-schema-ns: while try to deploy MF

Post new topic  Reply to topic
 BIP5029E: Error 's4s-elt-schema-ns: while try to deploy MF « View previous topic :: View next topic » 
Author Message
salberto
PostPosted: Tue Nov 01, 2016 11:04 am    Post subject: BIP5029E: Error 's4s-elt-schema-ns: while try to deploy MF Reply with quote

Novice

Joined: 08 Aug 2016
Posts: 14

HI All

I am facing an issue while I try to deploy a MF, I have the url of a WSDL that I need to use un a SOAP request node.

I have created the Message model with the information from the url (http://webService?wsdl) and the message set definition file as well, also I have generated the WSDL with the operations that I need without errors.

But when I try to deploy the MF I get the following error:



Quote:


Review related error messages to determine why the administration request failed.

BIP5024E: The creation and preprocessing of the XML schemas in message set 'NOTTEMP_WSDL' has failed.

Review previous messages to find out why the error occurred.

BIP5029E: Error 's4s-elt-schema-ns: The namespace of element 'definitions' must be from the schema namespace, 'http://www.w3.org/2001/XMLSchema'.' was encountered at line '1' while preprocessing XML Schema file 'schemaFile.xsd' in message set 'NOTTEMP_WSDL'

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.



I already checked the XML Schema file and the information is fine (according the url)
do you have any clue about how to proceed with this error?

Below the definitions that I got from the ?wsdl url:



Code:


<wsdl:definitions xmlns:ns1="http://schemas.xmlsoap.org/soap/http"
                xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
                xmlns:tns="http://service.web.com"
                xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
                xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="ServiceService"
targetNamespace="http://service.web.com/">

<wsdl:types>

Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue Nov 01, 2016 1:03 pm    Post subject: Reply with quote

Grand High Poobah

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

So it looks like the definitions element here is correctly prefixed with the wsdl namespace. Do you have a definitions element anywhere else in your message?
Like not in the wsdl but in a file named schemaFile.xsd??
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
salberto
PostPosted: Tue Nov 01, 2016 2:16 pm    Post subject: Reply with quote

Novice

Joined: 08 Aug 2016
Posts: 14

HI fjb_saper:

Yes I have the definitions elements in a xsd file that I have created

Quote:

<?xml version="1.0" encoding="UTF-8"?><wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" name="ServiceService" targetNamespace="http://service.web" xmlns:ns1="http://schemas.xmlsoap.org/soap/http" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://service.web.com" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Nov 02, 2016 4:31 am    Post subject: Reply with quote

Grand High Poobah

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

salberto wrote:
HI fjb_saper:

Yes I have the definitions elements in a xsd file that I have created

Code:

<?xml version="1.0" encoding="UTF-8"?><wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" name="ServiceService" targetNamespace="http://service.web" xmlns:ns1="http://schemas.xmlsoap.org/soap/http" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://service.web.com" xmlns:xsd="http://www.w3.org/2001/XMLSchema">


So if that's in an xsd, what's in your wsdl?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
salberto
PostPosted: Wed Nov 02, 2016 11:36 am    Post subject: Reply with quote

Novice

Joined: 08 Aug 2016
Posts: 14

HI fjb_saper

after a research I found the option to import the WSDL thru "webservices Explorer" in toolkit, I have imported the wsdl and Now I can deploy and test my MF.

I do not know what was exactly the issue when I tried to created it manually.

Do you know if is a good practice import the WSDL thru "webservices Explorer" option in toolkit?
normally I created the WSDL thru MessageSet (XMLSchema, MessageDefinitionFile..etc)

Thanks for your comments.

XSD
Code:

<?xml version="1.0" encoding="UTF-8"?><xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" attributeFormDefault="unqualified" elementFormDefault="unqualified" targetNamespace="http://service.web.com/" xmlns:ibmSchExtn="http://www.ibm.com/schema/extensions" xmlns:ns1="http://schemas.xmlsoap.org/soap/http" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://service.web.com/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">


WSDL
Code:

<?xml version="1.0" encoding="UTF-8"?><wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" name="ServiceService" targetNamespace="http://service.web.com/" xmlns:ns1="http://schemas.xmlsoap.org/soap/http" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://service.web.com/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
Back to top
View user's profile Send private message
timber
PostPosted: Wed Nov 02, 2016 1:07 pm    Post subject: Reply with quote

Grand Master

Joined: 25 Aug 2015
Posts: 1280

Quote:
after a research I found the option to import the WSDL thru "webservices Explorer" in toolkit, I have imported the wsdl and Now I can deploy and test my MF.
I don't know of any feature in the toolkit called ''webservices explorer'. Where did you find this button/menu item?

Quote:
I do not know what was exactly the issue when I tried to created it manually.
Do you know if is a good practice import the WSDL thru "webservices Explorer" option in toolkit?
normally I created the WSDL thru MessageSet (XMLSchema, MessageDefinitionFile..etc)
It is good practice to use the tools recommended in the Knowledge Center. Using Message Sets has been discouraged for a long time, especially for a new message flow application.
Back to top
View user's profile Send private message
salberto
PostPosted: Wed Nov 02, 2016 1:51 pm    Post subject: Reply with quote

Novice

Joined: 08 Aug 2016
Posts: 14

Hi timber

you can find the feature here:

-import
-Select Webservices folder and webservice option.
-Launch the WebServices Explorer to find a web service from a UDDI Registry.
-In corner select the option WSDL page.
-in the box put your url?wsdl and select go
-in the navigator section select the wsdl (after wsdl main)
-in the actions section you can find the option to import the WSDL to workbench or fileSystem.

The wsdl is imported with all the operations and definitions. so far is working fine.

Thanks for the comments about Message Sets, Im going to search more information about it.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » BIP5029E: Error 's4s-elt-schema-ns: while try to deploy MF
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.