Dear Wiki user, You have subscribed to a wiki page or wiki category on "Beehive Wiki" for change notification.
The following page has been changed by KyleMarvin: http://wiki.apache.org/beehive/WishList ------------------------------------------------------------------------------ - The purpose for this page is to capture ('''in brief''') wish list ideas for future release of the Apache Beehive project. It is '''not intended for bugs or minor enhancements to existing features''', which have more appropriate venues (JIRA), but new things that would improve Beehive. + The purpose for this page is to capture ('''in brief''') wish list ideas for future releases of the Apache Beehive project. It is '''not intended for bugs or minor enhancements to existing features''', which have more appropriate venues (JIRA), but new things that would improve Beehive. '''NOTE:''' This page is for recording ideas. The ''discussion'' of these ideas should take place on the beehive-user mailing list. @@ -17, +17 @@ A hole in the current Beehive app story is the ability to write some basic business logic and then add transaction or security semantics to it. This doesn't imply that Beehive needs a business logic container; the right answer might be to write the logic as a control (or annotated POJO) and provide a runtime mapping so that it runs inside of an EJB, Spring Bean, or other existing container that can provide the desired semantics. + = Better Support for Building Tests = + + Beehive shouldn't just help a Beehive developers author a new abstraction such a pageflow, web service, or control, it should also make it easy to bootstrap testing of the abstractions. We should look at both in-container and standalone (unit/TDD) testing. +
