wood burning stoves 2.0*
The moose likes JBoss/WildFly and the fly likes Transitioning from RI tool Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "Transitioning from RI tool" Watch "Transitioning from RI tool" New topic
Author

Transitioning from RI tool

Ronnie Phelps
Ranch Hand

Joined: Mar 12, 2001
Posts: 329
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?
Dave Salter
Ranch Hand

Joined: Jul 20, 2005
Posts: 292

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

Joined: Mar 12, 2001
Posts: 329
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?
Tom Marrs
Author
Ranch Hand

Joined: Sep 20, 2000
Posts: 67
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
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Transitioning from RI tool
 
Similar Threads
JMX impl
Environment set up for SCBCD self study
IntelliJ artifact confusion
deploying Entity bean with DB2 database
Generated stub classes for my ejb's remote client with JBoss app server