The new features that mostly caught my attention are:

• Built-in ORM based on Hibernate, this is a great addition and probably the biggest change to the product. I’m a fan of Transfer ORM and thankful for all the work Mark Mandel has put into the project for the CF Community. I don’t know if the built-in ORM will be better than Transfer or not yet. But having a ORM built-in to CF is definitely a great option to have. Especially when working with clients that are skeptical or have policies against Open Source software.
• Implicit getters and setters (finally!). This seemed obvious for sometime now. I’ve been using snippets to create the getters & setters for a long time but now I can better spend my time. One thing I hope and that is that the methods can be overwritten if needed.
• Closed gap between CFML and CFSCRIPT.  I write most of my code in CFScript so this is a big one for me. I’m not sure exactly what this means but if it means I can do everything that CFML does using only CFScript then (whoohoooo!) this makes me extremely happy.
• ColdFusion services exposed for Flex and AIR via Actionscript libraries.  This is powerful stuff and indeed one of the best additions to the product.

The ColdFusion Builder, which is based on the Eclipse IDE also looks very promising and is probably the most anticipated part of this release.  The community has been asking for a CF-IDE for sometime now, especially since the release of the Flex Builder.  With the CF Builder you will be able to manage servers and deploy projects right from the IDE by using FTP.  The IDE will also help by completing tags as you type and by listing things like datasources when typing “datasource=” inside a cfquery tag. For a list of the new features checkout the post by Ben Forta at http://www.adobe.com/devnet/coldfusion/articles/cfbuilder_whatsnew.html

To download the public beta version of the products visit http://www.adobe.com/cfusion/entitlement/index.cfm?e=labs_coldfusion9

Share on Facebook

EnvironmentConfig address this issue by allowing the developers define each environment and properties in an XML file once. This file is processed when the application starts and EC will automatically detect the environment the application is running at, based on the domain name. The environment’s specific properties are loaded and available to the developer for use in a several ways depending on configuration set.

stProperties

By default EC will return two structures with the properties set in the XML file. One follows the exact configuration set in the XML where you can declare both, simple values and structures of properties. This one is called stProperties .

stFlattened

stFlattened return the same properties and values as stProperties, however it flattens all structure properties and contains a single structure with all properties as single values.

GlobalConfig object

EC can be configured to create a GlobalConfig object (CFC). GlobalConfig is the default name but it can be named as desired and the path where is created can be set as well. If told to, EC will create this ColdFusion Component on the fly as a Bean with setters and getters for all the properties of that environment. The setters are set to private access while the getters are set to public encapsulating the properties and making them read-only through the life of the application.

You can choose to use any of the three options mentioned above to store and access the application properties. To make the accessible from anywhere in the application, you should place the selected option in the Application scope.

Notice that if the structures are used to handle the properties without the GlobalConfig object, these can be overwritten at anytime during the life of the application, while the properties are protected if the GlobalConfig object is used.

To Install EnvironmentConfig you can create a ColdFusion mapping to the EnvironmentConfig folder or just drop it in the root of your website.

Share on Facebook

As of version 1.1 you can:

• Use complex values as structures in the form of map->property (just like in ColdSpring). Thanks to Paul Marcotte for adding this functionality
• Use ColdFusion functions to format or generate output. For instance you can use #expandPath("/uploads")# and you will get the absolute path of the folder as the value of a property like “C:\sites\mysite\assets\uploads”
• Reuse properties as variables in the config file using the syntax ${propertyName}. For instance let’s say you have a folder path of /assets, but under assets you have /images, /videos, etc. You can now set a property for assets as
  <property name="assetsPath">/assets</property>
  then you can set the images and videos path as
  <propertyname="imagesPath">${assetsPath}/images</property>
<property name="videosPath">${assetsPath}/videos</property>
• EC now return two structures with the properties, one is a structure with sub-structures (if you use complex values) and another one flattened (thanks to Tom De Manincor)
• Another new feature is that EC can create a properties Bean for you on the fly. So, if instead of using properties in a struct as properties.myProperty you can encapsulate them in a Bean object. The properties will be read-only and you would access them like GlobalConfig.getMyProperty(). You can specify where you want it written to by passing the object notation path as 'model.GlobalConfig', EC will create the file then under ‘/model’ as ‘GlobalConfig.cfc’  I prefer this over the structure as the application properties are read-only and no one can modify them during the application’s life.
• If you use ColdSpring as your object factory, tell EC to create the ColdSpring definition file for you and all you have to do is add the include line at the bottom of your main ColdSpring file. From there on you can ask ColdSpring for the properties bean as you’d do with any other object.

This version still on Beta, but if you want to try it feel free to download it from the RIA Forge page http://environmentconfig.riaforge.org/

I look forward to getting feedback from you on features you’d like to see added. Report bugs at the RIAForge page.

Following will be a series of posts with samples of the multiple ways you can use EnvironmentConfig.

Share on Facebook

I’ve never been a big fan of certifications but they certainly help and many companies require them to give you the job. That is indeed why I got the certification (I’m still hapily with AboutWeb), because we needed it to get a contract. So, I finally had to confront the elephant in the room. Now, I only whish I had done this earlier.  Maybe my fear was the “what if”, but at the end I was “forced” to do it and got a score of 95%.

I’m glad I took it and encourange everyone in the CF Community to take the test.  Is good to have the peace of paper to back up your resume.  Think of it as a letter of recommendation from Adobe’s President & CEO …yes it’s signed by him.

P.S. I wanted to have an e-copy of the certificate and tried out lighting technique that worked pretty good. This is what I got:

ACE Advanced CF8 Certificate

For details on how I took the picture go to my Photography blog

Share on Facebook

First make sure you get the blank line error when validating your RSS feed at http://validator.w3.org/feed/

In my case I had two blank lines at the beginning of the RSS feed and found the problem on these two files:

• /wp-settings.php (in the root)
• /wp-includes/functions.php

Is this doesn’t fix it, try these other files as explained in the W3C website (http://validator.w3.org/feed/docs/error/WPBlankLine.html)

• /wp-config.php
• functions.php inside your themes directory
• wp-rss2.php
• wp-atom.php

If you get the error still, start disabling your plugins one by one until the error goes away.

Hope this helps. Good luck!

Share on Facebook

What seems to be a sudden change has been, actually, a long period of testing and contemplation of different blogging solutions.  Being mainly a CFer, I seriously considered several ColdFusion based blogging apps, as well as a JAVA based solution, Blojsom.  While they are very good I was convinced that the right solution for what I needed was Wordpress.  Why?

Even though my CF-Angel tells me not to go with a PHP based blogging engine, the truth of the matter is that I just need a solution that works well, adapts to changes in technology and blogging trends (ie Social media/micro-blogging) and is easy to manage. Wordpress is very well known and used, stable with tons (literally) of plugins and templates right off the bat.  I really don’t want to modify the code under the hood to get what I want and this seems to have everything I need want so far:

• Easy plugin install (over 4,000 of them and I can search & install them right from the admin)
• Easy theme switcher (thousands of them free)
• Easy import from RSS feeds (I had to write code to import the comments though)
• Permalink support (pretty URLs)
• Multiple RSS formats
• Twitter plugin (better than many of the plugins I’ve seen from other blog engines)
• Facebook plugin (various plugins & features)
• SEO plugin (powerful)
• Google Analytics
• Stats plugins (multiple plugins to track the stats of your blog)
• Anti Spam plugin (I hope this saves me a few headaches)
• Mobile plugin (present blog in suitable format for mobile devices)
• Full Screen WYSIWYG editor (so convenient!)
• Global Translator (translates your post into 34 different langs. Not interested on this one for now)

I can keep going on and on, but as I said the list is over 4k.  

For now I’m happy with the move and with the peace of mind that if I ever want to move my blog again (to BlogCFC or MangoBlog?), all my posts are using “pretty URLs” so with a few rewrites I should be back on track and not loose the indexed pages in the search engines.  That’s is not the case right now as I’m don’t think I’ll spend the time figuring out all the uuid’s of my old cagetories and blog posts to match the new ones. For this time I’ll only make the redirects for the  RSS feed URL, Transfer Config and Environment Config projects, the rest will have 301 redirects to the home page of the blog. From there just hope that Google and other search engines decide to index all my pages again.

Note: My take here is ONLY on blogging solutions that are available on ColdFusion, PHP & JAVA, NOT on how these three compare to each other as programming languages.

Share on Facebook

Share on Facebook

By glancing through the schedule I'm already looking forward to Advanced Techniques With The ColdBox Framework  by Luis Majano; ColdSpring 1337 by Chris Scott; Transfer ORM Caching Mechanics by Mark Mandel.  There are other ones which I need to make my mind for since they overlap like the workshop by John Paul Ashenfelter (I attended to one of his pressos in CFUnited and it was great) and CF with Air by Samer Sadek ( a coworker of mine).

Regardless of what I pick,  I'm sure this will be a great learning experience as well as a good chance to share the great guys of the CF community. If you haven't buy your tickets yet, hurry up and get registered!

See you at Objective!

Share on Facebook

First let’s understand how LiveCycle renders a form in the workspace for a specific process. When you set your process you set an input variable which holds the form to render. LiveCycle by default assigns the “Default Renderer” service to this variable so that it gets rendered properly in the Workspace. This “Default Renderer” is just a short-lived process with several activities that sets variables and enables your form for the workspace.

If you want to pre-populate a form with data, all you have to do is create your custom renderer service. For instance, let’s say you want to render a PDF form in the Workspace. So we need the “Render PDF Form” (see image 1) from the “Samples Forms” category (this samples should be in your process list unless you/the administrator didn’t upload the LiveCycle Archives that comes with the installation). This process takes a PDF form and renders it to the Workspace. First the short-lived process sets some parameters, then renders the form using the renderPDFForm operation from the Forms Service, and then enables the PDF Form to be rendered in the workspace.

    

Render PDF Process

To pre-populate the form we need to get the logged in user info and inject that into the form before getting to the “render Form” activity. To do that you can copy the “Render PDF Form” process into a new process. Then to your new process you want to: <more />

1-      Add two input variables: one called “userId” of type string and another one xmlData of type xml. 

2-      In the first step of the process you want to extract the form’s XML data and assign that to the xmlData variable. 

3-      Then, use the “Query Single Row” operation from the “JDBCService” and query the LiveCycle database to get the user’s info based on the “userId” variable. You can use the LiveCycle’s default datasource which should be “IDP_DS”. Your query will look something like 

SELECT canonicalname, commonname, email, organization, address
                FROM edcprincipalentity e
                                WHERE e.id = [xpath to your userId variable]

4-      Now that you have the form’s XML data you can assign values to the fields by using XPath. So, parse the query results and assign the values to the correspondent fields. LiveCycle won’t be able to decipher the XPath to the form fields, so you need to know those. However, that should be simple. Just use your main process (where your form variable is defined) and look at the path of your fields) and get your XPath from there. Beware that the xmlData variable of your rendering process matches to the last “data” node of your form variable in the main process. So that your xmlData XPath matches the main process form’s variable XPath like this:

/process_data/xmlData/ = /process_data/[formVarName]/object/data/xdp/datasets/data/
This means that if your form’s fields XPath translates to /process_data/[formVarName]/object/data/xdp/datasets/data/txtFullNameThen, your path translates to /process_data/xmlData/txtFullName  in your rendering process.

5-      Once you have assigned all the values you want to your xmlData variable, you have to inject now this new XML into the input document. If you copied the Render PDF Form, as I mentioned at the beginning, then your input doc var is called inDocData. By assigning the xmlData to the inDocData, LC will know that all you want to do is replace the XML part of the document variable.

Remember that on your main process you need to set this as the rendering service for the input form. Once you select this as your rendering service, you’ll notice that the userId variable you set on your rendering service will appear as a “Service Input” variable. Assign the “User’s Id” variable from the “task” to the “userId” input variable. Set the rest of the variables the with the same values as when you use the Render PDF Form service. 

Now, if you initiate your process from the workspace, you’ll get the form pre-populated with the logged in user info. If it doesn’t, read this post again and make sure you understand all the services used here. Also, remember that you can debug your process using the “Variable Logger” service.

Share on Facebook

What’s all the buzz about Adobe LiveCycle ES?

Have you heard about LiveCycle and how great it is but never had a chance to see it in action? Maybe you’ve heard how it can unlock PDF documents, control who can view/print/copy documents even when these have left your network, render forms in multiple formats (HTML, PDF and SWF) all with a single file. Learn why the buzz about LiveCycle ES and why renowned companies like Wachovia and the Federal Government are using LiveCycle ES to automate their business processes.

Unleash the power of Reader Extensions ES

Have you ever filled out a PDF form and, after all the effort, noticed you cannot save your data? Or maybe try to add attachments, comments, signatures, connect to a database but are unable because of the limitations of Adobe Reader? Learn how you can use LiveCycle Reader Extensions ES to unlock these and more capabilities for single or bulk PDF documents.

I'll be preceded by Curtis Layton, whom will be speaking on: Intro to Object Oriented Programming in ColdFusion.

You can get more details about the event at the BAUG website: http://baltimore-aug.org/

Share on Facebook