users@glassfish.java.net

Best practices for evolving existing code

From: <vince.kraemer_at_Sun.COM>
Date: Thu, 09 Feb 2006 16:23:01 -0800

Does anybody have a pointer to what folks should do with their existing J2EE 1.4 code/applications?

What are the migration/evolution best practices?

For example: if I have a J2EE 1.4 ejb-jar and I want to start doing EJB 3.0, what should I do?

a. change the namespace in my existing jar, then rock and roll...
b. create a new jar for my EJB 3.0 components and "call" back and forth between the two jars...

I would imagine that we don't get to mix-and-match @Entity and CMPs...

What other "gotchas" are there?

vbk