Issue Details (XML | Word | Printable)

Key: ROO-1
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Ben Alex
Reporter: Rod Johnson
Votes: 5
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
Spring Roo

Dramatically improve Java developer productivity

Created: 13/May/09 08:51 PM   Updated: 21/May/09 07:40 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Environment: All platforms


 Description  « Hide

While Spring has improved it greatly, enterprise Java productivity is still not ideal. Development involves excessive effort in numerous areas, including JSP authoring, build scripts, web.xml deployment descriptors and JPA persistence. Creating a new project involves excessive integration and coding effort, as does adding new functionality or introducing additional technologies.

This allows proponents of platforms beside the JVM to offer significant productivity advantages for simple application scenarios, even though they fail to scale to meet increased complexity or scale requirements. This is undesirable as it leaves users the danger of starting down an initially productive approach that will lead them to a dead end.

We need a solution that builds on the lessons of other platforms and frameworks but innovates to offer similar benefits to Java developers, without the tradeoffs. We need a solution that builds on our existing Spring vision of simplicity and power and dramatically improves productivity to make Java highly competitive for ALL applications, from simple to complex.

Such a solution should offer a higher level of abstraction for common operations (such as creating a web-editable entity), enabling concise expression of the developer's intent. It should have the following characteristics:

  • Easy to use
  • Produce demonstrable productivity benefit
  • Reuse existing developer knowledge, skills and experience
  • Facilitate the creation of best practice enterprise Spring applications
  • Never compromise engineering integrity (speed, power, flexibility)
  • Support non-web app profiles (eg batch, next-gen clients etc)
  • Use established technologies
  • Leverage existing Java tools (and thus knowledge) where feasible
  • Allow users to adopt it incrementally without a "big bang"


Rod Johnson made changes - 21/May/09 07:20 PM
Field Original Value New Value
Reporter Ben Alex [ balex ] Rod Johnson [ rod.johnson ]
Assignee Ben Alex [ balex ]
Summary TBC Dramatically improve Java developer productivity
Description While Spring makes it much easier, enterprise Java development still involves tedious hand coding in numerous areas, including JSP authoring, build scripts, web.xml deployment descriptors and JPA.

This allows proponents of platforms beside the JVM to offer significant productivity advantages for simple application scenarios, even though they fail to scale to meet increased complexity or scale requirements. This is undesirable as it leaving users the danger of starting down an initially productive approach that will lead them to a problematic

We need a solution that dramatically improves productivity to make Java highly competitive for <i>all</i> applications, from simple to complex--a tool that builds on our existing Spring vision of simplicity and power, and ensures Java developers can build quality, best-practice Spring applications in Java with exceptionally high productivity.

Such a tool should be:

- Easy to use
- Produce demonstrable productivity benefit
- Reuse existing developer knowledge, skills and experience
- Facilitate the creation of best practice enterprise Spring applications
- Never compromise engineering integrity (speed, power, flexibility)
- Support non-web app profiles (eg batch, next-gen clients etc)
- Use established, mainstream technologies (eg JSP, JPA, MVN etc)
- Leverage existing Java tools (+ thus knowledge) where feasible
- Allow users to incrementally adopt the tool without a "big bang"

Rod Johnson made changes - 21/May/09 07:25 PM
Description While Spring makes it much easier, enterprise Java development still involves tedious hand coding in numerous areas, including JSP authoring, build scripts, web.xml deployment descriptors and JPA.

This allows proponents of platforms beside the JVM to offer significant productivity advantages for simple application scenarios, even though they fail to scale to meet increased complexity or scale requirements. This is undesirable as it leaving users the danger of starting down an initially productive approach that will lead them to a problematic

We need a solution that dramatically improves productivity to make Java highly competitive for <i>all</i> applications, from simple to complex--a tool that builds on our existing Spring vision of simplicity and power, and ensures Java developers can build quality, best-practice Spring applications in Java with exceptionally high productivity.

Such a tool should be:

- Easy to use
- Produce demonstrable productivity benefit
- Reuse existing developer knowledge, skills and experience
- Facilitate the creation of best practice enterprise Spring applications
- Never compromise engineering integrity (speed, power, flexibility)
- Support non-web app profiles (eg batch, next-gen clients etc)
- Use established, mainstream technologies (eg JSP, JPA, MVN etc)
- Leverage existing Java tools (+ thus knowledge) where feasible
- Allow users to incrementally adopt the tool without a "big bang"

While Spring had made it much easier, enterprise Java development still involves excessive effort in numerous areas, including JSP authoring, build scripts, web.xml deployment descriptors and JPA.

This allows proponents of platforms beside the JVM to offer significant productivity advantages for simple application scenarios, even though they fail to scale to meet increased complexity or scale requirements. This is undesirable as it leaving users the danger of starting down an initially productive approach that will lead them to a problematic

We need a solution that builds on the lessons of other platforms and frameworks but innovates to offer similar benefits to Java developers, without the tradeoffs. We need a solution that builds on our existing Spring vision of simplicity and power and dramatically improves productivity to make Java highly competitive for <i>all</i> applications, from simple to complex.

Such a tool should offer a higher level of abstraction for common operations (such as creating a web-editable entity), and have the following characteristics:

- Easy to use
- Produce demonstrable productivity benefit
- Reuse existing developer knowledge, skills and experience
- Facilitate the creation of best practice enterprise Spring applications
- Never compromise engineering integrity (speed, power, flexibility)
- Support non-web app profiles (eg batch, next-gen clients etc)
- Use established, mainstream technologies (eg JSP, JPA, MVN etc)
- Leverage existing Java tools (+ thus knowledge) where feasible
- Allow users to incrementally adopt the tool without a "big bang"

Environment All platforms
Rod Johnson made changes - 21/May/09 07:37 PM
Description While Spring had made it much easier, enterprise Java development still involves excessive effort in numerous areas, including JSP authoring, build scripts, web.xml deployment descriptors and JPA.

This allows proponents of platforms beside the JVM to offer significant productivity advantages for simple application scenarios, even though they fail to scale to meet increased complexity or scale requirements. This is undesirable as it leaving users the danger of starting down an initially productive approach that will lead them to a problematic

We need a solution that builds on the lessons of other platforms and frameworks but innovates to offer similar benefits to Java developers, without the tradeoffs. We need a solution that builds on our existing Spring vision of simplicity and power and dramatically improves productivity to make Java highly competitive for <i>all</i> applications, from simple to complex.

Such a tool should offer a higher level of abstraction for common operations (such as creating a web-editable entity), and have the following characteristics:

- Easy to use
- Produce demonstrable productivity benefit
- Reuse existing developer knowledge, skills and experience
- Facilitate the creation of best practice enterprise Spring applications
- Never compromise engineering integrity (speed, power, flexibility)
- Support non-web app profiles (eg batch, next-gen clients etc)
- Use established, mainstream technologies (eg JSP, JPA, MVN etc)
- Leverage existing Java tools (+ thus knowledge) where feasible
- Allow users to incrementally adopt the tool without a "big bang"

While Spring has improved it greatly, enterprise Java productivity is still not ideal. Development involves excessive effort in numerous areas, including JSP authoring, build scripts, web.xml deployment descriptors and JPA persistence. Creating a new project involves excessive integration and coding effort, as does adding new functionality or introducing additional technologies.

This allows proponents of platforms beside the JVM to offer significant productivity advantages for simple application scenarios, even though they fail to scale to meet increased complexity or scale requirements. This is undesirable as it leaving users the danger of starting down an initially productive approach that will lead them to a dead end.

We need a solution that builds on the lessons of other platforms and frameworks but innovates to offer similar benefits to Java developers, without the tradeoffs. We need a solution that builds on our existing Spring vision of simplicity and power and dramatically improves productivity to make Java highly competitive for <i>all</i> applications, from simple to complex.

Such a tool should offer a higher level of abstraction for common operations (such as creating a web-editable entity), enabling concise expression of the developer's intent. It should have the following characteristics:

- Easy to use
- Produce demonstrable productivity benefit
- Reuse existing developer knowledge, skills and experience
- Facilitate the creation of best practice enterprise Spring applications
- Never compromise engineering integrity (speed, power, flexibility)
- Support non-web app profiles (eg batch, next-gen clients etc)
- Use established, mainstream technologies (eg JSP, JPA, MVN etc)
- Leverage existing Java tools (+ thus knowledge) where feasible
- Allow users to incrementally adopt the tool without a "big bang"

Rod Johnson made changes - 21/May/09 07:38 PM
Description While Spring has improved it greatly, enterprise Java productivity is still not ideal. Development involves excessive effort in numerous areas, including JSP authoring, build scripts, web.xml deployment descriptors and JPA persistence. Creating a new project involves excessive integration and coding effort, as does adding new functionality or introducing additional technologies.

This allows proponents of platforms beside the JVM to offer significant productivity advantages for simple application scenarios, even though they fail to scale to meet increased complexity or scale requirements. This is undesirable as it leaving users the danger of starting down an initially productive approach that will lead them to a dead end.

We need a solution that builds on the lessons of other platforms and frameworks but innovates to offer similar benefits to Java developers, without the tradeoffs. We need a solution that builds on our existing Spring vision of simplicity and power and dramatically improves productivity to make Java highly competitive for <i>all</i> applications, from simple to complex.

Such a tool should offer a higher level of abstraction for common operations (such as creating a web-editable entity), enabling concise expression of the developer's intent. It should have the following characteristics:

- Easy to use
- Produce demonstrable productivity benefit
- Reuse existing developer knowledge, skills and experience
- Facilitate the creation of best practice enterprise Spring applications
- Never compromise engineering integrity (speed, power, flexibility)
- Support non-web app profiles (eg batch, next-gen clients etc)
- Use established, mainstream technologies (eg JSP, JPA, MVN etc)
- Leverage existing Java tools (+ thus knowledge) where feasible
- Allow users to incrementally adopt the tool without a "big bang"

While Spring has improved it greatly, enterprise Java productivity is still not ideal. Development involves excessive effort in numerous areas, including JSP authoring, build scripts, web.xml deployment descriptors and JPA persistence. Creating a new project involves excessive integration and coding effort, as does adding new functionality or introducing additional technologies.

This allows proponents of platforms beside the JVM to offer significant productivity advantages for simple application scenarios, even though they fail to scale to meet increased complexity or scale requirements. This is undesirable as it leaves users the danger of starting down an initially productive approach that will lead them to a dead end.

We need a solution that builds on the lessons of other platforms and frameworks but innovates to offer similar benefits to Java developers, without the tradeoffs. We need a solution that builds on our existing Spring vision of simplicity and power and dramatically improves productivity to make Java highly competitive for ALL applications, from simple to complex.

Such a tool should offer a higher level of abstraction for common operations (such as creating a web-editable entity), enabling concise expression of the developer's intent. It should have the following characteristics:

- Easy to use
- Produce demonstrable productivity benefit
- Reuse existing developer knowledge, skills and experience
- Facilitate the creation of best practice enterprise Spring applications
- Never compromise engineering integrity (speed, power, flexibility)
- Support non-web app profiles (eg batch, next-gen clients etc)
- Use established, mainstream technologies (eg JSP, JPA, MVN etc)
- Leverage existing Java tools (+ thus knowledge) where feasible
- Allow users to incrementally adopt the tool without a "big bang"

Rod Johnson made changes - 21/May/09 07:39 PM
Description While Spring has improved it greatly, enterprise Java productivity is still not ideal. Development involves excessive effort in numerous areas, including JSP authoring, build scripts, web.xml deployment descriptors and JPA persistence. Creating a new project involves excessive integration and coding effort, as does adding new functionality or introducing additional technologies.

This allows proponents of platforms beside the JVM to offer significant productivity advantages for simple application scenarios, even though they fail to scale to meet increased complexity or scale requirements. This is undesirable as it leaves users the danger of starting down an initially productive approach that will lead them to a dead end.

We need a solution that builds on the lessons of other platforms and frameworks but innovates to offer similar benefits to Java developers, without the tradeoffs. We need a solution that builds on our existing Spring vision of simplicity and power and dramatically improves productivity to make Java highly competitive for ALL applications, from simple to complex.

Such a tool should offer a higher level of abstraction for common operations (such as creating a web-editable entity), enabling concise expression of the developer's intent. It should have the following characteristics:

- Easy to use
- Produce demonstrable productivity benefit
- Reuse existing developer knowledge, skills and experience
- Facilitate the creation of best practice enterprise Spring applications
- Never compromise engineering integrity (speed, power, flexibility)
- Support non-web app profiles (eg batch, next-gen clients etc)
- Use established, mainstream technologies (eg JSP, JPA, MVN etc)
- Leverage existing Java tools (+ thus knowledge) where feasible
- Allow users to incrementally adopt the tool without a "big bang"

While Spring has improved it greatly, enterprise Java productivity is still not ideal. Development involves excessive effort in numerous areas, including JSP authoring, build scripts, web.xml deployment descriptors and JPA persistence. Creating a new project involves excessive integration and coding effort, as does adding new functionality or introducing additional technologies.

This allows proponents of platforms beside the JVM to offer significant productivity advantages for simple application scenarios, even though they fail to scale to meet increased complexity or scale requirements. This is undesirable as it leaves users the danger of starting down an initially productive approach that will lead them to a dead end.

We need a solution that builds on the lessons of other platforms and frameworks but innovates to offer similar benefits to Java developers, without the tradeoffs. We need a solution that builds on our existing Spring vision of simplicity and power and dramatically improves productivity to make Java highly competitive for ALL applications, from simple to complex.

Such a tool should offer a higher level of abstraction for common operations (such as creating a web-editable entity), enabling concise expression of the developer's intent. It should have the following characteristics:

- Easy to use
- Produce demonstrable productivity benefit
- Reuse existing developer knowledge, skills and experience
- Facilitate the creation of best practice enterprise Spring applications
- Never compromise engineering integrity (speed, power, flexibility)
- Support non-web app profiles (eg batch, next-gen clients etc)
- Use established technologies
- Leverage existing Java tools (and thus knowledge) where feasible
- Allow users to incrementally adopt the tool without a "big bang"

Rod Johnson made changes - 21/May/09 07:40 PM
Description While Spring has improved it greatly, enterprise Java productivity is still not ideal. Development involves excessive effort in numerous areas, including JSP authoring, build scripts, web.xml deployment descriptors and JPA persistence. Creating a new project involves excessive integration and coding effort, as does adding new functionality or introducing additional technologies.

This allows proponents of platforms beside the JVM to offer significant productivity advantages for simple application scenarios, even though they fail to scale to meet increased complexity or scale requirements. This is undesirable as it leaves users the danger of starting down an initially productive approach that will lead them to a dead end.

We need a solution that builds on the lessons of other platforms and frameworks but innovates to offer similar benefits to Java developers, without the tradeoffs. We need a solution that builds on our existing Spring vision of simplicity and power and dramatically improves productivity to make Java highly competitive for ALL applications, from simple to complex.

Such a tool should offer a higher level of abstraction for common operations (such as creating a web-editable entity), enabling concise expression of the developer's intent. It should have the following characteristics:

- Easy to use
- Produce demonstrable productivity benefit
- Reuse existing developer knowledge, skills and experience
- Facilitate the creation of best practice enterprise Spring applications
- Never compromise engineering integrity (speed, power, flexibility)
- Support non-web app profiles (eg batch, next-gen clients etc)
- Use established technologies
- Leverage existing Java tools (and thus knowledge) where feasible
- Allow users to incrementally adopt the tool without a "big bang"

While Spring has improved it greatly, enterprise Java productivity is still not ideal. Development involves excessive effort in numerous areas, including JSP authoring, build scripts, web.xml deployment descriptors and JPA persistence. Creating a new project involves excessive integration and coding effort, as does adding new functionality or introducing additional technologies.

This allows proponents of platforms beside the JVM to offer significant productivity advantages for simple application scenarios, even though they fail to scale to meet increased complexity or scale requirements. This is undesirable as it leaves users the danger of starting down an initially productive approach that will lead them to a dead end.

We need a solution that builds on the lessons of other platforms and frameworks but innovates to offer similar benefits to Java developers, without the tradeoffs. We need a solution that builds on our existing Spring vision of simplicity and power and dramatically improves productivity to make Java highly competitive for ALL applications, from simple to complex.

Such a solution should offer a higher level of abstraction for common operations (such as creating a web-editable entity), enabling concise expression of the developer's intent. It should have the following characteristics:

- Easy to use
- Produce demonstrable productivity benefit
- Reuse existing developer knowledge, skills and experience
- Facilitate the creation of best practice enterprise Spring applications
- Never compromise engineering integrity (speed, power, flexibility)
- Support non-web app profiles (eg batch, next-gen clients etc)
- Use established technologies
- Leverage existing Java tools (and thus knowledge) where feasible
- Allow users to adopt it incrementally without a "big bang"