date:20120411

Hi,

after updating from Wicket 1.4 to 1.5.4 I get a 404 error when doing a form
submit.
I get this error when calling a SubmitLink or a normal page submit.
It's working in Tomcat 6, but not with Websphere 6.1

My Log output is empty - no error log !
The only message is (german): 
Error 404: Berichteter Fehler: 404

I already contacted our IBM support but they say it's an application problem
(Wicket problem)
They say that the root is a HTTP Statuscode 302 found

I have absolutly no idea what could be the problem!

The same  application was/is running without problems under Wicket 1.4.18 on
Websphere 6.1 and Tomcat5 and also under Wicket 1.5.4 on Tomcat6. But not
with Wicket 1.5.4 and Websphere 6.1

Do you have any hints?

Thanks in advance

Ralph

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/404-error-using-Wicket-1-5-4-and-Websphere-6-1-tp4548356p4548356.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: 404 error using Wicket 1.5.4 and Websphere 6.1

Hi,

On Wed, Apr 11, 2012 at 12:03 PM, rawe ralph.wey...@dachser.com wrote:
 Hi,

 after updating from Wicket 1.4 to 1.5.4 I get a 404 error when doing a form
 submit.
 I get this error when calling a SubmitLink or a normal page submit.
 It's working in Tomcat 6, but not with Websphere 6.1

 My Log output is empty - no error log !
 The only message is (german):
 Error 404: Berichteter Fehler: 404

 I already contacted our IBM support but they say it's an application problem
 (Wicket problem)
 They say that the root is a HTTP Statuscode 302 found

For a paid support I think they have to give you more detailed
explanation what exactly they find as a problem in normal redirect.


 I have absolutly no idea what could be the problem!

 The same  application was/is running without problems under Wicket 1.4.18 on
 Websphere 6.1 and Tomcat5 and also under Wicket 1.5.4 on Tomcat6. But not
 with Wicket 1.5.4 and Websphere 6.1

 Do you have any hints?

Put a breakpoint in WicketServlet#doGet and #doPost methods and see
whether these methods are called at all and why Wicket decides that it
should not handle the request.


 Thanks in advance

 Ralph

 --
 View this message in context: 
 http://apache-wicket.1842946.n4.nabble.com/404-error-using-Wicket-1-5-4-and-Websphere-6-1-tp4548356p4548356.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: Re: Page Expired with Google Analytics Tracking Code

2012-04-11 Thread wicket

Hi,

thank you for the answer.

The they are not completely empty means the following. My results variable
is a Vector that contains LoadableDetachableModel's in the form of the
LoaableListingEntryModel. This model contains a class that has two variables
that I access with getResults() and getTime().
The content of the getResults() variable is a class that implements the 
Serializable
interface. The getTime() variable just has a Vector with time strings.

Now comes the interesting part. When I click on one of the links from the 
PagingNavigator, the content of the getTime() variable is displayed in each
single ListItem. The getResults() class is empty. The content of the 
getResults()
class is only shown after a page reload and once again empty after clicking
on one of the links from the PagingNavigator.
That's the reason why I said it is not completely empty.

I know that there are 60 results to display. The PagingNavigator shows 6
links for 10 entries per page. But after clicking on one of the links, the 
objects
from the getResults() class are empty.

Any idea?
Andre

- Original Message -
From: b...@iswd.nl
To: users@wicket.apache.org
Date: 11.04.2012 00:51:38
Subject: Re: Page Expired with Google Analytics Tracking Code


 Hi,
 
 It sounds a lot like you are not using models properly. E.g. your 
 results method parameter has a length which overflows the page size 
 (and thus the pagingnavigator renders page links), but on a second 
 request the contents of results are null/empty?
 
 Try debugging PageableListView#populateItem() and check what its model 
 points to.
 
 Can you be more specific with regard to they are not completely empty? 
 What exactly do you see, and what do you expect?
 
 Kind regards,
 
 Bas
 
 Op 10-4-2012 22:19, schreef Andre Schütz:
 Hi,
 
 nobody an idea why the PageableListView is empty after clicking
 on one of the links from the PagingNavigator?
 After reloading of the page, the PageableListView is filled and
 once again empty when I click on oe of the links from the
 PagingNavigator.
 
 It seems, that the Listitem's are empty when I click on one of
 the links in the PagingNavigator. But there are definitely more
 items than just for one page and the PagingNavigator shows 6
 possible pages.
 
 Thanks,
 Andre
 
 On Mon, 9 Apr 2012 19:44:34 +0200
 Andre Schützwic...@faustas.de  wrote:
 
 Hello,
 
 I tried your approach and could find one mistake in my code.
 After the stepwise adding of the components to my results page,
 I found an error in two of my classes that are used on that page.
 These two classes did not implement the Serializable interface.
 I added the interface to these two classes and the PageExpired
 error was gone.
 
 But there is still another error. My PageableListView does not
 display the results when I click on one of the links in the
 AjaxPagingNavigator. The first page is displayed but the other
 pages in the list are nearly empty.
 They are not completely empty. I have 3 elements in an item of
 the PageableListView populateItem Method that must be filled
 in the html page.
 The elements are title, description and time.
 
 My code looks as follows:
 
 /***
   * Code
   */
 
 private void displayResults(VectorLoadableListingEntryModel  results, int 
 entriesPerPage) {
 WebMarkupContainer datacontainer = new 
 WebMarkupContainer(listviewContainer);
 datacontainer.setOutputMarkupId(true);
 add(datacontainer);
 
 PageableListView listview = new PageableListView(listview, results, 
 entriesPerPage) {
 StringBuilder sb;
 
 @Override
 protected void populateItem(ListItem item) {
 if (item != null) {
 LoadableListingEntryModel model = 
 (LoadableListingEntryModel)item.getModelObject();
 DefaultSearchResult s = model.getObject().getResult();
 String description = s.getDescription();
 String title = s.getTitle();
 
 item.add(new ExternalLink(title, title));
 item.add(new Label(description, description));
 item.add(new Label(time, 
 s.getTime()).setEscapeModelStrings(false));
 }
 }
 };
 
  listview.setReuseItems(true);
 datacontainer.add(listview);
  AjaxPagingNavigator apn = new AjaxPagingNavigator(navigator, 
 listview){
  @Override
  protected void onAjaxEvent(AjaxRequestTarget target) {
  super.onAjaxEvent(target);
  target.appendJavaScript(scrollTo(0,0));
  }
  };
 datacontainer.add(apn);
 datacontainer.setVersioned(false);
 }
 
 /***
   * Code
   */
 
 The LoadableListingEntryModel was one of the two classes
 that got the Serializable interface.
 When I click on one of the links of the AjaxPagingNavigator,
 the title and the description fields are emtpy. The time
 field is filled.
 
 I checked the items and have e.g. 60 items with title,

Re: Page Expired with Google Analytics Tracking Code

2012-04-11 Thread Bas Gooren

Well, for starters I wonder why you are using multiple 
LoadableDetachableModels in a Vector?


What we do 99% of the time is this:
- Wrap the entire resultset in a LDM
- Feed that LDM to a ListView or a variant (we have a custom 
RepeatingView for paged database listings)
- Use PropertyModels inside the repeater item(s) (or not, since the 
ListView will refresh itself anyway)


I'm pretty sure you don't need setReuseItems(true) in this case; The 
only reason I've seen where it's required on a ListView is when you use 
it inside a form and need form validation to work. Since I don't see any 
form fields inside your listview I guess this is not the case.


I also wonder why you had datacontainer.setVersioned(false)?

E.g.:

private void displayResults(IModelListDefaultSearchResult  results, int 
entriesPerPage) {
WebMarkupContainer datacontainer = new 
WebMarkupContainer(listviewContainer);
datacontainer.setOutputMarkupId(true);
add(datacontainer);

PageableListViewDefaultSearchResult  listview = new 
PageableListViewDefaultSearchResult(listview, results, entriesPerPage) {
StringBuilder sb;

@Override
protected void populateItem(ListItemDefaultSearchResult  item) {
DefaultSearchResult s = item.getModelObject();

// Either (A)
item.add(new ExternalLink(title, new PropertyModel(item.getModel(), 
title));
// Or (B)
item.add(new ExternalLink(title, s.getTitle());

item.add(new Label(description, new PropertyModel(item.getModel(), 
description)));
item.add(new Label(time, 
s.getTime()).setEscapeModelStrings(false));
}
};

datacontainer.add(listview);
 AjaxPagingNavigator apn = new AjaxPagingNavigator(navigator, 
listview){
 @Override
 protected void onAjaxEvent(AjaxRequestTarget target) {
 super.onAjaxEvent(target);
 target.appendJavaScript(scrollTo(0,0));
 }
 };
datacontainer.add(apn);
}




Op 11-4-2012 11:22, schreef wic...@faustas.de:

Hi,

thank you for the answer.

The they are not completely empty means the following. My results variable
is a Vector that contains LoadableDetachableModel's in the form of the
LoaableListingEntryModel. This model contains a class that has two variables
that I access with getResults() and getTime().
The content of the getResults() variable is a class that implements the 
Serializable
interface. The getTime() variable just has a Vector with time strings.

Now comes the interesting part. When I click on one of the links from the
PagingNavigator, the content of the getTime() variable is displayed in each
single ListItem. The getResults() class is empty. The content of the 
getResults()
class is only shown after a page reload and once again empty after clicking
on one of the links from the PagingNavigator.
That's the reason why I said it is not completely empty.

I know that there are 60 results to display. The PagingNavigator shows 6
links for 10 entries per page. But after clicking on one of the links, the 
objects
from the getResults() class are empty.

Any idea?
Andre

- Original Message -
From: b...@iswd.nl
To: users@wicket.apache.org
Date: 11.04.2012 00:51:38
Subject: Re: Page Expired with Google Analytics Tracking Code



Hi,

It sounds a lot like you are not using models properly. E.g. your
results method parameter has a length which overflows the page size
(and thus the pagingnavigator renders page links), but on a second
request the contents of results are null/empty?

Try debugging PageableListView#populateItem() and check what its model
points to.

Can you be more specific with regard to they are not completely empty?
What exactly do you see, and what do you expect?

Kind regards,

Bas

Op 10-4-2012 22:19, schreef Andre Schütz:

Hi,

nobody an idea why the PageableListView is empty after clicking
on one of the links from the PagingNavigator?
After reloading of the page, the PageableListView is filled and
once again empty when I click on oe of the links from the
PagingNavigator.

It seems, that the Listitem's are empty when I click on one of
the links in the PagingNavigator. But there are definitely more
items than just for one page and the PagingNavigator shows 6
possible pages.

Thanks,
Andre

On Mon, 9 Apr 2012 19:44:34 +0200
Andre Schützwic...@faustas.de   wrote:


Hello,

I tried your approach and could find one mistake in my code.
After the stepwise adding of the components to my results page,
I found an error in two of my classes that are used on that page.
These two classes did not implement the Serializable interface.
I added the interface to these two classes and the PageExpired
error was gone.

But there is still another error. My PageableListView does not
display the results when I click on one of the links in the
AjaxPagingNavigator. The first page is displayed but the other
pages in the list are nearly empty.
They are not

RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)

2012-04-11 Thread Heikki Uotinen

Hi,

I tested against apache-wicket-6.0.0-beta1 with that simple example in the 
first mail.

Application still leaked memory on IE9 document mode, same behavior as with 
1.5.5.

Confirmed that it is using jQuery:

script type=text/javascript 
src=../resource/org.apache.wicket.resource.JQueryResourceReference/jquery/jquery-ver-1334139767559.js/script

script type=text/javascript 
src=../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/res/js/wicket-event-jquery-ver-1334139767559.js/script

script type=text/javascript 
src=../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/res/js/wicket-ajax-jquery-ver-1334139767559.js/script

Suggestions ?


-Original Message-
From: Chris Colman [mailto:chr...@stepaheadsoftware.com] 
Sent: 11. huhtikuuta 2012 11:47
To: users@wicket.apache.org
Subject: RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)

 how exactly did you solve it with jQuery ?

Since this leak seems to be caused by wicket-ajax calls then solution
would
be bypassing
those, this would be the last resort.

Wicket 6 uses jQuery for its AJAX backhauling. I wonder if, therefore, if your 
app were ported to Wicket 6 if the IE9 problem goes away.


-
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: 404 error using Wicket 1.5.4 and Websphere 6.1

What I see in Firebug on tab network, when running the application under
tomcat is: 

/POST page?9-3.IFormSubmitListener-frmOrderDetail 302 Moved Temporarily
localhost:8080  0 127.0.0.1:8080/

Normally I get a status of 200. 
That's why Websphere can't find the page : 302 Moved Temporarily

 Ralph

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/404-error-using-Wicket-1-5-4-and-Websphere-6-1-tp4548356p4548554.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: 404 error using Wicket 1.5.4 and Websphere 6.1

Doing a redirect is a normal operation in the web. That's why there is
a HTTP status code for it, even several codes - 3xy.

Check http://en.wikipedia.org/wiki/Post/Redirect/Get

On Wed, Apr 11, 2012 at 1:53 PM, rawe ralph.wey...@dachser.com wrote:
 What I see in Firebug on tab network, when running the application under
 tomcat is:

 /POST page?9-3.IFormSubmitListener-frmOrderDetail 302 Moved Temporarily
 localhost:8080  0 127.0.0.1:8080/

 Normally I get a status of 200.
 That's why Websphere can't find the page : 302 Moved Temporarily

  Ralph

 --
 View this message in context: 
 http://apache-wicket.1842946.n4.nabble.com/404-error-using-Wicket-1-5-4-and-Websphere-6-1-tp4548356p4548554.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: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)

Hi,

From your mails I still don't understand how exactly you measure the
memory consumption.
You have two options:
1) google for javascript memory leak. You can add Internet
explorer in the search term too
I'm not sure whether IE has tools to deal with that but you can use
https://developers.google.com/chrome-developer-tools/docs/heap-profiling
and see whether it helps somehow

2) create a ticket in Wicket Jira with a quickstart and detailed
description how to reproduce and how to measure and let someone else
to debug it for you.

On Wed, Apr 11, 2012 at 1:50 PM, Heikki Uotinen
heikki.uoti...@syncrontech.com wrote:
 Hi,

 I tested against apache-wicket-6.0.0-beta1 with that simple example in the 
 first mail.

 Application still leaked memory on IE9 document mode, same behavior as with 
 1.5.5.

 Confirmed that it is using jQuery:

 script type=text/javascript 
 src=../resource/org.apache.wicket.resource.JQueryResourceReference/jquery/jquery-ver-1334139767559.js/script

 script type=text/javascript 
 src=../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/res/js/wicket-event-jquery-ver-1334139767559.js/script

 script type=text/javascript 
 src=../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/res/js/wicket-ajax-jquery-ver-1334139767559.js/script

 Suggestions ?


 -Original Message-
 From: Chris Colman [mailto:chr...@stepaheadsoftware.com]
 Sent: 11. huhtikuuta 2012 11:47
 To: users@wicket.apache.org
 Subject: RE: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)

 how exactly did you solve it with jQuery ?

Since this leak seems to be caused by wicket-ajax calls then solution
 would
be bypassing
those, this would be the last resort.

 Wicket 6 uses jQuery for its AJAX backhauling. I wonder if, therefore, if 
 your app were ported to Wicket 6 if the IE9 problem goes away.


 -
 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: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)

2012-04-11 Thread Heikki Uotinen

Hi,

1) Process Explorer and IE developer tools

2) ok

-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org] 
Sent: 11. huhtikuuta 2012 14:14
To: users@wicket.apache.org
Subject: Re: IE9 Memory leak when updating component with Ajax (Wicket 1.5.5)

Hi,

From your mails I still don't understand how exactly you measure the memory 
consumption.
You have two options:
1) google for javascript memory leak. You can add Internet explorer in the 
search term too I'm not sure whether IE has tools to deal with that but you can 
use  
and see whether it helps somehow

2) create a ticket in Wicket Jira with a quickstart and detailed description 
how to reproduce and how to measure and let someone else to debug it for you.

On Wed, Apr 11, 2012 at 1:50 PM, Heikki Uotinen 
heikki.uoti...@syncrontech.com wrote:
 Hi,

 I tested against apache-wicket-6.0.0-beta1 with that simple example in the 
 first mail.

 Application still leaked memory on IE9 document mode, same behavior as with 
 1.5.5.

 Confirmed that it is using jQuery:

 script type=text/javascript 
 src=../resource/org.apache.wicket.resource.JQueryResourceReference/jq
 uery/jquery-ver-1334139767559.js/script

 script type=text/javascript 
 src=../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/re
 s/js/wicket-event-jquery-ver-1334139767559.js/script

 script type=text/javascript 
 src=../resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/re
 s/js/wicket-ajax-jquery-ver-1334139767559.js/script

 Suggestions ?

 -Original Message-
 From: Chris Colman [mailto:chr...@stepaheadsoftware.com]
 Sent: 11. huhtikuuta 2012 11:47
 To: users@wicket.apache.org
 Subject: RE: IE9 Memory leak when updating component with Ajax (Wicket 
 1.5.5)

 how exactly did you solve it with jQuery ?

Since this leak seems to be caused by wicket-ajax calls then solution
 would
be bypassing
those, this would be the last resort.

 Wicket 6 uses jQuery for its AJAX backhauling. I wonder if, therefore, if 
 your app were ported to Wicket 6 if the IE9 problem goes away.

 -
 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

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

Re: 404 error using Wicket 1.5.4 and Websphere 6.1

Yes, also when a redirect is a normal operation it seems that
Websphere 6.1 cannot handle it.
see also the known problem with glassfish:
https://issues.apache.org/jira/browse/WICKET-2732
https://issues.apache.org/jira/browse/WICKET-2732 

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/404-error-using-Wicket-1-5-4-and-Websphere-6-1-tp4548356p4548678.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

Handling nested form submission on enter



I have a nested form that works as expected when it's submit button (an 
IndicatingAjaxButton) is pressed but not when the user presses the enter 
key when one of it's form fields is focused. Is it possible to capture 
this enter key press to trigger the nested form's submit instead?


Manos

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

Re: Handling nested form submission on enter

2012-04-11 Thread Andrea Del Bene


Hi,

already tried form setDefaultButton method (see JavaDoc)?
I have a nested form that works as expected when it's submit button 
(an IndicatingAjaxButton) is pressed but not when the user presses the 
enter key when one of it's form fields is focused. Is it possible to 
capture this enter key press to trigger the nested form's submit instead? 



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

rawInput, page reload and error messages

2012-04-11 Thread Thomas Götz

Hi!

I have the following situation (Wicket 1.5.5):

- a Form with a TextFieldString with some Validator
- you input invalid data and submit - error message, fine.
- (invalid) rawInput is shown in the TextField, fine.
- now I do a page reload, invalid rawInput still in the TextField, but no error 
message shown

What I'd like to achieve is that upon a page reload the (invalid) rawInput is 
shown in the TextField, but the error message also needs to be shown again. How 
can this be done?

I already tried to trigger validation manually by calling 
formComponent.validate(), but this calls AbstractTextComponent.convertInput(), 
which tries to pull the input data from the request (and there is no data 
because of page reload, so validation won't fail …).

Cheers,
   -Tom


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

RE: Using Wicket 1.5 with Oracle Application Server

2012-04-11 Thread Thomas.Norton

I wrapped the init method of WicketServlet in a try...catch block and the 
following exception got logged:

java.lang.SecurityException: Unauthorized access from application: RIDGIDPortal 
to MBean: java.lang:type=ClassLoading
at 
oracle.oc4j.admin.jmx.shared.UserMBeanServer.checkRegisterAccess(UserMBeanServer.java:873)
at 
oracle.oc4j.admin.jmx.shared.UserMBeanServer.registerMBean(UserMBeanServer.java:400)
at 
oracle.oc4j.admin.jmx.server.state.LocalizationFilterMBeanServer.registerMBean(LocalizationFilterMBeanServer.java:348)
at 
sun.management.ManagementFactory$1.run(ManagementFactory.java:240)
at java.security.AccessController.doPrivileged(Native Method)
at 
sun.management.ManagementFactory.addMBean(ManagementFactory.java:235)
at 
sun.management.ManagementFactory.addMBean(ManagementFactory.java:223)
at 
sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:266)
at 
java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:512)
at org.apache.wicket.jmx.Initializer.init(Initializer.java:152)
at 
org.apache.wicket.Application.callInitializers(Application.java:605)
at 
org.apache.wicket.Application.initializeComponents(Application.java:515)
at 
org.apache.wicket.Application.initApplication(Application.java:808)
at 
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:346)
at 
org.apache.wicket.protocol.http.WicketServlet.init(WicketServlet.java:271)
at 
filters.WrappedWicketServlet.init(WrappedWicketServlet.java:25)
at javax.servlet.GenericServlet.init(GenericServlet.java:256)
at 
com.evermind.server.http.HttpApplication.loadServlet(HttpApplication.java:2361)
at 
com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4810)
at 
com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4734)
at 
com.evermind.server.http.HttpApplication.initPreloadServlets(HttpApplication.java:4922)
at 
com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:1134)
at 
com.evermind.server.http.HttpApplication.init(HttpApplication.java:738)
at 
com.evermind.server.ApplicationStateRunning.getHttpApplication(ApplicationStateRunning.java:414)
at 
com.evermind.server.Application.getHttpApplication(Application.java:545)
at 
com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.createHttpApplicationFromReference(HttpSite.java:1990)
at 
com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.init(HttpSite.java:1909)
at 
com.evermind.server.http.HttpSite.initApplications(HttpSite.java:645)
at 
com.evermind.server.http.HttpSite.setConfig(HttpSite.java:290)
at 
com.evermind.server.http.HttpServer.setSites(HttpServer.java:270)
at 
com.evermind.server.http.HttpServer.setConfig(HttpServer.java:177)
at 
com.evermind.server.ApplicationServer.initializeHttp(ApplicationServer.java:2450)
at 
com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:998)
at 
com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:131)
at java.lang.Thread.run(Thread.java:595)

Does anyone have any ideas on what could cause this?

From: Norton, Thomas [External/Top Echelon]
Sent: Tuesday, April 10, 2012 10:57 AM
To: 'users@wicket.apache.org'
Subject: Using Wicket 1.5 with Oracle Application Server

We use WebLogic 11g as our development environment and OAS 10.1.3.1 for 
everything else.  Our wicket pages work fine in WebLogic but generate 500 
status codes in OAS.  After looking around on online for a little bit, I found 
some suggestions that I should use the WicketServlet instead of the 
WicketFilter.  After switching to the WicketServlet, WebLogic still works and 
OAS still gets 500s.  Even though the 500 code is being returned in the 
response, no errors are being logged by either OAS or log4j.

On server start up, the only wicket-related logs are:
INFO  2012-04-05 16:03:22,994 org.apache.wicket.util.file.WebXmlFile  - 
web.xml: url mapping found for servlet with name AdminWicketApplication: 
[/admin/*]
INFO  2012-04-05 16:03:23,494 org.apache.wicket.Application  - 
[AdminWicketApplication] init: Wicket core library initializer
INFO  2012-04-05 16:03:23,510 org.apache.wicket.RequestListenerInterface  - 
registered listener interface [RequestListenerInterface name=IBehaviorListener, 
method=public abstract void 
org.apache.wicket.behavior.IBehaviorListener.onRequest()]
INFO  2012-04-05 16:03:23,510

Re: Using Wicket 1.5 with Oracle Application Server

Any reason to have wicket-jmx.jar in the classpath ?
If it is not needed just remove it.

On Wed, Apr 11, 2012 at 4:44 PM,  thomas.nor...@emerson.com wrote:
 I wrapped the init method of WicketServlet in a try...catch block and the 
 following exception got logged:

 java.lang.SecurityException: Unauthorized access from application: 
 RIDGIDPortal to MBean: java.lang:type=ClassLoading
                at 
 oracle.oc4j.admin.jmx.shared.UserMBeanServer.checkRegisterAccess(UserMBeanServer.java:873)
                at 
 oracle.oc4j.admin.jmx.shared.UserMBeanServer.registerMBean(UserMBeanServer.java:400)
                at 
 oracle.oc4j.admin.jmx.server.state.LocalizationFilterMBeanServer.registerMBean(LocalizationFilterMBeanServer.java:348)
                at 
 sun.management.ManagementFactory$1.run(ManagementFactory.java:240)
                at java.security.AccessController.doPrivileged(Native Method)
                at 
 sun.management.ManagementFactory.addMBean(ManagementFactory.java:235)
                at 
 sun.management.ManagementFactory.addMBean(ManagementFactory.java:223)
                at 
 sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:266)
                at 
 java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:512)
                at org.apache.wicket.jmx.Initializer.init(Initializer.java:152)
                at 
 org.apache.wicket.Application.callInitializers(Application.java:605)
                at 
 org.apache.wicket.Application.initializeComponents(Application.java:515)
                at 
 org.apache.wicket.Application.initApplication(Application.java:808)
                at 
 org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:346)
                at 
 org.apache.wicket.protocol.http.WicketServlet.init(WicketServlet.java:271)
                at 
 filters.WrappedWicketServlet.init(WrappedWicketServlet.java:25)
                at javax.servlet.GenericServlet.init(GenericServlet.java:256)
                at 
 com.evermind.server.http.HttpApplication.loadServlet(HttpApplication.java:2361)
                at 
 com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4810)
                at 
 com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4734)
                at 
 com.evermind.server.http.HttpApplication.initPreloadServlets(HttpApplication.java:4922)
                at 
 com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:1134)
                at 
 com.evermind.server.http.HttpApplication.init(HttpApplication.java:738)
                at 
 com.evermind.server.ApplicationStateRunning.getHttpApplication(ApplicationStateRunning.java:414)
                at 
 com.evermind.server.Application.getHttpApplication(Application.java:545)
                at 
 com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.createHttpApplicationFromReference(HttpSite.java:1990)
                at 
 com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.init(HttpSite.java:1909)
                at 
 com.evermind.server.http.HttpSite.initApplications(HttpSite.java:645)
                at 
 com.evermind.server.http.HttpSite.setConfig(HttpSite.java:290)
                at 
 com.evermind.server.http.HttpServer.setSites(HttpServer.java:270)
                at 
 com.evermind.server.http.HttpServer.setConfig(HttpServer.java:177)
                at 
 com.evermind.server.ApplicationServer.initializeHttp(ApplicationServer.java:2450)
                at 
 com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:998)
                at 
 com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:131)
                at java.lang.Thread.run(Thread.java:595)

 Does anyone have any ideas on what could cause this?

 From: Norton, Thomas [External/Top Echelon]
 Sent: Tuesday, April 10, 2012 10:57 AM
 To: 'users@wicket.apache.org'
 Subject: Using Wicket 1.5 with Oracle Application Server

 We use WebLogic 11g as our development environment and OAS 10.1.3.1 for 
 everything else.  Our wicket pages work fine in WebLogic but generate 500 
 status codes in OAS.  After looking around on online for a little bit, I 
 found some suggestions that I should use the WicketServlet instead of the 
 WicketFilter.  After switching to the WicketServlet, WebLogic still works and 
 OAS still gets 500s.  Even though the 500 code is being returned in the 
 response, no errors are being logged by either OAS or log4j.

 On server start up, the only wicket-related logs are:
 INFO  2012-04-05 16:03:22,994 org.apache.wicket.util.file.WebXmlFile  - 
 web.xml: url mapping found for servlet with name AdminWicketApplication: 
 [/admin/*]
 INFO  2012-04-05 16:03:23,494 org.apache.wicket.Application  - 
 [AdminWicketApplication] init: Wicket core library initializer
 INFO  2012-04-05 16:03:23,510 org.apache.wicket.RequestListenerInterface  - 
 registered listener

Re: Handling nested form submission on enter


On 04/11/2012 04:14 PM, Andrea Del Bene wrote:

already tried form setDefaultButton method (see JavaDoc)?


Thanks, I just did and the flow is the one desired, but for some reason 
the nested form field models are not updated with the field inputs when 
the submit buttons onSubmit() is called. Is there something obvious I 
might be missing?


Manos

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

Re: 404 error using Wicket 1.5.4 and Websphere 6.1

2012-04-11 Thread Andrew Geery

Wicket 1.5 requires servlet 2.5 [
https://cwiki.apache.org/WICKET/migration-to-wicket-15.html#MigrationtoWicket1.5-%2528RC1%2529UpgradedtoServletAPI2.5
],
but WAS 6.1 only supports J2EE 1.4 (servlet 2.4) [
http://en.wikipedia.org/wiki/IBM_WebSphere_Application_Server#Version_6.1 ],
so I wouldn't expect Wicket 1.5 to work on WAS 6.1.

Andrew

On Wed, Apr 11, 2012 at 7:50 AM, rawe ralph.wey...@dachser.com wrote:

 Yes, also when a redirect is a normal operation it seems that
 Websphere 6.1 cannot handle it.
 see also the known problem with glassfish:
 https://issues.apache.org/jira/browse/WICKET-2732
 https://issues.apache.org/jira/browse/WICKET-2732

 --
 View this message in context:
 http://apache-wicket.1842946.n4.nabble.com/404-error-using-Wicket-1-5-4-and-Websphere-6-1-tp4548356p4548678.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: 404 error using Wicket 1.5.4 and Websphere 6.1

On Wed, Apr 11, 2012 at 5:05 PM, Andrew Geery andrew.ge...@gmail.com wrote:
 Wicket 1.5 requires servlet 2.5 [
 https://cwiki.apache.org/WICKET/migration-to-wicket-15.html#MigrationtoWicket1.5-%2528RC1%2529UpgradedtoServletAPI2.5
 ],
 but WAS 6.1 only supports J2EE 1.4 (servlet 2.4) [
 http://en.wikipedia.org/wiki/IBM_WebSphere_Application_Server#Version_6.1 ],
 so I wouldn't expect Wicket 1.5 to work on WAS 6.1.

I may be wrong but I think Wicket doesn't use any feature from 2.5
that doesn't exist in 2.4.


 Andrew

 On Wed, Apr 11, 2012 at 7:50 AM, rawe ralph.wey...@dachser.com wrote:

 Yes, also when a redirect is a normal operation it seems that
 Websphere 6.1 cannot handle it.
 see also the known problem with glassfish:
 https://issues.apache.org/jira/browse/WICKET-2732
 https://issues.apache.org/jira/browse/WICKET-2732

 --
 View this message in context:
 http://apache-wicket.1842946.n4.nabble.com/404-error-using-Wicket-1-5-4-and-Websphere-6-1-tp4548356p4548678.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: 404 error using Wicket 1.5.4 and Websphere 6.1

Yes, I think the problem could be the servlet-api version.
WAS 6.1 is running with servlet-api 2.4, so I won't install a wicket 1.5
application on it!
Thanks for your help!

Ralph

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/404-error-using-Wicket-1-5-4-and-Websphere-6-1-tp4548356p4548975.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

How to enable SSI in wicket framework.

2012-04-11 Thread vaibhav228

Hi All,
   I have configured the SSI in apache Tomcat 7.0 by un-commenting the
tags in web.xml for ssi and adding  privileged=true in the context.xml.
   I am using the wicket framework and the project is running at the
root level.But unfortunately the framework is not processing the include tag
and it outputs in the HTML as it is.

   Is there anything that I can do to enable the Server Side Include tag
ion wicket framework. or It will not process that tag.

   If I deploy the project which doesn't uses wicket framework, then SSI
works properly. It renders the page completely. But when I use project with
wicket framework, then include tag is not getting rendered.

Please help me.

Thanks
Vaibhav228 

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/How-to-enable-SSI-in-wicket-framework-tp4548962p4548962.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: Using Wicket 1.5 with Oracle Application Server

2012-04-11 Thread Thomas.Norton

That was the problem.

Thanks!

-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org] 
Sent: Wednesday, April 11, 2012 9:48 AM
To: users@wicket.apache.org
Subject: Re: Using Wicket 1.5 with Oracle Application Server

Any reason to have wicket-jmx.jar in the classpath ?
If it is not needed just remove it.

On Wed, Apr 11, 2012 at 4:44 PM,  thomas.nor...@emerson.com wrote:
 I wrapped the init method of WicketServlet in a try...catch block and the 
 following exception got logged:

 java.lang.SecurityException: Unauthorized access from application: 
 RIDGIDPortal to MBean: java.lang:type=ClassLoading
                at 
 oracle.oc4j.admin.jmx.shared.UserMBeanServer.checkRegisterAccess(UserM
 BeanServer.java:873)
                at 
 oracle.oc4j.admin.jmx.shared.UserMBeanServer.registerMBean(UserMBeanSe
 rver.java:400)
                at 
 oracle.oc4j.admin.jmx.server.state.LocalizationFilterMBeanServer.regis
 terMBean(LocalizationFilterMBeanServer.java:348)
                at 
 sun.management.ManagementFactory$1.run(ManagementFactory.java:240)
                at java.security.AccessController.doPrivileged(Native 
 Method)
                at 
 sun.management.ManagementFactory.addMBean(ManagementFactory.java:235)
                at 
 sun.management.ManagementFactory.addMBean(ManagementFactory.java:223)
                at 
 sun.management.ManagementFactory.createPlatformMBeanServer(ManagementF
 actory.java:266)
                at 
 java.lang.management.ManagementFactory.getPlatformMBeanServer(Manageme
 ntFactory.java:512)
                at 
 org.apache.wicket.jmx.Initializer.init(Initializer.java:152)
                at 
 org.apache.wicket.Application.callInitializers(Application.java:605)
                at 
 org.apache.wicket.Application.initializeComponents(Application.java:51
 5)
                at 
 org.apache.wicket.Application.initApplication(Application.java:808)
                at 
 org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:34
 6)
                at 
 org.apache.wicket.protocol.http.WicketServlet.init(WicketServlet.java:
 271)
                at 
 filters.WrappedWicketServlet.init(WrappedWicketServlet.java:25)
                at 
 javax.servlet.GenericServlet.init(GenericServlet.java:256)
                at 
 com.evermind.server.http.HttpApplication.loadServlet(HttpApplication.j
 ava:2361)
                at 
 com.evermind.server.http.HttpApplication.findServlet(HttpApplication.j
 ava:4810)
                at 
 com.evermind.server.http.HttpApplication.findServlet(HttpApplication.j
 ava:4734)
                at 
 com.evermind.server.http.HttpApplication.initPreloadServlets(HttpAppli
 cation.java:4922)
                at 
 com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.j
 ava:1134)
                at 
 com.evermind.server.http.HttpApplication.init(HttpApplication.java:7
 38)
                at 
 com.evermind.server.ApplicationStateRunning.getHttpApplication(Applica
 tionStateRunning.java:414)
                at 
 com.evermind.server.Application.getHttpApplication(Application.java:54
 5)
                at 
 com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.crea
 teHttpApplicationFromReference(HttpSite.java:1990)
                at 
 com.evermind.server.http.HttpSite$HttpApplicationRunTimeReference.ini
 t(HttpSite.java:1909)
                at 
 com.evermind.server.http.HttpSite.initApplications(HttpSite.java:645)
                at 
 com.evermind.server.http.HttpSite.setConfig(HttpSite.java:290)
                at 
 com.evermind.server.http.HttpServer.setSites(HttpServer.java:270)
                at 
 com.evermind.server.http.HttpServer.setConfig(HttpServer.java:177)
                at 
 com.evermind.server.ApplicationServer.initializeHttp(ApplicationServer
 .java:2450)
                at 
 com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java
 :998)
                at 
 com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLau
 ncher.java:131)
                at java.lang.Thread.run(Thread.java:595)

 Does anyone have any ideas on what could cause this?

 From: Norton, Thomas [External/Top Echelon]
 Sent: Tuesday, April 10, 2012 10:57 AM
 To: 'users@wicket.apache.org'
 Subject: Using Wicket 1.5 with Oracle Application Server

 We use WebLogic 11g as our development environment and OAS 10.1.3.1 for 
 everything else.  Our wicket pages work fine in WebLogic but generate 500 
 status codes in OAS.  After looking around on online for a little bit, I 
 found some suggestions that I should use the WicketServlet instead of the 
 WicketFilter.  After switching to the WicketServlet, WebLogic still works and 
 OAS still gets 500s.  Even though the 500 code is being returned in the 
 response, no errors are being logged by either OAS or log4j.

 On server start up, the only wicket-related logs are:
 INFO  2012-04-05 16:03:22,994 org.apache.wicket.util.file.WebXmlFile  
 - web.xml: url mapping

Re: Handling nested form submission on enter

2012-04-11 Thread Andrea Del Bene

Well, I couldn't say why it doesn't work. Can you post some code of your 
nested forms?
Thanks, I just did and the flow is the one desired, but for some 
reason the nested form field models are not updated with the field 
inputs when the submit buttons onSubmit() is called. Is there 
something obvious I might be missing? 



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

Re: Handling nested form submission on enter


On 04/11/2012 05:39 PM, Andrea Del Bene wrote:

Well, I couldn't say why it doesn't work. Can you post some code of your
nested forms?


Sort of found what the problem is but have no clue on how to solve it. 
Pressing enter in one of the nested forms submits the last nested form 
in the page.


Each form is within a custom FormComponentPanel I made to implement a 
widget, but it seems the nested forms are mixed up if more than one of 
these are used in the same page. Each of these FormComponentPanels is an 
instance of my MultipleValuesTextField:


http://code.google.com/p/calipso/source/browse/trunk/calipso-war/src/main/java/gr/abiss/calipso/wicket/components/formfields/MultipleValuesTextField.java

 Manos

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

Re: How to enable SSI in wicket framework.

SSI is implemented with its own servlet which is totally separate from
Wicket's filter, so you cannot use both Wicket and SSI for a single page.
However, Wicket provides a variety of ways to include content into pages it
renders: panels, fragments, labels, and more. Once you're familiar with
these mechanisms, you'll find that they're considerably more powerful than
SSI. A good place for examples is
http://www.wicket-library.com/wicket-examples/compref/.

Hope this helps,
Dan

On Wed, Apr 11, 2012 at 8:12 AM, vaibhav228 vaibhav...@gmail.com wrote:

Hi All,
I have configured the SSI in apache Tomcat 7.0 by un-commenting the
tags in web.xml for ssi and adding privileged=true in the context.xml.
I am using the wicket framework and the project is running at the
root level.But unfortunately the framework is not processing the include
tag
and it outputs in the HTML as it is.

Is there anything that I can do to enable the Server Side Include tag
ion wicket framework. or It will not process that tag.

If I deploy the project which doesn't uses wicket framework, then SSI
works properly. It renders the page completely. But when I use project with
wicket framework, then include tag is not getting rendered.

Please help me.

Thanks
Vaibhav228

--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/How-to-enable-SSI-in-wicket-framework-tp4548962p4548962.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: rawInput, page reload and error messages

You might want to subclass Form to retain additional state. It could save
the validation errors and put them back onto components in onBeforeRender,
clearing them when validation is eventually successful. This could probably
also be accomplished with a Behavior.

On Wed, Apr 11, 2012 at 7:19 AM, Thomas Götz t...@decoded.de wrote:

 Hi!

 I have the following situation (Wicket 1.5.5):

 - a Form with a TextFieldString with some Validator
 - you input invalid data and submit - error message, fine.
 - (invalid) rawInput is shown in the TextField, fine.
 - now I do a page reload, invalid rawInput still in the TextField, but no
 error message shown

 What I'd like to achieve is that upon a page reload the (invalid) rawInput
 is shown in the TextField, but the error message also needs to be shown
 again. How can this be done?

 I already tried to trigger validation manually by calling
 formComponent.validate(), but this calls
 AbstractTextComponent.convertInput(), which tries to pull the input data
 from the request (and there is no data because of page reload, so
 validation won't fail …).

 Cheers,
   -Tom


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

Re: Handling nested form submission on enter

2012-04-11 Thread Andrea Del Bene

It's like if JavaScript can't tell apart a form from another. Can you 
check the HTML generated for your page and see if forms have an unique id?

On 04/11/2012 05:39 PM, Andrea Del Bene wrote:

Well, I couldn't say why it doesn't work. Can you post some code of your
nested forms?


Sort of found what the problem is but have no clue on how to solve it. 
Pressing enter in one of the nested forms submits the last nested form 
in the page.


Each form is within a custom FormComponentPanel I made to implement a 
widget, but it seems the nested forms are mixed up if more than one of 
these are used in the same page. Each of these FormComponentPanels is 
an instance of my MultipleValuesTextField:


http://code.google.com/p/calipso/source/browse/trunk/calipso-war/src/main/java/gr/abiss/calipso/wicket/components/formfields/MultipleValuesTextField.java 



 Manos

-
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: Javascript call on AjaxFallbackDefaultDataTable

Yes. You're returning your decorator in an AjaxLink#getAjaxCallDecorator()
override? I think you'll need to pastebin some code for us to help.

On Tue, Apr 10, 2012 at 11:27 PM, cellis christopher.el...@uwa.edu.auwrote:

 I've tried to implement the ajaxCallDecorator as you specified, but I fail
 to
 see the javascript being appended/prepended. ie only the var wcall
 =wicketAjaxGet... is ever decorated. Has anyone else attempted this
 successfully?

 --
 View this message in context:
 http://apache-wicket.1842946.n4.nabble.com/Javascript-call-on-AjaxFallbackDefaultDataTable-tp1850777p4548007.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: Handling nested form submission on enter


On 04/11/2012 07:53 PM, Andrea Del Bene wrote:

It's like if JavaScript can't tell apart a form from another. Can you
check the HTML generated for your page and see if forms have an unique id?


Checked, the IDs are unique. I couldn't figure out what the actual 
problem is so, to bypass it, I just added this to intercept the enter 
key and explicitly use my nested form's submit:



final TextFieldString newValueField =
		new TextFieldString(newValueField, new 
PropertyModel(newSubFieldValues, [ + index + ])){

@Override
protected void onComponentTag(ComponentTag tag){
super.onComponentTag(tag);
tag.put(onkeypress, if(event.keyCode == 13) 
{document.getElementById('  + addButton.getMarkupId() + 
').click();return false;});

}
};

Hope this helps someone else with nested forms and the enter key.

Manos

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

Re: Wicket 1.5.5 + JBoss 7.1.1 + CDI - ClassNotFoundException

2012-04-11 Thread James Carman

I would recommend checking out one of the existing libraries that does
Wicket/CDI integration.

On Wed, Apr 11, 2012 at 3:54 PM, Jonathan Tougas jtou...@gmail.com wrote:
 I'm running Wicket 1.5 on JBoss 7.1.1 with some CDI thrown in to the mix.
 In certain cases when Wicket deserializes a Page containing a reference to
 a CDI bean, I get this exception:

 15:10:30,841 ERROR [org.apache.wicket.request.RequestHandlerStack]
 (http--127.0.0.1-8080-1) Error detaching RequestHandler:
 java.lang.RuntimeException: Could not deserialize object using: class
 org.apache.wicket.serialize.java.JavaSerializer$ClassResolverObjectInputStream
 at
 org.apache.wicket.serialize.java.JavaSerializer.deserialize(JavaSerializer.java:137)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.pageStore.DefaultPageStore.deserializePage(DefaultPageStore.java:388)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.pageStore.DefaultPageStore.getPage(DefaultPageStore.java:127)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.page.PageStoreManager$SessionEntry.getPage(PageStoreManager.java:192)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.page.PageStoreManager$PersistentRequestAdapter.getPage(PageStoreManager.java:327)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.page.AbstractPageManager.getPage(AbstractPageManager.java:102)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.page.PageManagerDecorator.getPage(PageManagerDecorator.java:50)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.page.PageAccessSynchronizer$2.getPage(PageAccessSynchronizer.java:257)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.DefaultMapperContext.getPageInstance(DefaultMapperContext.java:117)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.request.handler.PageProvider.getStoredPage(PageProvider.java:292)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.request.handler.PageProvider.isNewPageInstance(PageProvider.java:205)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.request.handler.PageProvider.getPageParameters(PageProvider.java:184)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.request.handler.logger.PageLogData.init(PageLogData.java:51)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.request.handler.logger.ListenerInterfaceLogData.init(ListenerInterfaceLogData.java:56)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.request.handler.ListenerInterfaceRequestHandler.detach(ListenerInterfaceRequestHandler.java:134)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.detach(RequestCycle.java:792)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.request.RequestHandlerStack.detach(RequestHandlerStack.java:180)
 [wicket-request-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.request.cycle.RequestCycle.onDetach(RequestCycle.java:596)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.request.cycle.RequestCycle.detach(RequestCycle.java:539)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:287)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:185)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:241)
 [wicket-core-1.5.5.jar:1.5.5]
 at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
 [jbossweb-7.0.10.Final.jar:]
 at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
 [jbossweb-7.0.10.Final.jar:]
 at
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
 [jbossweb-7.0.10.Final.jar:]
 at
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
 [jbossweb-7.0.10.Final.jar:]
 at
 org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154)
 [jboss-as-web-7.1.0.Final.jar:7.1.0.Final]
 at
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
 [jbossweb-7.0.10.Final.jar:]
 at
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
 [jbossweb-7.0.10.Final.jar:]
 at
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 [jbossweb-7.0.10.Final.jar:]
 at
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
 [jbossweb-7.0.10.Final.jar:]
 at
 org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
 [jbossweb-7.0.10.Final.jar:]
 at
 org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
 [jbossweb-7.0.10.Final.jar:]
 at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
 [jbossweb-7.0.10.Final.jar:]
 at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_02]
 Caused by: java.lang.ClassNotFoundException:
 org.jboss.msc.service.ServiceName from [Module deployment.wicket.war:main
 from Service

Re: Wicket 1.5.5 + JBoss 7.1.1 + CDI - ClassNotFoundException

2012-04-11 Thread Jonathan Tougas

Using wicket-cdi https://github.com/42Lines/wicket-cdi the problem still
exists. I'll update the example in a moment.

On Wed, Apr 11, 2012 at 3:58 PM, James Carman ja...@carmanconsulting.comwrote:

 I would recommend checking out one of the existing libraries that does
 Wicket/CDI integration.

 On Wed, Apr 11, 2012 at 3:54 PM, Jonathan Tougas jtou...@gmail.com
 wrote:
  I'm running Wicket 1.5 on JBoss 7.1.1 with some CDI thrown in to the mix.
  In certain cases when Wicket deserializes a Page containing a reference
 to
  a CDI bean, I get this exception:
 
  15:10:30,841 ERROR [org.apache.wicket.request.RequestHandlerStack]
  (http--127.0.0.1-8080-1) Error detaching RequestHandler:
  java.lang.RuntimeException: Could not deserialize object using: class
 
 org.apache.wicket.serialize.java.JavaSerializer$ClassResolverObjectInputStream
  at
 
 org.apache.wicket.serialize.java.JavaSerializer.deserialize(JavaSerializer.java:137)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.pageStore.DefaultPageStore.deserializePage(DefaultPageStore.java:388)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.pageStore.DefaultPageStore.getPage(DefaultPageStore.java:127)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.page.PageStoreManager$SessionEntry.getPage(PageStoreManager.java:192)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.page.PageStoreManager$PersistentRequestAdapter.getPage(PageStoreManager.java:327)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.page.AbstractPageManager.getPage(AbstractPageManager.java:102)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.page.PageManagerDecorator.getPage(PageManagerDecorator.java:50)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.page.PageAccessSynchronizer$2.getPage(PageAccessSynchronizer.java:257)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.DefaultMapperContext.getPageInstance(DefaultMapperContext.java:117)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.handler.PageProvider.getStoredPage(PageProvider.java:292)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.handler.PageProvider.isNewPageInstance(PageProvider.java:205)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.handler.PageProvider.getPageParameters(PageProvider.java:184)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.handler.logger.PageLogData.init(PageLogData.java:51)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.handler.logger.ListenerInterfaceLogData.init(ListenerInterfaceLogData.java:56)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.handler.ListenerInterfaceRequestHandler.detach(ListenerInterfaceRequestHandler.java:134)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.detach(RequestCycle.java:792)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.RequestHandlerStack.detach(RequestHandlerStack.java:180)
  [wicket-request-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.cycle.RequestCycle.onDetach(RequestCycle.java:596)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.cycle.RequestCycle.detach(RequestCycle.java:539)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:287)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:185)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:241)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
  [jbossweb-7.0.10.Final.jar:]
  at
 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
  [jbossweb-7.0.10.Final.jar:]
  at
 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
  [jbossweb-7.0.10.Final.jar:]
  at
 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
  [jbossweb-7.0.10.Final.jar:]
  at
 
 org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154)
  [jboss-as-web-7.1.0.Final.jar:7.1.0.Final]
  at
 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
  [jbossweb-7.0.10.Final.jar:]
  at
 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
  [jbossweb-7.0.10.Final.jar:]
  at
 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  [jbossweb-7.0.10.Final.jar:]
  at
 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
  [jbossweb-7.0.10.Final.jar:]
  at
 
 org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
  [jbossweb-7.0.10.Final.jar:]
  at

Re: Wicket 1.5.5 + JBoss 7.1.1 + CDI - ClassNotFoundException

2012-04-11 Thread James Carman

The Wicketopia example application doesn't run into those troubles.  I
may not be doing exactly what you're doing, though:

https://github.com/jwcarman/Wicketopia



On Wed, Apr 11, 2012 at 4:26 PM, Jonathan Tougas jtou...@gmail.com wrote:
 Using wicket-cdi https://github.com/42Lines/wicket-cdi the problem still
 exists. I'll update the example in a moment.

 On Wed, Apr 11, 2012 at 3:58 PM, James Carman 
 ja...@carmanconsulting.comwrote:

 I would recommend checking out one of the existing libraries that does
 Wicket/CDI integration.

 On Wed, Apr 11, 2012 at 3:54 PM, Jonathan Tougas jtou...@gmail.com
 wrote:
  I'm running Wicket 1.5 on JBoss 7.1.1 with some CDI thrown in to the mix.
  In certain cases when Wicket deserializes a Page containing a reference
 to
  a CDI bean, I get this exception:
 
  15:10:30,841 ERROR [org.apache.wicket.request.RequestHandlerStack]
  (http--127.0.0.1-8080-1) Error detaching RequestHandler:
  java.lang.RuntimeException: Could not deserialize object using: class
 
 org.apache.wicket.serialize.java.JavaSerializer$ClassResolverObjectInputStream
  at
 
 org.apache.wicket.serialize.java.JavaSerializer.deserialize(JavaSerializer.java:137)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.pageStore.DefaultPageStore.deserializePage(DefaultPageStore.java:388)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.pageStore.DefaultPageStore.getPage(DefaultPageStore.java:127)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.page.PageStoreManager$SessionEntry.getPage(PageStoreManager.java:192)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.page.PageStoreManager$PersistentRequestAdapter.getPage(PageStoreManager.java:327)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.page.AbstractPageManager.getPage(AbstractPageManager.java:102)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.page.PageManagerDecorator.getPage(PageManagerDecorator.java:50)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.page.PageAccessSynchronizer$2.getPage(PageAccessSynchronizer.java:257)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.DefaultMapperContext.getPageInstance(DefaultMapperContext.java:117)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.handler.PageProvider.getStoredPage(PageProvider.java:292)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.handler.PageProvider.isNewPageInstance(PageProvider.java:205)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.handler.PageProvider.getPageParameters(PageProvider.java:184)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.handler.logger.PageLogData.init(PageLogData.java:51)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.handler.logger.ListenerInterfaceLogData.init(ListenerInterfaceLogData.java:56)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.handler.ListenerInterfaceRequestHandler.detach(ListenerInterfaceRequestHandler.java:134)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.detach(RequestCycle.java:792)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.RequestHandlerStack.detach(RequestHandlerStack.java:180)
  [wicket-request-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.cycle.RequestCycle.onDetach(RequestCycle.java:596)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.cycle.RequestCycle.detach(RequestCycle.java:539)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:287)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:185)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:241)
  [wicket-core-1.5.5.jar:1.5.5]
  at
 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
  [jbossweb-7.0.10.Final.jar:]
  at
 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
  [jbossweb-7.0.10.Final.jar:]
  at
 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
  [jbossweb-7.0.10.Final.jar:]
  at
 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
  [jbossweb-7.0.10.Final.jar:]
  at
 
 org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154)
  [jboss-as-web-7.1.0.Final.jar:7.1.0.Final]
  at
 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
  [jbossweb-7.0.10.Final.jar:]
  at
 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
  [jbossweb-7.0.10.Final.jar:]
  at
 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  [jbossweb-7.0.10.Final.jar:]
  at

JQuery and Wicket 1.5 question

2012-04-11 Thread Sandor Feher

Hi,


I would like to use some visural wicket components so I need to initialize
JQuery first.
I'm wondering how to initialize it in wicket 1.5.
The example shown below does not work in 1.5.
Thank you in advance!


Regards., Sandor

--

package com.myapp.wicket;   

import com.jquery.JQueryResourceReference;
import org.apache.wicket.markup.html.JavascriptPackageResource;
import org.apache.wicket.protocol.http.WebApplication;

public class Application extends WebApplication {

public Application() {
   
addRenderHeadListener(JavascriptPackageResource.getHeaderContribution(new
JQueryResourceReference()));
}

public Class getHomePage() {
return HomePage.class;
}
}


--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/JQuery-and-Wicket-1-5-question-tp4549988p4549988.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: Page Expired with Google Analytics Tracking Code

2012-04-11 Thread Andre Schütz

Hi,

I implemented your version but still I get the same error, if
I have the Google Analytics Code in the head.

Could it be an error with the way I insert the Google
Analytics Code? I do it in the following way.

In my WebPage class I overwrite the following method:

@Override
public void renderHead(HeaderResponse response) {
  String script = var _gaq = _gaq || ...;
  response.renderJavaScript(script, null);
}

Andre

On Wed, 11 Apr 2012 11:38:52 +0200
Bas Gooren b...@iswd.nl wrote:

 Well, for starters I wonder why you are using multiple 
 LoadableDetachableModels in a Vector?
 
 What we do 99% of the time is this:
 - Wrap the entire resultset in a LDM
 - Feed that LDM to a ListView or a variant (we have a custom 
 RepeatingView for paged database listings)
 - Use PropertyModels inside the repeater item(s) (or not, since the 
 ListView will refresh itself anyway)
 
 I'm pretty sure you don't need setReuseItems(true) in this case; The 
 only reason I've seen where it's required on a ListView is when you use 
 it inside a form and need form validation to work. Since I don't see any 
 form fields inside your listview I guess this is not the case.
 
 I also wonder why you had datacontainer.setVersioned(false)?
 
 E.g.:
 
 private void displayResults(IModelListDefaultSearchResult  results, int 
 entriesPerPage) {
  WebMarkupContainer datacontainer = new 
 WebMarkupContainer(listviewContainer);
  datacontainer.setOutputMarkupId(true);
  add(datacontainer);
 
  PageableListViewDefaultSearchResult  listview = new 
 PageableListViewDefaultSearchResult(listview, results, entriesPerPage) {
  StringBuilder sb;
 
  @Override
  protected void populateItem(ListItemDefaultSearchResult  item) {
  DefaultSearchResult s = item.getModelObject();
 
  // Either (A)
   item.add(new ExternalLink(title, new 
 PropertyModel(item.getModel(), title));
   // Or (B)
   item.add(new ExternalLink(title, s.getTitle());
 
  item.add(new Label(description, new 
 PropertyModel(item.getModel(), description)));
  item.add(new Label(time, 
 s.getTime()).setEscapeModelStrings(false));
  }
  };
 
  datacontainer.add(listview);
   AjaxPagingNavigator apn = new AjaxPagingNavigator(navigator, 
 listview){
   @Override
   protected void onAjaxEvent(AjaxRequestTarget target) {
   super.onAjaxEvent(target);
   target.appendJavaScript(scrollTo(0,0));
   }
   };
  datacontainer.add(apn);
 }
 
 
 
 
 Op 11-4-2012 11:22, schreef wic...@faustas.de:
  Hi,
 
  thank you for the answer.
 
  The they are not completely empty means the following. My results variable
  is a Vector that contains LoadableDetachableModel's in the form of the
  LoaableListingEntryModel. This model contains a class that has two variables
  that I access with getResults() and getTime().
  The content of the getResults() variable is a class that implements the 
  Serializable
  interface. The getTime() variable just has a Vector with time strings.
 
  Now comes the interesting part. When I click on one of the links from the
  PagingNavigator, the content of the getTime() variable is displayed in each
  single ListItem. The getResults() class is empty. The content of the 
  getResults()
  class is only shown after a page reload and once again empty after clicking
  on one of the links from the PagingNavigator.
  That's the reason why I said it is not completely empty.
 
  I know that there are 60 results to display. The PagingNavigator shows 6
  links for 10 entries per page. But after clicking on one of the links, the 
  objects
  from the getResults() class are empty.
 
  Any idea?
  Andre
 
  - Original Message -
  From: b...@iswd.nl
  To: users@wicket.apache.org
  Date: 11.04.2012 00:51:38
  Subject: Re: Page Expired with Google Analytics Tracking Code
 
 
  Hi,
 
  It sounds a lot like you are not using models properly. E.g. your
  results method parameter has a length which overflows the page size
  (and thus the pagingnavigator renders page links), but on a second
  request the contents of results are null/empty?
 
  Try debugging PageableListView#populateItem() and check what its model
  points to.
 
  Can you be more specific with regard to they are not completely empty?
  What exactly do you see, and what do you expect?
 
  Kind regards,
 
  Bas
 
  Op 10-4-2012 22:19, schreef Andre Schütz:
  Hi,
 
  nobody an idea why the PageableListView is empty after clicking
  on one of the links from the PagingNavigator?
  After reloading of the page, the PageableListView is filled and
  once again empty when I click on oe of the links from the
  PagingNavigator.
 
  It seems, that the Listitem's are empty when I click on one of
  the links in the PagingNavigator. But there are definitely more
  items than just for one page and the PagingNavigator shows 6

Same versioned link opens different pages on different machines

2012-04-11 Thread Alec Swan

Hello,

I received a link from a customer to a versioned page (.version at the
end of the URL). However, when I click on the link I see a completely
different page.

We are using Wicket 1.4.17 and the page is mounted  as:

mount(new HybridUrlCodingStrategy(mp, MyPage.class));

Why is this happening and how can I fix this?

Thanks,

Alec

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

Re: Same versioned link opens different pages on different machines

2012-04-11 Thread Igor Vaynberg

page 5 in your session can be completely different then page 5 in
user's session.

non-bookmarkable urls cannot be emailed...thats kind of the point.

-igor

On Wed, Apr 11, 2012 at 2:37 PM, Alec Swan alecs...@gmail.com wrote:
 Hello,

 I received a link from a customer to a versioned page (.version at the
 end of the URL). However, when I click on the link I see a completely
 different page.

 We are using Wicket 1.4.17 and the page is mounted  as:

 mount(new HybridUrlCodingStrategy(mp, MyPage.class));

 Why is this happening and how can I fix this?

 Thanks,

 Alec

 -
 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: Same versioned link opens different pages on different machines

2012-04-11 Thread Bertrand Guay-Paquet


Hi,

A ticket regarding this was created and resolved in 1.5 (WICKET-4488). 
From the work log:

There was code for this situation but it didn't cover the case 100%.
Now if a request to page2?0 is made and the type of the found page with 
id=0 is not Page2 then a new instance of Page2 is instantiated.




On 11/04/2012 5:56 PM, Igor Vaynberg wrote:

page 5 in your session can be completely different then page 5 in
user's session.

non-bookmarkable urls cannot be emailed...thats kind of the point.

-igor

On Wed, Apr 11, 2012 at 2:37 PM, Alec Swanalecs...@gmail.com  wrote:

Hello,

I received a link from a customer to a versioned page (.version at the
end of the URL). However, when I click on the link I see a completely
different page.

We are using Wicket 1.4.17 and the page is mounted  as:

mount(new HybridUrlCodingStrategy(mp, MyPage.class));

Why is this happening and how can I fix this?

Thanks,

Alec

-
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: Page Map versions and Ajax Requests

2012-04-11 Thread Nelson Segura

I found the same problem, in my case it is page reload. I have a
simple QS that has a button that increments a counter using ajax. When
the user refreshes the page, the counter shows the correct number of
clicks. More clicks, and a new refresh, the counter shows as expected.
However, if I add an unrelated ListView to the same page, then page
refreshes do not reflect the clicks/ajax updates. This is because the
Ajax requests are going to a different version of the page as that one
being displayed. The list view is making the page dirty on each
refresh.
-nelson

On Fri, Dec 9, 2011 at 12:20 PM, Mark Lichtenberg
mlichtenb...@machenergy.com wrote:
 I'm seeing requests logged when the RequestLogger is enabled during page 
 reloads and when the back button is used. The same code under 1.4 does not. I 
 assumed the extra request was to fetch the latest render of the page if it 
 was updated via ajax.

 On Friday, December 9, 2011 at 1:59 PM, Dan Retzlaff wrote:

 I wouldn't say there are extra requests, just extra page versions due to
 re-population of the list view. Seems like the re-population process should
 be engineered in a way that doesn't advance the page number. But I'll leave
 that to the experts. :)

 On Fri, Dec 9, 2011 at 11:50 AM, Mark Lichtenberg 
 mlichtenb...@machenergy.com (mailto:mlichtenb...@machenergy.com) wrote:

  That's exactly what I'm experiencing. In 1.5 it appears there's a few
  extra requests during a reload that I assume are retrieving the latest page
  version. I'll create a bug report. Thanks for your help.
 
  Mark
 
  On Friday, December 9, 2011 at 1:26 PM, Dan Retzlaff wrote:
   I confirmed this behavior in our application. Simply reloading a page
 
  with
   a ListView a few times advances the page ID but not the URL. AJAX links
   know to target the new page ID, but any updates they make get lost if the
   page gets reloaded from the URL. Sounds like a bug to me. Wicket 1.4
  
 
  didn't
   behave this way.
  
   On Fri, Dec 9, 2011 at 10:26 AM, Dan Retzlaff dretzl...@gmail.com 
   (mailto:dretzl...@gmail.com)(mailto:
  dretzl...@gmail.com (mailto:dretzl...@gmail.com)) wrote:
  
Without reusing the ListView items, the item.add(...) will get called
with each render. I expect that'll cause
   
  
  
 
  MarkupContainer#addedComponent()
to WebPage#componentAdded() to WebPage#dirty() which sets a new page
  
 
  ID.
Sorry I don't have time to test the theory at the moment.
   
   
On Fri, Dec 9, 2011 at 8:27 AM, Mark Lichtenberg 
mlichtenb...@machenergy.com (mailto:mlichtenb...@machenergy.com)
   
  
 
  wrote:
   
 1.5.3.

 I've narrowed the problem to a ListView being present on the page.
 Whenever there's a ListView with setReuseItems set to false (the

   
   
  
 
  default)
 the Page ID gets incremented whenever the back button is used to
   
  
 
  return to
 the page. I confirmed this with a call to getPage().getPageId() in an
 onComponentTag method. After returning via the back button the URL

   
  
 
  is still
 at the original Page ID while there's a newer version in the page
   
  
 
  map.

 Without a ListView present on the page using the back button does not
 increment the Page ID and everything works as expected.

 I have a quickstart app that illustrates the problem. Here is the
  page
 with the applicable code: http://pastebin.com/jn9czHK8

 Mark


 On Friday, December 9, 2011 at 9:56 AM, Nazaret Kazarian wrote:
  Which version of Wicket are you using?
 
 
  2011/12/7 Lichtenberg, Mark mlichtenb...@machenergy.com 
  (mailto:mlichtenb...@machenergy.com) (mailto:
  mlichtenb...@machenergy.com (mailto:mlichtenb...@machenergy.com)) (mailto:
 mlichtenb...@machenergy.com (mailto:mlichtenb...@machenergy.com)):
   I have a page containing a number of AjaxLinks that when clicked
 


 fetch data
   and update some panels. When a user leaves one of these pages and
 


 returns
   via the back button the state of the page isn't always how they
 


   
  
 
  left
 


 it.
   However, this behavior happens only when the page is returned to
 


   
  
 
  the
 


 second
   time. Using the the request logger I've been able to partially
 


 explain this
   with the page IDs:
  
  
   1. First visit to page X has a page ID of 3
   2. AjaxLink requests for this page also have a page ID of 3.
   3. User leaves page then returns to page X via the back button;
  
 


   
  
 
  this
   request also has ID of 3
   4. User clicks AjaxLinks again, but here a new X page is created
  
 


 with an
   ID of 5
   5. User leaves page and again returns with the back button. Here
  
 


   
  
 
  the
   page state is as they left it in #2,

Re: Page Map versions and Ajax Requests

Yeah, that sounds like the same issue:
https://issues.apache.org/jira/browse/WICKET-4286

On Wed, Apr 11, 2012 at 6:52 PM, Nelson Segura nsegu...@gmail.com wrote:

 I found the same problem, in my case it is page reload. I have a
 simple QS that has a button that increments a counter using ajax. When
 the user refreshes the page, the counter shows the correct number of
 clicks. More clicks, and a new refresh, the counter shows as expected.
 However, if I add an unrelated ListView to the same page, then page
 refreshes do not reflect the clicks/ajax updates. This is because the
 Ajax requests are going to a different version of the page as that one
 being displayed. The list view is making the page dirty on each
 refresh.
 -nelson

 On Fri, Dec 9, 2011 at 12:20 PM, Mark Lichtenberg
 mlichtenb...@machenergy.com wrote:
  I'm seeing requests logged when the RequestLogger is enabled during page
 reloads and when the back button is used. The same code under 1.4 does not.
 I assumed the extra request was to fetch the latest render of the page if
 it was updated via ajax.
 
  On Friday, December 9, 2011 at 1:59 PM, Dan Retzlaff wrote:
 
  I wouldn't say there are extra requests, just extra page versions due to
  re-population of the list view. Seems like the re-population process
 should
  be engineered in a way that doesn't advance the page number. But I'll
 leave
  that to the experts. :)
 
  On Fri, Dec 9, 2011 at 11:50 AM, Mark Lichtenberg 
  mlichtenb...@machenergy.com (mailto:mlichtenb...@machenergy.com)
 wrote:
 
   That's exactly what I'm experiencing. In 1.5 it appears there's a few
   extra requests during a reload that I assume are retrieving the
 latest page
   version. I'll create a bug report. Thanks for your help.
  
   Mark
  
   On Friday, December 9, 2011 at 1:26 PM, Dan Retzlaff wrote:
I confirmed this behavior in our application. Simply reloading a
 page
  
   with
a ListView a few times advances the page ID but not the URL. AJAX
 links
know to target the new page ID, but any updates they make get lost
 if the
page gets reloaded from the URL. Sounds like a bug to me. Wicket 1.4
   
  
   didn't
behave this way.
   
On Fri, Dec 9, 2011 at 10:26 AM, Dan Retzlaff 
dretzl...@gmail.com(mailto:
 dretzl...@gmail.com)(mailto:
   dretzl...@gmail.com (mailto:dretzl...@gmail.com)) wrote:
   
 Without reusing the ListView items, the item.add(...) will get
 called
 with each render. I expect that'll cause

   
   
  
   MarkupContainer#addedComponent()
 to WebPage#componentAdded() to WebPage#dirty() which sets a new
 page
   
  
   ID.
 Sorry I don't have time to test the theory at the moment.


 On Fri, Dec 9, 2011 at 8:27 AM, Mark Lichtenberg 
 mlichtenb...@machenergy.com (mailto:mlichtenb...@machenergy.com)

   
  
   wrote:

  1.5.3.
 
  I've narrowed the problem to a ListView being present on the
 page.
  Whenever there's a ListView with setReuseItems set to false (the
 


   
  
   default)
  the Page ID gets incremented whenever the back button is used to

   
  
   return to
  the page. I confirmed this with a call to getPage().getPageId()
 in an
  onComponentTag method. After returning via the back button the
 URL
 

   
  
   is still
  at the original Page ID while there's a newer version in the
 page

   
  
   map.
 
  Without a ListView present on the page using the back button
 does not
  increment the Page ID and everything works as expected.
 
  I have a quickstart app that illustrates the problem. Here is
 the
   page
  with the applicable code: http://pastebin.com/jn9czHK8
 
  Mark
 
 
  On Friday, December 9, 2011 at 9:56 AM, Nazaret Kazarian wrote:
   Which version of Wicket are you using?
  
  
   2011/12/7 Lichtenberg, Mark mlichtenb...@machenergy.com(mailto:
 mlichtenb...@machenergy.com) (mailto:
   mlichtenb...@machenergy.com (mailto:mlichtenb...@machenergy.com))
 (mailto:
  mlichtenb...@machenergy.com (mailto:mlichtenb...@machenergy.com
 )):
I have a page containing a number of AjaxLinks that when
 clicked
  
 
 
  fetch data
and update some panels. When a user leaves one of these
 pages and
  
 
 
  returns
via the back button the state of the page isn't always how
 they
  
 
 

   
  
   left
  
 
 
  it.
However, this behavior happens only when the page is
 returned to
  
 
 

   
  
   the
  
 
 
  second
time. Using the the request logger I've been able to
 partially
  
 
 
  explain this
with the page IDs:
   
   
1. First visit to page X has a page ID of 3
2. AjaxLink requests for this page also have a page ID of 3.
3. User leaves page then returns to page X via the back
 button;

Re: Page Map versions and Ajax Requests

2012-04-11 Thread Nelson Segura

This is easily reproduceable in the wicket sample pages:

http://www.wicket-library.com/wicket-examples/ajax/links

1. Click on the increment link for Counter 2 for times. Counter shows 4.
2. CTRL-R/refresh 4 times, the counter still shows 4.
3. Click on link 4 more times. Counter shows 8
4.CTRL-R/refresh once more, the counter shows 4!

I don't know exactly what is making the page dirty in this case.

Can you confirm this behavior in the sample page?

-Nelson

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

Re: Page Map versions and Ajax Requests

2012-04-11 Thread Nelson Segura

Sorry, you dont have to refresh 4 times, just once :p
-Nelson

On Wed, Apr 11, 2012 at 6:08 PM, Nelson Segura nsegu...@gmail.com wrote:
 This is easily reproduceable in the wicket sample pages:

 http://www.wicket-library.com/wicket-examples/ajax/links

 1. Click on the increment link for Counter 2 for times. Counter shows 4.
 2. CTRL-R/refresh 4 times, the counter still shows 4.
 3. Click on link 4 more times. Counter shows 8
 4.CTRL-R/refresh once more, the counter shows 4!

 I don't know exactly what is making the page dirty in this case.

 Can you confirm this behavior in the sample page?

 -Nelson

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

RE: Error during start of wicket application

2012-04-11 Thread Alex Rass

Seems like a classpath issue.
Make sure that all the wicket jars that you need are included in your path.

- Alex 

-Original Message-
From: André Schütz [mailto:andre-p...@gmx.de] 
Sent: Thursday, February 23, 2012 12:13 PM
To: users@wicket.apache.org
Subject: Error during start of wicket application

Hello,

I get the following error message during a start of the tomcat server with a 
clean packed wicket application:

/**
 * BEGIN
 */

Exception in thread Thread-2 java.lang.NoClassDefFoundError: 
org/apache/wicket/ApplicationListenerCollection$2
at 
org.apache.wicket.ApplicationListenerCollection.onBeforeDestroyed(ApplicationListenerCollection.java:44)
at org.apache.wicket.Application.internalDestroy(Application.java:639)
at 
org.apache.wicket.protocol.http.WebApplication.internalDestroy(WebApplication.java:563)
at 
org.apache.wicket.protocol.http.WicketFilter.destroy(WicketFilter.java:478)
at 
org.apache.catalina.core.ApplicationFilterConfig.release(ApplicationFilterConfig.java:357)
at 
org.apache.catalina.core.StandardContext.filterStop(StandardContext.java:3873)
at 
org.apache.catalina.core.StandardContext.stop(StandardContext.java:4605)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1098)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1098)
at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:448)
at 
org.apache.catalina.core.StandardService.stop(StandardService.java:584)
at org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)
at org.apache.catalina.startup.Catalina.stop(Catalina.java:643)
at 
org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catalina.java:687)
Caused by: java.lang.ClassNotFoundException: 
org.apache.wicket.ApplicationListenerCollection$2
at 
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1484)
at 
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1329)
... 14 more

/**
 * END
 */

Any ideas about this error?

Thanks,
Andre
--
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis 
zu 50,- Euro! https://freundschaftswerbung.gmx.de

-
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: Page Map versions and Ajax Requests

 I don't know exactly what is making the page dirty in this case.

The AJAX debug window has a ListView in it.

On Wed, Apr 11, 2012 at 7:09 PM, Nelson Segura nsegu...@gmail.com wrote:

 Sorry, you dont have to refresh 4 times, just once :p
 -Nelson

 On Wed, Apr 11, 2012 at 6:08 PM, Nelson Segura nsegu...@gmail.com wrote:
  This is easily reproduceable in the wicket sample pages:
 
  http://www.wicket-library.com/wicket-examples/ajax/links
 
  1. Click on the increment link for Counter 2 for times. Counter shows 4.
  2. CTRL-R/refresh 4 times, the counter still shows 4.
  3. Click on link 4 more times. Counter shows 8
  4.CTRL-R/refresh once more, the counter shows 4!
 
  I don't know exactly what is making the page dirty in this case.
 
  Can you confirm this behavior in the sample page?
 
  -Nelson

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

tomcat deployment issues

2012-04-11 Thread Alex Rass

If someone could help me out with this issue, that would be awesome.

Currently:
Deploying on Tomcat 6.

Default deploy folder is webapps
webapps/ROOT is where my 1st wicket app is (lets call it App1)
webapps.web2 is another Host record for a different URL.
webapps.web2/app2 is my wicket app #2

No matter what I tried, app#2 doesn't get started (but servlets from same 
context work fine).
When I go to the url, it says:

java.lang.IllegalStateException: Application with name 'App2' already exists.'
org.apache.wicket.Application.setName(Application.java:854)
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:337)

org.apache.wicket.protocol.http.WicketServlet.init(WicketServlet.java:271)
javax.servlet.GenericServlet.init(GenericServlet.java:212)
...

I tried renaming it to App3 (in web.xml and I get same message except it says 
App3).
I checked all the web.xml files on the server, no other one has App2 in it.

I have lib folders under each app. I don't share anything beside DB drivers in 
Tomcat's lib folder.
I have Wicket 1.5.4 for App1 and 1.5.5 for App2 (donno if that makes a diff).

Any ideas?

Regards,
- Alex.



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

IDataProvider#size()

Hi all. Time to start a thread of my own. :)

Many of Wicket's powerful repeaters depend on IDataProvider. This interface
has a size() method which returns a non-null integer. This makes it easy to
determine the total number of pages in a pageable view, but IMO the
required computation and application complexity are not always called for.
In many cases, a pageable but open-ended data view is adequate. Have you
experienced this impedance mismatch yourselves? What was your solution?

To elaborate on my experience:

For SQL-based views, the application complexity comes from the need to
construct a count(*) query with exactly the same criteria as the subsequent
result query. In my experience, this pollutes DAO interfaces and
IDataProvider implementation non-trivially. We initially had separate
methods for counting and querying (same args), but eventually moved to a
single method that returns a List,Integer-tuple with both the results and
total size which our IDataProvider caches. This lets us do some Hibernate
trickery to introduce a MySQL SQL_CALC_FOUND_ROWS query hint, avoiding
separate count/results queries in most cases. It's still not simple, and
for large counts is still expensive.

The situation is worse for non-SQL data stores which don't have a
fully-functional count(*) capability. We use Cassandra whose native where
clause support is limited, requiring significant client-side filtering.
Paging through an entire column (or CF) in this way is prohibitively
expensive, especially considering our users rarely even go to page 2. To
solve this, we've created a parallel set of view/paging classes that define
windows using previously discovered result keys instead of start indices
(tokens and column names in Cassandra). But having a full suite of
IUnsizedDataProvider-based classes smells. I love that Wicket devs have
solved some tough/tedious problems with DataViewBase and friends, and I
want to make use of them!

Comments or suggestions?

Cheers,
Dan

Wicket 1.5 - Generic JSON Response

2012-04-11 Thread Ahijah

I've been working on various implementations of this all day, to try and
output a simple JSON response, as Content-Type: application/json, with
absolutely no luck.  My current class is setup as below.  However, when
sending a request to the Feed URL, it comes back as text/plain, with the
JSON formatted string embedded below.  What am I doing wrong?  Thanks.

-
public class Feed extends WebPage implements IMarkupResourceStreamProvider {

private static final long serialVersionUID = 1L;

@Override 
protected void configureResponse(WebResponse response) { 
super.configureResponse(response); 
response.setContentType(application/json); 
response.addHeader(Content-Type, application/json);
} 

@Override 
public void renderPage() { 
   
getResponse().write([{'id':111,'title':'MainEvent','start':'2012-04-10T07:00:00','end':'2012-04-10T09:30:00','url':'?EventID=111','allDay':false}]);
 
} 

public IResourceStream getMarkupResourceStream(MarkupContainer 
container,
Class? containerClass) { 
return new StringResourceStream(); 
} 

}

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-Generic-JSON-Response-tp4550807p4550807.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: Wicket 1.5 - Generic JSON Response