susaliner.blogg.se - Jrebel install

JREBEL INSTALL PATCH
JREBEL INSTALL CODE

And it should also work with my current technology stack… Sounds pretty cool, doesn’t it?

JREBEL INSTALL CODE

That means that no more long deployment procedures (mvn clean install…) are necessary for simple code changes. JRebel promises faster and much more pleasant Java application development because of mapping the project workspace directly to a running application. Motivated by the talk Do you really get class loaders? from Jevgeni Kabanov devoxx in Antwerpen, I’ve downloaded the demo version of JRebel this evening. You can find some Integration-Javadocs about that on the webpage of zeroturnaround.

JREBEL INSTALL PATCH

I’ve also tried to write an own JRebel plugin to patch the Sling/JCR Classloader, but at the moment it’s not that stable to use it in productivity. We plan to use it in the next couple of weeks and will for sure find some pitfalls… (hopefully not, but you know… 😉 ) With this configuration I can save my java files in Eclipse, reload the page and the changes are immediately viewable.įor now, this configuration isn’t tested in productive work. The parameter -Drebel.packages_exclude=sun.reflect is a kind of a workaround of a JRebel bug, in the newest version it shouldn’t be necessary anymore.

In the start script of CQ, I added the following parameters:ĬQ_JVM_OPTS="-noverify -javaagent:/jrebel.jar -Drebel.packages_exclude=sun.reflect".

In the pom.xml of the project, I had to add the following line.

In my maven project, I saved rebel.xml under src/main/resources, it contains the path to the classes folder of my eclipse workspace.

The result first: after a couple of mails with Lauri Tulmin from zeroturnaround, it finally worked. So to load a page, two different classloaders are used, first DynamicRepositor圜lassLoader (Sling/JCR) which loads the jsp out of the repository and then instantiates a class (for example for a tag) that is served by the OSGI bundle, for which FelixModuleClassLoader is used.Īs you can read on Felix with JRebel is beta support, so why not try to use it with CQ at least to eliminate the deploy process of the OSGI bundle? All the stuff that is needed to generate the view (jsp, xslt) is saved directly into CRX, the JCR of CQ5.

Our basic approach to write components, services, tags and so on is to add all logic (java classes) into a OSGI bundle and deploy that on Felix. It’s based on Apache Sling which uses Apache Felix as OSGI Container and a JSR-283 compliant java content repository to persist it’s content/data. As I’ve mentioned in my last technology post, I’ve now also tried to use JRebel with a WCMS system, namely Day CQ5.3.