Try overriding isVersioned (of you page, though it works on components
as well) and let it return false.
Eelco
On 4/27/07, jamieballing [EMAIL PROTECTED] wrote:
We are experiencing a problem in our application because we are doing
something out of the ordinary.
We have an applet on our
This is wrong. Even if page version increments, the ajax links should
be valid. There was a bug in wicket 1.3 where the wicket still allowed
you to do unversioned ajax requests, but that's should be gone
already. Can you please test it with most recent 1.3?
-Matej
On 4/27/07, jamieballing [EMAIL
Hello everybody,
I just updated my application from Wicket 1.2.5 to 1.2.6. The update
broke one of my pages, which had a rather special requirement: it
needed to use my own implementation of HtmlBodyContainer. The way I
did it was like this:
public EmailPage()
{
you can most likely move that code to page.onattach() and do
Component body=get(BodyOnLoadHandler.BODY_ID);
if (body!=null) {
if (!(body instanceof MyHtmlBodyContainer)) {
remove(BodyOnLoadHandler.BODY_ID);
body=null;
}
}
if (body==null) {
add(new ...);
}
-igor
On
I will not stay here. There was no fiddling around once the Rodger Young
stopped braking.
He addressed himself to the doctor, but was replying to me. InWindow Simple
Playback in a Window.
Find out about Packaging Recommendations. Good relative - a dead relative.
She stood upright, her prominent
Wicket supports nested forms. The inner form tags are replaced with
span elements. This is a component framework, where you expect forms
to be able to be nested (form on a reusable panel anyone?).
I'm just starting to work on a similar thing: an address form panel to
be used in other forms.
One note: this is a 1.3 feature so only expect it to work there.
What happens with the nested forms is that the buttons stay, and iirc
only the inner form is submitted when a button is pressed inside that
inner form.
I think the discussion never got to a conclusion on what happens when
the outer
imho all he should do is extend a panel, and make sure that panel is always
inside a form.
there is no need to have a form to group a few fields together.
-igor
On 4/29/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
One note: this is a 1.3 feature so only expect it to work there.
What
Hello Igor,
thanks for your help, it was a very close hit :) I actually had to put
the code into internalOnttatch like this:
protected void internalOnAttach() {
super.internalOnAttach();
Component body=get(BodyOnLoadHandler.BODY_ID);
if (body!=null) {
if (!(body instanceof
well if you look at the code, the way it works is: only do it if it hasnt
been done already. so this code only does anything on the first attach, then
it becomes a noop.
-igor
On 4/29/07, Rüdiger Schulz [EMAIL PROTECTED] wrote:
Hello Igor,
thanks for your help, it was a very close hit :) I
Ah, you're right :) Here is the check I didn't consider:
if (bodyContainer == null) {
...
}
2007/4/29, Igor Vaynberg [EMAIL PROTECTED]:
well if you look at the code, the way it works is: only do it if it hasnt
been done already. so this code only does anything on the first attach, then
it
neato. i did not know that. i vaguely recall doing this once
and i recall being really suprised it worked. now i know why! ;-)
Martijn Dashorst wrote:
On 4/27/07, jan_bar [EMAIL PROTECTED] wrote:
I think that you cannot nest form in HTML. You have to nest them with
CSS. This will also
well, it depends on what kind of reuse you want. if you have a particularly
cool form panel, it might be something that should stand on its own or nest.
but i think you're probably right in general. i've got quite a few panels
that just hold some fields for inclusion in a form.
igor.vaynberg
Hi,
It appears that the javascript this object is different when I
hardcode the javascript into the html vs. using an AjaxEventBehavior
and appendJavascript. For instance, the this in this refers to the
TR which is correct and the selectRow functions works properly:
tr
Hi,
It appears that the javascript this object is different when I
hardcode the javascript into the html vs. using an AjaxEventBehavior
and appendJavascript. For instance, the this in this refers to the
TR which is correct and the selectRow functions works properly:
tr
Hi,
I have added a rounded corners border component to wicket-minis jira.
Anyone who might need it/or want to contribute/suggest styles for
it/suggest more styled borders can have a look .
http://wicketstuff.org/jira/browse/WSMINIS-2
hi all,
i'm just starting with wicket and have a simple search
form, that leads to a SearchResultsPage.
the SearchResultsPage is mounted as a bookmarkable page (via
mountBookmarkablePage(/search, SearchResultsPage.class);),
although the url that is shown then contains s.th. like
no, once the form is submitted the page is no longer bookmarkable and so it
will lose any bookmarkable/mounted url.
if you want to keep it you can call setresponsepage(page.class, params) in
onsubmit(), but in your case that is silly since searchresultspage probably
contains the submitted form
On Sun, 2007-04-29 at 17:41 -0700, Igor Vaynberg wrote:
no, once the form is submitted the page is no longer bookmarkable and
so it will lose any bookmarkable/mounted url.
if you want to keep it you can call setresponsepage(page.class,
params) in onsubmit(), but in your case that is silly
in reality this isnt how its supposed to work.
usually you would have something like this:
searchpage {
private criteria crit;
searchpage() {
add(new searchform(form, new PropertyModel(this, crit));
add(new resultsview(view, new PropertyModel(this, crit));
}
}
that way the form
Sure thing, more than happy :) thanks
Josh
On 4/27/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
David and Thomas, you're both in. Make something beautiful :)
And Josh, thanks for your previous effort. Hope you don't mind this,
and you like anyone else are most welcome to help with the it.
Hi all, just want to say that I've relatively new to Wicket but am loving
every minute of it! In just a few weeks of learning and programming I have
been able to create a robust, javascripted, ajaxified app for our company.
Great work to the devs!
However, I have one problem which I'm a
I found the problem.
It turned out to be a very silly deployment error.
We had the same application running at two different
contexts.
Inside our code we had some static url mappings to one of the
contexts. This lead the the user being switched between the urls,
and hence different sessions.
We are currently using the incubating-beta1 release. I was stepping through
the source in a debugger and I'm not sure older versions of the page are
preserved in the cache (at least when update by an ajax request). I did a
simple test:
* I went to a versioned page
* clicked an ajax control which
24 matches
Mail list logo
