Blog

I was working on setting the transaction isolation level for the first CF9 ORM application I have put into production and thought I would share what I learned.

The first thing I learned is that by default, hibernate will use whatever isolation the datasource it is using has set.  In the drivers Coldfusion uses for MSSQL, the default is TRANSACTION_READ_COMMITTED. 

What I needed for my application was TRANSACTION_READ_UNCOMMITTED, so I knew that this had to change.  I researched how to change it at the datasource level, but couldn't find a "quick and dirty" way to do that, so I decided that since this application was using hibernate ORM, I would set it there.  If anyone of you knows how to change this setting at the datasource level on CF9, feel free to chime in.  I know how to change it on CF 6/7, but that doesn't work on CF 9.

Just a reminder that our Ontario, California ColdBox training is in 11 days and only a few seats are left.  So book your training today to reserve your seat.

OVERVIEW

Core ColdBox is our 2-day flagship intensive training course that will get you started with ColdBox even if you have no previous OO experience. The course is constructed in such a manner that both gurus and novices can take advantage of our materials.

More Information and Requirements

SCHEDULE

February 20, Saturday - CBOX 101 - Day 1

February 21, Sunday - CBOX 101 - Day 2

* The night of the 20th we will have a group dinner (optional) and a open BOF.

 

I ran into an interesting issue using the jQuery UI tabs ajax style and Internet Explorer. 

If you setup the tabs with the with the cache turned off, they will still be cached in IE.   I had worked around this issue by adding a counter that changed every time to my href for the tab, but I found a more elegant solution and thought I would share.

Hi,

My name is Curt Gratz, and I'm a Coldbox Junkie...

Before I started posting to the Coldbox blog, I thought I should introduce myself.  I am a long time (13+ year) Coldfusion developer, part owner of Coldbox Alliance Partner Computer Know How, and the newest member of Team Coldbox. 

This week we would like to showcase Label A's ColdBox case study.  They have some excellent applications and products based on the ColdBox Platform that is really awesome work.  Their case study can be found here: http://wiki.coldbox.org/wi...

Just a reminder that our Early Bird pricing for our Ontario, California ColdBox training ends this Friday at 11:59 PM PST.  So book your training today and just as a last early bird week gift, use the discount code: cfug and get an extra $100 chopped off the early bird price.

OVERVIEW

Core ColdBox is our 2-day flagship intensive training course that will get you started with Col...

This January 28th at 5PM PST our free book contest ends, so get your entries submitted by then.  All you have to do is submit code entries to ForgeBox and the person with the most amount of submitted projects wins a free ColdBox book!! That's it! So get to i...

The eclipse help plugins have been updated for this 3.0.0 M4 release. So update now.

Just an FYI that I just updated the bits for the 3.0.0 M4 download. I had some leftover branch code I forgot to cleanup in the build creation. So the build that is correct is coldbox-buildID-201001190809. So please check your build id's. This is the latest and should be ok. Thanks.

...

WOW! This one took a while but finally our M4 release is now available. So is this a final release, beta, or what? Well, we are taking off the beta name and will use our Milestone release as it is now deemed production ready even though I see a lot of users already running production sites with 3.0.0 Beta. Anyways, this milestone release has tons of fixes and updates in preparation for our next milestone which we should introduce in the coming months in preparation for a Release Candidate in Mid or Late April. Our milestones are evolving as planned and our core is getting more solid and solid with each release. This one especially really tightens the bolts on a lot of features introduced since the first betas. So let's start looking at what we did. However, please look at the tickets that have a (COMPATIBILITY) tag on them, if they do, then this means that this release has changed behavior from previous releases and you must see if you use that particular piece of code because most likely it needs to be updated. Please bear with us as all our docs are been reviewed for updates and more are added every day. Our new wiki is also online, powered by CodexWiki of course, and it will contain only 3.0.0 documentation. The 2.6.4 and less docs will remain in the orginal location. Here are the tickets for this milestone: