> Do I really need all of jetspeeds functionality or should I just
> implement the Cocoon stuff directly within turbine?
We went even further. Because we feel that Cocoon and Jetspeed are still in
a lot of flux (Jetspeedsters please forgive me ;-) ) we decided to stick to
just Turbine for the moment and do our XML in this way:
XML with embedded WebMacro ---- XSLT ----> HTML / WML / whatever
The XSLT is done directly with Xalan, and to get portal functionality we
built our own VERY simple portlet-like stuff. When the full Cocoon 2 becomes
a reality, and Jetspeed settles some outstanding issues, like the current
PSML shortcomings, etc., we will definitely start using them.
In the mean while, time is money for an extremely small startup like ours.
And with most of the components we would like to use still in various states
of beta, sticking to "raw" Turbine (which is pretty GREAT actually), is our
best bet.
You may require more than the simple functionality we're using, but I'm just
trying to say what works for us.
Frank Conradie
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
