Hi jacek,
On 9/15/06, Jacek Wiślicki <[EMAIL PROTECTED]> wrote:
Wiadomosc od Edgar Poce z 2006-09-15 19:53 brzmiala:
>> > Unfortunately this code only works when the request is a
>> > RenderRequest, it seems that in ActionRequests the ContentFragment can
>> > not be retrieved. Is there any way to get the ContentFragment from an
>> > ActionRequest?
>> I afraid not :(
> is there any reason for it not being available in ActionRequests?,
> shoud I open a JIRA issue?
See JSR-168 for details...
I will, thanks. I guess I'll have to pass the path in a hidden field.
>> > Another problem is that I can't navigate the hierarchy from a fragment
>> > to the parent page. There's no method in ContentFragment that allows
>> > me to get the parent fragment and thus build a path that includes the
>> > decorator fragments. Is there any way to build that path that I'm
>> > missing.
>> As far as I remember, a Fragment implements a Node interface. This
>> interface ensures getParent() method.
> Well, as far as I can see the inheritance is something like
> SecuredResource > BaseElement > Fragment > ContentFragment
> and none of those interfaces has a method to get the parent.
You are right, my memory seems to be worse than I thought ;) (Node
implements BaseElement, not BaseElement implements Node). And what about
looping throuh all page fragments in order to establish a child-parent
relationship? A number of page fragments is rather limited (just a few
ones) and such a process should be efficient, I guess.
I'll give it a try.
thank you very much for your help,
edgar
--
pozdrawiam,
Jacek Wislicki
[EMAIL PROTECTED]
http://www.nauka-biznes.org.pl/jetspeed/portal/
tel.: +48 502 408 444
gg: 2540358
skype: jacek_wislicki
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
