Skip to main content

Best Practices for evolving existing applications

2 replies [Last post]
vbkraemer
Offline
Joined: 2003-09-03

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?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
vbkraemer
Offline
Joined: 2003-09-03

While I haven't been able to get any comments in this thread, I have continued to scour the net for info about this.

I found this entry, http://www.logemann.org/blojsom/blog/default/2005/01/24/mt_223.html which is very disturbing...

It seems the author is convinced that migrattion requires a rewrite.

Is that the best we can do?

vbkraemer
Offline
Joined: 2003-09-03

I feel like the economics teacher....
http://www.imdb.com/title/tt0091042/quotes