You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Francisco Passos <fr...@gmail.com> on 2007/06/22 12:17:22 UTC
[Trinidad & Tomahawk] t:jsCookMenu inside tr:form
Good morning.
It seems jsCookMenu entries do not navigate properly when placed inside a
tr:form, whereas if we use a h:form if works fine.
Is this a bug? Is there a known workaround?
--Francisco
Re: [Trinidad & Tomahawk] t:jsCookMenu inside tr:form
Posted by Francisco Passos <fr...@gmail.com>.
Thank you and sorry for the confusion.
On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
>
> works now....
>
> moved and said dup of https://issues.apache.org/jira/browse/TOMAHAWK-1029
>
> On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > For some reasons I am currently NOT able to edit/move issues.
> >
> > Can somebody give me the rights back ...
> >
> > On 6/22/07, Adam Winer <aw...@gmail.com> wrote:
> > > It should be reported against TOMAHAWK, not TRINIDAD.
> > >
> > > -- Adam
> > >
> > >
> > > On 6/22/07, Francisco Passos <fr...@gmail.com> wrote:
> > > > Just reported it.
> > > >
> > > > Thanks.
> > > >
> > > >
> > > > On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > > > > add the bug to the jira at apaache (tomahawk has a separate)
> > > > >
> > > > > On 6/22/07, Francisco Passos <fr...@gmail.com> wrote:
> > > > > > Hey Matthias,
> > > > > >
> > > > > > I'll gladly report it, but who should I report it to?
> > > > > >
> > > > > > Tomahawk to suggest not to require a naming container based
> form?
> > > > > > Or Trinidad to suggest making one such environment available
> from
> > > > tr:form?
> > > > > >
> > > > > >
> > > > > > As for Adam's response, thank you for your suggestion.
> > > > > >
> > > > > > The solution you proposed is valid and I'm keeping it: using two
> > > > separate
> > > > > > forms, one h:form for jscookmenu and one tr:form for other
> purposes
> > > > where I
> > > > > > require the extended functionality.
> > > > > >
> > > > > > --Francisco
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > > > > > > Francisco,
> > > > > > >
> > > > > > > I think it (jscookm.) requires a naming container based form
> (the
> > > > > > jsCookMenu),
> > > > > > > so please file a bug against it.
> > > > > > >
> > > > > > > -M
> > > > > > >
> > > > > > > On 6/22/07, Adam Winer <awiner@gmail.com > wrote:
> > > > > > > > You can use h:form with Trinidad, FWIW, so if
> > > > > > > > jsCookMenu isn't working you could switch that way.
> > > > > > > >
> > > > > > > > -- Adam
> > > > > > > >
> > > > > > > >
> > > > > > > > On 6/22/07, Francisco Passos < francisco.passos@gmail.com>
> wrote:
> > > > > > > > > No errors, neither on the client, nor on the server...
> > > > > > > > >
> > > > > > > > > The page we're on just refreshes, like when returning a
> null
> > > > > > navigation
> > > > > > > > > string from an action.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On 6/22/07, Matthias Wessendorf <matzew@apache.org >
> wrote:
> > > > > > > > > > do you get any errors ?
> > > > > > > > > > on the client (javascript)
> > > > > > > > > > or on the server ?
> > > > > > > > > >
> > > > > > > > > > the difference between h:form and tr:form is, for
> instance, that
> > > > > > > > > > tr:form isn't a namingContainer.
> > > > > > > > > >
> > > > > > > > > > -M
> > > > > > > > > >
> > > > > > > > > > On 6/22/07, Francisco Passos <
> francisco.passos@gmail.com>
> > > > wrote:
> > > > > > > > > > > Good morning.
> > > > > > > > > > >
> > > > > > > > > > > It seems jsCookMenu entries do not navigate properly
> when
> > > > placed
> > > > > > inside
> > > > > > > > > a
> > > > > > > > > > > tr:form, whereas if we use a h:form if works fine.
> > > > > > > > > > >
> > > > > > > > > > > Is this a bug? Is there a known workaround?
> > > > > > > > > > >
> > > > > > > > > > > --Francisco
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Matthias Wessendorf
> > > > > > > > > >
> > > > > > > > > > further stuff:
> > > > > > > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > > > > > > mail: matzew-at-apache-dot-org
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Matthias Wessendorf
> > > > > > >
> > > > > > > further stuff:
> > > > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > > > mail: matzew-at-apache-dot-org
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Matthias Wessendorf
> > > > >
> > > > > further stuff:
> > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > mail: matzew-at-apache-dot-org
> > > > >
> > > >
> > > >
> > >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > further stuff:
> > blog: http://matthiaswessendorf.wordpress.com/
> > mail: matzew-at-apache-dot-org
> >
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> mail: matzew-at-apache-dot-org
>
Re: [Trinidad & Tomahawk] t:jsCookMenu inside tr:form
Posted by Matthias Wessendorf <ma...@apache.org>.
works now....
moved and said dup of https://issues.apache.org/jira/browse/TOMAHAWK-1029
On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
> For some reasons I am currently NOT able to edit/move issues.
>
> Can somebody give me the rights back ...
>
> On 6/22/07, Adam Winer <aw...@gmail.com> wrote:
> > It should be reported against TOMAHAWK, not TRINIDAD.
> >
> > -- Adam
> >
> >
> > On 6/22/07, Francisco Passos <fr...@gmail.com> wrote:
> > > Just reported it.
> > >
> > > Thanks.
> > >
> > >
> > > On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > > > add the bug to the jira at apaache (tomahawk has a separate)
> > > >
> > > > On 6/22/07, Francisco Passos <fr...@gmail.com> wrote:
> > > > > Hey Matthias,
> > > > >
> > > > > I'll gladly report it, but who should I report it to?
> > > > >
> > > > > Tomahawk to suggest not to require a naming container based form?
> > > > > Or Trinidad to suggest making one such environment available from
> > > tr:form?
> > > > >
> > > > >
> > > > > As for Adam's response, thank you for your suggestion.
> > > > >
> > > > > The solution you proposed is valid and I'm keeping it: using two
> > > separate
> > > > > forms, one h:form for jscookmenu and one tr:form for other purposes
> > > where I
> > > > > require the extended functionality.
> > > > >
> > > > > --Francisco
> > > > >
> > > > >
> > > > >
> > > > > On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > > > > > Francisco,
> > > > > >
> > > > > > I think it (jscookm.) requires a naming container based form (the
> > > > > jsCookMenu),
> > > > > > so please file a bug against it.
> > > > > >
> > > > > > -M
> > > > > >
> > > > > > On 6/22/07, Adam Winer <awiner@gmail.com > wrote:
> > > > > > > You can use h:form with Trinidad, FWIW, so if
> > > > > > > jsCookMenu isn't working you could switch that way.
> > > > > > >
> > > > > > > -- Adam
> > > > > > >
> > > > > > >
> > > > > > > On 6/22/07, Francisco Passos < francisco.passos@gmail.com> wrote:
> > > > > > > > No errors, neither on the client, nor on the server...
> > > > > > > >
> > > > > > > > The page we're on just refreshes, like when returning a null
> > > > > navigation
> > > > > > > > string from an action.
> > > > > > > >
> > > > > > > >
> > > > > > > > On 6/22/07, Matthias Wessendorf <matzew@apache.org > wrote:
> > > > > > > > > do you get any errors ?
> > > > > > > > > on the client (javascript)
> > > > > > > > > or on the server ?
> > > > > > > > >
> > > > > > > > > the difference between h:form and tr:form is, for instance, that
> > > > > > > > > tr:form isn't a namingContainer.
> > > > > > > > >
> > > > > > > > > -M
> > > > > > > > >
> > > > > > > > > On 6/22/07, Francisco Passos < francisco.passos@gmail.com>
> > > wrote:
> > > > > > > > > > Good morning.
> > > > > > > > > >
> > > > > > > > > > It seems jsCookMenu entries do not navigate properly when
> > > placed
> > > > > inside
> > > > > > > > a
> > > > > > > > > > tr:form, whereas if we use a h:form if works fine.
> > > > > > > > > >
> > > > > > > > > > Is this a bug? Is there a known workaround?
> > > > > > > > > >
> > > > > > > > > > --Francisco
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Matthias Wessendorf
> > > > > > > > >
> > > > > > > > > further stuff:
> > > > > > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > > > > > mail: matzew-at-apache-dot-org
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Matthias Wessendorf
> > > > > >
> > > > > > further stuff:
> > > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > > mail: matzew-at-apache-dot-org
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > >
> > > > further stuff:
> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > mail: matzew-at-apache-dot-org
> > > >
> > >
> > >
> >
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> mail: matzew-at-apache-dot-org
>
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
Re: [Trinidad & Tomahawk] t:jsCookMenu inside tr:form
Posted by Matthias Wessendorf <ma...@apache.org>.
For some reasons I am currently NOT able to edit/move issues.
Can somebody give me the rights back ...
On 6/22/07, Adam Winer <aw...@gmail.com> wrote:
> It should be reported against TOMAHAWK, not TRINIDAD.
>
> -- Adam
>
>
> On 6/22/07, Francisco Passos <fr...@gmail.com> wrote:
> > Just reported it.
> >
> > Thanks.
> >
> >
> > On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > > add the bug to the jira at apaache (tomahawk has a separate)
> > >
> > > On 6/22/07, Francisco Passos <fr...@gmail.com> wrote:
> > > > Hey Matthias,
> > > >
> > > > I'll gladly report it, but who should I report it to?
> > > >
> > > > Tomahawk to suggest not to require a naming container based form?
> > > > Or Trinidad to suggest making one such environment available from
> > tr:form?
> > > >
> > > >
> > > > As for Adam's response, thank you for your suggestion.
> > > >
> > > > The solution you proposed is valid and I'm keeping it: using two
> > separate
> > > > forms, one h:form for jscookmenu and one tr:form for other purposes
> > where I
> > > > require the extended functionality.
> > > >
> > > > --Francisco
> > > >
> > > >
> > > >
> > > > On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > > > > Francisco,
> > > > >
> > > > > I think it (jscookm.) requires a naming container based form (the
> > > > jsCookMenu),
> > > > > so please file a bug against it.
> > > > >
> > > > > -M
> > > > >
> > > > > On 6/22/07, Adam Winer <awiner@gmail.com > wrote:
> > > > > > You can use h:form with Trinidad, FWIW, so if
> > > > > > jsCookMenu isn't working you could switch that way.
> > > > > >
> > > > > > -- Adam
> > > > > >
> > > > > >
> > > > > > On 6/22/07, Francisco Passos < francisco.passos@gmail.com> wrote:
> > > > > > > No errors, neither on the client, nor on the server...
> > > > > > >
> > > > > > > The page we're on just refreshes, like when returning a null
> > > > navigation
> > > > > > > string from an action.
> > > > > > >
> > > > > > >
> > > > > > > On 6/22/07, Matthias Wessendorf <matzew@apache.org > wrote:
> > > > > > > > do you get any errors ?
> > > > > > > > on the client (javascript)
> > > > > > > > or on the server ?
> > > > > > > >
> > > > > > > > the difference between h:form and tr:form is, for instance, that
> > > > > > > > tr:form isn't a namingContainer.
> > > > > > > >
> > > > > > > > -M
> > > > > > > >
> > > > > > > > On 6/22/07, Francisco Passos < francisco.passos@gmail.com>
> > wrote:
> > > > > > > > > Good morning.
> > > > > > > > >
> > > > > > > > > It seems jsCookMenu entries do not navigate properly when
> > placed
> > > > inside
> > > > > > > a
> > > > > > > > > tr:form, whereas if we use a h:form if works fine.
> > > > > > > > >
> > > > > > > > > Is this a bug? Is there a known workaround?
> > > > > > > > >
> > > > > > > > > --Francisco
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Matthias Wessendorf
> > > > > > > >
> > > > > > > > further stuff:
> > > > > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > > > > mail: matzew-at-apache-dot-org
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Matthias Wessendorf
> > > > >
> > > > > further stuff:
> > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > mail: matzew-at-apache-dot-org
> > > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > further stuff:
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > mail: matzew-at-apache-dot-org
> > >
> >
> >
>
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
Re: [Trinidad & Tomahawk] t:jsCookMenu inside tr:form
Posted by Adam Winer <aw...@gmail.com>.
It should be reported against TOMAHAWK, not TRINIDAD.
-- Adam
On 6/22/07, Francisco Passos <fr...@gmail.com> wrote:
> Just reported it.
>
> Thanks.
>
>
> On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > add the bug to the jira at apaache (tomahawk has a separate)
> >
> > On 6/22/07, Francisco Passos <fr...@gmail.com> wrote:
> > > Hey Matthias,
> > >
> > > I'll gladly report it, but who should I report it to?
> > >
> > > Tomahawk to suggest not to require a naming container based form?
> > > Or Trinidad to suggest making one such environment available from
> tr:form?
> > >
> > >
> > > As for Adam's response, thank you for your suggestion.
> > >
> > > The solution you proposed is valid and I'm keeping it: using two
> separate
> > > forms, one h:form for jscookmenu and one tr:form for other purposes
> where I
> > > require the extended functionality.
> > >
> > > --Francisco
> > >
> > >
> > >
> > > On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > > > Francisco,
> > > >
> > > > I think it (jscookm.) requires a naming container based form (the
> > > jsCookMenu),
> > > > so please file a bug against it.
> > > >
> > > > -M
> > > >
> > > > On 6/22/07, Adam Winer <awiner@gmail.com > wrote:
> > > > > You can use h:form with Trinidad, FWIW, so if
> > > > > jsCookMenu isn't working you could switch that way.
> > > > >
> > > > > -- Adam
> > > > >
> > > > >
> > > > > On 6/22/07, Francisco Passos < francisco.passos@gmail.com> wrote:
> > > > > > No errors, neither on the client, nor on the server...
> > > > > >
> > > > > > The page we're on just refreshes, like when returning a null
> > > navigation
> > > > > > string from an action.
> > > > > >
> > > > > >
> > > > > > On 6/22/07, Matthias Wessendorf <matzew@apache.org > wrote:
> > > > > > > do you get any errors ?
> > > > > > > on the client (javascript)
> > > > > > > or on the server ?
> > > > > > >
> > > > > > > the difference between h:form and tr:form is, for instance, that
> > > > > > > tr:form isn't a namingContainer.
> > > > > > >
> > > > > > > -M
> > > > > > >
> > > > > > > On 6/22/07, Francisco Passos < francisco.passos@gmail.com>
> wrote:
> > > > > > > > Good morning.
> > > > > > > >
> > > > > > > > It seems jsCookMenu entries do not navigate properly when
> placed
> > > inside
> > > > > > a
> > > > > > > > tr:form, whereas if we use a h:form if works fine.
> > > > > > > >
> > > > > > > > Is this a bug? Is there a known workaround?
> > > > > > > >
> > > > > > > > --Francisco
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Matthias Wessendorf
> > > > > > >
> > > > > > > further stuff:
> > > > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > > > mail: matzew-at-apache-dot-org
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > >
> > > > further stuff:
> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > mail: matzew-at-apache-dot-org
> > > >
> > >
> > >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > further stuff:
> > blog: http://matthiaswessendorf.wordpress.com/
> > mail: matzew-at-apache-dot-org
> >
>
>
Re: [Trinidad & Tomahawk] t:jsCookMenu inside tr:form
Posted by Francisco Passos <fr...@gmail.com>.
Just reported it.
Thanks.
On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
>
> add the bug to the jira at apaache (tomahawk has a separate)
>
> On 6/22/07, Francisco Passos <fr...@gmail.com> wrote:
> > Hey Matthias,
> >
> > I'll gladly report it, but who should I report it to?
> >
> > Tomahawk to suggest not to require a naming container based form?
> > Or Trinidad to suggest making one such environment available from
> tr:form?
> >
> >
> > As for Adam's response, thank you for your suggestion.
> >
> > The solution you proposed is valid and I'm keeping it: using two
> separate
> > forms, one h:form for jscookmenu and one tr:form for other purposes
> where I
> > require the extended functionality.
> >
> > --Francisco
> >
> >
> >
> > On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > > Francisco,
> > >
> > > I think it (jscookm.) requires a naming container based form (the
> > jsCookMenu),
> > > so please file a bug against it.
> > >
> > > -M
> > >
> > > On 6/22/07, Adam Winer <awiner@gmail.com > wrote:
> > > > You can use h:form with Trinidad, FWIW, so if
> > > > jsCookMenu isn't working you could switch that way.
> > > >
> > > > -- Adam
> > > >
> > > >
> > > > On 6/22/07, Francisco Passos < francisco.passos@gmail.com> wrote:
> > > > > No errors, neither on the client, nor on the server...
> > > > >
> > > > > The page we're on just refreshes, like when returning a null
> > navigation
> > > > > string from an action.
> > > > >
> > > > >
> > > > > On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > > > > > do you get any errors ?
> > > > > > on the client (javascript)
> > > > > > or on the server ?
> > > > > >
> > > > > > the difference between h:form and tr:form is, for instance, that
> > > > > > tr:form isn't a namingContainer.
> > > > > >
> > > > > > -M
> > > > > >
> > > > > > On 6/22/07, Francisco Passos < francisco.passos@gmail.com>
> wrote:
> > > > > > > Good morning.
> > > > > > >
> > > > > > > It seems jsCookMenu entries do not navigate properly when
> placed
> > inside
> > > > > a
> > > > > > > tr:form, whereas if we use a h:form if works fine.
> > > > > > >
> > > > > > > Is this a bug? Is there a known workaround?
> > > > > > >
> > > > > > > --Francisco
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Matthias Wessendorf
> > > > > >
> > > > > > further stuff:
> > > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > > mail: matzew-at-apache-dot-org
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > further stuff:
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > mail: matzew-at-apache-dot-org
> > >
> >
> >
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> mail: matzew-at-apache-dot-org
>
Re: [Trinidad & Tomahawk] t:jsCookMenu inside tr:form
Posted by Matthias Wessendorf <ma...@apache.org>.
> add the bug to the jira at apaache (tomahawk has a separate)
add it against tomahawk.
> On 6/22/07, Francisco Passos <fr...@gmail.com> wrote:
> > Hey Matthias,
> >
> > I'll gladly report it, but who should I report it to?
> >
> > Tomahawk to suggest not to require a naming container based form?
> > Or Trinidad to suggest making one such environment available from tr:form?
> >
> >
> > As for Adam's response, thank you for your suggestion.
> >
> > The solution you proposed is valid and I'm keeping it: using two separate
> > forms, one h:form for jscookmenu and one tr:form for other purposes where I
> > require the extended functionality.
> >
> > --Francisco
> >
> >
> >
> > On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > > Francisco,
> > >
> > > I think it (jscookm.) requires a naming container based form (the
> > jsCookMenu),
> > > so please file a bug against it.
> > >
> > > -M
> > >
> > > On 6/22/07, Adam Winer <awiner@gmail.com > wrote:
> > > > You can use h:form with Trinidad, FWIW, so if
> > > > jsCookMenu isn't working you could switch that way.
> > > >
> > > > -- Adam
> > > >
> > > >
> > > > On 6/22/07, Francisco Passos < francisco.passos@gmail.com> wrote:
> > > > > No errors, neither on the client, nor on the server...
> > > > >
> > > > > The page we're on just refreshes, like when returning a null
> > navigation
> > > > > string from an action.
> > > > >
> > > > >
> > > > > On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > > > > > do you get any errors ?
> > > > > > on the client (javascript)
> > > > > > or on the server ?
> > > > > >
> > > > > > the difference between h:form and tr:form is, for instance, that
> > > > > > tr:form isn't a namingContainer.
> > > > > >
> > > > > > -M
> > > > > >
> > > > > > On 6/22/07, Francisco Passos < francisco.passos@gmail.com> wrote:
> > > > > > > Good morning.
> > > > > > >
> > > > > > > It seems jsCookMenu entries do not navigate properly when placed
> > inside
> > > > > a
> > > > > > > tr:form, whereas if we use a h:form if works fine.
> > > > > > >
> > > > > > > Is this a bug? Is there a known workaround?
> > > > > > >
> > > > > > > --Francisco
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Matthias Wessendorf
> > > > > >
> > > > > > further stuff:
> > > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > > mail: matzew-at-apache-dot-org
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > further stuff:
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > mail: matzew-at-apache-dot-org
> > >
> >
> >
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> mail: matzew-at-apache-dot-org
>
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
Re: [Trinidad & Tomahawk] t:jsCookMenu inside tr:form
Posted by Matthias Wessendorf <ma...@apache.org>.
add the bug to the jira at apaache (tomahawk has a separate)
On 6/22/07, Francisco Passos <fr...@gmail.com> wrote:
> Hey Matthias,
>
> I'll gladly report it, but who should I report it to?
>
> Tomahawk to suggest not to require a naming container based form?
> Or Trinidad to suggest making one such environment available from tr:form?
>
>
> As for Adam's response, thank you for your suggestion.
>
> The solution you proposed is valid and I'm keeping it: using two separate
> forms, one h:form for jscookmenu and one tr:form for other purposes where I
> require the extended functionality.
>
> --Francisco
>
>
>
> On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > Francisco,
> >
> > I think it (jscookm.) requires a naming container based form (the
> jsCookMenu),
> > so please file a bug against it.
> >
> > -M
> >
> > On 6/22/07, Adam Winer <awiner@gmail.com > wrote:
> > > You can use h:form with Trinidad, FWIW, so if
> > > jsCookMenu isn't working you could switch that way.
> > >
> > > -- Adam
> > >
> > >
> > > On 6/22/07, Francisco Passos < francisco.passos@gmail.com> wrote:
> > > > No errors, neither on the client, nor on the server...
> > > >
> > > > The page we're on just refreshes, like when returning a null
> navigation
> > > > string from an action.
> > > >
> > > >
> > > > On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > > > > do you get any errors ?
> > > > > on the client (javascript)
> > > > > or on the server ?
> > > > >
> > > > > the difference between h:form and tr:form is, for instance, that
> > > > > tr:form isn't a namingContainer.
> > > > >
> > > > > -M
> > > > >
> > > > > On 6/22/07, Francisco Passos < francisco.passos@gmail.com> wrote:
> > > > > > Good morning.
> > > > > >
> > > > > > It seems jsCookMenu entries do not navigate properly when placed
> inside
> > > > a
> > > > > > tr:form, whereas if we use a h:form if works fine.
> > > > > >
> > > > > > Is this a bug? Is there a known workaround?
> > > > > >
> > > > > > --Francisco
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Matthias Wessendorf
> > > > >
> > > > > further stuff:
> > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > mail: matzew-at-apache-dot-org
> > > > >
> > > >
> > > >
> > >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > further stuff:
> > blog: http://matthiaswessendorf.wordpress.com/
> > mail: matzew-at-apache-dot-org
> >
>
>
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
Re: [Trinidad & Tomahawk] t:jsCookMenu inside tr:form
Posted by Francisco Passos <fr...@gmail.com>.
Hey Matthias,
I'll gladly report it, but who should I report it to?
Tomahawk to suggest not to require a naming container based form?
Or Trinidad to suggest making one such environment available from tr:form?
As for Adam's response, thank you for your suggestion.
The solution you proposed is valid and I'm keeping it: using two separate
forms, one h:form for jscookmenu and one tr:form for other purposes where I
require the extended functionality.
--Francisco
On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
>
> Francisco,
>
> I think it (jscookm.) requires a naming container based form (the
> jsCookMenu),
> so please file a bug against it.
>
> -M
>
> On 6/22/07, Adam Winer <aw...@gmail.com> wrote:
> > You can use h:form with Trinidad, FWIW, so if
> > jsCookMenu isn't working you could switch that way.
> >
> > -- Adam
> >
> >
> > On 6/22/07, Francisco Passos <fr...@gmail.com> wrote:
> > > No errors, neither on the client, nor on the server...
> > >
> > > The page we're on just refreshes, like when returning a null
> navigation
> > > string from an action.
> > >
> > >
> > > On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > > > do you get any errors ?
> > > > on the client (javascript)
> > > > or on the server ?
> > > >
> > > > the difference between h:form and tr:form is, for instance, that
> > > > tr:form isn't a namingContainer.
> > > >
> > > > -M
> > > >
> > > > On 6/22/07, Francisco Passos < francisco.passos@gmail.com> wrote:
> > > > > Good morning.
> > > > >
> > > > > It seems jsCookMenu entries do not navigate properly when placed
> inside
> > > a
> > > > > tr:form, whereas if we use a h:form if works fine.
> > > > >
> > > > > Is this a bug? Is there a known workaround?
> > > > >
> > > > > --Francisco
> > > > >
> > > >
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > >
> > > > further stuff:
> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > mail: matzew-at-apache-dot-org
> > > >
> > >
> > >
> >
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> mail: matzew-at-apache-dot-org
>
Re: [Trinidad & Tomahawk] t:jsCookMenu inside tr:form
Posted by Matthias Wessendorf <ma...@apache.org>.
Francisco,
I think it (jscookm.) requires a naming container based form (the jsCookMenu),
so please file a bug against it.
-M
On 6/22/07, Adam Winer <aw...@gmail.com> wrote:
> You can use h:form with Trinidad, FWIW, so if
> jsCookMenu isn't working you could switch that way.
>
> -- Adam
>
>
> On 6/22/07, Francisco Passos <fr...@gmail.com> wrote:
> > No errors, neither on the client, nor on the server...
> >
> > The page we're on just refreshes, like when returning a null navigation
> > string from an action.
> >
> >
> > On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > > do you get any errors ?
> > > on the client (javascript)
> > > or on the server ?
> > >
> > > the difference between h:form and tr:form is, for instance, that
> > > tr:form isn't a namingContainer.
> > >
> > > -M
> > >
> > > On 6/22/07, Francisco Passos < francisco.passos@gmail.com> wrote:
> > > > Good morning.
> > > >
> > > > It seems jsCookMenu entries do not navigate properly when placed inside
> > a
> > > > tr:form, whereas if we use a h:form if works fine.
> > > >
> > > > Is this a bug? Is there a known workaround?
> > > >
> > > > --Francisco
> > > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > further stuff:
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > mail: matzew-at-apache-dot-org
> > >
> >
> >
>
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
Re: [Trinidad & Tomahawk] t:jsCookMenu inside tr:form
Posted by Adam Winer <aw...@gmail.com>.
You can use h:form with Trinidad, FWIW, so if
jsCookMenu isn't working you could switch that way.
-- Adam
On 6/22/07, Francisco Passos <fr...@gmail.com> wrote:
> No errors, neither on the client, nor on the server...
>
> The page we're on just refreshes, like when returning a null navigation
> string from an action.
>
>
> On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > do you get any errors ?
> > on the client (javascript)
> > or on the server ?
> >
> > the difference between h:form and tr:form is, for instance, that
> > tr:form isn't a namingContainer.
> >
> > -M
> >
> > On 6/22/07, Francisco Passos < francisco.passos@gmail.com> wrote:
> > > Good morning.
> > >
> > > It seems jsCookMenu entries do not navigate properly when placed inside
> a
> > > tr:form, whereas if we use a h:form if works fine.
> > >
> > > Is this a bug? Is there a known workaround?
> > >
> > > --Francisco
> > >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > further stuff:
> > blog: http://matthiaswessendorf.wordpress.com/
> > mail: matzew-at-apache-dot-org
> >
>
>
Re: [Trinidad & Tomahawk] t:jsCookMenu inside tr:form
Posted by Francisco Passos <fr...@gmail.com>.
No errors, neither on the client, nor on the server...
The page we're on just refreshes, like when returning a null navigation
string from an action.
On 6/22/07, Matthias Wessendorf <ma...@apache.org> wrote:
>
> do you get any errors ?
> on the client (javascript)
> or on the server ?
>
> the difference between h:form and tr:form is, for instance, that
> tr:form isn't a namingContainer.
>
> -M
>
> On 6/22/07, Francisco Passos <fr...@gmail.com> wrote:
> > Good morning.
> >
> > It seems jsCookMenu entries do not navigate properly when placed inside
> a
> > tr:form, whereas if we use a h:form if works fine.
> >
> > Is this a bug? Is there a known workaround?
> >
> > --Francisco
> >
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> mail: matzew-at-apache-dot-org
>
Re: [Trinidad & Tomahawk] t:jsCookMenu inside tr:form
Posted by Matthias Wessendorf <ma...@apache.org>.
do you get any errors ?
on the client (javascript)
or on the server ?
the difference between h:form and tr:form is, for instance, that
tr:form isn't a namingContainer.
-M
On 6/22/07, Francisco Passos <fr...@gmail.com> wrote:
> Good morning.
>
> It seems jsCookMenu entries do not navigate properly when placed inside a
> tr:form, whereas if we use a h:form if works fine.
>
> Is this a bug? Is there a known workaround?
>
> --Francisco
>
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org