-
1. Re: Inc. hot deployment classloader blues
nickarls Jan 14, 2008 2:55 AM (in response to 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" -
2. Re: Inc. hot deployment classloader blues
pmuir Jan 14, 2008 6:04 AM (in response to nickarls)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) -
3. Re: Inc. hot deployment classloader blues
nickarls Jan 14, 2008 6:21 AM (in response to 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. -
4. Re: Inc. hot deployment classloader blues
pmuir Jan 14, 2008 12:06 PM (in response to nickarls)"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. -
5. Re: Inc. hot deployment classloader blues
nickarls Jan 15, 2008 2:18 AM (in response to 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 :-)