On 1/11/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
Imo, it would be intuitive to keep the order in which they were added.
Unless there is some urgent reason why the ajax engine should want to
give components priority over others
+1
thats a weird error because looking at the stacktrace you go through
WicketServlet.doGet()
and this is done there:
// First, set the webapplication for this thread
Application.set(webApplication);
So i have no idea how that then can suddenly be null again.
Please set a breakpoint
To my presentation im doing both a jsp version and a wicket version of a very
small applikation (might just be a form or two separate pages with forms), btw
would it be an idea to put the presentation with examples up somewhere perhaps
the wiki (when im done with it?)?
However upon doing
Oeh btw this is wicket 1.2.3
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nino Wael
Sent: 12. januar 2007 13:27
To: wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] wicket presentation
To my presentation im doing both a jsp
Hi I
Get an error when the page are calling this line, on my html :
body onunload=deleteWicketCookie('pm-null/jobindsatsViewerComponentServlet');
I think I know why it's failing, it's because the browser does not allow cookie
and therefore the cookie cant be deleted.. What can I do
Hi Igor,
thanks for the hint. This works perfect! I still don't no why it works with
the SubmitBehavior, because in my eyes it actually is a change and therefore
an update and not a submit, but thanks again. Can I use the same thing for
Input validation on an inputfield or something similar?
This is running wicket 1.2 btw, I'll try to remember version numbers in the
original mails from now on.
Regards Nino
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nino Wael
Sent: 12. januar 2007 13:50
To: wicket-user@lists.sourceforge.net
thats really old...
those cookies are not used anymore thats now done based on the window name.
johan
On 1/12/07, Nino Wael [EMAIL PROTECTED] wrote:
This is running wicket 1.2 btw, I'll try to remember version numbers in
the original mails from now on.
Regards Nino
Frank Bille wrote:
On 1/11/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
Imo, it would be intuitive to keep the order in which they were added.
Unless there is some urgent reason why the ajax engine should want to
give components priority over others
+1
Igor's suggestion worked (that is,
It is difficult to explain but the functionality is simple.
You got a field to search. and a link to make advanced search. When making
an advance search, we want to open a pop-up window to get more searching
functionality. When the search is done, we display a list of item
corresponding to this
Oh, and thanks in advance if there is an answer to that!
Marc
On 1/12/07, Marc-Andre Houle [EMAIL PROTECTED] wrote:
It is difficult to explain but the functionality is simple.
You got a field to search. and a link to make advanced search. When
making an advance search, we want to open a
there is an example in wicket-examples/ajax that shows ajaxified form
validation
-igor
On 1/12/07, Cliff Pereira [EMAIL PROTECTED] wrote:
Hi Igor,
thanks for the hint. This works perfect! I still don't no why it works
with the SubmitBehavior, because in my eyes it actually is a change and
in 1.2 it was used through, just upgrade to 1.2.4
-igor
On 1/12/07, Johan Compagner [EMAIL PROTECTED] wrote:
thats really old...
those cookies are not used anymore thats now done based on the window
name.
johan
On 1/12/07, Nino Wael [EMAIL PROTECTED] wrote:
This is running wicket 1.2
there is no way to communicate between windows in the http spec, so what you
have to do is this:
when you create the popup, you have to add a parameter to the generated url
- and that should be the pagename of the page that is opening the popup.
wicket sets window.name=pagemapname, and if you
Hi all,
I just found a bug (?) about AjaxFormSubmitBehavior when doing some
browser back botton, like:
(1) X page has a Form and use AjaxFormSubmitBehavior
(2) navigate X to Y by a link
(3) browser back to X
(4) submit form of X by AjaxFormSubmitBehavior
(5) then:
*INFO: *
*INFO: *
Now, my popup code look like this :
String parentPageMap = wicket:default;
if(pp != null)
{
parentPageMap = (String)pp.get (parent_page_map);
}
Class pageClass = PagingFactory.getInstance ().getPageClass (
NodeTypeConstants.RULE);
add(new
you are not adding the target attribute to the link which is what is
supposed to redirect the link to the other window
String pagemapnameparam=.;
String
pagemapname=(wicket:default.equals(pagemapnameparam))?null:pagemapnameparam;
PageMap pagemap=PageMap.forName(pagemapname);
BPL link=new
In fact, since r462394, bookmarkablepagelinks automatically add an
attribute modifier to set the target when you set the page map (if it
is not null) on that link.
Eelco
On 1/12/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
you are not adding the target attribute to the link which is what is
neat!
is that in 2.0 or 1.x also?
-igor
On 1/12/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
In fact, since r462394, bookmarkablepagelinks automatically add an
attribute modifier to set the target when you set the page map (if it
is not null) on that link.
Eelco
On 1/12/07, Igor Vaynberg
both.
Eelco
On 1/12/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
neat!
is that in 2.0 or 1.x also?
-igor
On 1/12/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
In fact, since r462394, bookmarkablepagelinks automatically add an
attribute modifier to set the target when you set the page
Hi, I using an AjaxFallbackDefaultDataTable to show some data. I also need
to captura the event onclick on a row and lunch an ajax code. The html
code is the following:
div
span wicket:id=tableTitle[title]/span
table class=dataview cellspacing=0
wicket:id=table[table]/table
/div
try overriding newrowitem() on the datatable and adding an ajax onclick
behavior to the item returned by calling super
-igor
On 1/12/07, Gustavo Yoshizaki [EMAIL PROTECTED] wrote:
Hi, I using an AjaxFallbackDefaultDataTable to show some data. I also need
to captura the event onclick on a row
This is weird. Can you please check if there is no exception in the log?
-Matej
Ingram Chen wrote:
Hi all,
I just found a bug (?) about AjaxFormSubmitBehavior when doing some
browser back botton, like:
(1) X page has a Form and use AjaxFormSubmitBehavior
(2) navigate X to Y by a
WicketMessage: Error attaching this container for rendering: [Page
class = packedge.EditPage, id = 9]
Root cause:
java.lang.IllegalStateException: wicket.Component has not been
properly attached. Something in the hierarchy of
wicket.extensions.ajax.markup.html.modal.ModalWindow has not called
extensions has been aligned with wicket refactorings, so it looks like you
got a new wicket jar, but not a new extensions jar. update your extensions.
-igor
On 1/12/07, Otan [EMAIL PROTECTED] wrote:
WicketMessage: Error attaching this container for rendering: [Page class =
Thank you much.
igor.vaynberg wrote:
fixed
-igor
On 1/8/07, De Soca [EMAIL PROTECTED] wrote:
Hello,
I receive the following error when attempting to run an app with the
AjaxFallbackDefaultDataTable in 2.0. Replacing that component with the
non-Ajax version DefaultDataTable,
I turn on log4j.logger.wicket=DEBUG and only see one message:
DEBUG - Session- wicket.Session=updateSession():
Attaching session to PageMap [PageMap name=null, access=[[Access id=0,
version=0], [Access id=1, version=0], [Access id=2, version=0]]]
and no exception. It doesn't
27 matches
Mail list logo
