It would likely just get forked- that's the nice thing about OSS, you should know better than to suggest that Oracle would bury GF just because it might cut into Weblogic's market share. And they couldn't kill it if they wanted to at this point. At best this is a modest JBoss win for small shops where they're willing to go without commercial support.Ĥ) Oracle has made it clear that Glassfish is not "going away". Also, most large conservative corporations would kick you out of the room if you suggested going without support on EITHER JBoss or Glassfish, so either way you're attached to someone. First, less vendor lock-in is the main benefit of OSS-and both are OSS, so this isn't a major issue even if the dependence is slightly greater. (WOW!)Ģ) ? Like what? And does it really matter? Performance, scalability, usability, and reliability all trump non-standard niche features.ģ) Dependence is not as high on Red Hat? Meh, this is a weak one. Glassfish was found to be the app server of choice for 73% of new JEE projects according to Ohloh. See this link, where it shows Glassfish overtaking JBoss, and skyrocketing in popularity. I don't hate JBoss, and I prefer it to just about anything else out there, but you force me to point out the flaws in these talking points which read more like an ad than an honest analysis.ġ) JBoss may have a bigger and more active community base, but Glassfish appears to be eroding it largely at the expense of JBoss ( and Weblogic, shocking huh?) The future of JBoss projects looks great under their leadership. It is being nurtured by RedHat, the #1 open source company, which though commercial, has till date shown to be only company championing open source philosophy at all times. The active and widespread community base ensures the product quality vis-a-vis development, testing is top notch.ħ. The commercial version for the production deployments are much robust from JBoss/RedHat, not to mention the professional support they offer (which is being rated as #1 for many years now.)Ħ. Oracle would not like to create anything that eats into Weblogic revenue.ĥ. Oracle acqquisition has ensured there lot of chaos and uncertainty about Glassfish open source community. In an highly unlikely event of RedHat not supporting JBoss projects, the projects would still survive and grow.Ĥ. The dependence on Red Hat / JBoss as an organisation is not as high as in case of Glassfish on Sun. The level of innovation and choice of various projects/product lines is higher for both open source and commercial versions.ģ. JBoss has the bigger and more active community base.Ģ. If you intend to port it on prod, would you keep the same app server or change it to proprietary?Īs for addressing your question directly: -ġ. Are you choosing it for merely development or do you intend to port it on production env?Ģ. JBossPropertySet.It would be nice to know what and why you need to compare.Ĭertain things play important role in comparison.ġ. GeneralPropertySet.IGNORE_NON_EXISTING_PROPERTIES JBossPropertySet.JBOSS_MANAGEMENT_HTTPS_PORTĬ JBossPropertySet.JBOSS_MANAGEMENT_HTTP_PORT JBossPropertySet.ALTERNATIVE_DEPLOYMENT_DIR JBossPropertySet.DEPLOYER_KEEP_ORIGINAL_WAR_FILENAME The WildFly 22.x container can be used with the JBoss Enterprise Application Platform (EAP) version 7.4 i.e.The WildFly 18.x container can be used with the JBoss Enterprise Application Platform (EAP) version 7.3 i.e. The WildFly 13.x container can be used with the JBoss Enterprise Application Platform (EAP) version 7.2 i.e.The WildFly 11.x container can be used with the JBoss Enterprise Application Platform (EAP) version 7.1 i.e.The WildFly 10.x container can be used with the JBoss Enterprise Application Platform (EAP) version 7.0 i.e.the build from JBoss Application Server (AS) version 7.5 released in October 2015 What Cargo calls JBoss 7.5.x is what JBoss refers to as JBoss Enterprise Application Platform (EAP) version 6.4 i.e.the build from JBoss Application Server (AS) version 7.4 released in June 2014 What Cargo calls JBoss 7.4.x is what JBoss refers to as JBoss Enterprise Application Platform (EAP) version 6.3 i.e.the build from JBoss Application Server (AS) version 7.3 released in October 2013 What Cargo calls JBoss 7.3.x is what JBoss refers to as JBoss Enterprise Application Platform (EAP) version 6.2 i.e.the build from JBoss Application Server (AS) version 7.2 released in May 2013 What Cargo calls JBoss 7.2.x is what JBoss refers to as JBoss Enterprise Application Platform (EAP) version 6.1 i.e.What Cargo calls JBoss 6.1.x is what JBoss refers to as JBoss Application Server version 6.1 i.e.With the opening of the JBoss EAP to the public and the split between JBoss and WildFly, the below naming correspondence should be used with JBoss EAP containers: Codehaus Cargo > Containers > WildFly 10.x
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |