Did a quick search and couldn't see anything so ticket raised:
https://issues.apache.org/jira/browse/WICKET-4146 WICKET-4146
-
Eric is learning how to use Wicket and enjoying the experience so far...
--
View this message in context:
Martin Grigorov-4 wrote:
What do you think?
I think this problem deserves a ticket to be discussed in more details.
I'd like to see this resolved for the dynamic image case. Example use case:
1. I have a form that I'd like to re-use between two roles - Admin and
Read-only User. That is,
On Tue, Oct 4, 2011 at 5:08 AM, cellis christopher.el...@uwa.edu.au wrote:
ok, so its the parent.isEnabledInHierarchy that's forcing the
RequestListenerInterface - component not enabled or visible; ignoring
call.
Any chance I could override that somehow, or should I/we refactor our design
On Tue, 4 Oct 2011 10:41:27 +0200
Martin Grigorov mgrigo...@apache.org wrote:
RequestListenerInterface stops the execution of callbacks for disabled
and/or invisible components/behaviors but its seems it also forbids
requesting a resource ...
I think this is a not-so-easy problem, actually.
On Tue, Oct 4, 2011 at 10:55 AM, Carl-Eric Menzel cmen...@wicketbuch.de wrote:
On Tue, 4 Oct 2011 10:41:27 +0200
Martin Grigorov mgrigo...@apache.org wrote:
RequestListenerInterface stops the execution of callbacks for disabled
and/or invisible components/behaviors but its seems it also
On Tue, 4 Oct 2011 10:59:53 +0200
Martin Grigorov mgrigo...@apache.org wrote:
I think this is a not-so-easy problem, actually. In this use case
(render an image) it seems obvious that even though the whole panel
is disabled, it is being rendered, so the image resource should
work.
Define
On Tue, Oct 4, 2011 at 4:08 PM, Carl-Eric Menzel cmen...@wicketbuch.de wrote:
On Tue, 4 Oct 2011 10:59:53 +0200
Martin Grigorov mgrigo...@apache.org wrote:
I think this is a not-so-easy problem, actually. In this use case
(render an image) it seems obvious that even though the whole panel
Thanks for the feedback/answers guys.
I can see both the pros and cons as you've mentioned and agree with both
(dammit!).
I've resorted to not show the image at all now (not entirely needed anyway)
as it was in fact a small image (100kb) that was stored in the database,
and returned via a
ok, so its the parent.isEnabledInHierarchy that's forcing the
RequestListenerInterface - component not enabled or visible; ignoring
call.
Any chance I could override that somehow, or should I/we refactor our design
to not have view/edit forms (groan)
--
View this message in context:
