XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
search
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Home » Boards » Stylus Studio Developer Network » Stylus Studio Technical Forum » [resolved] Namespace (and prefixes) generation from WSDL source
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> + predefined macros ${ (4)
-> - TRADACOMS - EDI (1)
-> + SUM not working (3)
-> - Large xml file handling gives ... (1)
-> + 2011 Enterprise code folding f... (9)
-> + custom xml converter (3)
-> - Start Excel feter the mapping ... (1)
-> + Uninstall (2)
-> + xpath to compare two values fr... (2)
-> - xpath to compare two values fr... (1)
-> + SS2011 cannot save XML files u... (3)
-> + SS 2011 Enterprise saying 2010... (2)
-> + How to change the way whitespa... (7)
-> + Updating Relational Data Using... (4)
-> - Contract Stylus Studio help. ... (1)
-> + UTF_8 characters not displayed (6)
-> + Problem XSL to PDF ( dont reco... (2)
-> + HIPAA EDI - Looping question (4)
-> - HIPAA EDI - Looping question (1)
-> + Does XML Report support column... (2)
-- Previous [481-500] [501-520] [521-540] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
S WSubject: [resolved] Namespace (and prefixes) generation from WSDL source
Author: S W
Date: 12 Jul 2010 06:31 AM
Originally Posted: 08 Jul 2010 12:00 PM
Hi,

I'm trying to make a transformation with a validated RPC WSDL file as input.

When I use the mapper to affect a field to another Stylus generates the following code:

<xsl:value-of select="recupIDsMissionsSigma/envVeolia/env:id"/>

As you can see, there is no prefix namespace on "recupIDsMissionsSigma" and "envVeolia".

However these fields are defined in a namespace in the WSDL which is ignored by Stylus.

Is it an expected behaviour? And if so why?
Is there any parameter configuration that can be set to indicate Stylus to generate these prefixes?

Thank you for your support,
Seb!
Postnext
Ivan PedruzziSubject: Namespace (and prefixes) generation from WSDL source
Author: Ivan Pedruzzi
Date: 08 Jul 2010 12:53 PM

Which Stylus Studio build number are you running?

Could you share source and target schema?

Ivan Pedruzzi
Stylus Studio Team
Postnext
S WSubject: Namespace (and prefixes) generation from WSDL source
Author: S W
Date: 08 Jul 2010 01:44 PM
Hi,

- I'm using "Stylus Studio enterprise 2010 build 1540b"

- Please, find attached my Stylus project.

RPC use case:
-source=RPC.wsdl
-target=outModel.xml
-xslt=RPC_to_XML.xsl

Document use case:
-source=Document.wsdl
-target=outModel.xml
-xslt=Document_to_XML.xsl


Thank you for your quick answer: I appreciated it.
Best regards,
Seb!


DocumentRPC_vs_Document.zip
Postnext
Ivan PedruzziSubject: Namespace (and prefixes) generation from WSDL source
Author: Ivan Pedruzzi
Date: 09 Jul 2010 06:00 PM
Hi Seb,

As far as I can tell envVeolia is in the default namespace and the behavior is correct.

document.wsdl defines a global element RecupIDsMissionsSigma_ReqMsgType, notice that elementFormDefault is not set therefore by default is unqualified; both local elements envVeolia and declencheur are unqualified.

With RPC things get hairy, Stylus Studio always force the operation element root to the default namespace

Hope this helps
Ivan Pedruzzi
Stylus Studio Team
Posttop
S WSubject: [resolved] Namespace (and prefixes) generation from WSDL source
Author: S W
Date: 12 Jul 2010 06:30 AM
Hi,

Thank you for your support, it definitely helped me!

For "Document" WSDL, I didn't well know this "elementFormDefault" attribute and it does the job!

For "RPC" WSDL, "elementFormDefault" is not supported. In a RPC WSDL, the operation is defined with a namespace attribute in the soap:body element of the operation binding. Defining this attribute to somewhat makes Stylus generate the expected prefix. Without this declaration, the operation is "unqualified" so it's correct behaviour that Stylus doesn't generate any namespace.

This issue is then closed on my side either for Document or RPC WSDL style.
Thank you very much again!

Seb!
   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.