Rob Gonda's Blog

cflocation vs getPageContext().forward() = java.lang.OutOfMemoryError

How can help me with this? My home page was throwing some "java.lang.OutOfMemoryError : Java heap space" errors and I traced it down to a getPageContext().forward("/blog")...

It turns out that after I switched it per a <cflocation url = "/blog"> the error went away.

I also used the CF8 built-in monitor and confirmed that my jrun never ran out of memory; I've always had at least 100-200mb of available JVM memory ...

So, is it so wrong to use server-side relocation? I've been using it for years and never ran into this problem...

Can anyone shed some light?

Aptana Jaxer: server-side Ajax

Aptana released Jaxer: the first ever Ajax server... you got that right, server-side Ajax ... the concept is pretty interesting, a server-side API that wraps for client-side Ajax app to better optimize it and allows you to interface with the file system and database.... Oh, wait a minute, isn't this really similar to AIR? AIR also extends for your JavaScript libraries to allow file system and database access, except that AIR is a client desktop runtime and Jaxer is a server runtime... nevertheless, they solve the same problem... They allow you to leverage existing JavaScript skills to integrate seamlessly with components that will allow you to deploy full apps without the need of any traditional server-side programming language.

I always thought Aptana was just a nice Eclipse plugin, but this is pretty innovative. It integrates for your Apache web server as a simple extension (no IIS for now), it deploys as a war file for your Apache Tomcat Java server, or even runs in Amazon EC2 ...

I personally haven't tried it, and I have no complaints about ColdFusion, .NET, PHP, or Ruby processing my server requests, in fact, I believe they would be much more robust and reliable than server-side JavaScript, however, this looks great for small and light applications. I'm sure that's their first niche since the only two supported databases are sqlite and mysql, it's a good indicative ...

Anyone see a good immediate use for this new technology?

Speaking at the NYCFUG

I will be speaking at the New York ColdFusion User Group this Wednesday, April 16, with the topic of "AJAXify Your ColdFusion Applications". I promise it will be fun, a good learning experience, and perhaps we may even go out afterwards and have some drinks.

There will be tons of nice give-aways:
1 x Ticket to CFUNITED ($999 Value!)
2 x jQuery Reference Guide
2 x Learning jQuery: Better Interaction Design and Web Development with Simple JavaScript Techniques
2 x Tickets to Flex Camp Wall Street
1 x FusionDebug License....

They're all excellent... I love jQuery and CFUnited is the most popular CF event of the year .... hope to see many familiar faces, so don't miss it.

ColdFusion 8.0.1 Ajax Improvements

Adobe ColdFusion 8 Update 1 (8.0.1) was released April 3rd (most of you knew already). The good and safe news is that it seems to work fine... nothing broke with the update.

What was updated? You can get the full list here, but I will concentrate only on the Ajax part.

The docs say "We have improved functionality in several areas including AJAX functions, CFPDF, and CFIMAGE. And we have updated several software libraries including Yahoo YUI, EXT JS, Spry, and the FCKEditor."

The FCKEditor component used in the cftextarea tag’s rich text editor has been updated to version 2.5. As a result, the rich text editor now supports Safari 3 and Opera 9.50 browsers. This is great news, but 2.5 was released 11/30/2007... 2.6 was just released, so they went with the latest stable, though it was pretty safe to try the 2.6 RC, which was released a while back.

Next, the Spry framework has been updated to version 1.6.... not too much to say there, I don't care much about it.

Now the important part, the Yahoo YUI Library used for some AJAX-based controls has been updated to version 2.3 and the Ext JS framework used for some AJAX-based controls has been updated to version 1.1.1... I assume they did this because Ext JS 2.0 (released in October 2007 btw) was a major update and it would have taken too much to adapt it? Adobe, trust me, I understand SDLC, but in today's world CF helps us keep up with rapid changing technology and it would be totally worth it ... you will have to upgrade it at some point .... hopefully 8.0.2 will incorporate the a much newer version of Ext.

This blog is running version 5.9.003. Contact Blog Owner