Portlet Factory, Version 6.1.2
Generated file names and limitations
Some application servers have a limit on the length of a path name.
On some application servers, there is a limit of 255 characters on the length of path names (including the file name). In IBM® WebSphere Portlet Factory, JSP files and Java classes are generated based on the model name and any profiles applied to the model. Typically, the file name lengths are under 255 characters.
However, when you use the model as a portlet in nested portals, the generated file name could cause the path length limitation to be exceeded.
To prevent the generation of file names that are too long, the profile names are converted to a unique ID. You can control the file name length at which the WebSphere Portlet Factory converts the profile name portion of a generated file name to an ID by setting the following property in the WEB-INF/config/cluster.properties file.
bowstreet.profiles.maxKeyLengthThe default value for this property is 60.
Note: The maxKeyLength value does not include the length of the whole file name, just the length of the profile name portion. As a result, set the maxKeyLength value low enough to account for the portlet name, widget name, model name, and any other parts of the path to the generated file. For example, the datatablepage that is used as a portlet in a nested portal can have the following file name.
dataviewportlet_main_external_partners_premium_techsource_personalizationroot_techuser_pressreleases_datatabletablepage.javaWebSphere Portlet Factory checks the length of the profile names embedded in the name. If the length exceeds the value of the maxKeyLength property, the profile names are converted to an ID. The following is the result of converting the profile name in the previous example to an ID.
dataviewportlet_160568228_datatabletablepage.javaParent topic: Directory structure for IBM WebSphere Portlet Factory Web applications
Library | Support |