Many times the complexities of the portal can be alleviated by relying on your knowledge of plain old
Servlets and JSPs.
With Servlet and
JSP apps, the session can't cross a war file. The exact same thing can be said for a portlet war file - you can't share sessions across a war.
Why not put both of these portlets in the same war? If there's a compelling reason for them to communicate, then perhaps they should be packaged as part of the same app. Just add another entry to the portlet.xml file. So many portlet books (not mine of course) only ever show one portlet per war file. I can't think of too many
J2EE applications with only one command object, so why would most portlet applications only have one portlet? (sorta equiavlent to a
JSF or
Struts command object).
Think about it.
-Cameron McKenzie
[ January 28, 2008: Message edited by: Cameron McKenzie ]