• 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

JSF + JBoss Seam [will appreciate any feedback]

 
Ranch Hand
Posts: 131
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Ranchers,

What do you think about prospects of using JBoss Seam in an enterpise application?ONJava Article on JBoss Seam

I mean the merits & demerits of adhereing to a particular vendor [JBoss ]

I'm thinking of a web application with following architecture:
1> AJAX + JSF based presentation Layer
2> POJO's for components[ EJB's not mandatory...simply b'coz no DB transactions involved... I only need a comprehensive session management mechanism... Thats why I'm exploring EJB3 to find out benefits(if any please let me know) viz. sessions ]
3> I use JNI to talk to Enterprise Layer

Which of the following approaches is better:
1> JBoss-Seam & EJB 3.0 Session beans to backup JSF components [ advantage being my application could be deployed in a clustered environment]
OR
2> Normal web application with JSF & POJO's [no vendor lock in... relatively simple to develop & maintain ]

I'm know similar questions have been posted before but none of them touch JSF... Also I'm relatively novice when it comes to Enterprise application development..

Please move to EJB forums if its not suitable here.

I would dearly appreciate any suggestions/feedback

Ravi
[ April 25, 2006: Message edited by: Ravi Sathish ]
 
Ranch Hand
Posts: 2874
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I would ask, any particular reason to use JNI?
 
Ravi Sathish
Ranch Hand
Posts: 131
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks Adeel

Well legacy application is written in C; Currently I have all the stubs auto generated ; May be someday we will directly talk to the DB using JDBC but until then JNI is my friend

Ravi
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic