Hi All you struts/magnolia users,
Sorry for the cross post, but I'm not sure if this is a development question
or a user question. Since you don't absolutely have to write jsps to be a
user, but you might.
The Question:
Are people doing anything more interesting with struts than always using
redirects and static handle references?
Some Thoughts:
I have been working a little on integrating some struts based jsp pages as
templates used in magnolia, and I've come to a conflict between the
architectures that I don't yet have a good solution too. It seems to me the
problem is a conflict between the struts' approach based on a limited set of
jsps and Magnolia's approach based on a flexible set of pages with jsps being
pulled in when (at all) needed.
I see two problems so far:
1. If I don't forward without a redirect, then the usual filter machinery of
magnolia is left out of the loop, and I can't forward to a traditional
magnolia path/handle and let Magnolia do it's work of security and template
selection and what not.
2. I don't want to always use redirects.
Okay there are actually four problems.
3. The struts forwards configured in my external (to Magnolia)
struts-config.xml file have static path references. I'd rather be able to
able to configure paths for my actions more dynamically so that I can take
advantage of the dynamic page/node structure of magnolia.
4. I suppose my struts config could reference the jsps directly (yuck) and
they could figure out themselves what node to load up and bypass all the
Magnolia filter/security/login machinery. (also yuck)
Cheers,
Chris
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
