Thanks for your reply.
Reason I'm asking is, we're displaying the end output
as HTML, but that display is changing based on
user-input.
For instance, a user has several chances to change
their minds on the same form. It submits to the same
action class, essentially updating the XML of their
respective session.
(this example is simplified, b/c we're actually using
Adobe's Document server, and tweaking the respective
commands file needed to produce JPG's, and an SVG to
accompany the ADS call but, here's a barebones
example:)
So, the first time a user comes thru, we start up the
"job ticket" of their session as a xml document, and
retain it in their HttpSession.
<jobticket>
<options>
<option name="one" value="Hello"/>
<option name="two" value="World"/>
</options>
</jobticket>
This would be placed in their session, assuming
default values of "Hello" and "World"
Now, the user has the option of updating those values,
and/or adding more.
To add more would simply add another first level
element, like this:
<jobticket>
<options>
... same as above
</options>
<furtherOptions>
<option name="alpha" value="Laverne"/>
<option name="beta" value="Shirley"/>
</furtherOptions>
</jobticket>
User can now, update anything in the //options/option
or //furtherOptions/option
where attrib(value) would be the changing item.
So, you're recommending that I transform the first XML
(the one w/o the <furtherOptions> element) and get a
Stream returned, then transform that Stream with the
<furtherOptions> element, right?
thanks again..
Paul
--- [EMAIL PROTECTED] wrote:
> A lot depends on your display technology. Are
> you displaying them as raw xml in an XML aware
> environment? Or prettying them up with HTML or
> PDF? Creating a display file directly, or
> using something like JSPs?
>
> In general, I would start by trying to format
> each individual document into the final
> display format separately. Only if you run
> into some snags would I look at creating a new
> aggregate XML doc. Remember, if you create an
> aggregate doc, you are effectively creating an
> aggregate DTD. If one of the pieces changes
> its definition, you might have to change quite
> a bit with the aggregate.
>
> Also, if you create an aggregate, the final
> XSL you use to generate the display format
> will probably identify the pieces and treat
> them separately anyway.
>
> Kevin
>
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
