rollatwork
Oct 15th, 2004, 01:19 PM
I've been doing J2EE since '00 and recently was turned on to Spring. At about the same time I "Sprung" the development of a project I was working on, I also stumbled across Laszlo and was perfect timing as I was looking for an RTC solution and Laszlo just open-sourced.
Just completed my first iteration and delivered a small release to my client who is astounded by the quality of the UI and speed of development with which the candidate architecture was built up.
Had I used traditional J2EE (SLSB, BDs, DTOs, Svc. Locators, plumbing, plumbing, plumbing...) and a web MVC framework such as Struts, I know I wouldn't have produced such a quality release in such a short amount of time.
In almost the same way XDoclet gave me the promise of a simpler J2EE a couple of years ago, Spring has really opened my eyes once again and shown me that there is a better J2EE.
You guys kick arse!
Coupled with a rich thin client framework like Laszlo or Flex, I think the expressiveness our users want, and the ease of maintenance development teams crave is now at our finger tips.
Just completed my first iteration and delivered a small release to my client who is astounded by the quality of the UI and speed of development with which the candidate architecture was built up.
Had I used traditional J2EE (SLSB, BDs, DTOs, Svc. Locators, plumbing, plumbing, plumbing...) and a web MVC framework such as Struts, I know I wouldn't have produced such a quality release in such a short amount of time.
In almost the same way XDoclet gave me the promise of a simpler J2EE a couple of years ago, Spring has really opened my eyes once again and shown me that there is a better J2EE.
You guys kick arse!
Coupled with a rich thin client framework like Laszlo or Flex, I think the expressiveness our users want, and the ease of maintenance development teams crave is now at our finger tips.