-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
When integrating pluto-1.0.1-rc4 with wsrp4j I found what I think is a pluto
bug. In ConfigService.properties, with rc4 there's a new property:
...
portletcontainer.supportsBuffering=no
...
This property is used in org.apache.pluto.PortletContainerImpl:
...
private static String CONTAINER_SUPPORTS_BUFFERING =
"portletcontainer.supportsBuffering";
...
public void init(...) {
...
Boolean b = (Boolean)properties.get(CONTAINER_SUPPORTS_BUFFERING);
...
}
But in org.apache.pluto.portalImpl.Servlet it's not used at all, it's ignored:
...
Properties properties = new Properties();
try
{
PortletContainerFactory.
getPortletContainer().
init(uniqueContainerName, config, environment, properties);
}
...
So? I've had some problems with this integrating pluto & wsrp4j because the
current version of wsrp4j passed null in properties field.
Carsten or Elliot, if you think this is a pluto bug, please forward it to
pluto-dev. Thank you.
Regards.
Diego.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFDE9aqgyzZYflJelERAmfKAJ9hmaJiRXG/pU1U+WABgrYezCB4jQCeIDC4
WyoVGvGtsKeT5wWkap3Osd8=
=F3uI
-----END PGP SIGNATURE-----
