Asankha, This makes sense, but maybe a little bit inconsistent. Policy files can be referenced on the local file system (file:/c:/...) , but JKS files should be referenced relative to $ESB_HOME.
As a good pratice, I personally prefer to keep these "configuration files" closely together and the repository seems to be a good place for this. Regards, Stefan Lecho. asankha wrote: > > Stefan >> I'm trying to configure WSO2 ESB for using Rampart. The used policy file >> contains the following definition for the JKS file: "<ramp:property >> name="org.apache.ws.security.crypto.merlin.file">../keystore/MyKeystore.jks</ramp:property>". >> >> >> I've tried several settings for the reference to the JKS file, but I'm >> always receiving "java.io.FileNotFoundException: >> ..\keystore\MyKeystore.jks >> (The system cannot find the path specified)". >> >> Looking at the sample policy files contained in the distribution, I've >> noticed that the JKS is always referenced through the repository >> (repository/conf/....). Adding MyKeystore.JKS to the repository solves >> this >> issue. >> >> Although policy files do not necessarily have to, I suppose that JKS file >> are obliged to reside in the repository structure. >> >> Is this supposition correct ? >> > I think this is because we set the working directory to $ESB_HOME (i.e. > the main ESB install directory) when we start the ESB. So any relative > links will be with respect to that.. does this make sense? > > asankha > > _______________________________________________ > Esb-java-user mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user > > -- View this message in context: http://www.nabble.com/Reference-to-JKS-file-in-Rampart-configuration-tp15978136p16012603.html Sent from the WSO2 ESB Users mailing list archive at Nabble.com. _______________________________________________ Esb-java-user mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
