Hi Rusty,
Some of the jsps use jsp:useBean to pull in beans from the service layer.
[...]
The way I've done it in the past would be to have a property on the
action bean, allComponents for example, with its getter, and to call
componentManager.allComponents() in the action bean to set the
jsp:useBean seems pretty useful to me. In a real web application,
there are all sorts of contextual things that are important to the
application (and the presentation of application status, situations,
context, etc) that span many separate pages (and therefore actions).
Having to litter lots of
I agree about littering action beans but what about integration testing?
Suppose you want to replace ComponentListActionBean with a stub or fake that
exercises corner cases that you need to test? Then in your tests instead of
ComponentManager you could inject into your action beans
Some of the jsps use jsp:useBean to pull in beans from the service layer. For
example, in BulkAddEditBugs.jsp is
jsp:useBean
id=componentManager
scope=page
class=net.sourceforge.stripes.examples.bugzooky.biz.ComponentManager
/
... and then further down
stripes:select
