openbd caveats

Tags: Coldfusion, OpenBD

I have been beginning to use this more and more, and one of the things I have to say is that most things I have thrown at it openBD has been up to the challenge. However, until it becomes available one has to be a little aware of what we in the Java world call context paths. Coldfusion does very well to shield us from this, but it is reality when you are not sure how to use. I am still coming to grips with Coldbox, the thing is that I can say at the moment it is very well written. And provides a framework that I can safely say is more than worth a look at.

But openBD is a little different, I dropped Coldbox into this expecting it to work right of the bat. Well it did, just that openBD had other ideas about it, or should I say my misunderstanding of how it works.

Even with my Java knowledge I still fell trap to it.

With mappings it is good to know that they exist, but it almost the opposite when it goes wrong. Or should I say doesn't exist?

With openBD, the admin has been removed and one has to manually add or modify the xml file for bluedragon. This includes the datasource, mappings etc., that one is usually used to when the Coldfusion Administrator does it all for you.

Anyway, the point is that take mappings and custom paths into consideration and don't just expect it to work without these modifcations. Well at least until the admin API/UI has been finalised.

Otherwise, I find this project worthy of some of our enterprsie solutions.

TweetBacks


Comments (Moderated) | Add Comment

There are no comments for this entry.