Re: PageExpired in non bookmarkable page with 1.5.2

[Martin Grigorov]

There is a ticket for this problem:
https://issues.apache.org/jira/browse/WICKET-4189
I'll attach the app to it.

On Wed, Nov 2, 2011 at 6:50 AM, Igor Vaynberg  wrote:
> please attach it to a jira issue.
>
> -igor
>
> On Tue, Nov 1, 2011 at 9:21 PM, Seko Masaya  wrote:
>> Hi.
>>
>> I prepared quickstart that reproduces the problem.
>> http://d.hatena.ne.jp/sekom/files/wicket152quickstart.zip?d=y
>>
>> Please do the following operations.
>> 1.click "next" link
>> 2.Wait a minute
>> 3.click "home" link
>> 4.Please check the console. Exception displayed.
>>
>>
>> --- On Tue, 2011/11/1, Martin Grigorov  wrote:
>>
>>> Hi,
>>>
>>> This is caused by the new implementation of RequestLogger internals.
>>> Can you provide a quickstart that reproduces the problem ?
>>>
>>> On Tue, Nov 1, 2011 at 3:45 AM, Seko Masaya  wrote:
>>> > Hi.
>>> > I'm having trouble PageExpired exception in non Bookmark page.
>>> > In the case of Wicket 1.5.2 is the log output when sending PageExpired 
>>> > exception.
>>> > No output in Wicket 1.5.0.
>>> > I hope behavior of Wicket 1.5.0.
>>> >
>>> > log:
>>> > ERROR - RequestHandlerStack        - Error detaching RequestHandler
>>> > org.apache.wicket.protocol.http.PageExpiredException: Page with id '1' 
>>> > has expired.
>>> >    at 
>>> > org.apache.wicket.request.handler.PageProvider.getPageInstance(PageProvider.java:169)
>>> >    at 
>>> > org.apache.wicket.request.handler.PageProvider.getPageClass(PageProvider.java:227)
>>> >    at 
>>> > org.apache.wicket.request.handler.logger.PageLogData.(PageLogData.java:49)
>>> >    at 
>>> > org.apache.wicket.request.handler.logger.ListenerInterfaceLogData.(ListenerInterfaceLogData.java:50)
>>> >    at 
>>> > org.apache.wicket.request.handler.ListenerInterfaceRequestHandler.detach(ListenerInterfaceRequestHandler.java:134)
>>> >    at 
>>> > org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.detach(RequestCycle.java:761)
>>> >    at 
>>> > org.apache.wicket.request.RequestHandlerStack.detach(RequestHandlerStack.java:180)
>>> >    at 
>>> > org.apache.wicket.request.cycle.RequestCycle.onDetach(RequestCycle.java:565)
>>> >    at 
>>> > org.apache.wicket.request.cycle.RequestCycle.detach(RequestCycle.java:508)
>>> >    at 
>>> > org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:284)
>>> >    at 
>>> > org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:162)
>>> >    at 
>>> > org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:218)
>>> >    at 
>>> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
>>> >    at 
>>> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>>> >    at 
>>> > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>>> >    at 
>>> > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>>> >    at 
>>> > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>>> >    at 
>>> > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>>> >    at 
>>> > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>>> >    at 
>>> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>>> >    at 
>>> > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
>>> >    at 
>>> > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
>>> >    at 
>>> > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
>>> >    at java.lang.Thread.run(Thread.java:662)
>>> >
>>> > -
>>> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>> > For additional commands, e-mail: users-h...@wicket.apache.org
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> Martin Grigorov
>>> jWeekend
>>> Training, Consulting, Development
>>> http://jWeekend.com
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

UTF-8 encoding RFE for warning?

[nino martinez wael]

Hi

I've UTF-8 encoded all my files, setup tomcat to support utf-8 and
everything.. But something did'nt work because my chars where all garble..

Then I tried all sorts of stuff, only to discover that nothing worked.
Finally I figured out that I was using .property files and not
.property.xml , apparently java does not support utf-8 in .property files.

A warning on having utf-8 content in .property files would be nice.. Or is
it just general knowledge?

regards Nino

Re: UTF-8 encoding RFE for warning?

[Martin Grigorov]

On Wed, Nov 2, 2011 at 10:54 AM, nino martinez wael
 wrote:
> Hi
>
> I've UTF-8 encoded all my files, setup tomcat to support utf-8 and
> everything.. But something did'nt work because my chars where all garble..
>
> Then I tried all sorts of stuff, only to discover that nothing worked.
> Finally I figured out that I was using .property files and not
> .property.xml , apparently java does not support utf-8 in .property files.
>
> A warning on having utf-8 content in .property files would be nice.. Or is
> it just general knowledge?

For me this is a well known fact but many people still hit this problem,
I'd love to see a Java program that accepts file as input and returns
what encoding is used. There are some tricks with checking the first
few bytes but I've never seen something stable that works for all
possible encodings.

>
> regards Nino
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: UTF-8 encoding RFE for warning?

[nino martinez wael]

It's a known fact for me aswell now :)

Ok it might be a no go then i guess. Might be the reason why eclipse also
has the "encoding determined from content" they actually have to read all
the content to *guess* what encoding it is.

regards Nino

2011/11/2 Martin Grigorov 

> On Wed, Nov 2, 2011 at 10:54 AM, nino martinez wael
>  wrote:
> > Hi
> >
> > I've UTF-8 encoded all my files, setup tomcat to support utf-8 and
> > everything.. But something did'nt work because my chars where all
> garble..
> >
> > Then I tried all sorts of stuff, only to discover that nothing worked.
> > Finally I figured out that I was using .property files and not
> > .property.xml , apparently java does not support utf-8 in .property
> files.
> >
> > A warning on having utf-8 content in .property files would be nice.. Or
> is
> > it just general knowledge?
>
> For me this is a well known fact but many people still hit this problem,
> I'd love to see a Java program that accepts file as input and returns
> what encoding is used. There are some tricks with checking the first
> few bytes but I've never seen something stable that works for all
> possible encodings.
>
> >
> > regards Nino
> >
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: [RELEASE] WASP/SWARM/Wicket security 1.4.1 released, roadmap for future direction

[Martijn Dashorst]

All is working now.

Martijn

On Tue, Nov 1, 2011 at 3:48 PM, Martijn Dashorst
 wrote:
> On Tue, Nov 1, 2011 at 3:41 PM, Martijn Dashorst
>  wrote:
>> It is not your problem, but strange enough the main page just works...
>
> It appears that mij hosting provider has reset/blocked the account for
> the mysql database. Investigating how to reset the password.
>
> Martijn
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

wicket AjaxCheckBox's onUpdate not called

[Martin A]

Hello,

In a Page I have an AjaxCheckBox, as so:



form.add(new AjaxCheckBox("image1_whole", new
PropertyModel(this, "image1Whole")) {

  private static final long serialVersionUID = 1L;

  @Override
  protected void onUpdate(AjaxRequestTarget target) {
image1PreviewArea.setVisible(!image1PreviewArea.isVisible());

target.add(image1PreviewArea);
  }

  @Override
  protected boolean wantOnSelectionChangedNotifications() {
return true;
  }

});

The component's onUpdate is never called. What am I missing?

Thanks,
Martin

Re: wicket AjaxCheckBox's onUpdate not called

[Ernesto Reinaldo Barreiro]

Just guessing... try getting rid of

  @Override
>      protected boolean wantOnSelectionChangedNotifications() {
>        return true;
>      }

Ernesto

On Wed, Nov 2, 2011 at 10:25 AM, Martin A  wrote:
> Hello,
>
> In a Page I have an AjaxCheckBox, as so:
>
>
>
>    form.add(new AjaxCheckBox("image1_whole", new
> PropertyModel(this, "image1Whole")) {
>
>      private static final long serialVersionUID = 1L;
>
>      @Override
>      protected void onUpdate(AjaxRequestTarget target) {
>        image1PreviewArea.setVisible(!image1PreviewArea.isVisible());
>
>        target.add(image1PreviewArea);
>      }
>
>      @Override
>      protected boolean wantOnSelectionChangedNotifications() {
>        return true;
>      }
>
>    });
>
> The component's onUpdate is never called. What am I missing?
>
> Thanks,
> Martin
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: wicket AjaxCheckBox's onUpdate not called

[Martin A]

The ajaxcheckbox didn't have it and wasn't working so I decided to put it
and still not working. So it doesn't work in both cases.

Thanks,
Martin

On Wed, Nov 2, 2011 at 11:28 AM, Ernesto Reinaldo Barreiro <
reier...@gmail.com> wrote:

> Just guessing... try getting rid of
>
>   @Override
> >  protected boolean wantOnSelectionChangedNotifications() {
> >return true;
> >  }
>
> Ernesto
>
> On Wed, Nov 2, 2011 at 10:25 AM, Martin A  wrote:
> > Hello,
> >
> > In a Page I have an AjaxCheckBox, as so:
> >
> >
> >
> >form.add(new AjaxCheckBox("image1_whole", new
> > PropertyModel(this, "image1Whole")) {
> >
> >  private static final long serialVersionUID = 1L;
> >
> >  @Override
> >  protected void onUpdate(AjaxRequestTarget target) {
> >image1PreviewArea.setVisible(!image1PreviewArea.isVisible());
> >
> >target.add(image1PreviewArea);
> >  }
> >
> >  @Override
> >  protected boolean wantOnSelectionChangedNotifications() {
> >return true;
> >  }
> >
> >});
> >
> > The component's onUpdate is never called. What am I missing?
> >
> > Thanks,
> > Martin
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: How to clear PageMap in Wicket 1.5?

[Andrea Del Bene]

Have you tried session.invalidate()? If you have an 
AuthenticatedWebSession you can also use signOut()

Hi

Upon logging out we need to keep the current user's session to still 
display some information but we want to remove all previous pages from 
the PageMap (or however that is solved in Wicket 1.5 now) so that he 
cannot go back and continue on these pages.
In Wicket 1.4 we found a way to achieve that, basically with  
session.clear()  (plus  session.untouch(getPage())  ). In Wicket 1.5.2 
the clear() method ist still there, but only contains an empty TODO 
comment


How do we clear the previous pages now so that if he goes back, the 
user receives a PageExpiredError ?


Thanks a lot

Matt




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: wicket AjaxCheckBox's onUpdate not called

[Ernesto Reinaldo Barreiro]

Try to make a quick-start so that others can test and see what´s happening?

Regards,

Ernesto

On Wed, Nov 2, 2011 at 10:30 AM, Martin A  wrote:
> The ajaxcheckbox didn't have it and wasn't working so I decided to put it
> and still not working. So it doesn't work in both cases.
>
> Thanks,
> Martin
>
> On Wed, Nov 2, 2011 at 11:28 AM, Ernesto Reinaldo Barreiro <
> reier...@gmail.com> wrote:
>
>> Just guessing... try getting rid of
>>
>>   @Override
>> >      protected boolean wantOnSelectionChangedNotifications() {
>> >        return true;
>> >      }
>>
>> Ernesto
>>
>> On Wed, Nov 2, 2011 at 10:25 AM, Martin A  wrote:
>> > Hello,
>> >
>> > In a Page I have an AjaxCheckBox, as so:
>> >
>> >
>> >
>> >    form.add(new AjaxCheckBox("image1_whole", new
>> > PropertyModel(this, "image1Whole")) {
>> >
>> >      private static final long serialVersionUID = 1L;
>> >
>> >      @Override
>> >      protected void onUpdate(AjaxRequestTarget target) {
>> >        image1PreviewArea.setVisible(!image1PreviewArea.isVisible());
>> >
>> >        target.add(image1PreviewArea);
>> >      }
>> >
>> >      @Override
>> >      protected boolean wantOnSelectionChangedNotifications() {
>> >        return true;
>> >      }
>> >
>> >    });
>> >
>> > The component's onUpdate is never called. What am I missing?
>> >
>> > Thanks,
>> > Martin
>> >
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: How to clear PageMap in Wicket 1.5?

[Martin Grigorov]

I implemented the feature in the ticket Matt created.
Please try it.

On Wed, Nov 2, 2011 at 11:35 AM, Andrea Del Bene  wrote:
> Have you tried session.invalidate()? If you have an AuthenticatedWebSession
> you can also use signOut()
>>
>> Hi
>>
>> Upon logging out we need to keep the current user's session to still
>> display some information but we want to remove all previous pages from the
>> PageMap (or however that is solved in Wicket 1.5 now) so that he cannot go
>> back and continue on these pages.
>> In Wicket 1.4 we found a way to achieve that, basically with
>>  session.clear()  (plus  session.untouch(getPage())  ). In Wicket 1.5.2 the
>> clear() method ist still there, but only contains an empty TODO comment
>>
>> How do we clear the previous pages now so that if he goes back, the user
>> receives a PageExpiredError ?
>>
>> Thanks a lot
>>
>> Matt
>>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Upgrading of Wicket application on server without losing state

[Robert Dahlström]

Well, IF you're really keen on non-intrusive upgrades you can always put 
in a version in the db and make the code handle both old & new version.


But that's admittedly a lot of extra work. Downtime is way easier when 
schemas change and for web-apps the downtime should be easy to keep short.


Regards
Robert

On 11/02/2011 12:38 AM, Igor Vaynberg wrote:

assuming you have no breaking changes to your db schema having no
downtime is relatively easy. while the process sounds involved it can
be easily automated - ie you write it once and from then one deploys
are easy.

* suppose you have two servers SA and SB in a load balancer pool PA
* create a new load balancer pool PB and put into it a server running
the upgraded version of your app SC
* instruct your load balancer to only send new sessions to PB
* wait until any server in pool PA is starved of its sessions and take
it out of the pool, upgrade, and put it into pool PB.
* once PA is empty drop it

this is not so easy if you have breaking schema changes (or changes to
other shared resources like webserivces) because once you upgrade the
schema you cant have any old code accessing it. for such breaking
changes you have to schedule a maintenance window.

-igor


On Tue, Nov 1, 2011 at 3:41 PM, taitai  wrote:

Hi guys,
I was wondering about the following standard scenario:

- application v0.1 deployed to your favorite servlet container
- you want to deploy version v0.2 with minimal downtime and without losing
any session state (because it's a web shop application for example)

Is there a convenient way to shut down a wicket application so that it saves
its complete state to e.g. the filesystem and the next wicket app that boots
up initially reads the state from those files? anyone else handling server
upgrades differently and in a better way?

Thanks!





--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Upgrading-of-Wicket-application-on-server-without-losing-state-tp3965762p3965762.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

wicketstuff-core 1.5.2 released?

[Sebastian]

Hi,

I can see a wicketstuff-core 1.5.2 release in the maven-repo, however in 
github no tag exists and no formal announcement has been made. So my 
question is, what's in it and what happened to the regular announcement?


Regards,

Seb


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Anyone going to Java2days?

[nino martinez wael]

Hi

Im going with a collegue.. Anybody else? Should we meet somewhere at the
conference?


regards Nino

Re: wicketstuff-core 1.5.2 released?

[nino martinez wael]

it's right on the homepage:

http://wicket.apache.org/

But are you thinking of a announcement here on the list?

2011/11/2 Sebastian 

> Hi,
>
> I can see a wicketstuff-core 1.5.2 release in the maven-repo, however in
> github no tag exists and no formal announcement has been made. So my
> question is, what's in it and what happened to the regular announcement?
>
> Regards,
>
> Seb
>
>
> --**--**-
> To unsubscribe, e-mail: 
> users-unsubscribe@wicket.**apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: wicketstuff-core 1.5.2 released?

[Sebastian]

I'm talking about wicketstuff http://wicketstuff.org/, not wicket. The 
releases used to be announced here too.


On 02.11.2011 12:13, nino martinez wael wrote:

it's right on the homepage:

http://wicket.apache.org/

But are you thinking of a announcement here on the list?

2011/11/2 Sebastian


Hi,

I can see a wicketstuff-core 1.5.2 release in the maven-repo, however in
github no tag exists and no formal announcement has been made. So my
question is, what's in it and what happened to the regular announcement?

Regards,

Seb


--**--**-
To unsubscribe, e-mail: 
users-unsubscribe@wicket.**apache.org
For additional commands, e-mail: users-h...@wicket.apache.org








-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Modal Window with Ajax in Firefox

[Andrea Del Bene]

Hi,

can you reproduce your problem in a separate project and upload it 
somewhere? It would help much to understand if this problem is a bug and 
to find a solution.



Hi,

i am sorry that i didnt  reply earlier. I forgot to mention that, when 
I close modal window with form, I show other modal window and it seems 
that javascript opens first window instead of new one.


On 10/27/2011 12:36 AM, Andrea Del Bene wrote:

Hi,
I've tried to reproduce your issue but without success. The modal 
window closes correctly. I've used the last version of Firefox, the 
7.  Java code for my test page is the following:


public class HomePage extends BasePage
{
private static final long serialVersionUID = 1L;

@Override
protected void onInitialize() {
super.onInitialize();

final MyModal myModal = new MyModal("myModal");

add(myModal);

add(new AjaxLink("openForm") {
@Override
public void onClick(AjaxRequestTarget target) {
myModal.show(target);
}
});
}

class MyModal extends ModalWindow {

public MyModal(String id) {
super(id);
MyPanel panel = new MyPanel(getContentId()) {
@Override
public void performAction(AjaxRequestTarget 
target) {

MyModal.this.close(target);
}
};
setContent(panel);

}
}


while the code for MyPanel is this:


public abstract class MyPanel extends Panel {

public MyPanel(String id) {
super(id);

Form form = new Form("form");
 add(form);
 AjaxButton submit = new AjaxButton("submit") {

@Override
protected void onSubmit(AjaxRequestTarget target,
Form form) {
performAction(target);

}
@Override
protected void onError(AjaxRequestTarget target,
Form form) {
}
   };
form.add(submit);
}
public abstract void performAction(AjaxRequestTarget target);
}
Thanks for quick reply. I close modal window in onError method of 
AjaxButton. Here is code:


public class MyModal extends ModalWindow {

public MyModal(String id) {
super(id);
MyPanel panel = new MyPanel(getContentId()) {
public void onError(AjaxRequestTarget target) {
MyModal.this.close(target);
}
}
setContent(panel);

}
}

and MyPanel class:

public abstract class MyPanel extends Panel {
public MyPanel(String id) {
super(id);
Form form = new Form("form);
 add(form);
 AjaxButton submit = new AjaxButton("submit) {
  public void onError(AjaxRequestTarget target, Form 
parent) {

 MyPanel.this.onError(target);
  }
  public void onSubmit(AjaxRequestTarget target, Form 
parent) {

//process form
  }
}
form.add(submit);

//remaining form components
}

public abstract void onError(AjaxRequestTarget target);
}





-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org






-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: wicketstuff-core 1.5.2 released?

[Martijn Dashorst]

Probably Michael hasn't gotten around to tagging and announcing.

Martijn

On Wed, Nov 2, 2011 at 12:08 PM, Sebastian  wrote:
> Hi,
>
> I can see a wicketstuff-core 1.5.2 release in the maven-repo, however in
> github no tag exists and no formal announcement has been made. So my
> question is, what's in it and what happened to the regular announcement?
>
> Regards,
>
> Seb
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: wicketstuff-core 1.5.2 released?

[Martin Grigorov]

Wicket is released, but WicketStuff is not yet.
Usually Michael releases it but I guess anyone can do it by following
his " howto release steps" in the wiki.

On Wed, Nov 2, 2011 at 1:13 PM, nino martinez wael
 wrote:
> it's right on the homepage:
>
> http://wicket.apache.org/
>
> But are you thinking of a announcement here on the list?
>
> 2011/11/2 Sebastian 
>
>> Hi,
>>
>> I can see a wicketstuff-core 1.5.2 release in the maven-repo, however in
>> github no tag exists and no formal announcement has been made. So my
>> question is, what's in it and what happened to the regular announcement?
>>
>> Regards,
>>
>> Seb
>>
>>
>> --**--**-
>> To unsubscribe, e-mail: 
>> users-unsubscribe@wicket.**apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Handling form ajax submit on enter key in form field

[Bas Gooren]

Hi,

Yes we currently do

form.add( new AjaxFormSubmitBehavior(form, "onsubmit"));

I've been testing what you describe (enter keys calls submit button), 
and this works.
99% of the time we only have one submit button, so that's good enough 
for us.


Thanks!

Op 1-11-2011 23:54, schreef Andrea Del Bene:

Hi,

if your form has just one submitting button, pressing enter key on a 
field should submit it by default. Anyway, I would solve this problem 
using a JavaScript library like JQuery rather then using a Wicket Ajax 
behavior. Can you give us more details about your 
AjaxFormSubmitBehavior? Are you using it like this:


form.add( new AjaxFormSubmitBehavior("onsubmit"))

Hi all,

To handle the case where somebody hits enter in a form field which 
has an (Ajax)Button to submit the entire form by ajax, we used an 
AjaxFormSubmitBehavior attached to the form's onsubmit in wicket 1.4.x


After upgrading to 1.5 our ajax indicator was not hidden after the 
ajax request, wich asked for some investigating.


It turns out, this is what happens:
- onsubmit is called by browser and calls wicketSubmitFormById()
- that method calls Wicket.Ajax.Call.SubmitForm() which in turn calls 
onsubmit again


The issue with the ajax indicator image remaining visible is simply 
due to showIncrementally being called twice, and hideIncrementally 
only once.


But let's ignore that for now, the bigger issue is how do we properly 
handle this use case? We chose a form onsubmit handler to prevent 
adding an onKeyUp handler (and checking for enter key) to all form 
fields, as this seems more elegant.
Having the form's onsubmit delegate to the ajaxbutton will create the 
exact same problem: a loop.


How do others solve this in 1.5?




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Anyone going to Java2days?

[Martin Grigorov]

In Sofia, Bulgaria ?
I'll miss it this year but Andrew Lombardi (kinabalu) will be there
and will present Wicket twice.

On Wed, Nov 2, 2011 at 1:11 PM, nino martinez wael
 wrote:
> Hi
>
> Im going with a collegue.. Anybody else? Should we meet somewhere at the
> conference?
>
>
> regards Nino
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Handling form ajax submit on enter key in form field

[Martin Grigorov]

On Wed, Nov 2, 2011 at 1:29 PM, Bas Gooren  wrote:
> Hi,
>
> Yes we currently do
>
> form.add( new AjaxFormSubmitBehavior(form, "onsubmit"));
>
> I've been testing what you describe (enter keys calls submit button), and
> this works.
> 99% of the time we only have one submit button, so that's good enough for
> us.

You can use 
org.apache.wicket.markup.html.form.Form.setDefaultButton(IFormSubmittingComponent)
if you have two or more submitting buttons.

>
> Thanks!
>
> Op 1-11-2011 23:54, schreef Andrea Del Bene:
>>
>> Hi,
>>
>> if your form has just one submitting button, pressing enter key on a field
>> should submit it by default. Anyway, I would solve this problem using a
>> JavaScript library like JQuery rather then using a Wicket Ajax behavior. Can
>> you give us more details about your AjaxFormSubmitBehavior? Are you using it
>> like this:
>>
>> form.add( new AjaxFormSubmitBehavior("onsubmit"))
>>>
>>> Hi all,
>>>
>>> To handle the case where somebody hits enter in a form field which has an
>>> (Ajax)Button to submit the entire form by ajax, we used an
>>> AjaxFormSubmitBehavior attached to the form's onsubmit in wicket 1.4.x
>>>
>>> After upgrading to 1.5 our ajax indicator was not hidden after the ajax
>>> request, wich asked for some investigating.
>>>
>>> It turns out, this is what happens:
>>> - onsubmit is called by browser and calls wicketSubmitFormById()
>>> - that method calls Wicket.Ajax.Call.SubmitForm() which in turn calls
>>> onsubmit again
>>>
>>> The issue with the ajax indicator image remaining visible is simply due
>>> to showIncrementally being called twice, and hideIncrementally only once.
>>>
>>> But let's ignore that for now, the bigger issue is how do we properly
>>> handle this use case? We chose a form onsubmit handler to prevent adding an
>>> onKeyUp handler (and checking for enter key) to all form fields, as this
>>> seems more elegant.
>>> Having the form's onsubmit delegate to the ajaxbutton will create the
>>> exact same problem: a loop.
>>>
>>> How do others solve this in 1.5?
>>>
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Handling form ajax submit on enter key in form field

[Bas Gooren]

Cool, thanks!

How about browser support for this? We've tested with current Firefox 
and Chrome releases and it works like a charm. But how about IE < 9 ?


Op 2-11-2011 12:33, schreef Martin Grigorov:

On Wed, Nov 2, 2011 at 1:29 PM, Bas Gooren  wrote:

Hi,

Yes we currently do

form.add( new AjaxFormSubmitBehavior(form, "onsubmit"));

I've been testing what you describe (enter keys calls submit button), and
this works.
99% of the time we only have one submit button, so that's good enough for
us.

You can use 
org.apache.wicket.markup.html.form.Form.setDefaultButton(IFormSubmittingComponent)
if you have two or more submitting buttons.


Thanks!

Op 1-11-2011 23:54, schreef Andrea Del Bene:

Hi,

if your form has just one submitting button, pressing enter key on a field
should submit it by default. Anyway, I would solve this problem using a
JavaScript library like JQuery rather then using a Wicket Ajax behavior. Can
you give us more details about your AjaxFormSubmitBehavior? Are you using it
like this:

form.add( new AjaxFormSubmitBehavior("onsubmit"))

Hi all,

To handle the case where somebody hits enter in a form field which has an
(Ajax)Button to submit the entire form by ajax, we used an
AjaxFormSubmitBehavior attached to the form's onsubmit in wicket 1.4.x

After upgrading to 1.5 our ajax indicator was not hidden after the ajax
request, wich asked for some investigating.

It turns out, this is what happens:
- onsubmit is called by browser and calls wicketSubmitFormById()
- that method calls Wicket.Ajax.Call.SubmitForm() which in turn calls
onsubmit again

The issue with the ajax indicator image remaining visible is simply due
to showIncrementally being called twice, and hideIncrementally only once.

But let's ignore that for now, the bigger issue is how do we properly
handle this use case? We chose a form onsubmit handler to prevent adding an
onKeyUp handler (and checking for enter key) to all form fields, as this
seems more elegant.
Having the form's onsubmit delegate to the ajaxbutton will create the
exact same problem: a loop.

How do others solve this in 1.5?



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: wicketstuff-core 1.5.2 released?

[Sebastian]

wicketstuff 1.5.2 has been released already: 
http://repo1.maven.org/maven2/org/wicketstuff/wicketstuff-core/1.5.2/


However, especially if - as you say - anyone can do this, it is even 
more relevant to understand the release's state and the included changes.


On 02.11.2011 12:31, Martin Grigorov wrote:

Wicket is released, but WicketStuff is not yet.
Usually Michael releases it but I guess anyone can do it by following
his " howto release steps" in the wiki.

On Wed, Nov 2, 2011 at 1:13 PM, nino martinez wael
  wrote:

it's right on the homepage:

http://wicket.apache.org/

But are you thinking of a announcement here on the list?

2011/11/2 Sebastian


Hi,

I can see a wicketstuff-core 1.5.2 release in the maven-repo, however in
github no tag exists and no formal announcement has been made. So my
question is, what's in it and what happened to the regular announcement?

Regards,

Seb


--**--**-
To unsubscribe, e-mail: 
users-unsubscribe@wicket.**apache.org
For additional commands, e-mail: users-h...@wicket.apache.org












-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Anyone going to Java2days?

[nino martinez wael]

Yup thats the one :)

Saw Andrew where presentating..

2011/11/2 Martin Grigorov 

> In Sofia, Bulgaria ?
> I'll miss it this year but Andrew Lombardi (kinabalu) will be there
> and will present Wicket twice.
>
> On Wed, Nov 2, 2011 at 1:11 PM, nino martinez wael
>  wrote:
> > Hi
> >
> > Im going with a collegue.. Anybody else? Should we meet somewhere at the
> > conference?
> >
> >
> > regards Nino
> >
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: wicketstuff-core 1.5.2 released?

[Martin Grigorov]

On Wed, Nov 2, 2011 at 1:48 PM, Sebastian  wrote:
> wicketstuff 1.5.2 has been released already:
> http://repo1.maven.org/maven2/org/wicketstuff/wicketstuff-core/1.5.2/

I didn't notice.

>
> However, especially if - as you say - anyone can do this, it is even more
> relevant to understand the release's state and the included changes.

$ git ls-remote origin

says that the last tag is 1.5.1
even GitHub web interface doesn't show tag 1.5.2
so it is not possible to generate the shortlog between 1.5.1 and 1.5.2

>
> On 02.11.2011 12:31, Martin Grigorov wrote:
>>
>> Wicket is released, but WicketStuff is not yet.
>> Usually Michael releases it but I guess anyone can do it by following
>> his " howto release steps" in the wiki.
>>
>> On Wed, Nov 2, 2011 at 1:13 PM, nino martinez wael
>>   wrote:
>>>
>>> it's right on the homepage:
>>>
>>> http://wicket.apache.org/
>>>
>>> But are you thinking of a announcement here on the list?
>>>
>>> 2011/11/2 Sebastian
>>>
 Hi,

 I can see a wicketstuff-core 1.5.2 release in the maven-repo, however in
 github no tag exists and no formal announcement has been made. So my
 question is, what's in it and what happened to the regular announcement?

 Regards,

 Seb



 --**--**-
 To unsubscribe, e-mail:
 users-unsubscribe@wicket.**apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org


>>>
>>
>>
>>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: How to clear PageMap in Wicket 1.5?

[Matthias Keller]

Hi Martin

Thanks for the quick reply.
The fix doesn't work for me though, I can still go back and press reload 
or do anything I like.
If I use session.replaceSession() it works as expected but as a side 
effect also changes the JSESSIONID which usually isn't what you want...


I'm using it like that in an onClick event of a button (and the session 
is NOT temporary):


if (getSession().isTemporary() == false) {
getSession().getPageManager().sessionExpired(getId());
}

setResponsePage(new ConfirmationPage(...));

Maybe it could be some kind of special situation like it was in Wicket 
1.4 where I manually had to untouch the current page to avoid it still 
being stored at the end of the request...?


Matt


On 2011-11-02 10:40, Martin Grigorov wrote:

I implemented the feature in the ticket Matt created.
Please try it.

On Wed, Nov 2, 2011 at 11:35 AM, Andrea Del Bene  wrote:

Have you tried session.invalidate()? If you have an AuthenticatedWebSession
you can also use signOut()

Hi

Upon logging out we need to keep the current user's session to still
display some information but we want to remove all previous pages from the
PageMap (or however that is solved in Wicket 1.5 now) so that he cannot go
back and continue on these pages.
In Wicket 1.4 we found a way to achieve that, basically with
  session.clear()  (plus  session.untouch(getPage())  ). In Wicket 1.5.2 the
clear() method ist still there, but only contains an empty TODO comment

How do we clear the previous pages now so that if he goes back, the user
receives a PageExpiredError ?

Thanks a lot

Matt





smime.p7s
Description: S/MIME Cryptographic Signature

Re: How to clear PageMap in Wicket 1.5?

[Martin Grigorov]

On Wed, Nov 2, 2011 at 2:09 PM, Matthias Keller
 wrote:
> Hi Martin
>
> Thanks for the quick reply.
> The fix doesn't work for me though, I can still go back and press reload or
> do anything I like.
> If I use session.replaceSession() it works as expected but as a side effect
> also changes the JSESSIONID which usually isn't what you want...
>
> I'm using it like that in an onClick event of a button (and the session is
> NOT temporary):
>
>        if (getSession().isTemporary() == false) {
>            getSession().getPageManager().sessionExpired(getId());
>        }

This code does the same as in 1.4 with page maps.
#untouchPage() as internal API in 1.4 and is not ported to 1.5.

Try by override Session#detach() and do:
super.detach();
clear();

>
>        setResponsePage(new ConfirmationPage(...));
>
> Maybe it could be some kind of special situation like it was in Wicket 1.4
> where I manually had to untouch the current page to avoid it still being
> stored at the end of the request...?
>
> Matt
>
>
> On 2011-11-02 10:40, Martin Grigorov wrote:
>>
>> I implemented the feature in the ticket Matt created.
>> Please try it.
>>
>> On Wed, Nov 2, 2011 at 11:35 AM, Andrea Del Bene
>>  wrote:
>>>
>>> Have you tried session.invalidate()? If you have an
>>> AuthenticatedWebSession
>>> you can also use signOut()

 Hi

 Upon logging out we need to keep the current user's session to still
 display some information but we want to remove all previous pages from
 the
 PageMap (or however that is solved in Wicket 1.5 now) so that he cannot
 go
 back and continue on these pages.
 In Wicket 1.4 we found a way to achieve that, basically with
  session.clear()  (plus  session.untouch(getPage())  ). In Wicket 1.5.2
 the
 clear() method ist still there, but only contains an empty TODO
 comment

 How do we clear the previous pages now so that if he goes back, the user
 receives a PageExpiredError ?

 Thanks a lot

 Matt
>
>
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

StatelessPage & Ajax

[Rodrigo Pereira]

Hi,
I am new to wicket and I am facing some issues with stateless page and ajax.
When I open 2 tabs with stateless pages,  i got page expired exception 
after making any ajax request on the 1st, while the 2nd tab keeps ok.
It seems like these 2 pages is never serialized, which seems to be 
correct, however I can only see 1 entry in my sessionCahe. It seems like 
it is only keeping the last accessed page in there, is it correct? Is 
there a way to tell wicket to keep the last XX pages in the sessionCache?


Regards,
Rodrigo Pereira

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: StatelessPage & Ajax

[Martin Grigorov]

On Wed, Nov 2, 2011 at 2:57 PM, Rodrigo Pereira  wrote:
>
> Hi,
> I am new to wicket and I am facing some issues with stateless page and ajax.
> When I open 2 tabs with stateless pages,  i got page expired exception after
> making any ajax request on the 1st, while the 2nd tab keeps ok.
> It seems like these 2 pages is never serialized, which seems to be correct,
> however I can only see 1 entry in my sessionCahe. It seems like it is only
> keeping the last accessed page in there, is it correct? Is there a way to
> tell wicket to keep the last XX pages in the sessionCache?

Correct.
Read more about this topic at: https://cwiki.apache.org/confluence/x/qIaoAQ

>
> Regards,
> Rodrigo Pereira
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: UTF-8 encoding RFE for warning?

[Wilhelmsen Tor Iver]

> It's a known fact for me aswell now :)

Note that even though properties files need to be in the "default" encoding, 
you can use non-iso-latin characters by way of the \u syntax, though a bit 
more cumbersome than "raw" Unicode characters.

- Tor Iver

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: StatelessPage & Ajax

[Rodrigo Pereira]

Thanks for your reply.
It seems like that it is still only keeping 1 entry in my sessionCache, 
eventhough I added the following in my MyApp.init()


super.init();

setPageManagerProvider( new DefaultPageManagerProvider( this ) {

   @Override
   protected IDataStore newDataStore() {

 return new HttpSessionDataStore( getPageManagerContext(), new 
PageNumberEvictionStrategy( 20 ) );

   }
} );

Is that all?

Thanks,
Rodrigo Pereira

On 11/02/2011 02:02 PM, Martin Grigorov wrote:

On Wed, Nov 2, 2011 at 2:57 PM, Rodrigo Pereira  wrote:

Hi,
I am new to wicket and I am facing some issues with stateless page and ajax.
When I open 2 tabs with stateless pages,  i got page expired exception after
making any ajax request on the 1st, while the 2nd tab keeps ok.
It seems like these 2 pages is never serialized, which seems to be correct,
however I can only see 1 entry in my sessionCahe. It seems like it is only
keeping the last accessed page in there, is it correct? Is there a way to
tell wicket to keep the last XX pages in the sessionCache?

Correct.
Read more about this topic at: https://cwiki.apache.org/confluence/x/qIaoAQ


Regards,
Rodrigo Pereira

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org








-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: StatelessPage & Ajax

[Martin Grigorov]

Do you use jolira's stateless components ?
Because for stateless Ajax a new page instance is created for each
request. I'm not sure why Wicket tries to find the old page. Maybe the
page is not stateless after all.

On Wed, Nov 2, 2011 at 4:04 PM, Rodrigo Pereira  wrote:
> Thanks for your reply.
> It seems like that it is still only keeping 1 entry in my sessionCache,
> eventhough I added the following in my MyApp.init()
>
> super.init();
>
> setPageManagerProvider( new DefaultPageManagerProvider( this ) {
>
>   @Override
>   protected IDataStore newDataStore() {
>
>         return new HttpSessionDataStore( getPageManagerContext(), new
> PageNumberEvictionStrategy( 20 ) );
>   }
> } );
>
> Is that all?
>
> Thanks,
> Rodrigo Pereira
>
> On 11/02/2011 02:02 PM, Martin Grigorov wrote:
>>
>> On Wed, Nov 2, 2011 at 2:57 PM, Rodrigo Pereira
>>  wrote:
>>>
>>> Hi,
>>> I am new to wicket and I am facing some issues with stateless page and
>>> ajax.
>>> When I open 2 tabs with stateless pages,  i got page expired exception
>>> after
>>> making any ajax request on the 1st, while the 2nd tab keeps ok.
>>> It seems like these 2 pages is never serialized, which seems to be
>>> correct,
>>> however I can only see 1 entry in my sessionCahe. It seems like it is
>>> only
>>> keeping the last accessed page in there, is it correct? Is there a way to
>>> tell wicket to keep the last XX pages in the sessionCache?
>>
>> Correct.
>> Read more about this topic at:
>> https://cwiki.apache.org/confluence/x/qIaoAQ
>>
>>> Regards,
>>> Rodrigo Pereira
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>
>>>
>>
>>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: Upgrading of Wicket application on server without losing state

[Wilhelmsen Tor Iver]

> Is there a convenient way to shut down a wicket application so that it saves
> its complete state to e.g. the filesystem and the next wicket app that boots
> up initially reads the state from those files? anyone else handling server
> upgrades differently and in a better way?

Well, if you put the Wicket session in the Http session (which is the default 
if I'm not mistaken) then e.g. Tomcat will serialize the sessions to disk on a 
controlled shutdown, and reread them on startup. Keep in mind serialVersionUID 
etc. Then the sessions becaome the responsibility of the container.

- Tor Iver

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: abort loading lazy components

[Michal Wegrzyn]

I've updated to Wicket 1.5.2 and I can see also some warnings surrounding 
exceptions.
Is it a bug or am I missing something?

Below full log:

15:31:11.847 user [http--2] WARN  o.a.w.r.h.render.WebPageRenderer - The 
Buffered response should be handled by BufferedResponseRequestHandler
15:32:24.028 user [http--5] ERROR o.a.wicket.DefaultExceptionMapper - 
Unexpected error occurred
org.apache.wicket.request.handler.ComponentNotFoundException: Could not find 
component 'folders:listContainer:itemList:29:itemPanel:folder:children' on page 
'class package.MyPage
at 
org.apache.wicket.request.handler.PageAndComponentProvider.getComponent(PageAndComponentProvider.java:167)
at 
org.apache.wicket.request.handler.ListenerInterfaceRequestHandler.getComponent(ListenerInterfaceRequestHandler.java:92)
at 
org.apache.wicket.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:169)
at 
org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:750)
at 
org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
at 
org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:252)
at 
org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:209)
at 
org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:280)
at 
org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:162)
at 
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:218)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
package.MyRequestContextFilter.doFilter(MyRequestContextFilter.java:43)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:368)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:109)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:83)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
at 
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:97)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
at 
org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:100)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
at 
org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:78)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
at 
org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
at 
org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:35)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
at 
org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:187)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
at 
org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
at 
org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:79)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
at 
org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:169)
at 
org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:237)
at 
org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167)
at 
org.apache.catalina.core.ApplicationFilte

Re: StatelessPage & Ajax

[Rodrigo Pereira]

Hi,
no, I don't use it should I?
I have some AjaxEditableLabel on that page, so during onSubmit I update 
the DB and show the new value for that field. Is it possible to look for 
the page due to this update?


Regards,
Rodrigo Pereira

On 11/02/2011 03:26 PM, Martin Grigorov wrote:

Do you use jolira's stateless components ?
Because for stateless Ajax a new page instance is created for each
request. I'm not sure why Wicket tries to find the old page. Maybe the
page is not stateless after all.

On Wed, Nov 2, 2011 at 4:04 PM, Rodrigo Pereira  wrote:

Thanks for your reply.
It seems like that it is still only keeping 1 entry in my sessionCache,
eventhough I added the following in my MyApp.init()

super.init();

setPageManagerProvider( new DefaultPageManagerProvider( this ) {

   @Override
   protected IDataStore newDataStore() {

 return new HttpSessionDataStore( getPageManagerContext(), new
PageNumberEvictionStrategy( 20 ) );
   }
} );

Is that all?

Thanks,
Rodrigo Pereira

On 11/02/2011 02:02 PM, Martin Grigorov wrote:

On Wed, Nov 2, 2011 at 2:57 PM, Rodrigo Pereira
  wrote:

Hi,
I am new to wicket and I am facing some issues with stateless page and
ajax.
When I open 2 tabs with stateless pages,  i got page expired exception
after
making any ajax request on the 1st, while the 2nd tab keeps ok.
It seems like these 2 pages is never serialized, which seems to be
correct,
however I can only see 1 entry in my sessionCahe. It seems like it is
only
keeping the last accessed page in there, is it correct? Is there a way to
tell wicket to keep the last XX pages in the sessionCache?

Correct.
Read more about this topic at:
https://cwiki.apache.org/confluence/x/qIaoAQ


Regards,
Rodrigo Pereira

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org






-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org








-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Upgrading of Wicket application on server without losing state

[Doug Leeper]

We are using Weblogic 10.3 and it has a nice feature that allows two versions
of the app to run concurrently.

What happens is this:
- V1 is running and sessions are currently active
- deploy V2
- existing V1 sessions will continue to use V1 code
- new request (i.e. new session) will use V2

This is OOTB nothing needed on our code or configuration.  No need to bring
down an app or server or cluster.  Happens automatically.

Very nice from a maintenance and administration stand point.

Negative: WL is expensive

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Upgrading-of-Wicket-application-on-server-without-losing-state-tp3965762p3974603.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: abort loading lazy components

[Martin Grigorov]

On Wed, Nov 2, 2011 at 4:49 PM, Michal Wegrzyn  wrote:
> I've updated to Wicket 1.5.2 and I can see also some warnings surrounding 
> exceptions.
> Is it a bug or am I missing something?
>
> Below full log:
>
> 15:31:11.847 user [http--2] WARN  o.a.w.r.h.render.WebPageRenderer - The 
> Buffered response should be handled by BufferedResponseRequestHandler

WICKET-4163
More or less harmless.

> 15:32:24.028 user [http--5] ERROR o.a.wicket.DefaultExceptionMapper - 
> Unexpected error occurred
> org.apache.wicket.request.handler.ComponentNotFoundException: Could not find 
> component 'folders:listContainer:itemList:29:itemPanel:folder:children' on 
> page 'class package.MyPage

Do you know how this is triggered ?

>        at 
> org.apache.wicket.request.handler.PageAndComponentProvider.getComponent(PageAndComponentProvider.java:167)
>        at 
> org.apache.wicket.request.handler.ListenerInterfaceRequestHandler.getComponent(ListenerInterfaceRequestHandler.java:92)
>        at 
> org.apache.wicket.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:169)
>        at 
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:750)
>        at 
> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
>        at 
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:252)
>        at 
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:209)
>        at 
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:280)
>        at 
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:162)
>        at 
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:218)
>        at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
>        at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>        at 
> package.MyRequestContextFilter.doFilter(MyRequestContextFilter.java:43)
>        at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
>        at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>        at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:368)
>        at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:109)
>        at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:83)
>        at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
>        at 
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:97)
>        at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
>        at 
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:100)
>        at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
>        at 
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:78)
>        at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
>        at 
> org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54)
>        at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
>        at 
> org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:35)
>        at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
>        at 
> org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:187)
>        at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
>        at 
> org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:105)
>        at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
>        at 
> org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:79)
>        at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380)
>        at 
> org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:169)
>        

Re: StatelessPage & Ajax

[Martin Grigorov]

On Wed, Nov 2, 2011 at 4:50 PM, Rodrigo Pereira  wrote:
> Hi,
> no, I don't use it should I?

Yes.
Wicket's default Ajax components/behaviors are stateful. I.e. the page
is also stateful and should be stored but for some reason it seems it
is not ...

> I have some AjaxEditableLabel on that page, so during onSubmit I update the
> DB and show the new value for that field. Is it possible to look for the
> page due to this update?
>
> Regards,
> Rodrigo Pereira
>
> On 11/02/2011 03:26 PM, Martin Grigorov wrote:
>>
>> Do you use jolira's stateless components ?
>> Because for stateless Ajax a new page instance is created for each
>> request. I'm not sure why Wicket tries to find the old page. Maybe the
>> page is not stateless after all.
>>
>> On Wed, Nov 2, 2011 at 4:04 PM, Rodrigo Pereira
>>  wrote:
>>>
>>> Thanks for your reply.
>>> It seems like that it is still only keeping 1 entry in my sessionCache,
>>> eventhough I added the following in my MyApp.init()
>>>
>>> super.init();
>>>
>>> setPageManagerProvider( new DefaultPageManagerProvider( this ) {
>>>
>>>   @Override
>>>   protected IDataStore newDataStore() {
>>>
>>>         return new HttpSessionDataStore( getPageManagerContext(), new
>>> PageNumberEvictionStrategy( 20 ) );
>>>   }
>>> } );
>>>
>>> Is that all?
>>>
>>> Thanks,
>>> Rodrigo Pereira
>>>
>>> On 11/02/2011 02:02 PM, Martin Grigorov wrote:

 On Wed, Nov 2, 2011 at 2:57 PM, Rodrigo Pereira
  wrote:
>
> Hi,
> I am new to wicket and I am facing some issues with stateless page and
> ajax.
> When I open 2 tabs with stateless pages,  i got page expired exception
> after
> making any ajax request on the 1st, while the 2nd tab keeps ok.
> It seems like these 2 pages is never serialized, which seems to be
> correct,
> however I can only see 1 entry in my sessionCahe. It seems like it is
> only
> keeping the last accessed page in there, is it correct? Is there a way
> to
> tell wicket to keep the last XX pages in the sessionCache?

 Correct.
 Read more about this topic at:
 https://cwiki.apache.org/confluence/x/qIaoAQ

> Regards,
> Rodrigo Pereira
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>
>>>
>>
>>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Upgrading of Wicket application on server without losing state

[Martin Grigorov]

On Wed, Nov 2, 2011 at 4:51 PM, Doug Leeper  wrote:
> We are using Weblogic 10.3 and it has a nice feature that allows two versions
> of the app to run concurrently.

http://www.tomcatexpert.com/blog/2011/05/31/parallel-deployment-tomcat-7

>
> What happens is this:
> - V1 is running and sessions are currently active
> - deploy V2
> - existing V1 sessions will continue to use V1 code
> - new request (i.e. new session) will use V2
>
> This is OOTB nothing needed on our code or configuration.  No need to bring
> down an app or server or cluster.  Happens automatically.
>
> Very nice from a maintenance and administration stand point.
>
> Negative: WL is expensive
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/Upgrading-of-Wicket-application-on-server-without-losing-state-tp3965762p3974603.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: abort loading lazy components

[Michal Wegrzyn]

It is triggered when there is already new "itemList" (it extends DataView), so 
I suppose that 
PageAndComponentProvider looks for "itemList:29", which does not exists anymore.

Scenario:

- Page is loaded but lazy components 
('folders:listContainer:itemList:itemPanel:folder:children') are still loading
- User triggers folder change (itemList is replaced)
- Exception occurs

If user triggers folder change when lazy components are completely loaded (or 
during loading the last one) there is no exception at all.

Best Regards,
Michal Wegrzyn

-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org] 
Sent: Wednesday, November 02, 2011 15:54
To: users@wicket.apache.org
Subject: Re: abort loading lazy components

On Wed, Nov 2, 2011 at 4:49 PM, Michal Wegrzyn  wrote:
> 15:32:24.028 user [http--5] ERROR o.a.wicket.DefaultExceptionMapper - 
> Unexpected error occurred
> org.apache.wicket.request.handler.ComponentNotFoundException: Could not find 
> component 'folders:listContainer:itemList:29:itemPanel:folder:children' on 
> page 'class package.MyPage

Do you know how this is triggered ?

Re: StatelessPage & Ajax

[Rodrigo Pereira]

If it does not store my page anywhere, how does it know which object to 
update? I mean, i pass in the object used on this page as modal



On 11/02/2011 03:56 PM, Martin Grigorov wrote:

On Wed, Nov 2, 2011 at 4:50 PM, Rodrigo Pereira  wrote:

Hi,
no, I don't use it should I?

Yes.
Wicket's default Ajax components/behaviors are stateful. I.e. the page
is also stateful and should be stored but for some reason it seems it
is not ...


I have some AjaxEditableLabel on that page, so during onSubmit I update the
DB and show the new value for that field. Is it possible to look for the
page due to this update?

Regards,
Rodrigo Pereira

On 11/02/2011 03:26 PM, Martin Grigorov wrote:

Do you use jolira's stateless components ?
Because for stateless Ajax a new page instance is created for each
request. I'm not sure why Wicket tries to find the old page. Maybe the
page is not stateless after all.

On Wed, Nov 2, 2011 at 4:04 PM, Rodrigo Pereira
  wrote:

Thanks for your reply.
It seems like that it is still only keeping 1 entry in my sessionCache,
eventhough I added the following in my MyApp.init()

super.init();

setPageManagerProvider( new DefaultPageManagerProvider( this ) {

   @Override
   protected IDataStore newDataStore() {

 return new HttpSessionDataStore( getPageManagerContext(), new
PageNumberEvictionStrategy( 20 ) );
   }
} );

Is that all?

Thanks,
Rodrigo Pereira

On 11/02/2011 02:02 PM, Martin Grigorov wrote:

On Wed, Nov 2, 2011 at 2:57 PM, Rodrigo Pereira
  wrote:

Hi,
I am new to wicket and I am facing some issues with stateless page and
ajax.
When I open 2 tabs with stateless pages,  i got page expired exception
after
making any ajax request on the 1st, while the 2nd tab keeps ok.
It seems like these 2 pages is never serialized, which seems to be
correct,
however I can only see 1 entry in my sessionCahe. It seems like it is
only
keeping the last accessed page in there, is it correct? Is there a way
to
tell wicket to keep the last XX pages in the sessionCache?

Correct.
Read more about this topic at:
https://cwiki.apache.org/confluence/x/qIaoAQ


Regards,
Rodrigo Pereira

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org






-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org








-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: navomatic example doesnt´t work

[jjg]

I am new to Wicket and had the same
issue.(http://wicket.apache.org/learn/examples/navomatic.html)
Updated the code to addToBorder(), and it started working. 

Re: navomatic example doesnt´t work

[Martin Grigorov]

Fixed with r1196632. Will be updated on the site soon
Thanks.

On Wed, Nov 2, 2011 at 4:03 PM, jjg  wrote:
> I am new to Wicket and had the same
> issue.(http://wicket.apache.org/learn/examples/navomatic.html)
> Updated the code to addToBorder(), and it started working.  image='smiley_beam.gif
>
>
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/navomatic-example-doesnt-t-work-tp3029232p3973360.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Error with tree component with 1.5.2

[PDiefent]

The same problem occurs if I use a PackageResourceReference as an image model
and try to update it in an AjaxLink. When erasing the toggleIcon component
from the target.add method, the error doesn't occur.

/**
 * @author Peter Diefenthäler
 * Link to toggle visibility of a dependent component.
 * 
 * Make sure that Component is Ajax enabled:
 * comp.setOutputMarkupPlaceholderTag(true);  
 */
public class ToggleLink extends AjaxFallbackLink {
private static final long serialVersionUID = 1L;
private static final Log LOG = LogFactory.getLog(ToggleLink.class);
private static final PackageResourceReference RES_MAXIMIZED = new
PackageResourceReference(ToggleLink.class,"icon_min_container.gif");
private static final PackageResourceReference RES_MINIMIZED = new
PackageResourceReference(ToggleLink.class,"icon_max_container.gif");
private final Image toggleIcon = new Image("toggleIcon",new
PropertyModel(this,"imgResource")); 

@SuppressWarnings("unused")
private PackageResourceReference imgResource;
private final Component toggleComp;

/**
 * Constructor
 * 
 * @param id
 *Identifier
 * @param comp
 *Content component to toggle visibility of
 */
public ToggleLink(String id, final Component comp) {
super(id);
this.setDefaultModel(new 
PropertyModel(comp,"visible"));
this.toggleComp = comp;
syncImg();
add(toggleIcon.setOutputMarkupId(true));
}

@Override
public void onClick(AjaxRequestTarget target) {
LOG.debug("toggle ...");
toggleComp.setVisible(!this.getModel().getObject());
syncImg();
LOG.debug("visible: " + toggleComp.isVisible());
target.add(toggleIcon,toggleComp);
}

private void syncImg() {
imgResource =  this.getModel().getObject() ? RES_MAXIMIZED :
RES_MINIMIZED;
}
}

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Error-with-tree-component-with-1-5-2-tp3956513p3978018.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Error with tree component with 1.5.2

[Martin Grigorov]

Hi,

I have Maven-ized your quickstart app in the ticket because I don't
use Eclipse WTP.
Unfortunately I wasn't able to reproduce this problem with it.
Please modify it so that it fail.

On Wed, Nov 2, 2011 at 6:58 PM, PDiefent  wrote:
> The same problem occurs if I use a PackageResourceReference as an image model
> and try to update it in an AjaxLink. When erasing the toggleIcon component
> from the target.add method, the error doesn't occur.
>
> /**
>  * @author Peter Diefenthäler
>  * Link to toggle visibility of a dependent component.
>  * 
>  * Make sure that Component is Ajax enabled:
>  * comp.setOutputMarkupPlaceholderTag(true);
>  */
> public class ToggleLink extends AjaxFallbackLink {
>        private static final long serialVersionUID = 1L;
>        private static final Log LOG = LogFactory.getLog(ToggleLink.class);
>        private static final PackageResourceReference RES_MAXIMIZED = new
> PackageResourceReference(ToggleLink.class,"icon_min_container.gif");
>        private static final PackageResourceReference RES_MINIMIZED = new
> PackageResourceReference(ToggleLink.class,"icon_max_container.gif");
>        private final Image toggleIcon = new Image("toggleIcon",new
> PropertyModel(this,"imgResource"));
>
>        @SuppressWarnings("unused")
>        private PackageResourceReference imgResource;
>        private final Component toggleComp;
>
>        /**
>         * Constructor
>         *
>         * @param id
>         *            Identifier
>         * @param comp
>         *            Content component to toggle visibility of
>         */
>        public ToggleLink(String id, final Component comp) {
>                super(id);
>                this.setDefaultModel(new 
> PropertyModel(comp,"visible"));
>                this.toggleComp = comp;
>                syncImg();
>                add(toggleIcon.setOutputMarkupId(true));
>        }
>
>        @Override
>        public void onClick(AjaxRequestTarget target) {
>                LOG.debug("toggle ...");
>                toggleComp.setVisible(!this.getModel().getObject());
>                syncImg();
>                LOG.debug("visible: " + toggleComp.isVisible());
>                target.add(toggleIcon,toggleComp);
>        }
>
>        private void syncImg() {
>                imgResource =  this.getModel().getObject() ? RES_MAXIMIZED :
> RES_MINIMIZED;
>        }
> }
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/Error-with-tree-component-with-1-5-2-tp3956513p3978018.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: UTF-8 encoding RFE for warning?

[Attila Király]

Nitpicking a bit: .properties files need to be in ISO 8859-1 encoding not
in default.

Attila

2011/11/2 Wilhelmsen Tor Iver 

> > It's a known fact for me aswell now :)
>
> Note that even though properties files need to be in the "default"
> encoding, you can use non-iso-latin characters by way of the \u syntax,
> though a bit more cumbersome than "raw" Unicode characters.
>
> - Tor Iver
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: Borders and inheritance in wicket 1.5

[bjolletz]

Igor Vaynberg-2 wrote:
> 
> extending panel A means that your components go into panel A not into
> one of its children.
> 

Yep. That's why I used setTransparentResolver on the sectionBorder in 1.4 to
make things work.


Igor Vaynberg-2 wrote:
> 
> you can provide a special addChild() method, or provide
> addChildren(WebMarkupContainer) callback that you call from A's
> onInitialize() or let your panel A implement IComponentResolver and
> try to locate children itself (this is not good for code that depends
> on the actual hierarchy to function).
> 
> -igor
> 

My scenario is that all panels that extend panel A should get the same
appearance, which is provided by the border component in panel A. The idea
was that users of Panel B should not have to be aware of any special
methods, they should just use "add" to add components as usual. So if I can
avoid it I would rather not add any special methods.

I guess my solution will be to replace the border in panel A with the actual
html of the border. It will work even if I lose the reusability I had with
keeping design in the border component. If I understand things correctly, it
is not possible to have a  element which is not a direct
child to the base panel, without providing some extra methods (or implement
IComponentResolver). I'm not saying this is a bad thing, just trying to
understand how things work now.

Thank you for your time!


On Tue, Nov 1, 2011 at 3:15 PM, bjolletz  wrote:
> Hi,
>
> I have the following setup:
>
> *A border:*
>
>
> *Panel A* (sectionBorder refers to my border component above)
>
>
> *Panel B* (extends Panel A)
>
>
> When I add the "someLabel" component to Panel B, the component hierarchy
> will be wrong since the someLabel component will be added to the base
> panel
> (Panel A), but in the markup it is really located under the
> "sectionBorder".
>
> In Wicket 1.4 I could solve this by using setTransparentResolver(true) on
> the border. In Wicket 1.5 however, setTransparentResolver seems to have
> been
> removed. Does this mean that the setup in my example is no longer
> possible,
> or is there another way to do it?
>
> I have read the section about borders in the migration guide, but I still
> dont really see how this one could be solved without
> setTransparentResolver.
>
> Any ideas?
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Borders-and-inheritance-in-wicket-1-5-tp3965704p3965704.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscribe@.apache
> For additional commands, e-mail: users-help@.apache
>
>

-
To unsubscribe, e-mail: users-unsubscribe@.apache
For additional commands, e-mail: users-help@.apache



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Borders-and-inheritance-in-wicket-1-5-tp3965704p3980989.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Borders and inheritance in wicket 1.5

[Igor Vaynberg]

if you are using inheritance why are you using a border? same effect
can be achieved with markup inheritance...

-igor

On Wed, Nov 2, 2011 at 11:55 AM, bjolletz  wrote:
>
> Igor Vaynberg-2 wrote:
>>
>> extending panel A means that your components go into panel A not into
>> one of its children.
>>
>
> Yep. That's why I used setTransparentResolver on the sectionBorder in 1.4 to
> make things work.
>
>
> Igor Vaynberg-2 wrote:
>>
>> you can provide a special addChild() method, or provide
>> addChildren(WebMarkupContainer) callback that you call from A's
>> onInitialize() or let your panel A implement IComponentResolver and
>> try to locate children itself (this is not good for code that depends
>> on the actual hierarchy to function).
>>
>> -igor
>>
>
> My scenario is that all panels that extend panel A should get the same
> appearance, which is provided by the border component in panel A. The idea
> was that users of Panel B should not have to be aware of any special
> methods, they should just use "add" to add components as usual. So if I can
> avoid it I would rather not add any special methods.
>
> I guess my solution will be to replace the border in panel A with the actual
> html of the border. It will work even if I lose the reusability I had with
> keeping design in the border component. If I understand things correctly, it
> is not possible to have a  element which is not a direct
> child to the base panel, without providing some extra methods (or implement
> IComponentResolver). I'm not saying this is a bad thing, just trying to
> understand how things work now.
>
> Thank you for your time!
>
>
> On Tue, Nov 1, 2011 at 3:15 PM, bjolletz  wrote:
>> Hi,
>>
>> I have the following setup:
>>
>> *A border:*
>>
>>
>> *Panel A* (sectionBorder refers to my border component above)
>>
>>
>> *Panel B* (extends Panel A)
>>
>>
>> When I add the "someLabel" component to Panel B, the component hierarchy
>> will be wrong since the someLabel component will be added to the base
>> panel
>> (Panel A), but in the markup it is really located under the
>> "sectionBorder".
>>
>> In Wicket 1.4 I could solve this by using setTransparentResolver(true) on
>> the border. In Wicket 1.5 however, setTransparentResolver seems to have
>> been
>> removed. Does this mean that the setup in my example is no longer
>> possible,
>> or is there another way to do it?
>>
>> I have read the section about borders in the migration guide, but I still
>> dont really see how this one could be solved without
>> setTransparentResolver.
>>
>> Any ideas?
>>
>> --
>> View this message in context:
>> http://apache-wicket.1842946.n4.nabble.com/Borders-and-inheritance-in-wicket-1-5-tp3965704p3965704.html
>> Sent from the Users forum mailing list archive at Nabble.com.
>>
>> -
>> To unsubscribe, e-mail: users-unsubscribe@.apache
>> For additional commands, e-mail: users-help@.apache
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscribe@.apache
> For additional commands, e-mail: users-help@.apache
>
>
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/Borders-and-inheritance-in-wicket-1-5-tp3965704p3980989.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Borders and inheritance in wicket 1.5

[bjolletz]

If panel A was the only place where the border was used, that would surely be
true. But I also use the border in other components where I want the same
appearance but dont want to extend from panel A.

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Borders-and-inheritance-in-wicket-1-5-tp3965704p3981920.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Borders and inheritance in wicket 1.5

[Igor Vaynberg]

afair add() method is not final, so you can overwrite it on panel A
and forward all calls to the border's body container.

-igor

On Wed, Nov 2, 2011 at 12:22 PM, bjolletz  wrote:
> If panel A was the only place where the border was used, that would surely be
> true. But I also use the border in other components where I want the same
> appearance but dont want to extend from panel A.
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/Borders-and-inheritance-in-wicket-1-5-tp3965704p3981920.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Borders and inheritance in wicket 1.5

[bjolletz]

Oh, that would probably solve my scenario! I think add() actually was final
in 1.4, but as you say that seems to have changed in 1.5. I wasn't aware of
that change so did not think that was an option...

Thanks you very much for your help and quick replies, much appreciated!

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Borders-and-inheritance-in-wicket-1-5-tp3965704p3982218.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: [RELEASE] WASP/SWARM/Wicket security 1.4.1 released, roadmap for future direction

[Leonardo D'Alimonte]

Great!
The main repository
(http://wicketstuff.org/maven/repository/org/apache/wicket/wicket-security/swarm/)
seems to miss the latest release of Swarm, I can see only 1.4-SNAPSHOT/ and
with incomplete dependencies...anyway the mirror repository works perfectly
:)

Leonardo


Martijn Dashorst wrote:
> 
> All is working now.
> 
> Martijn
> 
> On Tue, Nov 1, 2011 at 3:48 PM, Martijn Dashorst
>  wrote:
>> On Tue, Nov 1, 2011 at 3:41 PM, Martijn Dashorst
>>  wrote:
>>> It is not your problem, but strange enough the main page just works...
>>
>> It appears that mij hosting provider has reset/blocked the account for
>> the mysql database. Investigating how to reset the password.
>>
>> Martijn
>>
> 
> 
> 
> -- 
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> 
> -
> To unsubscribe, e-mail: users-unsubscribe@.apache
> For additional commands, e-mail: users-help@.apache
> 


--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/RELEASE-WASP-SWARM-Wicket-security-1-4-1-released-roadmap-for-future-direction-tp2543742p3983473.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Updating a child of a transparent resolver via ajax

[Allen Gilbert]

Hello,

Following Igor's example at
http://wicketinaction.com/2008/10/repainting-only-newly-created-repeater-items-via-ajax/,
I am trying to paint only the latest item added to a repeater.
Although the sample project from the article worked, I could not get
the approach to work on my page in my environment, as it failed with
the following error:

org.apache.wicket.WicketRuntimeException: Unable to find the markup
for the component. That may be due to transparent containers or
components implementing IComponentResolver: [MarkupContainer
[Component id = 3]]

After a bit of investigation, I realized that this error is related to
the fact that my repeating view's [eventual] parent is a transparent
resolver. To illustrate the problem, I modified the code in the sample
project from the article mentioned above and posted it here:
http://methodicapps.com/ajax-issue-src.zip

Is there any way I can get around this issue short of ensuring that
the repeater's parent is not a transparent resolver?

Thanks for your help!

-Allen

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

template navigation using ajax

[pen]

Hi All,

I need to build a Ajax pages, similar to wicket template example using
markup inheritance. Instead of refreshing whole pages when clicked on page1
or page2. Only the content on the right side should be refreshed using Ajax. 
What is the best way to implement this?

`Pen 

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/template-navigation-using-ajax-tp3983962p3983962.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: template navigation using ajax

[pen]

This is the wicket page example
http://www.wicket-library.com/wicket-examples/template/wicket/bookmarkable/org.apache.wicket.examples.template.pageinheritance.Page1?0

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/template-navigation-using-ajax-tp3983962p3983966.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

wicket job opportunity, we are hiring

[Igor Vaynberg]

the company i work for ( 42lines inc) is growing and we are looking
for a few good devs.

about our approach:

* we are a distributed company with employees based predominantly in
the usa, i think there are 22 of us now
* everyone telecommutes either from home or a coworking space if you
get cabin fever sitting at home
* we use a variation of agile methodology (daily scrums, iterations,
peer code reviews, etc)

tech as of now:

* wicket
* jpa/hibernate
* cdi/weld
* resteasy
* joda date/time
* querydsl
* guava
* metagen
* jquery
* jquery mobile

what we want from you:

* first and foremost you are smart and you know how to apply those
smarts to writing code
* you work on PST/EST +- 2 hours
* you have a decent internet connection capable of skype (we can help
you get one)
* you understand (not just know) java and oop
* you are comfortable in sql, hibernate, and wicket

there is lots more info, including how to apply, available off this blog post:

https://www.42lines.net/2011/10/15/now-hiring-3-new-java-engineers-and-2-new-qa-engineers/

cheers,
-igor

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: PageExpired in non bookmarkable page with 1.5.2

[Seko Masaya]

Thank you.

I wait for the fix.

--- On Wed, 2011/11/2, Martin Grigorov  wrote:

> There is a ticket for this problem:
> https://issues.apache.org/jira/browse/WICKET-4189
> I'll attach the app to it.
> 
> On Wed, Nov 2, 2011 at 6:50 AM, Igor Vaynberg  wrote:
> > please attach it to a jira issue.
> >
> > -igor
> >
> > On Tue, Nov 1, 2011 at 9:21 PM, Seko Masaya  wrote:
> >> Hi.
> >>
> >> I prepared quickstart that reproduces the problem.
> >> http://d.hatena.ne.jp/sekom/files/wicket152quickstart.zip?d=y
> >>
> >> Please do the following operations.
> >> 1.click "next" link
> >> 2.Wait a minute
> >> 3.click "home" link
> >> 4.Please check the console. Exception displayed.
> >>
> >>
> >> --- On Tue, 2011/11/1, Martin Grigorov  wrote:
> >>
> >>> Hi,
> >>>
> >>> This is caused by the new implementation of RequestLogger internals.
> >>> Can you provide a quickstart that reproduces the problem ?
> >>>
> >>> On Tue, Nov 1, 2011 at 3:45 AM, Seko Masaya  wrote:
> >>> > Hi.
> >>> > I'm having trouble PageExpired exception in non Bookmark page.
> >>> > In the case of Wicket 1.5.2 is the log output when sending PageExpired 
> >>> > exception.
> >>> > No output in Wicket 1.5.0.
> >>> > I hope behavior of Wicket 1.5.0.
> >>> >
> >>> > log:
> >>> > ERROR - RequestHandlerStack        - Error detaching RequestHandler
> >>> > org.apache.wicket.protocol.http.PageExpiredException: Page with id '1' 
> >>> > has expired.
> >>> >    at 
> >>> > org.apache.wicket.request.handler.PageProvider.getPageInstance(PageProvider.java:169)
> >>> >    at 
> >>> > org.apache.wicket.request.handler.PageProvider.getPageClass(PageProvider.java:227)
> >>> >    at 
> >>> > org.apache.wicket.request.handler.logger.PageLogData.(PageLogData.java:49)
> >>> >    at 
> >>> > org.apache.wicket.request.handler.logger.ListenerInterfaceLogData.(ListenerInterfaceLogData.java:50)
> >>> >    at 
> >>> > org.apache.wicket.request.handler.ListenerInterfaceRequestHandler.detach(ListenerInterfaceRequestHandler.java:134)
> >>> >    at 
> >>> > org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.detach(RequestCycle.java:761)
> >>> >    at 
> >>> > org.apache.wicket.request.RequestHandlerStack.detach(RequestHandlerStack.java:180)
> >>> >    at 
> >>> > org.apache.wicket.request.cycle.RequestCycle.onDetach(RequestCycle.java:565)
> >>> >    at 
> >>> > org.apache.wicket.request.cycle.RequestCycle.detach(RequestCycle.java:508)
> >>> >    at 
> >>> > org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:284)
> >>> >    at 
> >>> > org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:162)
> >>> >    at 
> >>> > org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:218)
> >>> >    at 
> >>> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> >>> >    at 
> >>> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> >>> >    at 
> >>> > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> >>> >    at 
> >>> > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> >>> >    at 
> >>> > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> >>> >    at 
> >>> > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> >>> >    at 
> >>> > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> >>> >    at 
> >>> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> >>> >    at 
> >>> > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
> >>> >    at 
> >>> > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
> >>> >    at 
> >>> > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> >>> >    at java.lang.Thread.run(Thread.java:662)
> >>> >
> >>> > -
> >>> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >>> > For additional commands, e-mail: users-h...@wicket.apache.org
> >>> >
> >>> >
> >>>
> >>>
> >>>
> >>> --
> >>> Martin Grigorov
> >>> jWeekend
> >>> Training, Consulting, Development
> >>> http://jWeekend.com
> >>>
> >>> -
> >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >>> For additional commands, e-mail: users-h...@wicket.apache.org
> >>>
> >>>
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >> For additional commands, e-mail: users-h...@wicket.apache.org
> >>
> >>
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
> 
> 
>