Announcement Announcement Module
Collapse
No announcement yet.
ReloadableResourceBundleMessageSource support for extended document root Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • ReloadableResourceBundleMessageSource support for extended document root

    We use ReloadableResourceBundleMessageSource to retrieve messages specifying "basename" and also reload them after duration configured by "cacheSeconds". And the "basename" used was actually a symbolic link name (in Unix) to a folder containing resource bundles. This worked fine until we applied a patch to Websphere which no longer recognizes symbol link.

    With patch, WebSphere now supports specifying what it calls "extendedDocumentRoot" in its proprietary format XML file (ibm-web-ext.xmi) where absolute file path can be given to make it look it up. Problem is, ReloadableResourceBundleMessageSource has no clue about the absolute file path (a.k.a "extendedDocumentRoot") to try looking into if it cannot find the "basename" specified for ReloadableResourceBundleMessageSource. Is there a way to specify it?

    Example: Bean definition in my spring.xml looks like say:
    <!-- _________________inside spring.xml________ --/>
    <bean id="dynamicProperties" class="org.springframework.context.support.ReloadableResourceBundleMessageSource">
    <property name="basename" value="/foo/folderNameHereIsSymLink"/> <!-- this folderNameHereIsSymLink is not there now! -->
    <property name="cacheSeconds" value="300"/>
    </bean>

    <!-- _________________end of spring.xml________ --/>

    What is needed if "/foo/folderNameHereIsSymLink" is NOT found, to somehow specify/make it instead look into an absolute path say "/foo/folderNameHereIsAbsPath".
    -----------------------
    Any insights/pointers are greatly appreciated.
    Thanks
    -Srini
Working...
X