Seam 3 booking example and IntelliJ

[mobwerner]

I am new to seam 3 and also to IntelliJ.(gave up on eclipse but sofar I enjoyed the ride with IntelliJ)

I have imported the maven seam booking example into my IDE. I got my module set to produce an artifact of the type war-exploded and configure my jboss run configuration with this artifact.

It works excellent when updating web sources like facelets. A browser refresh and the  page reflects the updates.

When I try to deploy from IntelliJ the exploded war it gave me an error. When I deployed the war via jboss-harddeploy (maven jboss plugin), it gave me no problems.

Does anyone have experience in using IntelliJ with the seam examples?

I do not mind to have no hot- deploy for my classes but I would like to be able to deploy or undeploy the exploded war to jboss from IntelliJ and not from the maven plugin.

My Jboss is version 6.0.0 final and my version of IntelliJ is 10.5.

I will provide the error later as I am posting this on my way back home.

[pgmjsd]

I'd use the Maven plugin, since it is working for you.

Personally I stopped using IDEAs app server integration a long time ago.  It was just too much of a pain for me to support it for all the developers on the team.   For hot deploy of web resources I usually make a simple ANT target and bind it to key-chords in IDEA for rapid development cycles.

[lightguard]

I feel the same, haven't used IDE + server integration for a while.

[mobwerner]

I got it working from inside IntelliJ.

The error I got was related to @PersistenceContext and hot deployment. I have seen in the jboss jira there is a pending issue about this.

See https://issues.jboss.org/browse/EJBTHREE-2256

I have changed the BookingAuthenticator class so it uses a SMPC (@Inject in bookingAuthenticator instead of @PersistenceContext, created a producer field for entitymanager)

Apparently this solves my problem when redeploying the seam booking from within IntelliJ Jboss Server integration.

[mobwerner]

Update:

Changing some stuff in AuthenticatorBooking worked with a simple deploy.

When I changed the BookingLog, it did not work without rebuilding the project.

I suppose a rebuild project will cause the implementation class of BookingLog to be generated.

My observation is that a normal build does not recreate the implementation class of BookingLog interface.