Gonzalo Aguilar Delgado wrote:
Hi everyone.
I see that when PortletWindowImpl does not find a portlet a Exception is
returned to the PortletTag class.
This means that whole portal stops because can't render anything.
I'm writing a small patch for this.
I can handle this several ways but two of them seem meaningful:
1.- Implement a custom portlet that will be rendered when the
requested one is not available.
This portlet will handle the situation and show a small message
saying that the portlet is not available.
While this is a good solution if something bad happens
and this portlet is also not available we will se again
the main crash of the portal.
2.- Implement a special renderer that will render the message
directly from the container.
Is there any useful solution?
What do you think it's best?
In Jetspeed-2 we handle this by capturing all container invocation errors and either returning an appropriate (pluggable/configurable) error
page for non-rendering processing (Action/Event/Resource), or display an appropriate message within the PortletWindow instead.
For Pluto Portal this might require some extensive changes to do something similar, which in that case might be out-of-scope for the purpose
of Pluto Portal itself (if doable with a small fix/patch would be fine however).
Be aware that Pluto Portal is not written for nor targeted at real production usage: its primary and only purpose is to provide a testbed
environment for the Pluto Container.
If you want to expand upon the Pluto Portal yourself, you might be looking at some major rewriting to get it to acceptable quality level
(for that purpose).
If you really need a production ready Portal I suggest looking at Jetspeed-2
Portal instead.
Regards,
Ate
Thank you.
____________________________________
Gonzalo Aguilar Delgado
Consultor CRM - Ingeniero en
Informática
M. +34 607814276
