Hi,
If you cannot use sticky sessions then you should not use
REDIRECT_TO_BUFFER because the pre-rendered response is saved/buffered
in the WebApplication on the current node and there is a (big) chance
that the next request wont be processed by the same node.
You can use either ONE_PASS_RENDER
See org.apache.wicket.markup.html.link.BookmarkablePageLink#linksTo(Page).
if (link.linksTo(getPage()) {
link.setEnable(false);
}
On Tue, Aug 21, 2012 at 7:54 PM, Mansour Al Akeel
mansour.alak...@gmail.com wrote:
Thank you a lot.
Both methods did the trick. One last question in the same
Sven while you are here:
why no documentation for Tree? Nothing at all? Right now I face a
problem - tree do not persist it's state (Bookmarcable links, copied
from example) and I have no clue where to see.
On 21 August 2012 21:38, Sven Meier s...@meiers.net wrote:
And the winner is ... Martin!
Hi,
These components have been merged in Wicket 6.
You can see the demo at
http://www.wicket-library.com/wicket-examples-6.0.x/tree
and the code in org.apache.wicket.extensions.markup.html.repeater.tree
package in wicket-extensions module.
The javadocs are also improved.
On Wed, Aug 22, 2012 at
Are you using wicket-tree or the new components in Wicket 6?
Please be more specific what information you're looking for. I'll gladly
provide more info in javadoc or in the wiki.
Sven
Alex Shubert alex.shub...@gmail.com schrieb:
Sven while you are here:
why no documentation for Tree? Nothing
I think I have found the problem.
Should be better with the fix in
https://issues.apache.org/jira/browse/WICKET-4722
On Fri, Aug 10, 2012 at 2:53 PM, Martin Grigorov mgrigo...@apache.org wrote:
No, these are no errors.
These are kept only in case of error.
We can improve though by removing
Thanks Martin for the response. Could you please answer the below question as
well?
What is the use of the below API?
getRequestCycleSettings().setBufferResponse(false);
Does it make any difference to the render strategy? I guess it makes some
difference to 'REDIRECT_TO_BUFFER'.
Thanks,
No, this is not related.
I just improved its javadoc:
https://git-wip-us.apache.org/repos/asf/wicket/repo?p=wicket.git;a=commitdiff;h=43878fc8c470044923f3b599953a1c4ff2aef63b
Is it cleaner now ?
On Wed, Aug 22, 2012 at 2:15 PM, sudeivas sureshkumar@gmail.com wrote:
Thanks Martin for the
I've added a scenario where i need to use wicket:fragments.
Following is my parent html.
html
body
wicket:child/
/body
/html
Now i'm giving child html which will replace wicket:child/ of my parent
html
html
body
wicket:extend
...
span wicket:id=myPanelExample input (will be removed)/span
Yes it is. Thanks
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Which-RENDER-STRATEGY-is-best-for-clustered-setup-tp4651420p4651433.html
Sent from the Users forum mailing list archive at Nabble.com.
After a day of changing a lot I got this message when starting wicket from
mvn jetty:run
I reinstalled older sources but still get this message
wicket.version1.5.7/wicket.version
Who can help on this?
2012-08-22 16:39:53.120::WARN: Error starting handlers
Java.lang.NoSuchMethodError:
Check for duplicated Wicket jars in the classpath
On Wed, Aug 22, 2012 at 5:49 PM, Delange delan...@telfort.nl wrote:
After a day of changing a lot I got this message when starting wicket from
mvn jetty:run
I reinstalled older sources but still get this message
Good afternoon,
Is there any way to have Comet channels using the wicket-atmosphere
API? For instance, with the Broadcaster API, you could use a
MetaBroadcaster which used to have a broadcasterID parameter.
I can't figure out how to integrate that in my wicket-atmosphere code
and the JavaDoc
I have a reusable Panel which contains a DropDownChoice.
The DropDownChoice has an Ajax onChange action defined on it,
protected void onUpdate(AjaxRequestTarget target) {
...
}
When I add the Panel to one of my forms, the Ajax action gets invoked
correctly on the DropDown change, but when I add
Looking further in our code, I see that the 2nd form (which has the problem)
defines an additional Ajax onchange on its own, it finds the dropdown and
adds this extra Ajax code:
final DropDownChoice myDropDown =
(DropDownChoice)((Panel)get(myPanel)).get(myDropDown);
myDropDown.add(new
Yes, this is the problem.
Only one of the two updates will be performed:
https://issues.apache.org/jira/browse/WICKET-214
Sven
On 08/22/2012 06:51 PM, eugenebalt wrote:
Looking further in our code, I see that the 2nd form (which has the problem)
defines an additional Ajax onchange on its
Don't know what caused the duplicate jars, but you where right. Many thanks!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/WebApplication-getComponentPreOnBeforeRenderListeners-not-fount-tp4651434p4651441.html
Sent from the Users forum mailing list archive at
Thanks
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Ajax-onUpdate-DropDown-Invoked-In-One-Place-But-Not-The-Other-tp4651438p4651442.html
Sent from the Users forum mailing list archive at Nabble.com.
Hi Balaji,
I am not sure if this helps but I have used fragments in wicket 1.5.7 and from
what I see in your code, it should work. Here is a simple snippet that shows
how I used it:
In my page class, here is what I have to different and show a scrolling
fragment or ordered list of items
19 matches
Mail list logo
