This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I don't know Spring Portlet MVC in detail, but the examples provided as download work on Pluto 1.0.1. So you should be able to deploy and test your portlets (if comparable to the examples) on this portlet container. Just use the Pluto Portal Driver, it is sufficient for testing.
I am not sure what "webshpere portal framework" is. If you mean WebSphere Portal Server -- yes I have deployed some portlet applications on this platform. Even JSR 168. Successfully ;-)
Greetings, Stefan [ January 05, 2006: Message edited by: Stefan Zoerner ]
Author of German LDAP-Book
Committer at Apache Directory Project
Hi You can deploy your portlet on any jsr-168 compliance portal. I prefer StringBeans portal , which imho , has a good future right now it is in version 3.0.1 and soon they will release version 3.1 I tried jsf portlet , Struts portlet on it sofar. you can find it at http://www.nabh.com/ there is also another project named Exo which will reace version 1.1 soon . it looks promissing.
I second the recommendation of StringBeans. A few months ago I went through a review of every open-source Java portal that I could find. The result was that with the exception of StringBeans the products fell into one or the other of two groups:
- a good portal (emphasis port*AL*) that lacked JSR-168 or its JSR-168 implementation was in rough shape
- a good portlet (emphasis port*LET*) container that mostly lacked real portal (user management, content management) features
StringBeans was the only Java portal I found that seemed to be both a really good portlet container and a tolerable portal in its own right. I suspect that by the end of this year the situation will be greatly improved, but at the moment the hype of some products isn't quite in step with what you'll encounter when you download them and attempt portlet development. Many of the options out there are ok if you just want something to learn Portlet development with, but aren't good enough to base a commercial project on. StringBeans was the only open-source solution I found that I thought I could recommend without regretting it.
Something you might find particularly interesting is that they have examples of using MVC frameworks for portlet development. [ January 11, 2006: Message edited by: Reid M. Pinchback ]
You list "Content management" as a real portal feature... Can you comment on that?
I have been evaluating different CMS systems for our company (specific project and in the future) separately from Portals. I noticed that some portals had a CMS piece, but figured that CMS functionality would be better addressed by a CMS-specific framework.
There are also different types of CMS: - CMS to hold web content (such as Wiki) - CMS to hold documents (workflow, permissions, metadata, etc)
Portals seem to focus on #1... But if #2 is on the horison I suppose whatever CMS a Portal can offer will fall short. Plus having a clean separation between presentation (Portal) and business (CMS) is nice. Your thoughts?