Hi,
I think using Page#Page(IModel) constructor is not very useful. It appears
to be anti-pattern lately.
There were several tickets related to ModalWindow when a model is shared
between the page that contains the modal and the page inside the modal. The
two different pages are being serialized
Hi all,
Just to confirm if overriding updateAjaxAttributes has any effect on
AutoCompleteBehavior?
I was tryng to do the following but see no popup nor code reflected in the
html source.
@Override
protected void updateAjaxAttributes(AjaxRequestAttributes
attributes) {
Hi,
I don't see why it should not work.
Actually AutoCompleteBehavior itself wont work without this method. It
overrides it to do:
attributes.setWicketAjaxResponse(false);
attributes.setDataType(html);
On Mon, Jan 21, 2013 at 10:09 AM, james yong i_yon...@yahoo.com.sg wrote:
Hi all,
Just
Hi,
Just put a breakpoint in your constructor and see what are the stacktraces.
On Sun, Jan 20, 2013 at 6:27 PM, kamiseq kami...@gmail.com wrote:
hi,
I try to understand why wicket (in 6th version) is constructing my page
always 3 times per every request. it is page constructor is called 3
Hi,
wicket-1.5.xsd defines only the elements - wicket:something.
wicket:for is an attribute to label element which is part of HTML spec.
Is there a way to define attributes to elements from a different namespace ?
If it is possible then please file a ticket with a patch. The same is valid
for
Hi Martin,
Thanks for the advice. So I will use PageParameters then and let
Wicket construct the page.
But:
I also have page constructors with PageReference parameter to link
back to. This would break bookmarkable as well. Would you have similar
concerns about PageReference?
Kind Regards,
You can pass the oldPageId as a request parameter too. Then use it: new
PageReference(oldPageId.toInt()).getPage()
On Mon, Jan 21, 2013 at 10:39 AM, Bernard bht...@gmail.com wrote:
Hi Martin,
Thanks for the advice. So I will use PageParameters then and let
Wicket construct the page.
But:
Hi Martin,
This is great.
Thanks for the quick response.
Bernard
On Mon, 21 Jan 2013 10:57:19 +0200, you wrote:
You can pass the oldPageId as a request parameter too. Then use it: new
PageReference(oldPageId.toInt()).getPage()
On Mon, Jan 21, 2013 at 10:39 AM, Bernard bht...@gmail.com
Well all this page stuff is not related to the topic in this thread.
Please open another thread for that.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-Spring-tp4655546p4655570.html
Sent from the Users forum mailing list archive at Nabble.com.
Thanks for your hard work.
But iam very sad that highchart its not free for commercial use :o/
Maybe anyone else could do such plugin with : http://www.jqplot.com/tests/
or http://code.google.com/p/flot/
--
View this message in context:
Any other ideas to do this with wicket?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-6-through-JSONP-tunneling-tp4655501p4655575.html
Sent from the Users forum mailing list archive at Nabble.com.
Hi Sven,
I just tried 6.5 and that's fixed it! Thank you very much.
If you still want a quickstart to have a look at the code that demonstrates
the issue in 6.4, then let me know.
As it turned out It wasn't to do with my BookmarkableMapper sub class
although the urls that the mapper handles
Hi,
Anyway let me know if you'd like the quickstart that shows the issue
in 6.4
We have no need for it.
Better create a quickstart for the next issue you'll find.
Thanks
Sven
On 01/21/2013 10:27 AM, Simon B wrote:
Hi Sven,
I just tried 6.5 and that's fixed it! Thank you very much.
If
Hi,
On Mon, Jan 21, 2013 at 10:20 AM, MattyDE ufer.mar...@gmail.com wrote:
Thanks for your hard work.
But iam very sad that highchart its not free for commercial use :o/
Maybe anyone else could do such plugin with : http://www.jqplot.com/tests
There is already such implementation.
Hi Martin,
I tried again with a simple application and pretty sure updateAjaxAttributes
has no effect on AutoCompleteBehavior. But then, I need to verify with
another party to verify/confirm whether this is a bug or intended feature.
It is working with AjaxFormComponentUpdatingBehavior.
Regards,
See another implementation wicket-jqplot in wicketstuff
(https://github.com/wicketstuff/core/wiki/JqPlot-Plugin-Integration)
Best regards,
Decebal
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Announce-Introducing-Wicked-Charts-tp4655519p4655581.html
Sent from
Hi,
I'm implementing some components that have a really dynamic behavior.
The JavaScript client side component properties changes as user interacts.
But the thing is that I don't really need an Ajax call after every change
to update this properties server-side. Just when the user clicks in
Hi,
On Mon, Jan 21, 2013 at 4:01 PM, Diogo Casado diogocas...@gmail.com wrote:
Hi,
I'm implementing some components that have a really dynamic behavior.
The JavaScript client side component properties changes as user interacts.
But the thing is that I don't really need an Ajax call after
Hi,
On Mon, Jan 21, 2013 at 3:01 PM, Diogo Casado diogocas...@gmail.com wrote:
Hi,
I'm implementing some components that have a really dynamic behavior.
The JavaScript client side component properties changes as user interacts.
But the thing is that I don't really need an Ajax call after
Martin,
Thanks. Unfortunately the component is not form based. It's a canvas.
Yeah I know that the Ajax interface in Wicket 1.6 is based on jQuery. It
sure is time to update it.
Thanks.
- Diogo
On Mon, Jan 21, 2013 at 12:11 PM, Martin Grigorov mgrigo...@apache.orgwrote:
Hi,
On Mon, Jan
Ernesto.
Thanks!
I will check on this function to see if we can avoid any specific patches.
I will also try to link against Wicket 1.6 to see how things go. Maybe
using jQuery ajax is better.
Regards,
- Diogo
On Mon, Jan 21, 2013 at 12:13 PM, Ernesto Reinaldo Barreiro
reier...@gmail.com
Hi,
On Mon, Jan 21, 2013 at 3:34 PM, Diogo Casado diogocas...@gmail.com wrote:
Ernesto.
Thanks!
I will check on this function to see if we can avoid any specific patches.
I will also try to link against Wicket 1.6 to see how things go. Maybe
using jQuery ajax is better.
I think work
CSS :)
~ Thank you,
Paul Bors
-Original Message-
From: Marios Skounakis [mailto:msc...@gmail.com]
Sent: Tuesday, January 15, 2013 2:18 PM
To: users@wicket.apache.org
Subject: Re: Multiple select drop down in Wicket
I've considered using select2 (it looks very impressive) but I was
I'm currently in the process of evaluating frameworks. We are currently
using Wicket 1.4.
The ones I've looked at so far have been Vaadin, Tapestry 5.4, and Wicket
6.0.
Vaadin I ruled out for various reasons.
One of the problems that our users have complained quite a bit about is the
dreaded
JCoder wrote:
Hi all,
Im just trying to setup a basic project structure in Eclipse with
Wicket and Spring. I think its pretty smart to separate both Wicket
and Spring into two different Eclipse projects, isnt it? Thus, I
created an Eclipse project for the Web part and one for the Spring
Why don't you just keep the session alive as long as the user has an
ajax page open? You can easily do this by letting the page do a timed
ajax call to the server every x minutes, where x is slightly less than
your session timeout.
On Mon, Jan 21, 2013, at 17:56, sthomps wrote:
I'm currently in
It's just not efficient.
We have users that will let their pages sit for hours before they come back
to them.
I would rather have these sessions/memory be reclaimed, and if a user has a
stale page, the Ajax action continues on as normal.
We also have a sudo portal that contains applications
Hi all,
I have a component containing a form with many TextFields.
The way it should work is that when changed, the value should be
persisted immediately (no Save button, all through AJAX).
The AJAX calls work fine, the value gets to the model.
The code to save the model (and the entity
I did, I dont see anything specific about this
java.lang.RuntimeException: test
at com.myapp.Page1.initialize(Page1.java:80)
at com.myapp.Page1.init(Page1.java:48)
at com.myapp.Page1.init(Page1.java:42)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
Wasn't there some problem with empty images (img src= ) and IE
reloading the page? At least I remember some old threads on this topic.
On Mon, Jan 21, 2013 at 8:07 PM, kamiseq kami...@gmail.com wrote:
I did, I dont see anything specific about this
java.lang.RuntimeException: test
at
I have something like this in logs, I will try remove it
pozdrawiam
Paweł Kamiński
kami...@gmail.com
pkaminski@gmail.com
__
On 21 January 2013 20:12, Ernesto Reinaldo Barreiro reier...@gmail.comwrote:
Wasn't there some problem with empty images (img src= ) and IE
yep that was it, why this happens?
thanks ernesto, it is not only on IE ;] firefox also
pozdrawiam
Paweł Kamiński
kami...@gmail.com
pkaminski@gmail.com
__
On 21 January 2013 20:36, kamiseq kami...@gmail.com wrote:
I have something like this in logs, I will try
Hi,
On Mon, Jan 21, 2013 at 8:42 PM, kamiseq kami...@gmail.com wrote:
yep that was it, why this happens?
To be honest I do not know the exact reason... I guess a second request is
launched to retrieve missing empty image... Just googled for it and
found this.
ok, thanks anyway, indeed it was killing me for some time now ;]
pozdrawiam
Paweł Kamiński
kami...@gmail.com
pkaminski@gmail.com
__
On 21 January 2013 21:13, Ernesto Reinaldo Barreiro reier...@gmail.comwrote:
Hi,
On Mon, Jan 21, 2013 at 8:42 PM, kamiseq
How does Tapestry solve the problem explained in the comments you pasted ?
On Mon, Jan 21, 2013 at 8:15 PM, sthomps stho...@gmail.com wrote:
It's just not efficient.
We have users that will let their pages sit for hours before they come back
to them.
I would rather have these
You can read the Tapestry response a
href=http://tapestry.1045711.n5.nabble.com/Session-Expiration-Ajax-td5719213.html;here.
Essentially there are no PageMaps/versions per users session.
--
View this message in context:
Well, I'll need some more technical details about Tapestry internals to
understand what they do.
You can check https://github.com/jolira/wicket-stateless - it provides few
Ajax behaviors and components which are stateless, i.e. they re-create the
whole page for each request.
I think this is what
Hi,
You can use MarkMail to see the activity in the mailing lists (there is a
Flash at the left-top corner)
- users:
http://markmail.org/search/?q=wicket#query:wicket%20list%3Aorg.apache.wicket.users+page:1+state:facets
- dev:
Hi,
Wicket updates the model with the new value. If this model is shared
between several components then all of them have the new value for free. No
need to notify them.
If you still need to notify then you can use #updateModel() method -
I have a panel that's too heavy so I'm using an an AjaxLazyLoadPanel to lazy
load it. That panel is being reloaded on every Ajax call that rerenders the
containing panel , but now I want to use lazy loading just once the page is
loaded, and when rerendering the containing panel I want to use a
Hi all,
guessing from a name, I would expect these two to do the same:
link.add( new OnChangeAjaxBehavior() {
@Override protected void onUpdate( AjaxRequestTarget target ) {
ReleaseTraitRowPanel.this.onUpdate( target );
}
});
Solved - it was wrong validator which never passed, so onModelChanged()
was never called.
Now I have related problem:
FeedbackPanel shows the error when a form is submitted, but not on AJAX.
It has setOutputMarkupId( true );
It is added to AjaxRequestTarget.
What should I check?
Thanks,
Maybe you can use something like this :
new AjaxLazyLoadPanel(PanelId) {
Panel myPanel;
@Override
public Component getLazyLoadComponent(String varMarkupId) {
if (myPanel == null) {
myPanel = new
Speaking of this, I had the same issue recently.
I wished for stateless pages but as I didn't know, I opted for
keep-alive ajax requests.
Is there some article, blog, tutorial or whatever on how to keep pages
stateless?
I know that if a page is bookmarkable and doesn't contain any
I use Wicket 6.3 and WASP to integrate security
(wicket-security-wasp-1.5-RC5.1.jar ).
When I deploy the WAR to tomcat, I get the message:
java.lang.NoSuchMethodError:
org.wicketstuff.security.log.IAuthorizationMessageSource.getMessage(Ljava/lang/String;)Ljava/lang/String;
On 01/21/2013 10:52 PM, Martin Grigorov wrote:
Hi,
Wicket updates the model with the new value. If this model is shared
between several components then all of them have the new value for free. No
need to notify them.
If you still need to notify then you can use #updateModel() method -
Forgot to write: My problem is that the Map item is deleted, but Wicket
renders the given sub-component with the old Map for some reason.
But on next Ajax request, it already uses the new one.
I'm a bit puzzled.
On 01/22/2013 05:49 AM, Ondrej Zizka wrote:
On 01/21/2013 10:52 PM, Martin
Hi,
To rectify problem 2, I changed the following in wicket-autocomplete.js,
Wicket.Event.add(obj,keypress,function(jqEvent){
if(Wicket.Event.keyCode(jqEvent)===KEY_ENTER){
if(selected-1||hidingAutocomplete===1){
hidingAutocomplete=0;
Ok, I got it.
Seems I have to manually refresh the ListView's model. So now it's like
below.
I thought it would re-load it between
* onDelete(), which is triggered in
AjaxEventBehavior(onclick)#onEvent(),
* and ListView rendering.
Could someone enlight me pls.
Thanks,
Ondra
Hi James,
please attach that info to WICKET-4990.
Thanks
Sven
On 01/22/2013 07:07 AM, james yong wrote:
Hi,
To rectify problem 2, I changed the following in wicket-autocomplete.js,
Wicket.Event.add(obj,keypress,function(jqEvent){
if(Wicket.Event.keyCode(jqEvent)===KEY_ENTER){
What about OnChangeAjaxBehavior#EVENT_NAME's javadoc? Isn't that sufficient?
Sven
On 01/21/2013 08:53 PM, Ondrej Zizka wrote:
Hi all,
guessing from a name, I would expect these two to do the same:
link.add( new OnChangeAjaxBehavior() {
@Override protected void onUpdate(
Just update your wicketstuff dependency to 6.3.0:
http://mvnrepository.com/artifact/org.wicketstuff/wicketstuff-security-wasp/6.3.0
Sven
On 01/21/2013 01:45 PM, BartBlackMagic wrote:
I use Wicket 6.3 and WASP to integrate security
(wicket-security-wasp-1.5-RC5.1.jar ).
When I deploy the WAR
Hi Martin,
I now have second thoughts before replacing a page constructor having
an IModel parameter with the use of PageParameters which I need when
letting Wicket create the page. It can be a nightmare.
Passing IModel server side on page constructon has many advantages. We
get security because
Hi Sven,
WICKET-4990 is for problem 1.
So I raised a jira issue for problem 2, together with its solution.
WICKET-4998.
Regards,
James
Sven Meier wrote
Hi James,
please attach that info to WICKET-4990.
Thanks
Sven
On 01/22/2013 07:07 AM, james yong wrote:
Hi,
To rectify problem
54 matches
Mail list logo
