Lets face it the technology moves quickly. So one way or the other if the code isn't updated to be current with these standards it is outdated anyway. These technology evolution is a large part of the reason frameworks evolve quickly too. At a recent Gartner IT/Symposium, they said frameworks are 90% iterative.
So yes they do move quickly. And without them you'd be doing it youself. And what you can't replicate is the 1000s of developers using it in real environments and it evolving based on what works and what doesn't. You are going to find out the hard way.
Why Use frameworks? J2EE frameworks enable a level of abstraction from the business logic. This clear separation enables the features of the application to evolve separately from the framework. You get to focus on your application instead! And once you have developed more than one application the benefits of a common framework across your applications is much greater.
Most people who develop their own end up with emeshed architecture code in their business logic which results in higher maintenance burden!
Gartner says frameworks are part of the productivity layer and recommend their client to use frameworks. As frameworks offer tighter integration with IDEs, code generators, wizards and the like you will find their adoption widespread. Have a look at www.mvc2frameworks.org for more information about mvc based frameworks and a comparison spreadsheet.
IMO being Struts based for example is a good sense for sales since it has become a defacto standard.
You could adopt another open source servlet-based toolkit such as the Expresso Framework at http://www.javacorporate.com/ which has a commitment to offer developers control over its direction through a full featured collaborative infrastructure - includes a Task List of those things developers want in the solution. It also has the benefit of being a mature tried and true solution. Rather than create another solution - let's embrace the advantage of open source and collaborate and build together!
What if one where to apply the benefits of open source to a commercial solution. I think it could create:
1. Source code included with product; 2. Inexpensive product; 3. Collaborative development with community and developers.
I think such a commercial source product could have some distinct advantages:
4. Support organization; 5. income to pay for full time developers and company infrastructure; 6. Possibly greater innovation.
The company I work for - http://www.javacorporate.com/ offers several open source projects. These worthy projects generate interest in our other commercial products - they are also loss leaders. To open source all of our products would put us out of business. The reality is - many developers download the open source but few as a percentage contribute back to the community or pay for premium support. So open source services has not paid for our full-time developers.
So we also offer a commercial source model on a number of products. We feel long term without the commercial source projects - innovation on our open source projects would be compromised without our fulltime developers who are leaders in the development and who support and encourage the community developers.
I think the javacorporate.com model is win/win to everyone. And the commonality is all of over products enjoy the benefits of source code and a collaborative infrastructure. I hope you'll have a look.
Slashdot Mirror
Lets face it the technology moves quickly. So one way or the other if the code isn't updated to be current with these standards it is outdated anyway. These technology evolution is a large part of the reason frameworks evolve quickly too. At a recent Gartner IT/Symposium, they said frameworks are 90% iterative.
So yes they do move quickly. And without them you'd be doing it youself. And what you can't replicate is the 1000s of developers using it in real environments and it evolving based on what works and what doesn't. You are going to find out the hard way.
Why Use frameworks? J2EE frameworks enable a level of abstraction from the business logic. This clear separation enables the features of the application to evolve separately from the framework. You get to focus on your application instead! And once you have developed more than one application the benefits of a common framework across your applications is much greater.
Most people who develop their own end up with emeshed architecture code in their business logic which results in higher maintenance burden!
Gartner says frameworks are part of the productivity layer and recommend their client to use frameworks. As frameworks offer tighter integration with IDEs, code generators, wizards and the like you will find their adoption widespread. Have a look at www.mvc2frameworks.org for more information about mvc based frameworks and a comparison spreadsheet.
IMO being Struts based for example is a good sense for sales since it has become a defacto standard.
You could adopt another open source servlet-based toolkit such as the Expresso Framework at http://www.javacorporate.com/ which has a commitment to offer developers control over its direction through a full featured collaborative infrastructure - includes a Task List of those things developers want in the solution. It also has the benefit of being a mature tried and true solution. Rather than create another solution - let's embrace the advantage of open source and collaborate and build together!
What if one where to apply the benefits of open source to a commercial solution. I think it could create:
1. Source code included with product;
2. Inexpensive product;
3. Collaborative development with community and developers.
I think such a commercial source product could have some distinct advantages:
4. Support organization;
5. income to pay for full time developers and company infrastructure;
6. Possibly greater innovation.
The company I work for - http://www.javacorporate.com/ offers several open source projects. These worthy projects generate interest in our other commercial products - they are also loss leaders. To open source all of our products would put us out of business. The reality is - many developers download the open source but few as a percentage contribute back to the community or pay for premium support. So open source services has not paid for our full-time developers.
So we also offer a commercial source model on a number of products. We feel long term without the commercial source projects - innovation on our open source projects would be compromised without our fulltime developers who are leaders in the development and who support and encourage the community developers.
I think the javacorporate.com model is win/win to everyone. And the commonality is all of over products enjoy the benefits of source code and a collaborative infrastructure. I hope you'll have a look.