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 » xlnlink question
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> - Stylus Studio - Registrar en o... (1)
-> + Stylus Studio - Registrar en o... (2)
-> + Can a pipeline send a file by ... (2)
-> + After Updateing WIN10 to WIN11... (12)
-> + Where do I add the custom java... (3)
-> + Where is the Diagram tab? (5)
-> + Applying XSLT to Word DOCX/XML (2)
-> - CSV conversion via ConvertToXM... (1)
-> + Text symbols in SS not same as... (4)
-> + Exposing xquery as webservice ... (6)
-> + Syntax Identifier (2)
-> + Saving a Converted XML as an X... (5)
-> + Output document cannot be pars... (4)
-> - Archiving output from conversi... (1)
-> + EDIFACT guideline from Stylus ... (3)
-> + CSV file putting all the data ... (5)
-> + Can't install Home version 64b... (5)
-> + presale - Can I covers this sc... (5)
-> + Problem with UNB (5)
-> + Splitting EDIFACT files pipeli... (4)
-- [1-20] [21-40] [41-60] 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
Ben HallSubject: xlnlink question
Author: Ben Hall
Date: 14 Jun 2001 08:08 AM
Hi!

We've been working with Stylus 2.0 and moved to 3.0 during Beta testing. Now we're using the GA release. Initially, we loved the xlnlink traversal the 3.0 version offers but now I have run into a problem.

My thinking had been that when Stylus brings in an XML document it traverses the linked nodes and makes the document *look* like it is all one big document.

But I believe that I am wrong here and it is causing serious document management/confusion issues. In reality it seems like if you make a change to a node that is below a node that is a traversed xlnlink the linked document nodes actually get pulled into the parent document. Is that a correct statement? Does this occur only in text editing mode (what I normally work in) or all of the editing modes.

This becomes extremely problematic because then the linked document is no longer in a consistent state with what was pulled into the parent. Is there a setting to change this? To maintain consistent data it seems like the update should take place in the actually linked document.

Thanks,

Ben
Posttop
Minollo I.Subject: Re: xlnlink question
Author: Minollo I.
Date: 14 Jun 2001 11:19 AM
At 08:13 AM 6/14/2001 -0400, you wrote:
>From: "Ben Hall"
>
>Hi!
>
>We've been working with Stylus 2.0 and moved to 3.0 during Beta
>testing. Now we're using the GA release. Initially, we loved the xlnlink
>traversal the 3.0 version offers but now I have run into a problem.
>
>My thinking had been that when Stylus brings in an XML document it
>traverses the linked nodes and makes the document *look* like it is all
>one big document.
>
>But I believe that I am wrong here and it is causing serious document
>management/confusion issues. In reality it seems like if you make a
>change to a node that is below a node that is a traversed xlnlink the
>linked document nodes actually get pulled into the parent document. Is
>that a correct statement? Does this occur only in text editing mode (what
>I normally work in) or all of the editing modes.

If you edit a Portal Server document containing xlnlink directives from
Stylus Studio, Stylus Studio doesn't know anything about the presence of
such directives; it just handles the whole traversed document.

If you edit the document and save the document as you would normally do, I
think Portal Server will loose the xlnlink directives it initially had in
the master document, and will just store the document as a single unit.

The only alternative which should work is that you edit your document in
the tree tab and then save the document *changes* as update grammar rather
than saving the whole document; you can do that, as mentioned, only in tree
mode (that's the only way we can keep track of your actions and translate
them into a Portal Server update grammar) and then clicking the "XUL
update" button in the XML editor document window (first button on the left
in the XML editor toolbar).

>This becomes extremely problematic because then the linked document is no
>longer in a consistent state with what was pulled into the parent. Is
>there a setting to change this? To maintain consistent data it seems like
>the update should take place in the actually linked document.

As mentioned, that can only work using update grams.

Hope this helps,
Minollo
   
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.