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 » mapper schema problem
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> + Report reverts back to XHTML-C... (2)
-> + Certificate error (7)
-> + Opening DITA files and associa... (4)
-> + Cannot see links from source d... (10)
-> + SS 2007 vs. SS 2008 calling a ... (3)
-> + Unable to compile java file (8)
-> + Unable to use xsi:type attribu... (2)
-> + Unable to save xslt file after... (5)
-> + .NET XslTransform Compiled out... (3)
-> + Reporting Comparison (2)
-> + problems setting up the fonts ... (3)
-> + XML conversion (5)
-> + XQUERY: Application Crash (3)
-> + Base type definition does not ... (5)
-> + Tip says Generate C# Code actu... (2)
-> + install help (4)
-> + saxon-license (3)
-> + Mapping 1 xml file layout to a... (2)
-> + Problem - Schema Representatio... (3)
-> + selecting the correct Line Ter... (2)
-> + Stylus Studio crashing (14)
-> + EXSLT extensions in Stylusstud... (4)
-> + "Indent XML Tags" introduces u... (8)
-> + unable to use Stylus Studio of... (4)
-> + Replace in selection not worki... (4)
-> + Activation Key (3)
-> + Berkeley support removed! ? (2)
-> + Report editor slows to a virtu... (2)
-> + StylusStudio will not stop pro... (2)
-> + Indent tags resolves NCRs in a... (4)
-> + XML Report Table Problem (2)
-> + document() function throws unk... (7)
-> + Report indentation (2)
-> + Report editor automatic scroll... (2)
-> + java.lang.ClassNotFoundExcepti... (4)
-> + Strange output (6)
-> + Built-In Processor Handling CD... (5)
-> + Parameter values with multiple... (3)
-> + Schema review (2)
-> + seperating values within one e... (2)
-> + Filtering 1000's of XML files ... (2)
-> + replace fop0.20 by 094 (2)
-> + HTML tables from sorted XSL (3)
-> + From dicisionshema to XML (4)
-> + Convert data from SQL database... (2)
-> + Really Really need help - xsl:... (2)
-> + xslt: xsl:include not finding ... (2)
-> + One field in multiple lines (3)
-> + Stylis studio editor slow (2)
-> + Schema Documentation (3)
-> + Convert PCL to XML (7)
-> + crashing when connected via VP... (3)
-> + Repeater err:XPST0003 (3)
-> + rtf to XML (4)
-> + Questions Regarding Existing B... (3)
-> + Bug: Saved Changes Lost Switch... (3)
-> + Adding Simple Types to Attribu... (4)
-> + SQL Table to XML Convert error... (9)
-> + please help me with style shee... (2)
-> + WSDL Misbehaving (4)
-> + Regarding XSLT logic for a sim... (2)
-> + Regarding XSLT logic for a sim... (2)
-> + Integration with VB.Net (5)
-> + License for end user (5)
-> + Error when running xalan sampl... (3)
-> + generate the date time in xslt... (2)
-> + Error When Using XMLConverters... (5)
-> + Viewing the toolbox pane (3)
-> + In Sync (2)
-> + Java EE 5 SDK vs. Java 2 SDK S... (2)
-> - Odd behavior of Begin Field in... (1)
-> + I/O-error while saving style s... (2)
-> + WEB Service Session (2)
-> - XML Report - Horizontal Line (1)
-> + XML feed to a txt file (2)
-> + problem with xml output (2)
-> + XSL Debugging (2)
-> + XML schema validation issue (t... (2)
-> + Problem during saving styleshe... (4)
-> + Slow Redraw (11)
-> + Source XML code updates in map... (2)
-> + converting XML to Excel (2)
-> + Pre-Sales Questions? And Mergi... (2)
-> + How can I download an earlier ... (2)
-> + Create multiple string outputs... (2)
-> + Alternate page masters indepen... (3)
-> + Flat to XML and back with Styl... (2)
-> + BUG: Byte Order Mark inserted ... (2)
-> + Schema Validation using the to... (7)
-> + Flat Text file to XML or XSD (6)
-> + Second time it should not go i... (2)
-> + How to sum Nodes which are at ... (2)
-> + Where has the wysiwyg editor g... (2)
-> + SS says my trial has expired -... (2)
-> + XSD input; SQL Table Output Ne... (2)
-> + Building Schema from XML (2)
-> + conditions on tag values expre... (3)
-> + XML converter "omit fields whe... (3)
-> + Marklogic XQuery support in St... (2)
-> + XSL switching stylesheet from ... (10)
-- Previous [1321-1340] [1341-1360] [1361-1380] 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
Kurt WaldSubject: mapper schema problem
Author: Kurt Wald
Date: 04 Sep 2007 09:50 AM
When a target schema is set in the mapper which contains a default namespace as the target namespace, that namespace is always prefixed in the resulting styleshheet.

If the prefix is manually removed in the stylesheet, before making any assignments, to get the unprefixed default namespace behaviour again, the target schema sequence is suddenly broken after a number of correctly established graphical links.

From that point on code resulting from graphical mapping is inserted immediately after the target root element.

I can imagine that this may also partially result from the structure of the target schema which doesn't really follow any of the known design patterns (see uploaded file EFACT_D96A_ORDRSP.xsd).

Kurt Wald


DocumentEFACT_D96A_ORDRSP.xsd
Postnext
(Deleted User) Subject: mapper schema problem
Author: (Deleted User)
Date: 04 Sep 2007 11:16 AM
Hi Kurt,
the schema you attached declares a target namespace, so the a prefix must be added to the XPath expressions in order to have correct queries. Removing the prefix from the XSLT itself will generate a whole different element, and this it will create a new tree in the target schema.
Can you elaborate why do you think that the code generated by mapper should not have a prefix? Can you attach a sample XSLT?

Thanks,
Alberto
Postnext
Kurt WaldSubject: mapper schema problem
Author: Kurt Wald
Date: 04 Sep 2007 11:50 AM
Hi Alberto,

a default namespace as target namespace to enable unprefixed instance documents seems to be legal to me.

I uploaded a pefixed and an unprefixed stylesheet version (orders01_ordrsp96a_def.xsl/orders01_ordrsp96a_pre.xsl). The instance documents created (.net) by both stylesheets are valid against the schema.

Kurt


Unknownorders01_ordrsp96a_def.xsl


Unknownorders01_ordrsp96a_pre.xsl
Postnext
(Deleted User) Subject: mapper schema problem
Author: (Deleted User)
Date: 04 Sep 2007 04:31 PM
Hi Kurt,
the generated XML cannot be valid in both cases: when the http://schemas.microsoft.com/BizTalk/EDI/EDIFACT/2006 is the default namespace, the UNH element and its children are placed in that namespace too, while when it is associated with the "a" prefix it is in the empty namespace.

Anyhow, if you still want to have the literal elements in the target schema to use a specific prefix (even the default one), you can define the prefix in the xsl:stylesheet root element and mapper will use it whenever it needs to pick one.

Hope this helps,
Alberto

Posttop
Kurt WaldSubject: mapper schema problem
Author: Kurt Wald
Date: 06 Sep 2007 04:46 PM
Hi Alberto,

for the unprefixed version I use the xsd with

elementFormDefault="qualified".

Thus the mapper seems to behave ok without prefix after making http://schemas.microsoft.com/BizTalk/EDI/EDIFACT/2006 the default namespace.

Kurt

   
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.