Get-localized-string usuage

Question

Hi,
I am trying to get this function to work in my bpel process. When I do as follows, it works fine :
orcl:get-localized-string('file:/d:/','','MyResourceBundle','','','','MY_KEY')
But I don't want my resource bundles to be present at D:, or want to give an absolute path to them. I want them to be bundles with the bpel suitcase. I have placed them there and tried a few combinations like below.
orcl:get-localized-string('','.','MyResourceBundle','','','','MY_KEY')
orcl:get-localized-string('.','','MyResourceBundle','','','','MY_KEY')
orcl:get-localized-string('./','','MyResourceBundle','','','','MY_KEY')
orcl:get-localized-string('','./','MyResourceBundle','','','','MY_KEY')
What would be the correct way to invoke this function. The error which I think is irrelative but I give it below anyways :
<Faulthttp://schemas.xmlsoap.org/ws/2003/03/business-process/http://schemas.xmlsoap.org/soap/envelope/>
<faultcode>null:selectionFailure</faultcode>
<faultstring>business exception</faultstring>
<faultactor>cx-fault-actor</faultactor>
<detail>
<summary>Leeres Ergebnis für Variable/Ausdruck. Der XPath-Ausdruck für Variable/Ausdruck "orcl:get-localized-string('','./','MyResourceBundle','','','','MY_KEY')" ist in Zeile 179 leer, wenn ein Lese- oder Kopiervorgang ausgeführt wird. Vergewissern Sie sich, dass das Ergebnis für Variable/Ausdruck "orcl:get-localized-string('','./','MyResourceBundle','','','','MY_KEY')" nicht leer ist. Mögliche Gründe für dieses Problem: Einige XML-Elemente/Attribute sind optional, oder die XML-Daten sind entsprechend dem XML-Schema ungültig. Zur Überprüfung, ob die von einem Prozess empfangenen XML-Daten gültig sind, kann der Benutzer den Schalter "validateXML" auf der Domänenadministrationsseite aktivieren. </summary>
</detail>
</Fault>
Regards,
Edited by: user638005 on May 19, 2009 12:04 PM

Answer 1

This is a last post to this to summarize the results of my experimentation. This is what I found.
What works
========
1. get-localized-string() works fine for absolute paths provided both as url or resource location. But construct should be as follows :
<from expression="orcl:get-localized-string('','file:/d:/','ResourceBundle','en','EN','','NO_OBJS')"/>
<from expression="orcl:get-localized-string('file:/d:/','','ResourceBundle','en','EN','','NO_OBJS')"/>
<from expression="orcl:get-localized-string('','file:/D:/ResourceBundle.zip','ResourceBundle','en','EN','','NO_OBJS')"/>
<from expression="orcl:get-localized-string('file:/D:/ResourceBundle.zip','','ResourceBundle','en','EN','','NO_OBJS')"/>
jars files donot work. Dont know why but thats how I found it to be. Also donot forget the "file:/" prefix. Things dont work without it, it seems.
2. What also works is that you create a jar/zip file of your resource bundles and tell the Oracle App Server where to find it.
2.1 This is done by editing your "server.xml" under your soa_home. Add a new entry for your jar/zip file under the shared-library name="oracle.bpel.common" section.
2.2 After doing this and restarting the SOA suite, you just have to provide the name of the resource bundle i.e the 3rd param and everything works.
2.3 There could be some performance impact here of which I have no idea (whereby the class loader searches all jar files in common location for the given resource bundle.)
2.4 I personally used the second parameter to atleast provide the name of the jar file which has my resources. Don't know if that has any effect or not.
2.5 Since the resources are looked up at run time and are not needed for bpel compilation by bpelc, there is no need of adding the resource bundle jar file to the bpelc classpath. E.g.
<from expression="orcl:get-localized-string('','ResourceBundle.jar','ResourceBundle','en','EN','','NO_OBJS')"/>
2.6 Here I found things work whether it is zip or jar file.
3. Specifying a zip file from which a resource bundle should be taken out works when you provide the absolute path as follows: (same applies for url)
What does not work
=============
1. the "." current directory construct does not seem to work. I.e you place the resource bundles in your bpel suitcase and think that the current directory will turn out to be the deploy location of the bpel suitcase. This assumption seems wrong.
2. Both these forms donot work:
<from expression="orcl:get-localized-string('','D:/ResourceBundle.zip','ResourceBundle','en','EN','','NO_OBJS')"/>
<from expression="orcl:get-localized-string('','D:/ResourceBundle.jar','ResourceBundle','en','EN','','NO_OBJS')"/>
Regards,