quote:

---

>
> I have a number of links in a portal theme that are hard-coded to a
> specific static server, but I would like the theme to be reusable in
> other
> environments by having those links pick up a value from a property
> file
> that could be set differently for each environment I deploy the theme
> to.
> I figured I would do this the same way that the sample themes already
> pick
> up values using the <wps:text> tag. I have a file Footer.jsp included
> in
> Default.jsp that has the following line:
>
> <a href='https://<wps:text key="fieldnet.host" bundle
> ="nls.Thrivent"/>/fahome/map/'>Site Map</a>
>
> This is not picking up the value of key "fieldnet.host" from the new
> file I
> created called Thrivent.properties, nor from its related file
> Thrivent_en.properties (which I added later, hoping that the
> language-neutral file would be picked up) that I placed in the
> directory:
>
> /usr/WebSphere/AppServer/installedApps/DAFAPOR001/wps.ear/wps.war/WEB_INF/classes/nls
>
> If I replace this line with:
>
> <a href='https://<wps:text key="link.my.portal" bundle
> ="nls.engine"/>/fahome/map/'>Site Map</a>
>
> the JSP correctly picks up the text "my portal" from either
> engine.properties or engine_en.properties in the same directory where
> I
> placed the Thrivent files. Maybe I have the wrong directory, or maybe
> I
> need to specify which property files are valid to load somewhere else.
> Maybe the bundle first needs to be referenced in Default.jsp. Maybe I
> really need to implement this code with JSTL like the Info Center
> suggests
> (but why does the code still work for other property files?). Any
> help on
> how to make this work would be appreciated.

---