You must have at least Java 1.5 installed and properly available on your system. Older versions of Java will cause some problems as there was some fundamental changes between Java 1.4 and 1.5. Most Java applications are forward compatible so you should have no problems in upgrading.
OpenBD is a J2EE application. In other words it requires a J2EE application server in which to run. OpenBD ships as a standard J2EE WAR file, which is basically a specially named ZIP file with a specific directory structure. Any J2EE container will happily run OpenBD, by simply dropping it into the corresponding application deploy directory.
For a list of all the currently available J2EE servers you can visit http://www.javaskyline.com/serv.html
If you do not want to install a J2EE server separately, then OpenBD ships with a ready configured alternative using the popular Jetty application server.
The engine is released under the GNU GPL v3 license. We feel this gives the project the most flexibility and is the truest form of open source license.
We support as many tags as possible, including adding in a number of OpenBD specific ones. You can find the list of supported tags here.
Yes of course, including the ability to serialise them into [session] scopes for use in a clustered environment.
OpenBD is a fork of the original BlueDragon commercial offering from New Atlanta. This happened on the 1st May 2008. Since then the code base has developed at a different pace than BlueDragon. New Atlanta engineers still contribute a lot of bug fixes to OpenBD's code base, and will continue to do so.
BlueDragon is a fully supported commercial CFML runtime engine, with a tight test and release schedule. It operates both on the Java and natively on the Microsoft .NET platform. OpenBD is purely a Java engine.
The direction of the OpenBD project is governed by the Steering Committee, who incidentally, does not have any NA representation on it. This small group of highly dedicated individuals, gather the comments and views from the community at large and debate/decide the future of OpenBD.
You can read an interview regarding that here.
For details on installation of various types, please see the installation category page.
Upgrading OpenBD is as simple as copying some files to your existing instance of OpenBD. The following applies to the WAR deployment of OpenBD; notes on upgrading the Ready2Run version will be coming soon.
This was a tip originally posted on the OpenBD mailing list by Chris Blackwell, who noted that Excel can happily import properly formatted HTML tables. You can force your page to 'pretend' to be an XLS by forcing the content type to Excel. You can either print out your query in nicer format, or simply dump it to the browser using CFDUMP.
<cfheader name="Content-Disposition" value='inline; filename="report.xls"'> <cfcontent type="application/vnd.ms-excel" reset="true"> <cfdump var="#myQuery#" expand="true">
Yes, with a bit of configuration. This came up in a question from Tom Jones on the OpenBD mailing list. Paul Bonfanti responded with a link to an FAQ on New Atlanta's site:
The CFLDAP tag can be used with SSL using the following steps:
cd JAVA_HOME/lib/security keytool -import -file ldap_server_cert.cer -keystore jssecacerts
For example, if BD J2EE is running with JDK 1.6 on Windows then the value of JAVA_HOME for the JRE would be: C:\Program Files\Java\jdk1.6.0\jre.
If you don't install the LDAP server's certificate in your JRE's database of trusted certificates then you'll receive the following General Runtime Error:
javax.naming.CommunicationException: simple bind failed: test.newatlanta.com:636 [Root exception is javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target]; ROOT CAUSE=sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
If you hit a non-SSL port with secure set to CFSSL_BASIC then you'll receive the following General Runtime Error:
javax.naming.CommunicationException: simple bind failed: test.newatlanta.com:389 [Root exception is javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?]; ROOT CAUSE=Unrecognized SSL message, plaintext connection?
Gmail requires SSL (TTLS) to connect to its services.
OpenBd can connect to GMail using Stunnel to encrypt the connection.
client = yes debug = debug [pop3s] accept = 127.0.0.1:1109 connect = pop.gmail.com:995 [smtps] accept = 127.0.0.1:259 connect = smtp.gmail.com:465
SMTP Server: youremail@gmail.com:yourPassword@127.0.0.1 SMTP Port: 259
<cfpop
server = "127.0.0.1"
port = "1109"
username = "youremail@gmail.com"
password = "yourPassword"
action = "getAll"
name = "popGoesTheGmail"
attachmentPath = "#ExpandPath('./gmailattachments')#"
timeout = "60"
maxRows = "1"
startRow = "1"
generateUniqueFilenames = "yes">
<cfmail from="youremail@gmail.com" to="youremail@gmail.com" subject="TESTING GMAIL/STUNNEL ON OPENBD"> IT WORKS! smtp.gmail.com port 465, TTLS enabled </cfmail>
If Open BlueDragon throws an internal error while attempting to add a web service, and the stack trace begins with "java.lang.NoClassDefFoundError: sun/tools/javac/Main", this indicates that you do not have Java's tools.jar in your classpath. To resolve this issue, either add the appropriate tools.jar to your classpath or copy tools.jar to Open BlueDragon's WEB-INF/lib directory.