Hi Nicolas,
This is because custom portlet modes are defined by a portal, not by a
portlet. Portal servers support the standard modes (view, edit, help)
and may define and support additional ones (custom). WebSphere Portal
for instance supports a configure mode as a custom portlet mode.
A portlet can check, which modes are supported by the runtime. This is
what your line
request.getPortalContext().getSupportedPortletModes();
does. Note that it is "getPortalContext", not "getPortletContext" ...
I hope this helps,
Stefan
---
SPEAKER @ JAX 2006
Conference on Java, XML, Web Services
May 8-12, 2006
Rhein-Main-Hallen Wiesbaden
www.jax.de