Subject: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.
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.