• 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:
  • Tim Cooke
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Rob Spoor
  • Junilu Lacar
  • paul wheaton
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
  • Scott Selikoff
Bartenders:
  • Piet Souris
  • Jj Roberts
  • fred rosenberger

Transitioning from RI tool

 
Ranch Hand
Posts: 329
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I've been using the RI tool to learn EJBs. I'm considering transitioning to JBoss since the RI tool is just for learning. Do you guys think I can benefit by purchasing a book after downloading JBoss or can I use on-line refrences to aid me during my personal devolopment projects?
 
Ranch Hand
Posts: 293
Mac OS X Netbeans IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
There are some good online resources availble on the JBoss wiki, however, personally I also like to read books to learn a new subject.

I like "JBoss at Work" - I think its a good book. It covers Stateless Session Beans, but not Stateful or entity beans. If you're lucky, you may win a copy this week !
 
Ronnie Phelps
Ranch Hand
Posts: 329
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Well once I am done with JBOSS, I would probably want to transition to WEBLogic. Is there a huge learning curve between the two servers?
 
Author
Posts: 67
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Once you know one J2EE application server, it's pretty easy to learn another one. Remember that J2EE is a specification, so your code and J2EE-standard descriptors will look the same regardless of your application server.

So, I would suggest learning the J2EE and understanding it well.

The main differences between application servers are: JMS Destination deployment, DataSource deployment, and registering JAAS LoginModules - there aren't any standards for this. Also, the application server-specific deployment descriptors are different between application servers, but they're all trying to do the same thing.

For now, you mitigate change/porting by using XDoclet to generate deployment descriptors. Once EJB 3.0 comes out, you won't need deployment descriptors, so porting will be even easier.

By the way, WebLogic is also a good application server. I've used it in the past and I was pretty happy with it.

Tom
 
pie. tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic