Fancy Bread

When developing OSS software, one should endeavour to maintain backward compatibility with each new release while adding improvements and new features (and fixing bugs). The current Metro release (0.6) is a significant departure from previous releases. While it maintains backward compatibility for service and gateway methods, it also provides improved support for validation rules and contexts thanks to a huge contribution from Matt Quackenbush. The changes are designed to promote building rich business objects. I removed some of the setup dependencies which I was unhappy with, and now use "import" for ColdSpring and "include" for Transfer to simplify configuration. Lastly, I have also re-organized sample code and support documents. Here is breakdown of the items requiring modification to use Metro 0.6.

Read more...

I'm pleased to announce the release of Metro 0.5. The biggest change for this release is compositeid support contributed by Bob Silverberg, cf.Objective() speaker and master of Transfer metadata. You'll find sample code in the new work package that models an Employee, EmployeeType and Department.

Recent circumstances leave me in a position to seek out my dream job. Ideally, my next employment will be with an an organization that understands the benefits associated with:

• object oriented software development
• agile software development practices
• software libraries and frameworks (MVC, ORM, Unit Test)
• telecommuting and teleconferencing
• continuous learning

If you are looking a passionate ColdFusion developer with a professional attitude and desire to write great software, please contact me.

My resume (MS Word format) is available for download.

A big thanks to John Whish for spotting a bug in the way the Metro ServiceFactory resolves component class paths. The componentPath and libPath init arguments are optional, so when both are empty strings, the ServiceFactory threw an error. This issue is resolved with revision 1 for Metro 0.4.

The latest Metro release (0.4) includes some bug fixes and a significant change to the included security package. After much consideration, I felt it was appropriate to separate the security package into "user" and "security" to facilitate integration with other projects and provide better separation of concerns. There is now a UserService which is responsible for managing the User, Role and Permission objects. The SecurityService is now primarily responsible for managing user sessions.

Additional meaningful updates below:

1. The loginUser() method found in UserService, now checks the Active status for a User.
2. The User decorator's hasPermission() method now accepts a comma separated list of permissions to check.