This week's book giveaway is in the Servlets forum.
We're giving away four copies of Murach's Java Servlets and JSP and have Joel Murach on-line!
See this thread for details.
The moose likes JBoss/WildFly and the fly likes Upgrade existing J2ee application to SEAM - any guidelines?? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "Upgrade existing J2ee application to SEAM - any guidelines??" Watch "Upgrade existing J2ee application to SEAM - any guidelines??" New topic
Author

Upgrade existing J2ee application to SEAM - any guidelines??

Varun Chopra
Ranch Hand

Joined: Jul 10, 2008
Posts: 211
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?


-Varun -
(My Blog) - Online Certifications - Webner Solutions
Padmarag Lokhande
Ranch Hand

Joined: May 29, 2008
Posts: 93
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.


- Padmarag Lokhande
SCJP5 - http://blog.padmarag.com
Mourouganandame Arunachalam
Ranch Hand

Joined: Oct 29, 2008
Posts: 396
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.



Mourougan
Open Source leads to Open Mind
 
jQuery in Action, 2nd edition
 
subject: Upgrade existing J2ee application to SEAM - any guidelines??
 
Similar Threads
Pro EJB 3.0: Refactoring
EJB 2 to EJB 3.0
Migration from Websphere v6.0 to Websphere v6.1 : Guideleines please
Migration of web application from WSAD 5.1.2 to RAD 6.0
Migrating to Portals & Portlets