There is a simple answer for your question: You can't.
It's due to how wicket works. Since Wicket manages your application
state and takes care of the urls for you, you can't alter them
significantly.
If you need tabbed panel like functionality while having nice urls, you
have to have
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag
von Matej Knopp
Gesendet: Dienstag, 10. Oktober 2006 13:49
An: wicket-user@lists.sourceforge.net
Betreff: Re: [Wicket-user] NiceURL and PagingNavigator
There is a simple answer for your question: You can't.
It's due to how wicket works
Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von
Matej Knopp
Gesendet: Dienstag, 10. Oktober 2006 13:49
An: wicket-user@lists.sourceforge.net
Betreff: Re: [Wicket-user] NiceURL and PagingNavigator
There is a simple answer for your question: You can't.
It's due
Anyway, there were couple of fixes concerning partial refresh of tree,
you might consider trying a current snapshot of 1.2.
-Matej
Marc-Andre Houle wrote:
The click is made on an object of the ajax tree and it is an ajax call.
Setting versionning to false work, only if it is set to the
What does it mean just refresh and completely update the page?
Your problem can that you do the loading of items in constructor. The
constructor is called only once in the page lifecycle. However, the page
life spans over multiple request. So even if you reload the page, you
can still be
Marc-Andre Houle wrote:
It is a matter of interogation I have and not directly related to a problem.
While trying to find a good solution about the problem described there
http://www.nabble.com/Refreshing-problem-with-ajax-component-tf2388856.html
, I begin to try to figure what is happening
Why don't put the images next to css files and have them attached to
page using css? (background-image can do lot of nice things).
This way you don't have to care about image resources at all.
-Matej
Philip A. Chapman wrote:
Everyone,
I have several intranet sites that I am working on.
constructor like this:
add(HeaderContributor.forCss(new
PackageResourceReference(BasePage.class, theme.css)));
Thanks!
On Mon, 2006-10-09 at 18:03 +0200, Matej Knopp wrote:
Why don't put the images next to css files and have them attached to
page using css? (background-image can do lot of nice
another ajax page, I get the null target
exception. So I cannot test the datepicker on the other pages.
Pierre-Yves
Matej Knopp a écrit :
This is very unfortunate. I'm not able to reproduce the stack overflow
problem even with huge ajax responses.
Can you plese replace the processNext
Your problem is that you create label with constant modal, that is set
to the value of currentItem.getName. So even if you change current item
later, the item container is not recreated, thus the label still shows
old current item name.
The solution would be to create the label like this
response that contains the
datepicker, this alert is displayed 10 times with values 0 to 9.
Pierre-Yves
Matej Knopp a écrit :
That's not really the problem. The javascript _is_ included only once.
Problem is the performance improvement I did, calling the run method
from call stack instead
Dear Wicket users,
we have launched a company that provides consultation, support and
training for Wicket. For more information visit
http://www.wicket-support.com.
We are looking forward to help you with this amazing framework in any
way you need.
Kind regards,
Matej Knopp, Wicket Support
But it should. I don't see reason why this wouldn't work? If I recall
correctly it worked for me.
-Matej
Leszek Gawron wrote:
Eelco Hillenius wrote:
I just wanted to share another way of injecting spring services into
wicket code. This one uses AOP.
- o - Why another approach?
was looking for the calendar.js
file, and not for wicket-ajax.js). It doesn't change anything. I still
have a too much recursion error at line 1796 of calendar.js
Pierre-Yves
Matej Knopp a ?crit :
I assume there's something wrong with your svn setup. The revision of
wicket-ajax.js in svn
() != this.getMonth())
this.setDate(28);
this.__msh_oldSetFullYear(y);
};
If I reload the page, the error disapears.
Pierre-Yves
Matej Knopp a ?crit :
Thanks for fixed files, I've already commited those.
-Matej
Pierre-Yves Saumont wrote:
Now it seems to work fine provided
Hi,
it should be fixed in SVN, but I can't really test it. I've simulated
updating of many elements so that I could reproduce the stack overflow,
but I don't know if that is your case.
please try the current version and let me know.
-Matej
Matej Knopp wrote:
Sorry for this, I've
I think the attribute could be prepended, why not?
-Matej
samyem wrote:
Any thoughts on this message?
samyem wrote:
If we have tags with wicket:id, the SRC and HREF attributes does not
prepend context path, but it does for simple tags. Is there a reason why
it is done this way (in
(AjaxRequestTarget.java:474)
However, having it working with full page reload is a very good point. I
think it will be enough
Pierre-Yves
Matej Knopp a écrit :
You won't find it there. It's wicket-1.x (and trunk).
1.2.2 is release. Current branch for 1.2 is under 1.x
-Matej
Hi,
I'm working on the date picker encoding problem. What I'll probably do
is to convert all non-unicode (latin1, ...) date picker locale strings
to utf-8 and add charset=utf-8 to the script element that includes
the script.
This should sove the problem, as xmlhttprequest (used to load script
script, and even an error
in the abreviated day names (it says monday, tuesday, tuesday, thursday
and there is no wednesday!). Do you want me to send you an edited file?
Pierre-Yves
Matej Knopp a écrit :
Hi,
I'm working on the date picker encoding problem. What I'll probably do
and there is no wednesday!). Do you want me to send you an edited file?
Pierre-Yves
Matej Knopp a écrit :
Hi,
I'm working on the date picker encoding problem. What I'll probably do
is to convert all non-unicode (latin1, ...) date picker locale strings
to utf-8 and add charset=utf-8
-Yves
Matej Knopp a écrit :
btw. it should be already in.
Pierre-Yves Saumont wrote:
Hi Matej,
Of course I will test it as soon as you commit it. BTW, there are
plenty of typos and spelling mistakes in the french script, and even
an error in the abreviated day names (it says monday, tuesday
You won't find it there. It's wicket-1.x (and trunk).
1.2.2 is release. Current branch for 1.2 is under 1.x
-Matej
Pierre-Yves Saumont wrote:
I can't find it in releases/wicket-1.2.2, only in trunk, but my app does
not work with 2.0 :-(
Pierre-Yves
Matej Knopp a écrit :
Sorry
the ThreadLocal variable one step up in
AbstractBehavior and making the cleanup method in AbstractBehavior set the
ThreadLocal to null. That fixed this problem apparently, but I'll let you
have the final say on this.
- Samyem
Matej Knopp wrote:
No matter what I do I just can't reproduce
you a
class html file?
-- Karl
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matej Knopp
Sent: Tuesday, September 26, 2006 12:33 AM
To: wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Problem Selecting Tree Nodes
Please send
Please send a test case, I'll look at it. your code seems to be fine,
it's nothing illegal, it can be bug in tree.
Would you mind testing svn version first, it _might_ be already fixed.
Thanks,
-Matej
Karl M. Davis wrote:
Matej,
I'm getting an ArrayIndexOutOfBounds when I go to select a
It also is fixed in wicket-1.x
-Matej
Pierre-Yves Saumont wrote:
Is it fixed only in trunk or also in releases ?
Pierre-Yves
Matej Knopp a écrit :
The problem was that AjaxRequestTarget called component.renderHead(),
without calling rendered() on component behaviors after that (co
I don't think it is a feature. Seems more like a bug to me.
-Matej
samyem wrote:
When I do setEnabled(false) on AjaxSubmitButton component, it does not
disable the button. However, it seems to work for other components like
textbox and checkboxes. Looks like a wicket problem? For now, I have
wicket.examples.ajax.builtin.BasePage;
import wicket.extensions.markup.html.tree.AbstractTree;
/**
* This is a base class for all pages with tree example.
*
* @author Matej Knopp
*/
public abstract class BaseTreePage extends BasePage
{
/**
* Default constructor
*/
public
. (Datepicker work, but
the encoding is wrong.)
Pierre-Yves
Matej Knopp a écrit :
It also is fixed in wicket-1.x
-Matej
Pierre-Yves Saumont wrote:
Is it fixed only in trunk or also in releases ?
Pierre-Yves
Matej Knopp a écrit :
The problem was that AjaxRequestTarget called
,
Samyem
Matej Knopp wrote:
The fix is in svn. (both 1.x and 2.0)
DatePicker in modal window panel now works, although the issue with
z-index still remains. As a side effect this also fixes the component
use check for components that render into head, so calling
getDebugSettings
Well, if this causes trouble, perhaps we could post the information. It
is a bit more work but it would be worth it.
-Matej
Johan Compagner wrote:
This is not a thing wicket can do something about.
This is the URI encoding that must be set in the tomcat connector itself:
URIEncoding=UTF-8
.
Pierre-Yves
Matej Knopp a écrit :
I've tested your quick start example with current svn and I worked as it
should. Tested with FF1.5, IE6 and opera 9.
Can you please test your project with current svn, if the problem persists?
-Matej
Pierre-Yves Saumont wrote:
And in some conditions
do work but the system is
old and equip
with a legacy database which is Big5 based
I could build a quickstart to demo it but it will be Chinese. Could
someone please
provide a different encoding and some charactors to me to build the demo ?
On 9/25/06, *Matej Knopp* [EMAIL
non-Big5
chars to #; automatically. Althought database still store
these escape chars, these chars can be re-rendered correctly on the
web page.
On 9/25/06, *Matej Knopp* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
That's strange. I've tried wicket
prepare
a quickstart to demonstrate these issues.
- Samyem
Matej Knopp wrote:
The fix is in svn. (both 1.x and 2.0)
DatePicker in modal window panel now works, although the issue with
z-index still remains. As a side effect this also fixes the component
use check for components
fresh
version, tried mvn clean, deleted manually the target and tried again !!
I have no problem with wicket-extensions.
Pierre-Yves
Matej Knopp a écrit :
This is strange. I've tested both current 1.x and 2.0
in 1.x all tests completed with no problem for me,
in 2.0 there are 4
There has been a problem with header contribution and modal dialog. It
should be already fixed. Can you please try wicket from svn?
-Matej
Steve Knight wrote:
Can a panel that is used in a modal window contribute to the header?
I've tried using HeaderContributor to include a javascript
step up in
AbstractBehavior and making the cleanup method in AbstractBehavior set the
ThreadLocal to null. That fixed this problem apparently, but I'll let you
have the final say on this.
- Samyem
Matej Knopp wrote:
No matter what I do I just can't reproduce this. Can you please
] On Behalf Of Matej Knopp
Sent: Saturday, September 23, 2006 11:43 AM
To: wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Problem with tree width
Sure, and don't forget to provide css to table layout the tree with lines
and everything that is at least as good as current solution
Matej Knopp wrote:
I don'y really understand why. I was able to reproduce the problem with
the files attached to bug report. And after I fixed the debug console,
the problems were no longer there (though there was other problem -
component not rendered except - for which it is necessary
) in application#init is no
longer necessary.
I'd appreciate if everyone who has issues with header contribution test
it with current svn. The more bugs we nail down the better! :)
-Matej
Matej Knopp wrote:
Hi,
It indeed is problem with modal window. Or, better said, with
AjaxRequestTarget. I've tried
. The
same problem would occur everytime the javascript/stylesheet are added
dynamically.
Matej Knopp wrote:
Well, I was working on it. But only to the degree that I disabled the
disabling of check during ajax request, because it was no longer
necessary.
Unfortunately head contribution
Btw. I've commited fix to 1.x that prevents the text from hiding (it's
being clipped instead).
-Matej
Matej Knopp wrote:
If it was only tree, I'd be probably using nested divs. The reason for
using div per row is actually the TreeTable. Initially, I wanted to
build tree table using tabletr
:
time to work on that magical tr replacing ajax stuff :)
-Igor
On 9/23/06, *Matej Knopp* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
Btw. I've commited fix to 1.x that prevents the text from hiding (it's
being clipped instead).
-Matej
Matej Knopp wrote
are added
dynamically.
Matej Knopp wrote:
Well, I was working on it. But only to the degree that I disabled the
disabling of check during ajax request, because it was no longer
necessary.
Unfortunately head contribution is something else, I'm not sure how to
do it the best way, again
I don't think so. I was working on header contribution and problem with
debug console calling document.write() (thus removing all head elements
from DOM).
This is something completely different, it's related to the component
rendered check. That's not my domain. I believe the problem are
I've fixed the problem of disappearing item captions, but only for
tree-table. I'll have to look at tree css, I just had no time. It might
some serious changes to stylesheet to get this working for Tree.
So if this really is a showstopper for you, try to use tree table (with
the css from
to the TreeTable.
Steve
On 9/21/06, * Matej Knopp* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
Scrolling shouldn't be a problem.
div style=overflow: scroll; height: 20em
div wicket:id=tree
/div
/div
Well. In 1.2.2 there was a problem with internet
about it to the list, I'm not sure what the outcome was.
-Matej
Igor Vaynberg wrote:
i thought you _were_ working on the component use check and ajax target
stuff?
-Igor
On 9/22/06, *Matej Knopp* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
I don't think so. I was working
Scrolling shouldn't be a problem.
div style=overflow: scroll; height: 20em
div wicket:id=tree
/div
/div
Well. In 1.2.2 there was a problem with internet explorer in standard
compliance mode, images were staying even if tree scrolled. In current
svn this is fixed. Can you please try current
One more thing. Instead overflow:scroll it would be better to have
overflow:auto.
-Matej
Matej Knopp wrote:
Scrolling shouldn't be a problem.
div style=overflow: scroll; height: 20em
div wicket:id=tree
/div
/div
Well. In 1.2.2 there was a problem with internet explorer in standard
Can you provide a test case? Or quick start project? I haven't
encountered this behavior. I'd like to look at it but I'd need to
reproduce it.
-Matej
Pierre-Yves Saumont wrote:
It appears that under some conditions, the script associated with the
date picker in the HTML is not executed when
It could be the old javascript still in browser cache. IE is rather
reluctant to evict some old files from the cache.
-Matej
Allen James wrote:
It is working now, but I cannot tell you why. I deleted all my offline
cached content and cookies, and once that was done, everything works as
Selects should be working with latest svn. Don't forget to clear IE's
cache, it tends to help.
-Matej
Stefan Lindner wrote:
select tag had a problem in Model Dialogs in IE. But it should have
been
solved by now. Try to do a svn update to get the latest model window
code.
I did a svn
This is really weird. Can you please either check if current svn version
helps the problem or provide a quick start application so that I can
look at that?
From what I can see the response seems to be ok.
-Matej
Allen James wrote:
I've ran into a scenario where I can use the ModalWindow in
ListChoice should be visible in modal window from current svn.
I can imagine autocomplete not working, perhaps the autocomplete div has
lower z-index. Anyway, if you need autocomplete/datepicker/other
javascript components that have absolute positioning, you may need to
use the modal window in
It depends whether you want to use component in a dialog or a separate page.
When using separate page (iframe) everything should work ok.
When using component, things are bit more complicated:
Non-working tab could be fixed I think, I'll have to look at that. Also
there was recently a bug
Dunno. It's web. What I'd do is that I'd let datepicker be and change
the modal window content to page instead of panel. There are also other
poblems with panel (hiding inputs in explorer), so for now I'd stick
with page.
-Matej
Eelco Hillenius wrote:
On 9/13/06, Igor Vaynberg [EMAIL
cookie name per modal
window instance would solve the problem in general.
Matej Knopp wrote:
Modal window width and height is stored in a cookie. First time initial
width and height is used, and after that the width and height from the
cookie is used.
What you need to do is set different
The fix should be in SVN. But there is a bug in 1.2 now that prevents
rendering datepicker in ajax response, so I wouldn't recommend updating
right now.
In the meanwhile you can try to disable ajax debug, it should help.
( getAjaxSettings().setAjaxDebugModeEnabled(false) ).
-Matej
Iuly
Modal window width and height is stored in a cookie. First time initial
width and height is used, and after that the width and height from the
cookie is used.
What you need to do is set different cookie id for different modal
windows. Or disable cookies at all (setCookieId(null)).
-Matej
window instance would solve the problem in general.
Matej Knopp wrote:
Modal window width and height is stored in a cookie. First time initial
width and height is used, and after that the width and height from the
cookie is used.
What you need to do is set different cookie id
Wow. Now that's a stupid safari bug. Please fill a bug, I'll look at it
as soon as I can. Thanks for finding it.
-Matej
Adam Smyczek wrote:
Problem found, it looks like safari aborts execution when
getElementsByTagName
is called on a text node (in contrast calling e.g. 'childNodes' works
Putting large objects into session is ok, as long as you
a) have enough memory and can afford it
b) don't replicate the session (clustering).
-Matej
Pierre-Yves Saumont wrote:
I already tried this method, but it is called just before the user can
see the page. What I need is to do something
Sorry, never mind. Wrong mail :)
-Matej
Matej Knopp wrote:
Per Ejeklint wrote:
I'm using 1.2-SNAPSHOT and the problem persists. No big deal, now that I
have a workaround. :)
What kind of workaround if I may ask?
-Matej
/Per
10 sep 2006 kl. 23.25 skrev Frank Bille:
Hehe I could try
that was waiting for 1.3
because of api breaks?
-Igor
On 9/11/06, *Matej Knopp* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
Ajax Header contribution is already working in 1.2.2. Scripts in ajax
response (scriptfunction() { }/script should work as well
mean placing scriptfunction() { }/script in the Ajax
response, it does not work in IE6 but it works in Firefox. (With Wicket
1.2.2)
Pierre-Yves
Matej Knopp a écrit :
Ajax Header contribution is already working in 1.2.2. Scripts in ajax
response (scriptfunction() { }/script should work
Yes,
this bug is in 1.2.2 only, happened during backporting it seems.
Easiest solution (workaround) I can think of is to add empty
WebMarkupContainer and add the header contributor there.
-Matej
Igor Vaynberg wrote:
i think this is a known header contributor bug in 1.2.2 - headers are
This is a known problem. Unfortunately, the tree column can't
automatically adjust the width according to the content. It's a
limitation of css and there's not much I can do about it.
I couldn't use table for treetable, as there are issues in IE and
opera when replacing table rows. Plus in FF
Heh, I'm not even sure, but I guess not. I'm way too busy lately :(
Maybe frankbille could have a look at that?
-Matej
Igor Vaynberg wrote:
did you fix it already in wicket-1.x?
-Igor
On 9/10/06, *Matej Knopp* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
Yes
Pierre-Yves Saumont wrote:
Hello,
I would be interested to hear about your experience in testing Wicket
application, particularly using Ajax.
My experience, after one week trying several solutions, is not so good.
I tried jWebUnit and ad a lot of problems with scripts. So I downgrade
sure it is. but you have to set it on tree state
(Tree#getTreeState()
- you'll find the method there.
-Matej
Steve Knight wrote:
Is it possible to programatically select a row in the new tree
component? I think the old version had setSelected(final
DefaultMutableTreeNode node).
Steve
#update(AjaxRequestTarget target) can update
the changed portions of tree.
-Matej
/Per
4 sep 2006 kl. 09.32 skrev Matej Knopp:
It's not in 2.0 extensions and probably it never will be.
It's in 2.0 core :-)
-Matej
Per Ejeklint wrote:
I looked at the live examples and found
How is this supposed to work in 1.2.1? I believe the header contribution
code is the same. getImplementationId() is the one causing problems
here. It should work ok in 2.0, as there is no getImplementationId()
anymore.
-Matej
Igor Vaynberg wrote:
this is a known header contribution bug in
Yeah, we know about it, it's unfortunate that there is such bug, seems
like no one (including me) has really tested contributors on page. So
far as workaround it should be possible to add empty WebMarkupContainer
to the page and add header contributors there.
-Matej
Jerry Smith wrote:
I guess I might know what's causing it. It's not the header contribution
code. It's the initialization code.
the thing is that prior 1.2.2 no javascript in the
component/component was executed. When setting outerhtml in Internet
explorer the javascript in the outer html is not executed. This
it with a WebMarkupContainer? Why do think it is
different from a page? May be the error no matter where it is attached
to.
Juergen
On 9/1/06, Matej Knopp [EMAIL PROTECTED] wrote:
Yeah, we know about it, it's unfortunate that there is such bug, seems
like no one (including me) has really tested
Stefan Jozsa wrote:
Hi,
Hi,
I have a Page component MessagePage(String message, Page backPage).
On closing a MessagePage returns to backPage
by doing setResponsePage(backPage);
I use a MessagePage like this:
setResponsePage(new MessagePage(someMessage, someBackPage);
How can
Hi,
sure, this is possible. With wicket you don't have to put a single thing
in your web directory or WEB-INF (except of course declaring one wicket
servlet (or filter in wicket 2) in web.xml).
All resources can be stored in classpath. Markup files (html) for
components and pages are stored
Great, the latest doesn't seem to work in IE either. Martijn, are you
listening? We need to postpone the release a bit.
-Matej
Igor Vaynberg wrote:
try the latest 1.2 from svn or wait for the official 1.2.2 tomorrow
-Igor
On 8/26/06, *Koji Lin* [EMAIL PROTECTED] mailto:[EMAIL
Hmm.. The bug is fixed, we've been adding paging navigator to response
even if the parent container has already been added.
-Matej
Matej Knopp wrote:
Great, the latest doesn't seem to work in IE either. Martijn, are you
listening? We need to postpone the release a bit.
-Matej
Igor
And how is caching done if you can't query objects by identity? Or does
this question make even sense?
-Matej
Geoff hendrey wrote:
Ohh my god yes
I ran into all these problems in JDOMax, and they are
all solved in Shades.
I won't drop the name, but some very influential
person on
be missing.
If your application does not keep a reference
to the pojo, the pojo doesn't stay in the cache. What
kind of cache is that? :-)
I think using soft references, the objects would be evicted only if out
of memory is about to happen.
-Matej
--- Matej Knopp [EMAIL PROTECTED] wrote
the javadoc.
--- Matej Knopp [EMAIL PROTECTED] wrote:
I was more concerned about second level cache. When
using loadable
detachable models it is possible to hold only object
id in session,
loading the entire object on the beginning on
request. In this scenario
second level cache really
Martijn Dashorst wrote:
o Wicket Extensions
- Backported AJAX header contribution code from 2.0.
Just a very minor detail. AJAX header contribution is part of core, not
extensions (have I put it to wrong changes.xml?).
-Matej
Have fun!
- The Wicket Team
--
Download
Nathan Hamblen wrote:
Take a look, if you haven't already: it's VERY well done. And it's done
in Tapestry. Yay for second-gen Web frameworks, or something.
Is it? 269 kb of javascript (not even compressed), I can't check limit
search to favorites in firefox (because I've different font set)...
It doesn't work in firefox because you placed the form directly to table.
This is not valid and firefox freaks out. You have to put it in table cell
(wrap the form in trtd and /td/tr)
-Matej
Dipu wrote:
Hi All,
I have the following hierarchy
Page
Panel
Form
And in
Yes, it is fragile. But it's quite unusual to make components that need
own markup as anonymous classes. Usually anonymous classes are used only
if you need to override methods like onClick or isVisible.
-Matej
Scott Swank wrote:
Which is why I like to use named inner classes instead of
I'm not sure I understand what's going on. Could you provide a test-case
or a quick start application?
-Matej
Pierre-Yves Saumont wrote:
Hi,
I was curious to see how many instance of components were created, so I
just added a counter to a panel. I appears that when I load the page for
places
(images, css, scipts, images from css, images from scripts
and even an html file loaded from within a script !)
I'll see if I can strip down the application and isolate what
is causing the problem.
Pierre-Yves
Matej Knopp a écrit :
I'm not sure I understand what's going on. Could
specificity, but things now work.
Thanks to all for your support.
Pierre-Yves
Matej Knopp a écrit :
Ah, that's the problem. It's wicket multi window support that causes you
trouble.
First, i guess you are using 1.2, or am I wrong? 1.2.1 should fix the
continuous parameters wicket-x
The problem here probably is that outerHTML in explrer doesn't execute
the javascript located in the replacement string.
Current svn version should fix this (as well as header contribution), so
please try it and let us know whether it does work.
-Matej
Pierre-Yves Saumont wrote:
Hello,
I
Well.. ab2 is an apache benchmarking tool. But I'm under the impression
that it's intended to measure the performance of static pages.
It doesn't use cookies, does it? If I recall correctly there should be a
possibility to specify a cookie value there, so you might be able to
reduce the number
1 [X]
Btw.
We are using ${key} everywhere (customized markup parsing) and it's much
more convenient than wicket:message :-)
-Matej
Eelco Hillenius wrote:
For localized attributes - so that you don't have to attach attribute
modifiers all over the place for that sole reason - we have two
Ajax calls and history just don't play nice together. Every link on page
has a version information in it. If you make an ajax request, increase
page version and replace component on page, all links on page would
point to previous version, so every link (except on the replaced
component) you
only
be done if we are saying to the browser that he has to make a new entry
in the history.
johan
On 7/31/06, *Matej Knopp* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
Ajax calls and history just don't play nice together. Every link on page
has a version information
Igor Vaynberg wrote:
this happens because ajax requests turn off versioning, otherwise there
would be all kinds of problems with page expiration - take selfupdating
ajax stuff - 10 updates and all other pages are out of the pagemap so if
you click the back button and a link on the prev page
Johan Compagner wrote:
need to see some more code or a test case.
On 7/25/06, *Paolo Di Tommaso* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
I'm trying to redirect after an ajax request doing something like that:
String url = (String)
I've just finished new (ajax based) tree (version for wicket 2.0 is in
svn (/svnroot/wicket/trunk/wicket-sandbox/users/matej_k/tree) )
It's about to be ported to wicket 1.2 and it will likely be a part of
wicket-extensions. It might help you because it works with TreeNode and
not
301 - 400 of 686 matches
Mail list logo
