Inc. hot deployment classloader blues

[nickarls]

I start out in JBoss Tools Seam Module by creating a new seam project (WAR), add an entity, and a backing bean method that inserts an entity and a button that calls that method => everything is inserted fine.

Then I add a dependency from the model to the action (all this domain-driven-rich-model-stuff, you know) => NoClassDefFounderror for the action. Not surprising, since the WEB-INF/dev has it's own classloader, so I try to put everything under /dev (the entities are POJOs anyway so I would like to have them there). Edit the output folder for the model. Now I get a "java.lang.IllegalArgumentException: Unknown entity: org.domain.Concept.model.Foo".

How come? The classes are there, the persistence.xml is there, seam.properties is there. How can you get the entire source tree available for incremental hot deployment?

[nickarls]

It looks like the WEB-INF classes is populated even if no source folder are outputting to the default place so I removed the "extra" persistence.xml from classes/META-INF so that there wouldn't be any classloading conflict but that only got me a

"[Ejb3Configuration] Could not find any META-INF/persistence.xml file in the classpath"

[pmuir]

You can't hot deploy entities. Sorry :(

The only solution is to not hot deploy action classes on which your model depends (normally your model wouldn't depend on your actions)

[nickarls]

Well, I doesn't have to be hot deployment for the entities, lukewarm would do and

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=127432

indicates that it would be possible. At least with ant scripts, although it is the eclipse-version I'm currently looking for.

[pmuir]

"nickarls" wrote:
Well, I doesn't have to be hot deployment for the entities, lukewarm would do and

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=127432

indicates that it would be possible.

Suggests that what would be possible?

The names in a seam-gen project might be misleading you? put anything you want hot deploying into src/action and anything you don't want hot deploying in src/model. You can't hot deploy entities. You can't have any dependencies from src/model to src/action. JBoss Tools works exactly the same way as seam-gen here.

[nickarls]

I was referring to "btw. the part that does not work when we say EAR hotdeployment does not work is the hotdeploy of EJBs" but I must say I'm a little unsure about the entity beans/POJO names in EJB3.

@Entity makes a class an Entity Bean which used to be a Enterprise Java Bean but now is an JPA entity which is a JavaSE POJO, sort of :-)