• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Upgrade existing J2ee application to SEAM - any guidelines??

 
Ranch Hand
Posts: 213
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Yuan & Jacob

I m relatively new to SEAM. We have a product developed in J2ee technologies (originally in EJB 1.1 and was upgraded to EJB 2.1 couple of years back). It uses JSPs and Servlets heavily, along with EJBs, DAOs and helper classes. Recently we decided to upgrade it to JBOSS SEAM because of various reasons, major being tough to maintain existing code.
But we are stuck because it is hard to find any guidelines to easily migrate existing J2ee code to SEAM. Looks like we will either have to start from scratch or spend a lot of time on splitting and putting code into corresponding programs under SEAM.

Would you say there are/can-be a set of guidelines to migrate existing J2ee applications to SEAM technology? Don't you think easy migration is a very important factor for a lot of projects, development from scratch is not the solution? Is there a blog/link/tutorial with an example of this case with successful migration?
 
Ranch Hand
Posts: 93
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Varun,
We are in a similar situation, But I feel it would be a lot easier to start from scratch than trying to migrate.

There are a no of issues you'll face
1) EJB3 is lot different from earlier versions.
2) You'll hvae to implement JPA to use Seam properly.
3) You'll need to use JSF for UI. It'll be very difficult to reuse anything from JSP/servlets.

You maybe able to reuse helper classes though.

It'll be better to start from scratch as it'll give you lot of options for redesign and flexibility.
 
Ranch Hand
Posts: 398
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes.... as highlighted, it will be pretty clean if you start from scratch.

By this way you can save lot of time, rather than fighting with performance issues in the case of directly migrating the exisitng code.


 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic