David Chaplin-Loebell wrote:
Yup, a Provider is one way. An (XSP|XPS|SAX Filter) taglib is another.Has anyone already written this provider? Am I on the right track in assuming this would be how to do it?
There's no hard and fast rule, but a good convention for deciding if a Provider or one of the other mechanisms is more apropriate is to determine what the *source* of the document really is.
For example, a product catalog page that combines data from different sources, or needs to insert a block of dynamic data from a database is probably best implemented using taglibs, while a content management system that is returning the *base* source XML itself from a database, is best done as a Provider.
Make sense?
-kip
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
