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 comment on the change is: Starting point, wil make a general call for input soon. New page: 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. '''NOTE:''' This page is for recording ideas. The ''discussion'' of these ideas should take place on the beehive-user mailing list. Please explain the idea and benefit '''in brief''' below. Longer descriptions can live on their own wiki pages, with a link from the short description below. '''Contents''' [[TableOfContents]] = Integration with J2EE App Server(s) = Supporting Tomcat alone is too limiting, as it is only a Servlet Container. Many capabilities can't be effectively demonstrated or tested, since they may need JMS, or EJBs, or ... Geronimo is a good target candidate since it also lives in Apache, but the build/configuration model should be flexible enough to support others, since a key goal of Beehive is to enable app portability across app servers. = Business Logic Abstraction = 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.
