Robert, don't you think it would be worthwhile to integrate SpringMVC into
magnolia so you could get SpringMVC's validation, conversion and navigation
functionality into the magnolia-templates?
I tried to do the same with JSF, but gave up for the time being.
Have you tried to do this with SpringMVC since you're saying it can't be done?
Can't SpringMVC's workings be modified to work with Magnolia's uri-handling (I'm
certain this can be done with JSF, but ran into other problems)?
I know we somewhat discussed this is the J2EE thread, but still nobody has shown
a web-framework interoperatable with magnolia. Bit of a shame, cause validation,
conversion and navigation would be really handy.
Gabhart, Robert Kyle @ Link wrote:
I am an avid proponent of Spring and Spring MVC. I even developed a custom
framework for my company that incorporates Spring. I have not attempted to
integrate Magnolia and Spring MVC, but my initial thought would be that they
are not compatible. Both of them provide controllers and attempt to capture
URIs and make processing decisions based upon URIs. Unless you were to
modify the Magnolia source, I don't think you can integrate them. I suggest
the following courses of action:
1) Use Spring (but not Spring MVC) within your templates to support
datasource access, cross-cutting concerns (IoC), loose-coupling of
components, etc.
2) Build Spring MVC apps and run them alongside magnolia as separate web
apps within the same server. Link between them and reference the respective
applications when necessary. I do this for my company's intranet. A Spring
MVC app is used to provide a news management console that writes to a
database. I then have templates that read from that database and display
news articles.
3) Get really ambitious and re-engineer Magnolia to operate within the
Spring Framework. ;)
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
