Link Details

I'm wondering if there is a misunderstanding of the Liberty Profile here. My understanding is that it is a separate runtime with a limited set of services. If a developer requires services not available in the Liberty Profile, he/she must use the traditional WAS runtime. I believe that the shift occurred with JBoss AS 7 & JBoss EAP 6 where the complete set of services are loaded on demand and configurable via profiles (Web/Full/Other) rather than separate runtimes. Having two separate runtimes only makes a developers job that much more difficult.

Hey Shane, Thanks for your comment (Disclaimer: Please note I'm a ZeroTurnaround employee and before that I used to work at IBM on the Liberty Profile). The liberty profile contains a subset of functionality compared to the WAS full profile. This subset of functionality is growing and growing as you can see from the WAS 8.5 release and the new WAS.next alpha release (now contains EJB lite and more). If you wanted to code against other services or runtime which was not in the liberty profile, then yes, you'd need to use the full WAS profiles. A couple of reactions to your separate runtimes comment... Firstly it's important to mention that apart from LP kernel (component and services loading, config etc), the runtime components and services are identical to the components and services in full profile, such as web container, transaction service, so you'll not have a big step between development and production like with say tomcat and WebSphere. The trend for the LP is to include more and more functionality as you can see from the recent alpha releases. Check out wasdev.net for more info. Hope that helps! Simon Maple (@sjmaple) Zero Turnaround Technical Evangelist