In Maverick 1.0, the command config would look like this:
<command name="foo">
<controller type="blah.blah.Blah"/>
<view name="success">
<domify node="yourNode">
<transform src="blah.xsl"/>
<transform src="another.xsl"/>
</domify>
</view>
</command>
In Maverick 2.0, the command config can look like this:
<command name="foo">
<controller value="blah.blah.Blah"/>
<view name="success" type="domify">
<transform type="xslt">
<path value="blah.xsl"/>
<path value="another.xsl"/>
</transform>
</view>
</command>
...and you can specify defaults for the view and transform type so that
you don't have to keep listing them everywhere.
Jeff
> -----Original Message-----
> From: Scott Hernandez
> Sent: Sunday, December 16, 2001 11:29 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [Mav-user] Browser caching and pass through XML
>
>
> Hey Barrie,
>
> 1.) Yes, The model that is returned from the controller is used as the
> input to the XSL transformation. So... if have some XML, in either DOM
> (Node) or stream (InputStream) or Reader form, you can return
> it as the
> model.
>
> public class MyController extends ControllerProtected
> {
> ...
> /** @return the model data which is used to render the view */
> // Default is to return "this" from base class impl.
> public Object model()
> {
> return XMLStream/XMLNode/XMLReader;
> }
> }
>
> Note: See maverick.flow.Pipeline.go() signatures and
> maverick.flow.ViewDomify.go(...) for more insight into how this works.
>
> Does that help any?
>
> 2.) Hmmm.... there are lots of possibilities here. Please check to see
> if the friendbook example has the same issues from the same browser.
>
> If you post a snippet of your controller/XSL for the problem form that
> might help too.
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of
> Barrie Selack
> Sent: Sunday, December 16, 2001 9:56 PM
> To: [EMAIL PROTECTED]
> Subject: [Mav-user] Browser caching and pass through XML
>
> I've got two questions (for now)
>
> 1) have a method that generates the XML to be sent out for a
> particular class, is there a way to just pass this through to the
> XSLT transformation?
>
> 2) I seem to be having browser caching issues when doing editing of a
> form... on the submit the changes get made (I'm looking at the
> database) but the page is not always updating on the return. (e.g.)
>
> http://localhost/editUser.m?userName=me
>
> on submit the update happens, then the object is repopulated from
> the database and sent back. new url: http://localhost/editUser.m
>
> it seems to be if I clear a field... the browser maintains the old
> value.. even if i change other values on the form.. they come back
> changed, but the (supposedly) empty field has the old value.
>
> Any thoughts?
>
> Thanks,
>
> Barrie
>
> _______________________________________________
> Mav-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/mav-user
>
_______________________________________________
Mav-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mav-user
