Whilst trying to setup hibernate search on an infinspan cluster for my RAP application I came accross another "hibernate doesn't like osgi" oddity.
The JMS setup for hibernate search is configured through JNDI. That wouldn't be a problem when running deployed on my tomcat instances, but how should this work in my develepment setup, where I use the RAP tooling and run on the embedded jetty http service? No JNDI there.
So I created a replacement for the JMSBackendprocessor from Hibernate Search, that looks up the jms connection through means of OSGi. Bye bye good old JNDI, never liked you either.
Now if I only had a failover for the workbench...