Jeff,
Thanks for the quick response.  I'll try to explain the second question a
little better.

http://cvs.apache.org/viewcvs/jakarta-velocity-tools/  This is the link
for the Velocity tools subproject.  I think they call it a "Pull-MVC".
I write something like a bean (or, a bean) that stores user info.  Then,
in the toolbox.xml file I assosicate the prefix "user" with my class,
com.mycompany.UserBean.  Then, in every velocity page on my site I can
access $user.firstName, or $user.lastName.

Without said tool I have to specifically put my UserBean into the context
in each servlet that would use it.  The tools way, it is always there, ready
for use.

Now, I'm not that familiar with Maverick yet, but it may already be doing
this some other way.  What the equivalent in domify would be a block of xml
being added to the dom for each object/class that I define.  So that in any
one of my xsl pages I could access <xsl:value of="//user/lastName"/> and
<xsl:value-of="//user/firstName"/>.

Does my explanation sound crazy?  Am I making sense?  Because it doesn't
seem
like it when I read over this message.


And just to make clear with my first question.  I define the
DomifyViewFactory
and then point my command to a controller and a view and my collections will
'automagically' be part of the dom?  Neato.


Charlie


> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Schnitzer,
> Jeff
> Sent: Monday, August 19, 2002 3:14 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: [Mav-user] domify: beginner questions
>
>
> > From: Charles N. Harvey III [mailto:[EMAIL PROTECTED]]
> >
> > 1) For a really simple test I want to create one class, and one
> view page.
> >    In this class file, what domify classes do I have to import/extend to
> >    create a dom object?  And, is there a certain type of
> collection that I
> >    have to use, ie. Map, Collection, Vector...
>
> You don't need to do anything special with your controllers to use domify.
> Just make sure you define the DomifyViewFactory module in your
> maverick.xml,
> and use <view type="domify"> (or set the default-view-type).
>
> Domify will translate the standard Java2 collection classes (which all
> basically implement Collection or Map).  Vector implements List which
> extends Collection, so that's fine, but ArrayList is a much better
> implementation.
>
> > 2) I was wondering if some Velocity functionality could be added to
> > domify.
> >    Specifically, the Tools subproject.  The ability to write a tool and
> > have
> >    it accessible to every view page via reflection is quite
> amazing.  And
> > I
> >    was wondering if such a thing would be possible in xsl.
>
> I'm not sure exactly what you're trying to do, but check out DVSL and
> Maverick's DVSL transform in the opt-velocity package.  Much of the
> declarative power of XSL, but using the Velocity template engine.  You can
> use domify with DVSL transforms - I wouldn't try to run a really
> high-traffic site this way, but it works great.
>
> Good luck,
> Jeff Schnitzer
> [EMAIL PROTECTED]
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> Mav-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/mav-user
> Archives are available at http://www.mail-archive.com/



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Mav-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mav-user
Archives are available at http://www.mail-archive.com/

Reply via email to