We have just launched a site for Land Rover in the US, it is designed to be a rich user experience for finding a certified pre-owned Land Rover cars in the USA.
For those of you in the US who have had to use UK Postcodes to try out our Used Vehicle Locators, struggle no more! We have just launched a site for Jaguar in the US.
It is designed to be a rich user experience for finding a certified pre-owned Jaguar car in the USA.
If you have to develop behind a proxy server, you may have encountered the following problem;
The ColdFusion (JRUN) JVM settings allow one to specify a proxy server, allowing your local ColdFusion to connect to external public URLs. However there is no proxy by-pass options, so when configured your ColdFusion cannot connect to local URLs which are not resolved by the proxy server, i.e. local development servers.
The following solution uses Apache to create a local proxy server for your local ColdFusion to use;
Apache Setup
Enable mod_proxy for Apache by un-commenting the following modules to load in your httpd.conf file. If you do not have the mod_proxy module, then you will need to install it.
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_http_module modules/mod_proxy_http.so (required for cfhttp)
Add the following virtual host configuration to your local httpd-vhosts.conf file
# Local Proxy for ColdFusion
Listen 8080
<VirtualHost *:8080>
DocumentRoot D:\InetPub\wwwroot
ServerName localhost
ProxyRequests On
ProxyVia On
ProxyRemote * http://your-proxy-server:8080
NoProxy .local 192.168
</VirtualHost>
Restart Apache
ColdFusion Setup
Edit ColdFusion (cfusion) JVM settings in your local JRun4 admin (or CF Admin for non JRun install) to add the following proxy setting
I have been playing around with implementing Design by Contract in ColdFusion using Coldspring's AOP functionality.
ColdContract is a Coldspring AOP Advice which allows Design by Contract assertions to be added to ColdFusion components and for those assertions to be executed during program execution.
Design by Contract assertions are a mechanism for defining the specification of software components, in such a way as to allow the implementation of the specification to be tested in-line with program execution. This provides a difference (and arguably quicker) method of implementing TDD to Unit Testing.
Assertions are added to components using meta data attributes as shown below:
<!---
/**
*
* Copyright (c) 2008 David Beale (http://www.BealeARTS.co.uk)
*
**/
--->
<cfcomponent displayname="Stack"
hint="A FILO Stack example showing the use of ColdContract assertions. Stack items cannot be objects (Components)."