Thanks Nino,
That is exactly what I was looking for.
On Fri, Jun 20, 2008 at 10:03 AM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
Theres also an unsecure way of doing it, namely this(from
applicationclass):
@Override
protected ISessionStore newSessionStore() {
AjaxFormValidatingBehavior extends AjaxFormSubmitBehavior. I do not
need the feedback update, so I tried AjaxFormSubmitBehavior.
The problem is that AjaxFormSubmitBehavior actually submits the form
(executes my form.onSubmit which actually tries to save the form when
still incomplete!!).
I can
Hopefully a simple problem for the group... What's the best way to be
notified when the application transitions from one page to another?
Does the application object receive any Wicket messages like
onPageTransition() or anything like that?
I ask because--in my application--when the user
Hi,
I am using DojoDropContainer from org.wicketstuff.dojo
The Conatainer is adding debug messages to the page.
How can I remove these messages?
this is the message:
DEBUG: DEPRECATED: dojo.widget.Manager.getImplementationName Could not
locate widget implementation for panel in wicket.widget
I see this in IE7 but not in FF
On Sun, Jun 22, 2008 at 10:35 AM, Eyal Golan [EMAIL PROTECTED] wrote:
Hi,
I am using DojoDropContainer from org.wicketstuff.dojo
The Conatainer is adding debug messages to the page.
How can I remove these messages?
this is the message:
DEBUG: DEPRECATED:
Hi,
I am trying to create a way that the Wicket application will remember the
user that was logged in.
(like gmail remembers my id when I go to it if I didn't log out).
I am using cookies for that.
In the Login page I have this:
*Cookie idCookie =
OK. Regarding the NULL thing, I added this:
Cookie userIdCookie = new
Cookie(EurekifyWebApplication.COOKIE_LOGIN_ID, userId);
userIdCookie.setMaxAge((int) Duration.days(30).seconds());
and then:
getWebRequestCycle().getWebResponse().addCookie(userIdCookie);
What about the
Take a look at how CookieValuePersister does it, basically the same as
you. you can use it by calling setPersistent(true) on a formcomponent.
Maurice
On Sun, Jun 22, 2008 at 12:52 PM, Eyal Golan [EMAIL PROTECTED] wrote:
OK. Regarding the NULL thing, I added this:
Cookie userIdCookie
Thanks Maurice,
I looked into the source and it is actually almost the same.
Unfortunately I can't use it. Mostly because I want to persist my password
field.
Also, When I load I want the cookie with me.
The Cookie Persister returns void for that.
It would be nice if load and save will return
since you are the one performing the transition from A to B you can
commit yourself, no?
-igor
On Sun, Jun 22, 2008 at 12:02 AM, Justin Morgan - Logic Sector
[EMAIL PROTECTED] wrote:
Hopefully a simple problem for the group... What's the best way to be
notified when the application
Hi,
as far as I noticed, Wicket first writes the code fragments of wicket:head
into the page and then the parts provided by the HeaderContributors. Is there
a way of changing that ordering? The background is that I want to load a
javascript library with a HeaderContributor and then use that
if we switch the ordering then someone else will complain :)
maybe they add a javascript library via wickethead and have a
contributor spitting out some dynamic javascript.
point is its a bad idea to depend on the ordering, whichever way it
currently is.
-igor
On Sun, Jun 22, 2008 at 9:52 AM,
Ok,
I understand your point and perhaps my whole setup is wrong. Here is my line
of thinking:
1. I have a component that needs some Javascript.
2. The Javascript relies on an external library.
3. There may be several instances of the component on the page.
4. Other components on the page may
Hi all,
I'm quite new to Wicket and I'd like to ask whether what I'm doing is
right. Say I have two pages A and B. Page A loads a list of information
from the database and keeps it in an instance field. When a link on page
A is clicked, a new page B is created and page A passes itself as one
Thanks for your response, but what do I do in case the case of the
error page, for example? I'm not performing the transition myself in
that case (but I still need to do a rollback).
Plus, there are a lot of ways to go from page to page. It seems a
pain to add commit code to every link
So, have your link/form logic actually call some other object's
method. Then, make that method transactional and use something like
Spring to manage your transaction demarcation.
On Sun, Jun 22, 2008 at 2:11 PM, Justin Morgan - Logic Sector
[EMAIL PROTECTED] wrote:
Thanks for your response,
This is the way we do it.
But I'll leave the expert respond to that :)
On Sun, Jun 22, 2008 at 8:53 PM, Serkan Camurcuoglu [EMAIL PROTECTED]
wrote:
Hi all,
I'm quite new to Wicket and I'd like to ask whether what I'm doing is
right. Say I have two pages A and B. Page A loads a list of
Calling setResponsePage(Page a) increases your session size by the size of a
serialized version of 'a'. If 'a' has a List of data that 'a' is going to
display, that size may be non-trivial. As long as you're okay with that,
it's fine... but I wouldn't recommend doing that unless there's a good
On Sun, Jun 22, 2008 at 12:03 PM, brian.diekelman [EMAIL PROTECTED] wrote:
Passing a Page instance to the constructor of another Page doesn't sound
right to me. Again, it depends on what you're trying to do, but I haven't
seen many instances where passing an instance of 'Page a' versus an
How about this option?
In page A:
add(new Link(linkToB) {
public void onClick() {
B other = new B(...);
other.setBackPage(A.this);
setResponsePage(other);
}
}
On Sun, Jun 22, 2008 at 8:53 PM, Serkan Camurcuoglu [EMAIL PROTECTED]
wrote:
Hi all,
I'm quite new to Wicket and I'd
Form has setOutputMarkupId(true) in the constructor.
On Tue, Jun 3, 2008 at 2:55 PM, jd17 [EMAIL PROTECTED] wrote:
Thanks and sorry to have bothered you. I will take a closer look and see
what
I overlooked in my code. I started migrating last tuesday and everything is
up and running, there
Hello ,
I created a new issue containing the codes : WICKET-1712
https://issues.apache.org/jira/browse/WICKET-1712
Thanks.
2008/6/22 Maurice Marrink [EMAIL PROTECTED]:
Sounds Like a bug.
Could you open up a jira request please and attach a quickstart
showing this behavior.
Thanks.
Ok, I got your point.. It's ok to reference pages from one another but
I'd rather focus on attaching/detaching and the amount of data I keep in
my models.. Thanks very much for the clarification..
Igor Vaynberg wrote:
On Sun, Jun 22, 2008 at 12:03 PM, brian.diekelman [EMAIL PROTECTED] wrote:
On Sat, 21 Jun 2008, Martin Makundi wrote:
The problem is, that even though I re-use the textField, it does not
know its convertedInput (probably because the form has not actually
been submitted?) and it resets itself to its original state. I would
like it to keep its state as it was when the
Something like:
ThisComponent.html:
wicket:panel
script wicket:id=script void(); /script
/wicket:panel
ThisComponent.java:
//..
final PackagedTextTemplate template = new
PackagedTextTemplate(ThisComponent.class, ThisComponent.js.template);
Label script = new Label(script, new Model() {
All,
I'm playing with the signin example over at wicketstuff, trying to get
familiar with Wicket, and am having a bit of an issue I'm sure is
something very obvious I'm missing.
The problem I am having is that after I authenticate using the
extended SignInPage, it is taking me to:
The problem is, that even though I re-use the textField, it does not
know its convertedInput (probably because the form has not actually
been submitted?) and it resets itself to its original state. I would
like it to keep its state as it was when the new dropdown value was
selected.
Have
you can put the javascript that uses your library into window's onload
or ondomready event, so it will be executed later. wicket-event.js and
WicketEventReference class make it easy.
another approach is to simply output the javascript that uses the lib
via a headercontributor as well. there is a
28 matches
Mail list logo
