Hi
I finally created an issue:
https://issues.apache.org/jira/browse/MYFACES-2946
and attached a patch there. In theory, we can include it on myfaces 2.0.x,
because composite:attribute targets opens the posibility to do it, so I'll
commit the patch soon.
regards,
Leonardo Uribe
This is cool, thank you for sending the fixed example! How comes this works,
though
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=755 is
retargeted to 2.2? Do you have one more in your magic box for actions or does
the spec issue remain valid here? If I do this:
Hi Ganesh,
Sorry, I was too fast in writing the answer. It works if you're using
f:actionListener, but it does not work correctly, if you're using a
parameter like action or actionListener (this is the related spec
issue).
Regards,
Jakob
2010/10/13 Ganesh gan...@j4fry.org:
This is cool, thank
ok, thank you, so I will not open a MyFaces issue on this but comment the spec
issue instead.
Best regards,
Ganesh
Am 13.10.2010 11:15, schrieb Jakob Korherr:
Hi Ganesh,
Sorry, I was too fast in writing the answer. It works if you're using
f:actionListener, but it does not work correctly, if
Hi,
If my test page calls a composite component in level 1:
xmlns:level1=http://java.sun.com/jsf/composite/level1;
level1:button value=test1
f:actionListener for=button1 binding=#{myBean.action1} /
/level1:button
where level1 button passes the action
Hi Ganesh,
This is a known problem of the JSF 2.0 spec, see [1]. Sadly it was
(re-)targeted for 2.2.
The problem is that when the ation listener is retargeted (from the
composite component to the inner (implementation) component), it
cannot be retargeted to another composite component, because
But anyhow, please open an issue for this. Thanks!
Regards,
Jakob
2010/10/12 Jakob Korherr jakob.korh...@gmail.com:
Hi Ganesh,
This is a known problem of the JSF 2.0 spec, see [1]. Sadly it was
(re-)targeted for 2.2.
The problem is that when the ation listener is retargeted (from the
Hi
I remember this one. Fortunately, MyFaces has many, many tests for composite
components. It also has a test for this specific issue and it works well:
testCompositeActionSource.xhtml
h:form id=testForm1
testComposite:compositeActionSource
f:actionListener for=button2
Hi
I tried your example and work in this way:
test page calls a composite component in level 1:
xmlns:level1=http://java.sun.com/jsf/composite/level1;
level1:button value=test1
f:actionListener for=button1 binding=#{myBean.action1}
/
/level1:button
level1
