• 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

What to do with a Seam 2.2.1 application code base - need help with a strategic decision

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear Saloon members,

in the year 2010 I created a small web portal application based on the JBoss Seam framework. It was not very comprehensive but still with a mid-sized feature set coming pretty close to a "Youtube in a nutshell". These were months of work in fulltime, and the architecture was geared towards building other things from a reusable code base (so not everything was hard-coded and some abstraction layers were used).

Now after three years being completely away from the Java/JEE world I am going to try out some other ideas and of course would like to reuse previous work. What are the options given very limited time resources?

1) Migrate to Seam 3.2.0. Final
2) Continue working with Seam 2.x, just make it run on JBoss 7 (or live with JBoss 5.x?!)
3) It is worth of migrating reusable parts to some other web framework
4) Just forget it, take another web framework and start from the scratch, the compatibility breaches with both 1) and 3) are too big


A side note is that I actually do not like building and testing a complex EAR and would like to have a business logic layer encapsulated in a standalone Hibernate/JPA project which can be tested and deployed on its own. But then how to connect it to the web app? Is a build dependency just enough or do I need to dive into some JMS/Webservices constructs?

Further question: Seam was a quite easy start for a JEE beginner compared to Spring, Tapestry and stuff as of 2010 and years before. Now much of my knowledge will be obsolete. May I assume that after three years the JEE world has become nicer and easier to get back? :-)

Thanks in advance!
kind regards
your JEE Noob.



 
Bartender
Posts: 1104
10
Netbeans IDE Java Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Peter,
Welcome to the Ranch!

Peter Thunderstone wrote:
1) Migrate to Seam 3.2.0. Final



Did you mean 2.3.0 Final? Because Seam 3 is actually very different from 2 - it is a module-based approach.

Peter Thunderstone wrote:
2) Continue working with Seam 2.x, just make it run on JBoss 7 (or live with JBoss 5.x?!)


I actually tried to take a Seam 2.2 app and have it run on JBoss 7, but found it very hard to do. But, it was a casual (few hours) approach.
Although, I have to add that, JBoss 7 is super-fast when compared to JBoss 5. So, this step might be a worthwhile try.
reply
    Bookmark Topic Watch Topic
  • New Topic