Re: Newbie Q about XSLT in Mav.NET
A.D. Kent <adkent <at> mindspring.com>
2004-09-13 15:58:37 GMT
Hi Aaron:
Thanks for the explanation. I'm still not clear on exactly how I would go
about leveraging the framework for my solution, which is in no small part a
result of my "newness" to Mav.NET framework.
In my most simplest of scenarios, I would want to retrieve a DOM object
that is session-specific via our own objects (we persist session
information to compressed XML and have loaders/unloaders for this).
Thereafter, I would simply want to apply the entire DOM model to one or
more XSLT's to render a particular view. Again, this is the most
straightforward of scenarios that we would have, as more complex renderings
of the View might include a mix of instance-specific XML data aggregated
together with application and session XML to create a page-specific DOM for
transforms.
I'm sure that I'm missing something really obvious in the equation here
perhaps, so I apologize if the answer to this question is clear and I just
haven't made the connection yet.
Best regards,
A.D. Kent
> [Original Message]
> From: Aaron Clauson <aza_rc <at> yahoo.com>
> To: <mavnet-user <at> lists.sourceforge.net>
> Date: 9/11/2004 8:20:10 AM
> Subject: Re: [Mavnet-user] Newbie Q about XSLT in Mav.NET
>
> Hi,
>
> If I understand correctly you could do something like:
>
> <command name="xsltTransform.aspx">
> <view name="success" type="document"
> path="./models/baseModel.xml">
> <transform type="xslt"
> path="./views/xsltTransform.xsl" />
> <transform type="xslt" path="./views/baseView.xsl"
> />
> </view>
> </command>
>
> This approach means you don't need to write any code
> you can just use your existing XML Model and XSL
> transforms in the View stage. This may be sufficient
> for you, in that you can add more pieces of XML in
> using the transforms?
>
> The problem I have with this approach (and I apologise
> to the mailing list for mentioning this again) is that
> I wanted to keep my XML completely seperate. To do
> this I needed a controller that could operate as an
> XML aggregator, as in:
>
> <command name="default|home|\/.*">
> <model>
> <path value="models/banner.xml" />
> <path value="models/mainMenu.xml" />
> <path value="models/productMenu.xml" />
> <path value="models/brochure.xml" />
> <path value="models/footer.xml" />
> </model>
> <view name="success">
> <transform path="views/banner.xsl"/>
> <transform path="views/home.xsl"/>
> </view>
> </command>
>
> In the above example the controller stage is
> responsible for aggregating each of the XML documents
> in the model node into a single DOM which is then
> passed to the View stage and the XSL transforms
> applied.
>
> If this is the kind of behaviour you are looking for
> (?) then all you need to do is write a custom
> controller that takes a list of XML DOMs and
> aggregates them using whatever rules you like. The
> Maverick xslt transform stage should be sufficient for
> applying a series of XSL transforms.
>
> Regards,
> Aaron
>
> > Message: 1
> > From: "A.D. Kent" <adkent <at> mindspring.com>
> > To: mavnet-user <at> lists.sourceforge.net
> > Date: Fri, 10 Sep 2004 13:32:56 -0400
> > Subject: [Mavnet-user] Newbie Q about XSLT in
> > Mav.NET
> > Reply-To: mavnet-user <at> lists.sourceforge.net
> >
> > ------=_NextPart_84815C5ABAF209EF376268C8
> > Content-type: text/plain; charset=US-ASCII
> >
> > As somebody new to the Maverick framework, I'm
> > trying to understand one very important facet of the
> > framework as it pertains to an application that I
> > oversee design and development for.
> >
> > Our solution essentially has a foundation in XML;
> > quite literally our entire "model" is XML as are all
> > of our application proprieties. All views are
> > rendered as an XSLT transform from our model, or a
> > subset of the model (a combination of raw data from
> > nodes or a smaller XmlDocument as arguments). We
> > have our own providers that manage state fullness of
> > the XML model as well.
> >
> > Now, maybe I'm really missing something in the
> > documentation or the examples, but how would one go
> > about using their internal XML model as the source
> > for one or many XSLT transforms? We do use some
> > XSLT inheritance, and have considered breaking those
> > up to make our transforms more iterative in nature.
> > How would one go about using a combination of a
> > dynamic XML model and static parameters for an XSLT
> > transform to create a specific View?
> >
> > I'm sorry if these are basic questions that have
> > already been answered, or if I'm missing something
> > obvious. Many thanks for your responses!
> >
> >
> > A.D. Kent
> > adkent <at> mindspring.com
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - 100MB free storage!
> http://promotions.yahoo.com/new_mail
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> Mavnet-user mailing list
> Mavnet-user <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mavnet-user
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
RSS Feed