Reinhard Poetz wrote:
From: AlanYup. Alan, take a look at the XMLDBSource and XMLDBSourceFactory. I think you'll find them reasonably similar to what you might want to do (in src/blocks/xmldb/java/org/apache/cocoon/components/source/impl)
* Geoff Howard <[EMAIL PROTECTED]> [2004-02-22 18:47]:
Alan wrote:memory overhead
* Upayavira <[EMAIL PROTECTED]> [2004-02-22 07:58]:Still, I think finding a way to use momento to reduce
I tend to think that Momento isn't suited to this need.
However, as an XML data repository, it seems very interesting.I've got a better idea of how Jisp is used in Cocoon from reading
all the discussion after my post.
I suggested Momento because someone suggested Xindice which led
me to believe Jisp handled an XML persistence task.
Might not be the best bet, no.
instart... (hint
working with large xml datasets has great potential. No one really knows how great, but a demo/sample using it would be a
hint :) )Working on it. As noted, I have JAXP implemented and SAX interface
to XUpdate. I have APIs. I am going to start working on services
next.
A Cocoon generator that takes a Momento data source and an XSLT
transform would be a start.
I'm not sure how to get information into Momento via Cocoon. I'm
thinking about some sort of Woody binding, but that goes beyond
my current understanding of Cocoon.
speaking without following this thread closly: What about implementing a Momento source?
If you implemented a MomentoSource, and made it implement ModifiableSource, then you would be able to read/write from within Cocoon. With this, you would be able to use Woody's binding functionality to bind forms directly to Momento data.
You could also do something like the XMLDBTransformer to allow updates (src/blocks/xmldb/java/org/apache/cocoon/transformation/XMLDBTransformer.java).
[NB. with an XML:DB interface to Momento, you wouldn't need to do anything to interface to Cocoon].
Hope this helps.
Regards, Upayavira
