I'm using Hibernate Search 3.1.1.GA and JPA (hence persistence.xml) and deploying to WebSphere Application Server 6.1.

The deployment will be clustered, and the desired target directories for the search indexes will include the unique node names. Therefore, it would be a huge help if I could include a reference to a WebSphere variable in the indexBase definition in the persistence.xml file. e.g.:


I haven't hit upon any standard way or any good reference, so I figured I'd ask to see if anyone can tell me if this is even possible?

Hi,

I guess there is no standard way of doing this. If you want to go down this path you will have to "intercept" the properties before they are used. You could do this either by sub-classing Configuration or AnnotationConfiguration depending on your setup. Hooking into Configuration would allow you to also modify/add other properties.

In case you are only interested in the directory provider, you could also sub-class FSDirectoryProvider. Just override initialize, expand your property and then call super.initalize(). I guess this would be the easiest to solve just this usecase.

--Hardy

Thanks for the reply, Hardy.

I went with sub-classing FSDirectoryProvider, and setting a JVM Custom Property in WebSphere that reads the desired WAS variable into a System Property. If such a System Property is found, I reset the indexBase before calling super.initialize().

The biggest pain was figuring out how working around the use of MaskedProperty, where naturally I managed to try every version that called the methods marked Unsupported until I finally RTFM and found a working solution.

Our middleware team is much more happy now. And now that I've figured the trick for setting System Properties via WebSphere out, we have a couple more tools we're using that will use the same strategy. Always like solutions that can be reused!