Affects Version/s: 1.1.5
Fix Version/s: None
Environment:HideOS X 10.5,
java version "1.5.0_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-237)
Java HotSpot(TM) Client VM (build 1.5.0_13-119, mixed mode, sharing),
uPortal 3.0.1 quickstart,
ShowOS X 10.5, java version "1.5.0_13" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-237) Java HotSpot(TM) Client VM (build 1.5.0_13-119, mixed mode, sharing), uPortal 3.0.1 quickstart, Pluto 1.1.5
When portlet.xml has resource-bundle defined with a package containing an empty messages.properties file, it appears to use the portlet-info title and short-title from portlet.xml (tested with pluto 1.1.5 in uPortal 3.0.1).
While that doesn't seem that bad, if it is ignoring an empty messages.properties file or ignoring the resource-bundle altogether and this is not compliant with the standard, that might be bad.
Eric Dalquist of uPortal mentioned that this behavior, seemingly introduced somewhere between pluto 1.0.1-rc2 and pluto 1.1.5, could be a bug, since in earlier versions of pluto (tested with 1.0.1.-rc2 in uPortal 126.96.36.199 GA) it would fail to load if the the portlet's resource-bundle was defined with a package containing an empty messages.properties file, even if the title and short-title was defined in portlet-info.
Here is the example portlet.xml that works with pluto 1.1.5 (even though maybe it shouldn't?) but doesn't work with pluto 1.0.1-rc2:
(put an empty messages.properties file in the package that it defines as the resource-bundle, which in this example is jasig.portlet.helloworld.MyPortlet)
<?xml version='1.0' encoding='UTF-8' ?>
<portlet-app xmlns='http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:schemaLocation='http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd' version='1.0'>