Ny now, most of the people heard about New Atlanta’s “soon to be released” Open Source release of the Blue Dragon J2EE Edition. Actually we are very excited about it, as we are soon going to announce one of our major products to be released as Open Source as well.
A lot of people have wondered what will not be included in the Open Source Edition and Vince Bonfanti has now released a statement which outlines the major changes of the commercial edition and the Open Source edition. Here is the statement:
[Quote]
There will be three differences between the commericial and open source editions of BlueDragon/J2EE:
1) The JTurbo JDBC driver for Microsoft SQL Server will not be included with the open source edition. JTurbo is a commercial product of New Atlanta’s that we are choosing not to release as open source. However, we plan to add support for Microsoft’s free JDBC driver for SQL Server (http://msdn2.microsoft.com/en-us/data/aa937724.aspx) so there should be no loss of functionality for the open source edition.
2) The CFDOCUMENT implementation is based on commercial libraries from ICEsoft Technologies Inc. (http://www.icesoft.com/) that cannot be included with the open source BD edition. We are investigating whether it will be possible to keep the “hooks” for the ICEsoft libraries in the open source BD edition, and then allow customers to purchase the libraries for ICEsoft if they need this feature.
3) The BD admin console contains New Atlanta trademarks and copyrighted material for which we do not wish to relinquish our intellectual property rights (for similar reasons that RedHat removes its trademarks and copyrighted material from Fedora). Therefore, the open source BD edition will not include the existing admin console and will need to be configured by editing the XML configuration file (bluedragon.xml). We expect that one of the first tasks identified by the BD open source steering committee will be the creation of a new admin console (but maybe not, hand-editing configuration files is pretty standard in the open source world). Certainly we’ll need to provide documentation on how to edit bluedragon.xml.
That’s it. Those will be the only three differences between the open source and commercial editions of BD/J2EE.
[/Quote]
One thing I don’t understand is how the Admin Console (point 3) has anything to do with open source or not. Hie example of RedHat/Fedora is valid, but in doing so RedHat is not “downgrading” Fedora in any way compared to the RedHat offering. Of course, changing values in a XML configuration file is no big deal, especially for a Server component (Apache, anyone:-) ), but still it would be nice to have a nice click and point admin interface.
Other then that, we are very much looking forward to the offering and have already started adjusting all of our applications to fit the Blue Dragon server one.
Sphere: Related ContentIf you enjoyed this post, make sure you subscribe to the RSS feed!
[...] Matt wrote an interesting post today onHere’s a quick excerptNy now, most of the people heard about New Atlanta’s “soon to be released” Open Source release of the Blue Dragon J2EE Edition. Actually we are very excited about it, as we are soon going to announce one of our major products to be … [...]
[...] Apr 1st, 2008 (3 seconds ago) by admin Vince Bonfanti was giving a talk to the ColdFusionWeeklyPodcast and in it he states that there will be a additional 4th feature that will not make the cut in the open source edition (we already stated the difference of the open source versus the commercial one). [...]