Hi,
I have a bunch of stateless pages, each calling setStatelessHint(true) in
the constructor to indicate this. I've now noticed that when one of these
pages calls setResponsePage, the target page is always considered
stateful, since RequestCycle#setResponsePage explicitly resets the hint.
Why is
Hi,
Because you pass an instance of a page and this instance to be
reachable in the next request should be stored.
Use setResponsePage(Class) instead. Your page is stateless, so
instantiating a completely new instance in the next request should be
the same.
On Mon, Sep 3, 2012 at 9:19 AM, Gereon
Hi
In my opinion the main advantage of the jqwicket over
wiquery/wicket-jquery-ui is the impressive list of jquery plugins (ui
components). See http://code.google.com/p/jqwicket/w/list for more details.
Of course, it's not difficult to accommodate these jquery components with
wiquery/wicket-jquery
Hi,
For wiquery there is project
http://code.google.com/p/wiquery-plugins/
which contains integrations with several plugins. A fraction of them can be
seen in action at
http://antiliasoft.com/wiquery-plugins/
Plugins are Wicket 1.4.x based but migrating them to 1.5.X and 6.0. should
be in most
Hi,
Yes, wicket-jquery-ui has been designed to allow the (easy?) implementation
of plugins.
I am little bit late on finishing writing the how-tos to implement the
plugins (the advanced part) but to begin, you already have the 2 first
parts:
http://code.google.com/p/wicket-jquery-ui/wiki/HowToCrea
Hi,
#error() method and others (info, success, ...) accept Serializable,
so you can even do: error(new ExternalLink("someId", someUrl))
Then you need to extend FeedbackPanel and its
org.apache.wicket.markup.html.panel.FeedbackPanel#newMessageDisplayComponent()
and return directly the link.
On Mon
hi,
Thanks for replying. If i use External link i have to provide wicket:id
in corresponding html page..The error message comes dynamically based on
the condition.At that time, we get exception that is missing...
On Mon, Sep 3, 2012 at 3:24 PM, Martin Grigorov-4 [via Apache Wicket] <
ml-node+s
See FeedbackPanel.java, it passes "message" as component id
(newMessageDisplayComponent("message", message);)
Passing a Component to error() maybe is a bad example. The idea is
that you can pass any Serializable, even a Component.
Pass your own Object and then in #newMessageDisplayComponent()
depe
hi,
How can i manipulate the wicket id ? because the error message comes
dynamically if condition is true.. thenonly the external link will be
executed..but what to do in the case of condition fails?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/How-to-create-th
I didnt get u exactly.. can you please provide me some sample example
My problem is basically, i have to generate the link in the error message
it self when the condition is true.
i want like this error("please * contact admin *");
if i click the link , it navigates to another page. (onclic
class Error implements Serializable {
String msg;
String url;
}
class MyFeedbackPanel() {
@Override protected Component newMessageDisplayComponent(String id,
FeedbackMessage fm) {
Serializable ser = fm.getMessage();
if (ser instanceof Error) {
Error err = ser;
return new
Thank you Martin. I have created an issue, looking forward for a fix.
https://issues.apache.org/jira/browse/WICKET-4742
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-6-and-Atmosphere-framework-integration-tp4651637p4651714.html
Sent from the Users forum m
Hi,
I have implemented authentication on my Wicket Pages by them extending a
Base Class that checks the session.
Those pages also add Panels and Ajax components. Its been really long but I
have forgotten if how Ajax requests works with sessions.
Also, I want to intercept it and re-direct it to a
Hi,
On Mon, Sep 3, 2012 at 3:33 PM, Arjun Dhar wrote:
> Hi,
> I have implemented authentication on my Wicket Pages by them extending a
> Base Class that checks the session.
Where exactly is this check ?
Do you use IAuthorizationStrategy ? Check it. This is what you need.
>
> Those pages also
Yess!
I found the an implementation of IAuthorizationStrategy and in the Site
Application I do:
getSecuritySettings().setAuthorizationStrategy(authStrategy);
I built an Annotation, where all pages using that annotation are mapped to
the Authorization Strategy. Its all come back on that front than
On Mon, Sep 3, 2012 at 4:27 PM, Arjun Dhar wrote:
> Yess!
>
> I found the an implementation of IAuthorizationStrategy and in the Site
> Application I do:
> getSecuritySettings().setAuthorizationStrategy(authStrategy);
>
> I built an Annotation, where all pages using that annotation are mapped to
>
Hi! I have a custom exception handler, and I have this method:
onException(RequestCycle cycle, Exception anException) {
}
Inside this method, how can I get the original page who caused the
exception? in other Wicket version, I had "onRuntimeException"
method, who already had the original
Hi,
See
https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/request/cycle/PageRequestHandlerTracker.java
Register it, then use it:
PageRequestHandlerTracker.getLastHandler(cycle).getPage()
On Mon, Sep 3, 2012 at 8:00 PM, Alfonso Quiroga wrote:
> Hi! I have
Hi,
exceptions are usually thrown with a reason - and the main reason why you
get so much in your log is that brix with wicket 6 isnt yet finished.
Especially the url-sharing part between brix and wicket is quite a problem
as brix relies on "full control" of the space while wickt 5 + 6 introduc
Hello,
I finally decided to bite the bullet and migrate to Wicket 1.5. It
turned out a lot harder than I expected. Here are some of the issues I
ran into:
* How to implement HybridUrlCodingStrategy in 1.5?
* I saw a ticket related to putClassAlias, but I couldn't figure out
how to port this one
BTW this code is on Wicket 1.4 (just FYI)
There seems to be a slight complication when protecting components in a
hierarchy.
I have protected some pages/Web-Components by marking them as protected via
Annotation / Marker Interfaces. In the following code of an impl of
IAuthorizationStrategy, the
Also ensure you're using an input tag with type="submit" instead of a button
tag.
IE has several issues handling the button tag.
Thanks,
-David Phillips
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Saturday, September 01, 2012 12:43 AM
To: users@wicket.a
Take a look at the migration guide, this will answer some (if not all) of your
questions:
https://cwiki.apache.org/WICKET/migration-to-wicket-15.html
-Tom
On 04.09.2012, at 02:36, Alec Swan wrote:
> Hello,
>
> I finally decided to bite the bullet and migrate to Wicket 1.5. It
> turned out
23 matches
Mail list logo