The Artima Developer Community
Sponsored Link

Java Answers Forum
Best practices for evolving existing J2EE code

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
vince kraemer

Posts: 1
Nickname: vkraemer
Registered: Mar, 2006

Best practices for evolving existing J2EE code Posted: Mar 26, 2006 1:26 PM
Reply to this message Reply
Advertisement
I have posted this question to a number of forums. Nobody seems to have an answer. So, I am posting it here.

I am looking for pointers to "Best Practices" for extending existing J2EE 1.4 applications into Java EE 5 environments.

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...

Are there other "gotchas" out there?

vbk

Topic: almost compiled Previous Topic   Next Topic Topic: Exceptions. Please help.

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use