JREBEL REMOTE PORTLET HOW TO
JREBEL REMOTE PORTLET CODE

Enhancements are mainly in documentation, integration between Liferay and WebSynergy. WebSynergy Milestone 3 Release ! This is the last milestone release before the upcoming commercial release. Still, this is much better than waiting a minute for your JBoss server to restart.Īnother month has passed, year end is close so let's see what happened this month in the portal space: Unfortunately when activating the builder Eclipse might prompt you when editing files and (depending on the speed of your machine) hang for a second or two after saving a file. Assert that Eclipse uses a dedicated output folder and not the Maven target/classes.Also take care that you always build with your specific hot deploy profile - otherwise make sure to clean before using the build again.Once you see that the builder does not fail, you can also switch off the console allocation in the 'Common' tab. The JRE you have configured is actually a JDK - otherwise the builder will fail.Make sure that the following conditions apply to your Eclipse setup: The new Maven build should look like the following: Simply go to the Eclipse Project properties and click 'New' on the 'Builders' properties. If you want to run a similar luxury setup as you get from JBoss Tools, you can add a Maven builder to your project. This is simplest done by adding it as a resource folder, which will copy the classes to the target/test-classes directory before the test classes are compiled:

Similarly, we have to add our output folder to the test classpath.

Note that it is recommended to create a profile for this build setup as both your continuous build as well as your operations team might not care too much about using hot deployment. The plugin configuration is straight forward as it's based on the regular compiler plugin and is shown in the XML snippet below. This is necessary for the Seam classloader to pick up the changes, only updating the file is not enough.

Remove outdated hot deployable class files from the JBoss deployment.

JREBEL REMOTE PORTLET CODE

The source code location is configurable as well as the output directory. Hook into the compile phase and compile the source code to a dedicated directory.The solution I came up with was to write a new Maven plugin which extends the Maven compiler plugin with a new hotdeploy:compile goal and the following functionalities (source code as well as a simple Maven 2 repository is available in our Google Code account): Make sure Seam unit tests still compile.Publish updated resources to JBoss, including domain model classes, seam components as well as XHTML pages.We need to be able to distinguish between hot and regular deployable code. Distinguishing compiler output: The Maven compiler plugin by default compiles everything in the same output folder.In order to avoid trouble and also to allow using hot deployment from a command line build, I experimented with several approaches to achieve hot deployment with Maven.

The reason was that Eclipse hot deployed classes to WEB-INF/dev where Seam expects them, but Maven being completely unaware of it packaging all classes in the common WEB-INF/classes folder. More than once I've seen the situation where JBoss Tools and Maven got in each others way, ending with JBoss rejecting to restart the application due to 'duplicate components'. Seam uses a special classloader and relies on monitoring the WEB-INF/dev folder for changed classes - where Maven is completely unaware of this and uses the standard WEB-INF/classes folder to deploy all classes in the project. While JBoss Tools provides a nice code hot deployment feature when working with Seam on JBoss, things can get a little hairy when using a Maven build with the project.

JREBEL REMOTE PORTLET HOW TO

Today I want to share some ideas on how to tackle the combination issues. While combining this with our favorite tooling suite consisting of Eclipse and Maven, we had to realize that Seam has a much longer tradition with Ant, and Maven support is only slowly moving in. As you might have read in previous posts, one of our favorite web application stacks consists of JBoss Seam.

Jrebel remote portlet