SSDN - Stylus Evaluation info needed

XML Editor

Sign Up

Search

Options

Chat

Help

News

Log in

Not Logged in

Topic

Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Christopher Atkins

Subject: Stylus Evaluation info needed
Author: Christopher Atkins
Date: 09 Jun 2005 05:49 PM

Is there a way when doing XSLT mapping to create nodes in the target document that are required by the target schema? For reason I don't understand, it is possible to do so for source schema.

Is it possible to use XSLT 2.0 commands in the mapping editor? How?

Ivan Pedruzzi

Subject: Stylus Evaluation info needed
Author: Ivan Pedruzzi
Date: 09 Jun 2005 06:55 PM

Hi Christopher,

1# right click on any elements on the target document using the context menu you can create elements and attributes

2# we currently don't support XSLT 2.0 specific features in XML to XML mapping tool, but you can still run/debug/profile using the text view

Hope this helps
Ivan Pedruzzi
Stylus Studio Team

Christopher Atkins

Subject: Stylus Evaluation info needed
Author: Christopher Atkins
Date: 09 Jun 2005 07:01 PM

Regarding #1, the target is a fully defined schema. I want to auto-generate elements for each required element in the target that I have not mapped yet. Can the tool do this?

Regarding #2, will the mapper view "break" if I use XSLT 2.0 syntax?

Ivan Pedruzzi

Subject: Stylus Evaluation info needed
Author: Ivan Pedruzzi
Date: 09 Jun 2005 11:57 PM

Mapper doesn't automatically generate required elements if they are not mapped.

Mapper tries to preserve what it doesn't understand.

Christopher Atkins

Subject: Stylus Evaluation info needed
Author: Christopher Atkins
Date: 10 Jun 2005 11:26 AM

Mapper does not recognize the maxOccurs="unbounded" for a xsd:choice either... I have to do a manual for-each for element types that have an unbounded choice. Not a big deal, but I'm beginning to wonder why this package is $500 or $1000 if it doesn't have this simple stuff working.

Ivan Pedruzzi

Subject: Stylus Evaluation info needed
Author: Ivan Pedruzzi
Date: 10 Jun 2005 12:07 PM

Christopher,

Having a more concrete example of what you are trying to do would help us to better respond.

Which Stylus Studio version are you running?

Are the elements in the Mapper tree marked repeatable?
Unbounded elements should be marked so.

Here an additional hint: if you draw the link using "right click" you will be able to choose which kind of link to create.

Hope this helps
Ivan Pedruzzi
Stylus Studio Team

Christopher Atkins

Subject: Stylus Evaluation info needed
Author: Christopher Atkins
Date: 10 Jun 2005 04:18 PM

It wasn't marked repeatable in the source (if by "marked repeatable" you mean the little parent-child icon instead of the default blue box) document.

The schema definition for the type looks like:
<xs:complexType name="CastorCoverages">
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element ref="coverage"/>
<xs:element ref="broadenedPipCoverage"/>
<xs:element ref="enterAllCoverage"/>
</xs:choice>
</xs:complexType>

I expected it should show up as repeatable.

Thanks for the right-click tip. The market is bereft of good stand-alone document-document mapping tools--I hope you guys will put more time into this part of the product. Some complaints:
* entire mapping area is reset when stylesheet is edited, causing me to have to scroll all the way back to the area I'm working on, in both source and target--this also expands all mapped nodes, not perserving my settings. this makes the mapping design surface nearly USELESS for keeping track of what has been mapped
* many parts of the help file have not been updated from the last release (right-click menu options in mapper for example)
* BUG: Giving focus to application window gives focus to help viewer when both are open.
* BUG: In using the XML Schema to XML document wizard, it will not allow me to change the schema root.
* mapper doesn't support XSLT2

Minollo I.

Subject: Stylus Evaluation info needed
Author: Minollo I.
Date: 10 Jun 2005 04:47 PM

>* BUG: Giving focus to application window gives focus to help viewer when both are open.

That's one of the default behaviors of online help systems; you can change that from Tools | Options > Application Settings > Always display Help window on top.

> * BUG: In using the XML Schema to XML document wizard, it will not allow me to change the schema root.

Can you give us more details to be able to reproduce that? I tried using the document wizard, I entered an XML Schema document name and the drop down list displaying all possible roots got populated with the proper entries from which I could choose the one I wanted.

> * mapper doesn't support XSLT2

Yes, mappers currently support XSLT 1.0 and the latest XQuery WD.

Minollo

Christopher Atkins

Subject: Stylus Evaluation info needed
Author: Christopher Atkins
Date: 10 Jun 2005 06:48 PM
Originally Posted: 10 Jun 2005 04:51 PM

Thanks for the information on the help viewer. I would like to send you the XSD that is causing the other (real) bug, as i cannot post it publically. Please let me know where I can send it.

Minollo I.

Subject: Stylus Evaluation info needed
Author: Minollo I.
Date: 10 Jun 2005 05:09 PM

stylus-field-report@stylusstudio.com

BTW, the problem you are experiencing with the choice group not being displayed as repeating is due to the fact that mapper displays as repeatable elements that are individually set to maxOccurrs unbounded.

Setting maxOccurrs unbounded on the choice or sequence has implications that mapper is not able to support. For example, an xs:sequence with maxOccurrs unbounded of a, b and c would imply that you need to create a,b,c,a,b,c,a,b,c,a,b,c,...; strictly speaking a, b and c are repeating, but with a very precise order.

Minollo

Christopher Atkins

Subject: Stylus Evaluation info needed
Author: Christopher Atkins
Date: 10 Jun 2005 06:52 PM

Thanks for the explanation on the choice/unbounded...though I would hope the product has plans to incorporate this functionality at some point (would be great to have all elements in the choice pointing to the same for-each block).

Also, I'm trying to preview my XSLT translation using various processors (built-in and MSFT .NET), but the information in the output window does not change--

Minollo I.

Subject: Stylus Evaluation info needed
Author: Minollo I.
Date: 10 Jun 2005 08:54 PM

>Thanks for the explanation on the choice/unbounded...though
>I would hope the product has plans to incorporate this
>functionality at some point (would be great to have all
>elements in the choice pointing to the same for-each block).

We do have plans to make mapper handle XML Schema information in a more flexible and sophisticated way.

>Also, I'm trying to preview my XSLT translation using various
>processors (built-in and MSFT .NET), but the information in
>the output window does not change--

You mean in the Preview window? Why do you expect it to change? Unless you use some extension or peculiarity of one of the processors, the result of processing against the same XSLT should be the same for all processors.

Minollo

Christopher Atkins

Subject: Stylus Evaluation info needed
Author: Christopher Atkins
Date: 13 Jun 2005 01:45 PM

I expected the error messages to change (useful for debugging purposes).

Christopher Atkins

Subject: Stylus Evaluation info needed
Author: Christopher Atkins
Date: 13 Jun 2005 04:57 PM

Does the preview/output window only ever use the built-in parser?

Minollo I.

Subject: Stylus Evaluation info needed
Author: Minollo I.
Date: 13 Jun 2005 05:30 PM

Preview and Output windows are two different entities in Stylus Studio.

The Preview window displays the result of some processing (typically XQuery or XSLT); the result can be seen in most cases as an XML tree, raw text or Internet Explorer rendering. The Preview window is populated by all XSLT and XQuery processors. The Preview window is also where back-mapping from the result to the source (for XSLT and XQuery) is triggered (for the processors that support it).

The Output window is less "crucial" to Stylus Studio; it is used to display errors/exceptions/status reported by external components (JVM, not-built-in processors, command lines); information is provided only as text. The built-in XSLT and XQuery processor will typically not display information in the Output window.

Hope this helps,
Minollo

Christopher Atkins

Subject: Stylus Evaluation info needed
Author: Christopher Atkins
Date: 14 Jun 2005 09:59 AM

Thanks for the clarification. Still, i was expecting the results of the post-preview validation to change in the output window when I switched from the built-in to .NET processor (or any other). The error message from the built-in processor does not supply the element name that was invalid, but rather a line number in the temp XML, which is rather useless.

Any suggestions?

Minollo I.

Subject: Stylus Evaluation info needed
Author: Minollo I.
Date: 14 Jun 2005 11:43 AM
Originally Posted: 14 Jun 2005 11:44 AM

The post-processing validation step is not tied to the processor used for the actual XSLT/XQuery processing; you can choose the validator in the post-validation tab.

That said, as the result isn't associated to a physical file/URL (unless you specify an output location in the main scenario tab), the information you will get will always be based on a temporary file. Your best options for further investigations on the post-processing validation errors are:
- Set the Output URL in the main scenario tab to a specific file, so you can open and inspect the problem in that file after processing
- Save the Preview window content (the disk button to the left of the preview window), and open the saved file

Hope this helps,
Minollo

Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

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 to Conference:

Log In Options Username: Password:

Site Map | Privacy Policy | Terms of Use | Trademarks

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.