snip
> I'm in the middle of working out a
> design for portal-like applications using Tiles and the very cool RSS
> Channel bean from the Commons-Digester. I'd love to add personalization
> to this as well.
A design for portal-like applications is of high interest to me. I would
love to hear as soon as you have this design (or draft) published. I could
see many instances where personalization is almost a necessity.
> While keeping this in a database is a good option, Jetspeed creates a
> folder for each user and stores the configurations there in XML. So
> that's something to think about too. I'm looking at Sixbs by Tagtraum
> (http://www.tagtraum.com/sixbs.html) to store user configurations this
> way. You can probably do the same thing with Castor, but this looks
> simplier to use.
I realize this is still a bit early but what is the interest for integrating
Struts/Tiles and the Jetspeed Portlet API? It's of high interest on my end.
It looks like this would offer performance with a solution based upon this
and background XML compilation. Take all the xml feeds, pre-compile them
into html / jsp fragments, and then all this would have to happen at request
time, is that the engine would assemble all the fragments that were already
precompiled. Is this what you were envisioning?
The things that are waiting technology-wise might be - is this a standstill
until this is done?:
1 - Completed integration of struts and tiles. May be a few months?
2 - Jetspeed implementation of the Portlet-API: not been fully integrated
into the main branch, and then some testing.
What are your thoughts?
