Hi,
You are right, this is a wicket 6 feature...
However, I have ported the mechanism into the wicket 1.5 version; just
replace this.setJavaScriptLibrarySettings(settings); by
ApplicationJavaScriptLibrarySettings.set(settings);
Thanks best regards,
Sebastien.
On Fri, Dec 20, 2013 at 7:48 AM,
I’m trying to use wicket-auth-roles (in Wicket 1.5.9) to make a component that
is enabled only for logged-in users. In my case if you’re not logged in, you
have only a role called GUEST. If you are logged in you have a role called
STUDENT (and also GUEST, since everything guests can do,
AnnotationsRoleAuthorizationStrategy#check() looks good to me.
Can you debug what's happening there in your case?
Sven
On 12/20/2013 01:53 PM, Boris Goldowsky wrote:
I’m trying to use wicket-auth-roles (in Wicket 1.5.9) to make a component that
is enabled only for logged-in users. In my
Martin Grigorov-4 wrote
.wicket-modal .w_close { display: none }
You may make this CSS rule even more specific because it will affect all
modal windows when it is applied.
I managed to implement this. However, the close (x) button is still there.
So the user may click it if he knows it is
You can remove it with Javascript.
$(.wicket-modal .w_close).remove() or something similar
Martin Grigorov
Wicket Training and Consulting
On Fri, Dec 20, 2013 at 4:18 PM, J.K. Baltzersen jornb...@pvv.org wrote:
Martin Grigorov-4 wrote
.wicket-modal .w_close { display: none }
You may
One oddity with AnnotationsRoleAuthorizationStrategy#check() is that specifying
deny = {} actually denies everyone (since
AbstractRoleAuthorizationStrategy.hasAny(roles) returns true for the empty list
of roles). But people might be depending on that behavior, so it would be hard
to recommend
Hi, Does anyone have some insight on this?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/AjaxLazyLoadPanel-in-wicket-6-tp4663083p4663163.html
Sent from the Users forum mailing list archive at Nabble.com.
I should have checked JIRA first. It looks like this was fixed, but only for
wicket 6, under this issue:
https://issues.apache.org/jira/browse/WICKET-3974
Boris
On Dec 20, 2013, at 8:17 AM, Sven Meier s...@meiers.net wrote:
AnnotationsRoleAuthorizationStrategy#check() looks good to me.
Is it possible to create a form submission that hits a specific URL and
doesn't modify the original URL displayed in the browser.
e.g. I have a single simple Page, that has a StatelessForm on it. I hit
this via http://localhost:8080/
When I hit the form submit button, the URL in the browser
