This post originated from an RSS feed registered with Java Buzz
by Marc Logemann.
Original Post: From Websphere to JBoss (The Start)
Feed Title: Marc's Java Blog
Feed URL: http://www.logemann.org/day/index_java.xml
Feed Description: Java related topics for all major areas. So you will see J2ME, J2SE and J2EE issues here.
sorry, cant deliver any technical facts right now, since i am just installing/configuring JBoss on my development machine. After some customer troubles with WAS, we are giving JBoss a try. But i can point out some hopes of the transition:
- faster spec adoption
We all know that WAS is not the fasted product when it comes to be compliant with latest J2EE specs. With the announcement of IBM to delay its WAS6, we think JBoss will be earlier with a final 1.4 compliant server
- less ressource hungry
WAS is not too friendly when it comes to resource usage, we expect some better number from JBoss.
- usage of standard JDKs
i personally never liked to be locked in to a IBM JDK
- Support / Fixpacks
As a long time consulter for IBM customers, i have seen too many bad support cases with IBM, either onsite or via telecommunications. Lets see how the JBoss certified companies do their work. I am excited. Another issue is how IBM handles the fixpacks. In some areas, you spent more know-how on how to apply fixpacks than in coding J2EE apps.
*-*-*
But there are also some fears. When you know where to look for, IBM has a massive documentation base. Dont know the JBoss docs, cause i have not bought them yet, but it can only be less conent than IBM.
Previous Topic
