Seam incremental hot deployment of JavaBean classes

[asookazian]

As per 2.8. Seam and incremental hot deployment of Seam 2.1.2.GA ref doc, why are there references to WEB-INF/dev as well as src/hot (which used to be src\action in previous versions IIRC)?

Does this mean that the seam-gen build.xml will package any JavaBean classes from src/hot into WEB-INF/dev when we do 'ant explode' or 'ant deploy', etc.?

Why can't we use an EAR and still have Seam's hot incremental deployment of JavaBean components (i.e. not using EJBs in our app but perhaps EJBs in JARs from a 3rd party or different project or utility classes, etc.)?

[asookazian]

That section also states the following:

the components must be JavaBean components, they cannot be EJB3 beans (we are working
on fixing this limitation)

I thought it was basically impossible (based on a recent thread on this forum) to hot deploy EJBs.  I know Java Rebel supports hot deployment of EJBs in the body, but not when your change the signature and/or add/delete methods in the local interface...

[asookazian]

Currently, I have a Seam seam-gen'd EAR project that I'd like to convert to hot incrementally deployable (i.e change SFSBs to JavaBeans).  Is this a good idea other than the fact that I'm aware I will lose EJB container services like tx management (Seam doesn't support all the tx types that CMT does) ejb timers and interceptors, for example.

[blabno]

I think that for early stages of project development working on WAR is great for Hot Deployment feature. It really increases performance.
I'm planning to work on WAR until some point, and later when my app will be almost ready for production and I will need to work on performance, I will move to EAR. I hope it won't be tough to do the switch, but I have no experience in this yet.