Re: Force child component enabled

2012-05-10 Thread Jürgen Lind
Since no further replies to this issue came up, the question remains whether this is works as design or a bug. Should I file an issue on this? And could maybe one of the developers explain why the Component#isEnabledInhierarchy is final? After reading some core code, I would guess that maybe

Re: Force child component enabled

2012-05-10 Thread Martin Grigorov
Hi, I'd say that it is by design. Component#canCallListenerInterface(Method) has been added recently because a user wanted its image to be shown in a disabled panel. File a ticket with a quickstart with the code from your earlier mail and I'll try to find what is the problem. On Thu, May 10,

Re: Force child component enabled

2012-05-10 Thread Jürgen Lind
Hi Martin, I have created a quickstart and filed an issue (WICKET-4551). Thank you for your help. J. On 10.05.2012 10:17, Martin Grigorov wrote: Hi, I'd say that it is by design. Component#canCallListenerInterface(Method) has been added recently because a user wanted its image to be shown

Force child component enabled

2012-05-09 Thread Jürgen Lind
Hi, I have a little problem in my application and maybe someone has an idea how to solve it: I have a complex form that is structured using a custom collapsible AJAX-panel to show/hide certain parts of the form. Now, if a user does not have the write permission for the form, the form is

Re: Force child component enabled

2012-05-09 Thread Martin Grigorov
Hi, Why don't use plain Javascript for this. It will be faster because it wont make roundtrip to the server and wont be disabled as a Wicket component ? On Wed, May 9, 2012 at 12:06 PM, Jürgen Lind juergen.l...@iteratec.de wrote: Hi, I have a little problem in my application and maybe someone

Re: Force child component enabled

2012-05-09 Thread Alexander Cherednichenko
Hi! I'd make this case more general -- we have faced the one like this in non-JS-case. For instance, there is a Panel which contains a DataTable. Each row of datatable represents a Document. Each row contains a set of buttons - Edit Confirm and Download. When panel is hidden due to security

Re: Force child component enabled

2012-05-09 Thread Jürgen Lind
Hi Martin, that was my initial approach. However, I would like the collapsible panels to keep their state between form submits, therefore I would need some sort of Javascript state management or I would simply use ajax links for that purpose. Which is what I would prefer... A later post

Re: Force child component enabled

2012-05-09 Thread Martin Grigorov
Hi, I think it is possible to do that for links. You'll need to override org.apache.wicket.markup.html.link.AbstractLink#isLinkEnabled() and org.apache.wicket.Component#canCallListenerInterface(Method) The first is needed to not render the link as disabled. The second is needed to be able to

Re: Force child component enabled

2012-05-09 Thread Jürgen Lind
Hi Martin, thanks for the hint, unfortunatly, it does not work :-( I've been looking through the relevant code and the approach seems right, however at some point, the returned values seem to be ignored and the link is still disabled (i.e. the onclick-handler is not rendered)... I will have

Re: Force child component enabled

2012-05-09 Thread Jürgen Lind
Ok, I stripped down everything to a very basic setup that should work according to Martins suggestions and the wicket documentation. Any ideas why canCallListenerInterface is never called here? J. import java.lang.reflect.Method; import org.apache.wicket.ajax.AjaxRequestTarget; import