And btw the various actions are also stored using the class name if I
remember well... so you can find your beans in the request scope when you
have more than one.
Cheers
Remi
2011/1/4 VANKEISBELCK Remi <r...@rvkb.com>
> Yeah sure, but it can be solved easily by storing the variable before
> inclusion, ans using this in the "main" page. You should have no problems
> inside the "fragments", as Stripes will override the request atrribute when
> executing the included event.
>
> I was more wondering if the jsp:include didn't behave as expected when
> including a Stripes action. I'm sure I've done this already without any
> problem...
>
> Cheers
>
> Remi
>
> 2011/1/4 Ben Gunter <gunter...@gmail.com>
>
> I think what Jonathan is saying is correct, though I've never personally
>> been troubled by it. Stripes stuffs the current ActionBean -- the one that
>> is handling the request -- into request scope under the key "actionBean".
>> (Of course you know that.) So if you're in a JSP that was forwarded from an
>> ActionBean and you <jsp:include> a request to a different ActionBean, then
>> ${actionBean} before the include is different from ${actionBean} after the
>> include.
>>
>> -Ben
>>
>> On Tue, Jan 4, 2011 at 8:39 AM, VANKEISBELCK Remi <r...@rvkb.com> wrote:
>>
>>> Not sure I understand. You say you can't do this :
>>>
>>> my.jsp :
>>> <html>
>>> <jsp:include page="/partial.action"/>
>>> <jsp:include page="/partial.action"/>
>>> </html>
>>>
>>> ?
>>>
>>> I think I've done this already... strange.
>>>
>>> As you say, Stripes does bind stuff to the request, but each include is
>>> isolated (it behaves like a full the request/response cycle).
>>>
>>> So unless your main controller action (the one handling the incoming http
>>> request) is the same as the one you include in the view (that would be quite
>>> weird :P), and you access this main controller after inclusions (like
>>> ${actionBean.xyz}), I can't see an issue here.
>>>
>>> Am I missing something ?
>>>
>>> Cheers
>>>
>>> Remi
>>>
>>> 2011/1/4 Jonathan <jesuisjonat...@gmx.fr>
>>>
>>> This seems to be the solution to first order, but Stripes keeps some
>>>> informations in the request (the action bean, the name of the event)
>>>> that
>>>> prevents this method to function (event name conflict in some cases,
>>>> impossible
>>>> to make multiple inclusions of same action bean since it's cached).
>>>> Based on feedback from the mailing list I think there is no "right way"
>>>> to do
>>>> that. I think the use of the JSTL tag <c:import/> is the closest answer
>>>> to what
>>>> I'm looking to do. An other solution : implementing a special include
>>>> tag that
>>>> wrap request to avoid conflicts between parameters and attributes of the
>>>> main
>>>> request and those of the include request.
>>>>
>>>> Thank you all for your help
>>>>
>>>>
>
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
