Ben,
That is interesting information. We plan on having multiple web apps
deployed in the same app server and each web app will at most be one
Stripes application.
If I understand you correctly I guess I can imagine someone trying to
put together multiple Stripes applications in a single web app but that
doesn't seem right in my opinion. I can also see some cases were its
desirable to do so if you have strict requirements on what the URI
prefixes need to be but personally I always prefer architecting a
reverse proxy layer in front of the UI layer for multiple reasons... one
of which being the ability to manipulate URI prefixes... etc...
Anyone know why Tim had this goal or better yet the use case he was
trying to satisfy for it?
Thanks,
--Nikolaos
Ben Gunter wrote:
All this sounds about right. I suggest you not try to use multiple
Stripes configurations in the same app. (Nor should you try to put
Stripes in a class loader that is shared among apps.) As I understand
it, one of Tim's goals when he first designed Stripes was that you
should be able to use multiple configurations in a single app.
However, I was unaware of that goal, and when I started contributing
for release 1.5 I did some things that made doing that iffy at best.
Maybe in a future release it will be OK, but not in 1.5.x.
-Ben
On Thu, Apr 29, 2010 at 5:53 PM, Oscar Westra van Holthe - Kind
<os...@westravanholthe.nl <mailto:os...@westravanholthe.nl>> wrote:
On 29-04-2010 at 17:16, Nikolaos Giannopoulos wrote:
> In Java there are 4 types of session scopes below.
>
> Clearly JSPs use "page" scope and a framework most likely will
> utilize "application scope" but does:
>
> 1) Stripes utilize "request" scope at all and if so where?
>
> 2) Stripes utilize "session" scope outside of ActionBeanContext and
> Flash Scope?
IIRC, Stripes does not use the application scope, but instead uses
a Filter
to scope a configuration to a specific set of URL's. This means
you _can_ use
Stripes with multiple configurations (whether you should is another
matter).
Stripes uses the session scope to implement it's flash scope only.
You can
use it to store ActionBean instances in the session as well, as
illustrated
by the @Session annotation in StripesStuff:
http://www.stripesframework.org/display/stripes/Save+ActionBean+fields+in+session
Stripes uses the request scope to store the action bean for the
JSP's it
forwards to. This allows the Stripes tags to access the properties
and public
fields of the ActionBean -- Stripes treats public fields as
properties, as a
convenience to not need to write boilerplate getters & setters.
Stripes does not use the page scope for its core functionality; it
may do so
for its layout tags, but I'm not sure about that.
Oscar
--
,-_
/() ) Oscar Westra van Holthe - Kind
http://www.xs4all.nl/~kindop/ <http://www.xs4all.nl/%7Ekindop/>
(__ (
=/ () DRM "manages access" in the same way that a jail "manages
freedom".
------------------------------------------------------------------------------
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
<mailto:Stripes-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/stripes-users
--
Nikolaos Giannopoulos
Director, BrightMinds Software Inc.
e. nikol...@brightminds.org
w. www.brightminds.org
t. 1.613.822.1700
c. 1.613.797.0036
f. 1.613.822.1915
------------------------------------------------------------------------------
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
