To answer your last question, maybe you can split your xml file using external
entities (as explained f.e. here:
http://xml.oreilly.com/news/learningxml_0101.html?CMP=ILC-0PY480989785). Though I did
not use this personally with the maverick xml file, it should work with any xml file.
1. It sounds to me that you do not need a lot of different commands, but
possibly a lot of different views... If you need to do some Java action on a
specific request, you can do that with a controller. You will (probably) at
least end up with the number commands that you need to have controller
Hi Jaap,
Thanks -
Peter
On Tuesday 15 June 2004 18:29, Jaap van Hengstum wrote:
To answer your last question, maybe you can split your xml file using
external entities (as explained f.e. here:
http://xml.oreilly.com/news/learningxml_0101.html?CMP=ILC-0PY480989785).
Though I did not use this
Hi Eelco,
Thank you for your reply - you are spot on in your assumption.
I am now trying to implement a first try of Mav and find it is so simple
and clean compared to Cocoon.
To illustrate my problem described in my previous post.
eg: http://easyspeedy.com/products/pricelist.html
