Actually managed to get around this one too, by defaulting to
buffering supported instead of
unsupported in Configuration.java.
I'd love to use the configuration file, however I've no clue where
this is to be included in my webapp, or what setting this property to
true actually means.
Anyone?
public static boolean isBufferingSupported() {
if (buffering == null) {
try {
String buffer = BUNDLE.getString(BUFFER_SUPPORT);
buffering = new Boolean(buffer);
} catch (MissingResourceException mre) {
//buffering = Boolean.FALSE;
buffering = Boolean.TRUE;
}
}
return buffering.booleanValue();
}
2007/8/15, landro <[EMAIL PROTECTED]>:
>
> I modified the evaluatePortletId() method in PortletTag.java (not very nice
> to do this, but we don't want to evaluate any EL in the portletId, so that's
> ok for us), and got a bit further.
>
> Now I'm getting this instead:
>
> Nested Exception is java.lang.IllegalStateException: portlet container does
> not support buffering
> at
> org.apache.pluto.internal.impl.RenderResponseImpl.setBufferSize(RenderResponseImpl.java:176)
> at
> weblogic.servlet.jsp.PageContextImpl.initialize(PageContextImpl.java:70)
>
> Any pointers on this one?
>
>
> private void evaluatePortletId() throws JspException {
> evaluatedPortletId = portletId;
> /*
> ExpressionEvaluatorProxy proxy =
> ExpressionEvaluatorProxy.getProxy();
> Object obj = proxy.evaluate(portletId, pageContext);
> if (LOG.isDebugEnabled()) {
> LOG.debug("Evaluated portletId to: " + obj);
> }
> evaluatedPortletId = (String) obj;
> */
> }
> --
> View this message in context:
> http://www.nabble.com/PortletTag-causes-ELParseException-on-weblogic-9.2-tf4271889.html#a12159000
> Sent from the Pluto - Dev mailing list archive at Nabble.com.
>
>
--
Bekk Open Source
http://boss.bekk.no
