Re: [WARN]Falling back to Redirect_To_Buffer render

[Martin Grigorov]

Put a breakpoint at WebPageRenderer#respond() and see.
It is not always possible to use ONE_PASS_RENDER because in this case
the Url in the address bar will become invalid for the currently
renderer page. And then if for example your user use F5 to refresh the
page he will see completely different page then the one (s)he just
had.

On Thu, Aug 30, 2012 at 2:42 AM, sudeivas  wrote:
> is it possible to find why its not using 'ONE_PASS_RENDER' ? I just want to
> make sure that I am not missing any configuration.
>
>
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/WARN-Falling-back-to-Redirect-To-Buffer-render-tp4651567p4651622.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: ObjectAutoCompleteBuilder in wicket 1.5.7 get is not a valid Serializable" error.

[Vignesh Palanisamy]

Hi martin,

   As well as i had implement the Serializable in Anonymous inner
class (DefaultObjectAutoCompleteBuilder.class) of HomePage now the
Exception didn't come but one warning message came like this.

WARN  - WebSession - Component-targetted feedback message
was left unrendered. This could be because you are missing a FeedbackPanel
on the page.  Message: [FeedbackMessage message = "'S' is not a valid
Serializable.", reporter = hiddenId, level = ERROR]

and the form doesn't submit.

-Vignesh Palanisamy

Re: ObjectAutoCompleteBuilder in wicket 1.5.7 get is not a valid Serializable" error.

[Sven Meier]

Check the first anonymous class inside HomePage, it is not serializable.

Sven

On 08/30/2012 06:12 AM, Vignesh Palanisamy wrote:

hi martin..

i implement Serializable for searchOption then i run It and gives error on
status class and i had implement serializable to status class too,

Now it gives this error exception.


ERROR - JavaSerializer - Error serializing object class
org.apache.wicket.quickstart.HomePage [object=[Page class =
org.apache.wicket.quickstart.HomePage, id = 0, render count = 1]]
org.apache.wicket.util.io.SerializableChecker$WicketNotSerializableException:
Unable to serialize class: org.apache.wicket.quickstart.HomePage$1
Field hierarchy is:
   0 [class=org.apache.wicket.quickstart.HomePage, path=0]
 private java.lang.Object org.apache.wicket.MarkupContainer.children
[class=[Ljava.lang.Object;]
   private java.lang.Object
org.apache.wicket.MarkupContainer.children[1]
[class=org.apache.wicket.markup.html.form.Form, path=0:form]
 private java.lang.Object org.apache.wicket.MarkupContainer.children
[class=org.wicketstuff.objectautocomplete.ObjectAutoCompleteField,
path=0:form:status]
   private final java.util.List
org.wicketstuff.objectautocomplete.ObjectAutoCompleteField.selectionChangeListeners
[class=java.util.ArrayList]
 private final java.util.List
org.wicketstuff.objectautocomplete.ObjectAutoCompleteField.selectionChangeListeners[write:1]
[class=org.apache.wicket.quickstart.DefaultObjectAutoCompleteBuilder$2]
   final
org.apache.wicket.quickstart.DefaultObjectAutoCompleteBuilder
org.apache.wicket.quickstart.DefaultObjectAutoCompleteBuilder$2.this$0
[class=org.apache.wicket.quickstart.HomePage$1] <- field that is not
serializable
 at
org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:395)
 at
org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
 at
org.apache.wicket.util.io.SerializableChecker.checkFields(SerializableChecker.java:655)
 at
org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:578)
 at
org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
 at
org.apache.wicket.util.io.SerializableChecker.access$500(SerializableChecker.java:65)
 at
org.apache.wicket.util.io.SerializableChecker$1InterceptingObjectOutputStream.replaceObject(SerializableChecker.java:534)
 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1124)
 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
 at java.util.ArrayList.writeObject(ArrayList.java:570)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at
java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
 at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469)
 at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
 at
org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:541)
 at
org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
 at
org.apache.wicket.util.io.SerializableChecker.checkFields(SerializableChecker.java:655)
 at
org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:578)
 at
org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
 at
org.apache.wicket.util.io.SerializableChecker.checkFields(SerializableChecker.java:655)
 at
org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:578)
 at
org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
 at
org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:440)
 at
org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
 at
org.apache.wicket.util.io.SerializableChecker.checkFields(SerializableChecker.java:655)
 at
org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:578)
 at
org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
 at
org.apache.wicket.util.io.SerializableChecker.writeObjectOverride(SerializableChecker.java:724)
 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
 at
org.apache.wicket.serialize.java.JavaSerializer$CheckerObjectOutputStream.writeObjectOverride(JavaSerializer.java:258)
 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
 at
org.apache.wick

Re: ObjectAutoCompleteBuilder in wicket 1.5.7 get is not a valid Serializable" error.

[Vignesh Palanisamy]

hi martin..

i implement Serializable for searchOption then i run It and gives error on
status class and i had implement serializable to status class too,

Now it gives this error exception.


ERROR - JavaSerializer - Error serializing object class
org.apache.wicket.quickstart.HomePage [object=[Page class =
org.apache.wicket.quickstart.HomePage, id = 0, render count = 1]]
org.apache.wicket.util.io.SerializableChecker$WicketNotSerializableException:
Unable to serialize class: org.apache.wicket.quickstart.HomePage$1
Field hierarchy is:
  0 [class=org.apache.wicket.quickstart.HomePage, path=0]
private java.lang.Object org.apache.wicket.MarkupContainer.children
[class=[Ljava.lang.Object;]
  private java.lang.Object
org.apache.wicket.MarkupContainer.children[1]
[class=org.apache.wicket.markup.html.form.Form, path=0:form]
private java.lang.Object org.apache.wicket.MarkupContainer.children
[class=org.wicketstuff.objectautocomplete.ObjectAutoCompleteField,
path=0:form:status]
  private final java.util.List
org.wicketstuff.objectautocomplete.ObjectAutoCompleteField.selectionChangeListeners
[class=java.util.ArrayList]
private final java.util.List
org.wicketstuff.objectautocomplete.ObjectAutoCompleteField.selectionChangeListeners[write:1]
[class=org.apache.wicket.quickstart.DefaultObjectAutoCompleteBuilder$2]
  final
org.apache.wicket.quickstart.DefaultObjectAutoCompleteBuilder
org.apache.wicket.quickstart.DefaultObjectAutoCompleteBuilder$2.this$0
[class=org.apache.wicket.quickstart.HomePage$1] <- field that is not
serializable
at
org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:395)
at
org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
at
org.apache.wicket.util.io.SerializableChecker.checkFields(SerializableChecker.java:655)
at
org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:578)
at
org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
at
org.apache.wicket.util.io.SerializableChecker.access$500(SerializableChecker.java:65)
at
org.apache.wicket.util.io.SerializableChecker$1InterceptingObjectOutputStream.replaceObject(SerializableChecker.java:534)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1124)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
at java.util.ArrayList.writeObject(ArrayList.java:570)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
at
org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:541)
at
org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
at
org.apache.wicket.util.io.SerializableChecker.checkFields(SerializableChecker.java:655)
at
org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:578)
at
org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
at
org.apache.wicket.util.io.SerializableChecker.checkFields(SerializableChecker.java:655)
at
org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:578)
at
org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
at
org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:440)
at
org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
at
org.apache.wicket.util.io.SerializableChecker.checkFields(SerializableChecker.java:655)
at
org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:578)
at
org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
at
org.apache.wicket.util.io.SerializableChecker.writeObjectOverride(SerializableChecker.java:724)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
at
org.apache.wicket.serialize.java.JavaSerializer$CheckerObjectOutputStream.writeObjectOverride(JavaSerializer.java:258)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
at
org.apache.wicket.serialize.java.JavaSerializer.serialize(JavaSerializer.java:77)
at
org.apache.wicket.pageStore.DefaultPageStore.serializePage(DefaultPageStore.java:368)
at
org.apach

override wicket mark up

[ramlael]

Hi Friends, 

I would like to override wicket page, will have same wicket id's with
different parent ids. 
Is it possible in wicket please help me... 

http://apache-wicket.1842946.n4.nabble.com/file/n4651624/wikcet-problem.png 

Regards,
Rambabu



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/override-wicket-mark-up-tp4651624.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: ObjectAutoCompleteBuilder in wicket 1.5.7 get is not a valid Serializable" error.

[Vignesh Palanisamy]

while implementing Serializable also the same error came martin!


On Wed, Aug 29, 2012 at 6:17 PM, Martin Grigorov wrote:

> This line says it all:
>
> private java.lang.Object
> org.apache.wicket.model.CompoundPropertyModel.target
> [class=org.apache.wicket.quickstart.HomePage$SearchOptions] <-
> field that is not serializable
>
>
> HomePage$SearchOptions is not Serializable
>
> On Wed, Aug 29, 2012 at 11:20 AM, Vignesh Palanisamy
>  wrote:
> > Hi martin,
> >
> >  Thanks for reply,
> >
> >  This is the log with exception stack trace:
> >
> >   ERROR - JavaSerializer - Error serializing object class
> > org.apache.wicket.quickstart.HomePage [object=[Page class =
> > org.apache.wicket.quickstart.HomePage, id = 0, render count = 1]]
> >
> org.apache.wicket.util.io.SerializableChecker$WicketNotSerializableException:
> > Unable to serialize class:
> > org.apache.wicket.quickstart.HomePage$SearchOptions
> > Field hierarchy is:
> >   0 [class=org.apache.wicket.quickstart.HomePage, path=0]
> > private java.lang.Object org.apache.wicket.MarkupContainer.children
> > [class=[Ljava.lang.Object;]
> >   private java.lang.Object
> org.apache.wicket.MarkupContainer.children[1]
> > [class=org.apache.wicket.markup.html.form.Form, path=0:form]
> > java.lang.Object org.apache.wicket.Component.data
> > [class=org.apache.wicket.model.CompoundPropertyModel]
> >   private java.lang.Object
> > org.apache.wicket.model.CompoundPropertyModel.target
> > [class=org.apache.wicket.quickstart.HomePage$SearchOptions] <- field
> > that is not serializable
> > at
> >
> org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:395)
> > at
> >
> org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
> > at
> >
> org.apache.wicket.util.io.SerializableChecker.checkFields(SerializableChecker.java:655)
> > at
> >
> org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:578)
> > at
> >
> org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
> > at
> >
> org.apache.wicket.util.io.SerializableChecker.checkFields(SerializableChecker.java:655)
> > at
> >
> org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:578)
> > at
> >
> org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
> > at
> >
> org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:440)
> > at
> >
> org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
> > at
> >
> org.apache.wicket.util.io.SerializableChecker.checkFields(SerializableChecker.java:655)
> > at
> >
> org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:578)
> > at
> >
> org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
> > at
> >
> org.apache.wicket.util.io.SerializableChecker.writeObjectOverride(SerializableChecker.java:724)
> > at
> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
> > at
> >
> org.apache.wicket.serialize.java.JavaSerializer$CheckerObjectOutputStream.writeObjectOverride(JavaSerializer.java:258)
> > at
> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
> > at
> >
> org.apache.wicket.serialize.java.JavaSerializer.serialize(JavaSerializer.java:77)
> > at
> >
> org.apache.wicket.pageStore.DefaultPageStore.serializePage(DefaultPageStore.java:368)
> > at
> >
> org.apache.wicket.pageStore.DefaultPageStore.storePage(DefaultPageStore.java:146)
> > at
> >
> org.apache.wicket.page.PageStoreManager$PersistentRequestAdapter.storeTouchedPages(PageStoreManager.java:383)
> > at
> >
> org.apache.wicket.page.RequestAdapter.commitRequest(RequestAdapter.java:171)
> > at
> >
> org.apache.wicket.page.AbstractPageManager.commitRequest(AbstractPageManager.java:94)
> > at
> >
> org.apache.wicket.page.PageManagerDecorator.commitRequest(PageManagerDecorator.java:68)
> > at
> >
> org.apache.wicket.page.PageAccessSynchronizer$2.commitRequest(PageAccessSynchronizer.java:281)
> > at org.apache.wicket.Application$2.onDetach(Application.java:1598)
> > at
> >
> org.apache.wicket.request.cycle.RequestCycleListenerCollection$3.notify(RequestCycleListenerCollection.java:99)
> > at
> >
> org.apache.wicket.request.cycle.RequestCycleListenerCollection$3.notify(RequestCycleListenerCollection.java:97)
> > at
> >
> org.apache.wicket.util.listener.ListenerCollection$1.notify(ListenerCollection.java:119)
> > at
> >
> org.apache.wicket.util.listener.ListenerCollection.reversedNotify(ListenerCollection.java:143)
> > at
> >
> org.apache.wicket.util.listener.ListenerCollection.reversedNotifyIgnoringExceptions(ListenerCollection.java:113)
> > at
> >
> org.apache.wicket.request.cycle.RequestCycleListenerCollection.onDetach(RequestCycleListenerCollec

Re: [WARN]Falling back to Redirect_To_Buffer render

[sudeivas]

is it possible to find why its not using 'ONE_PASS_RENDER' ? I just want to
make sure that I am not missing any configuration.



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/WARN-Falling-back-to-Redirect-To-Buffer-render-tp4651567p4651622.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: Css for panel

[Mansour Al Akeel]

Thank you all.


On Wed, Aug 29, 2012 at 1:49 PM, Paul Bors  wrote:
> See "Including CSS resources" at:
> https://cwiki.apache.org/WICKET/including-css-resources.html
>
> This is also covered by all of the books on Wicket:
> http://wicket.apache.org/learn/books/
>
> You should invest into such a Book.
> Personally I suggest "Wicket in Action" since its authors are Wicket
> developers and you see their names in many of the replies on those mailing
> lists :)
>
> http://wicket.apache.org/learn/books/wia.html
>
> ~ Thank you,
>   Paul Bors
>
> -Original Message-
> From: ronny.v...@consult.nordea.com [mailto:ronny.v...@consult.nordea.com]
> Sent: Wednesday, August 29, 2012 1:31 PM
> To: users@wicket.apache.org
> Subject: RE: Css for panel
>
> Hi
>
> Actually I am pretty new with Wicket, but I give it a shot... :-)
>
> @Override
> public void renderHead(IHeaderResponse response) {
> super.renderHead(response);
> response.renderCSSReference(YOUR_CSS_REF);
> }
>
> private static final ResourceReference YOUR_CSS_REF = new
> PackageResourceReference(...
>
>
> -Original Message-
> From: Mansour Al Akeel [mailto:mansour.alak...@gmail.com]
> Sent: 29 August 2012 19:20
> To: users
> Subject: Css for panel
>
> I have a component that extends panel. I need to add css customization to
> this panel. I can include the css in the over all site CSS, but I like to
> separate the CSS for this panel. For example,
>
> MyPanel.java
> MyPanel.html
> MyPanel.css
>
> I like to have MyPanel.css included in the header of the html when ever
> MyPanel is used.
> How do I do this with wicket 6.0 ??
>
> Thank you.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>

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

RE: Css for panel

[Paul Bors]

See "Including CSS resources" at:
https://cwiki.apache.org/WICKET/including-css-resources.html

This is also covered by all of the books on Wicket:
http://wicket.apache.org/learn/books/

You should invest into such a Book.
Personally I suggest "Wicket in Action" since its authors are Wicket
developers and you see their names in many of the replies on those mailing
lists :)

http://wicket.apache.org/learn/books/wia.html

~ Thank you,
  Paul Bors

-Original Message-
From: ronny.v...@consult.nordea.com [mailto:ronny.v...@consult.nordea.com] 
Sent: Wednesday, August 29, 2012 1:31 PM
To: users@wicket.apache.org
Subject: RE: Css for panel

Hi

Actually I am pretty new with Wicket, but I give it a shot... :-)

@Override
public void renderHead(IHeaderResponse response) {
super.renderHead(response);
response.renderCSSReference(YOUR_CSS_REF);
}

private static final ResourceReference YOUR_CSS_REF = new
PackageResourceReference(...


-Original Message-
From: Mansour Al Akeel [mailto:mansour.alak...@gmail.com] 
Sent: 29 August 2012 19:20
To: users
Subject: Css for panel

I have a component that extends panel. I need to add css customization to
this panel. I can include the css in the over all site CSS, but I like to
separate the CSS for this panel. For example,

MyPanel.java
MyPanel.html
MyPanel.css

I like to have MyPanel.css included in the header of the html when ever
MyPanel is used.
How do I do this with wicket 6.0 ??

Thank you.

-
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: Css for panel

[Ronny.Voss]

Hi

Actually I am pretty new with Wicket, but I give it a shot... :-)

@Override
public void renderHead(IHeaderResponse response) {
super.renderHead(response);
response.renderCSSReference(YOUR_CSS_REF);
}

private static final ResourceReference YOUR_CSS_REF = new 
PackageResourceReference(...


-Original Message-
From: Mansour Al Akeel [mailto:mansour.alak...@gmail.com] 
Sent: 29 August 2012 19:20
To: users
Subject: Css for panel

I have a component that extends panel. I need to add css customization to this 
panel. I can include the css in the over all site CSS, but I like to separate 
the CSS for this panel. For example,

MyPanel.java
MyPanel.html
MyPanel.css

I like to have MyPanel.css included in the header of the html when ever MyPanel 
is used.
How do I do this with wicket 6.0 ??

Thank you.

-
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

Css for panel

[Mansour Al Akeel]

I have a component that extends panel. I need to add css customization
to this panel. I can include the css in the over all site CSS, but
I like to separate the CSS for this panel. For example,

MyPanel.java
MyPanel.html
MyPanel.css

I like to have MyPanel.css included in the header of the html when
ever MyPanel is used.
How do I do this with wicket 6.0 ??

Thank you.

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

Re: ajax and browser back button in wicket 6

[Alec Swan]

I found the following class which adds back button support to AJAX
components: 
http://grepcode.com/file/repo1.maven.org/maven2/org.wicketstuff/jquery-examples/1.4.7/org/wicketstuff/jquery/ajaxbackbutton/Page4AjaxBackButton.java

Is this the recommended solution for 1.4.x? What are other alternatives?

Thanks,

Alec

On Tue, Jul 24, 2012 at 8:37 AM, Martin Grigorov  wrote:
> Hi Steve,
>
> There is nothing new about this in Wicket 6.
> It is as in Wicket 1.5 - back button is not supported out of the box for Ajax.
>
> On Tue, Jul 24, 2012 at 4:48 PM, Steve Lowery
>  wrote:
>> I did a search in the user list and found several references of various
>> ways to solve the back button using ajax problem, but most were a few years
>> old.  I was wondering if wicket 6 does can do this out of the box now.  One
>> of the stated goals on the wicket site is that it will "Fully solve back
>> button problem".  Does this hold true for ajax requests or just plain http
>> requests (or both)?
>
>
>
> --
> 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: Best practices for passing configurations, such as Facebook app_id, to JavaScript

[Alec Swan]

I implemented the solution proposed by Fergal, but I think I will redo
it with Pointbreak's approach which seems to be cleaner.

Thanks!

Alec

On Wed, Aug 29, 2012 at 7:20 AM, Pointbreak
 wrote:
> I would use PackageTextTemplate to render the javascript, e.g. put your
> javascript in MyPage.js along with the other templates, and use
> ${facebookId} for the id, then add this to your class:
>
> @Override public void renderHead(IHeaderResponse response) {
> super.renderHead(response);
> PackageTextTemplate javascript = new
> PackageTextTemplate(MyPage.class, MyPage.class.getSimpleName() +
> ".js");
> Map vars = new HashMap();
> vars.put("facebookId", facebookId);
> response.renderOnDomReadyJavaScript(javascript.asString(vars));
> }
>
> On Wed, Aug 29, 2012, at 15:09, Fergal Keating wrote:
>> *HTML*
>> *
>> *
>>
>> /* script will be
>> rendered here */
>>
>> *JAVA*
>>
>> String FacbookJS = " var facebookID = \"" +
>> this.getfacebookID(CurrentDomain) + "\"); ";
>> Label FacebookLabel = new Label("Facebookjs", FacbookJS );
>>
>> addOrReplace( FacebookLabel.setEscapeModelStrings(false));
>>
>> On 27 August 2012 15:33, Alec Swan  wrote:
>>
>> > Hello,
>> >
>> > We deploy our web app on different domains which means that JavaScript
>> > Facebook integration needs to use different app_id values. I am
>> > planning to store these values in a configuration file and wonder how
>> > to expose them to JavaScript. I would also like to write a unit test
>> > that verifies that settings were passed correctly.
>> >
>> > I could use a HeaderContributor to inject raw JavaScript, but this
>> > doesn't seem to be very unit-testable. I could create a  which
>> > attributes/elements contain the settings, which seems to be more
>> > unit-testable.
>> >
>> > Thoughts?
>> >
>> > Thanks,
>> >
>> > Alec
>> >
>> > -
>> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> > For additional commands, e-mail: users-h...@wicket.apache.org
>> >
>> >
>>
>>
>> --
>> Fergal Keating
>> IT Senior Engineer
>> ---
>> e. fergal.keat...@directski.com
>> p. NA
>> w. www.directski.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: Nested form submit problem

[Sandor Feher]

Many thanks Paul, I will go ahead.



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Nested-form-submit-problem-tp4651565p4651608.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: Nested form submit problem

[Paul Bors]

Looking over your model_copy.png I feel that my original suggestion holds.

* Have each of the rows holding on to the questions as Panels that extend an
interface you come up with to persist the question.
* Have the Repeating view's model be a list of Panels (I usually use
DataTables for this).
* When you submit the outer form, iterate through the repeating view's list
of Panels and call back to the interface methods that your create to persist
each of the questions.

Also you can still look over the Wizard and adopt that to your use-case.
Just think that each of the questions is a step in a Wizard only that you're
displaying all panels at once.

~ Thank you,
  Paul Bors

-Original Message-
From: Sandor Feher [mailto:sfe...@bluesystem.hu] 
Sent: Wednesday, August 29, 2012 3:00 AM
To: users@wicket.apache.org
Subject: RE: Nested form submit problem


Paul Bors wrote
> 
> Must you really have a nested form here?
> 
I think yes. I tried to sketch what I need for better understanding. For
example there is a quiestionnarie has five questions. Every question has id
and max points can be given and so one. I store the result in a result table
and get the ids and max points from a param table. So I created a form for
buttons and as many nested forms as questions I have. Every questions has
it's own model because they will be stored in different records.
The main goal is to submit once and persist all of the nested models while
get value field validated at field level. The problem is that I can only
persist my models at nested form's level on onSubmit event while onSubmit
fires even I click on reset or delete or whatever on the parent form.
I hope it's more clear now and sorry for making noise. Please suggest what
could be the best approach to achieve this. 

TIA, Sandor


http://apache-wicket.1842946.n4.nabble.com/file/n4651589/modell_copy.png 



--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Nested-form-submit-problem-tp4651
565p4651589.html
Sent from the Users forum mailing list archive at Nabble.com.

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



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

wicket jquery

[Pratibha]

 



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/wicket-jquery-tp4651606.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: Best practices for passing configurations, such as Facebook app_id, to JavaScript

[Pointbreak]

I would use PackageTextTemplate to render the javascript, e.g. put your
javascript in MyPage.js along with the other templates, and use
${facebookId} for the id, then add this to your class:

@Override public void renderHead(IHeaderResponse response) {
super.renderHead(response);
PackageTextTemplate javascript = new
PackageTextTemplate(MyPage.class, MyPage.class.getSimpleName() +
".js");
Map vars = new HashMap();
vars.put("facebookId", facebookId);
response.renderOnDomReadyJavaScript(javascript.asString(vars));
}

On Wed, Aug 29, 2012, at 15:09, Fergal Keating wrote:
> *HTML*
> *
> *
> 
> /* script will be
> rendered here */
> 
> *JAVA*
> 
> String FacbookJS = " var facebookID = \"" +
> this.getfacebookID(CurrentDomain) + "\"); ";
> Label FacebookLabel = new Label("Facebookjs", FacbookJS );
> 
> addOrReplace( FacebookLabel.setEscapeModelStrings(false));
> 
> On 27 August 2012 15:33, Alec Swan  wrote:
> 
> > Hello,
> >
> > We deploy our web app on different domains which means that JavaScript
> > Facebook integration needs to use different app_id values. I am
> > planning to store these values in a configuration file and wonder how
> > to expose them to JavaScript. I would also like to write a unit test
> > that verifies that settings were passed correctly.
> >
> > I could use a HeaderContributor to inject raw JavaScript, but this
> > doesn't seem to be very unit-testable. I could create a  which
> > attributes/elements contain the settings, which seems to be more
> > unit-testable.
> >
> > Thoughts?
> >
> > Thanks,
> >
> > Alec
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
> 
> 
> -- 
> Fergal Keating
> IT Senior Engineer
> ---
> e. fergal.keat...@directski.com
> p. NA
> w. www.directski.com

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

Re: Best practices for passing configurations, such as Facebook app_id, to JavaScript

[Fergal Keating]

*HTML*
*
*

/* script will be
rendered here */

*JAVA*

String FacbookJS = " var facebookID = \"" +
this.getfacebookID(CurrentDomain) + "\"); ";
Label FacebookLabel = new Label("Facebookjs", FacbookJS );

addOrReplace( FacebookLabel.setEscapeModelStrings(false));

On 27 August 2012 15:33, Alec Swan  wrote:

> Hello,
>
> We deploy our web app on different domains which means that JavaScript
> Facebook integration needs to use different app_id values. I am
> planning to store these values in a configuration file and wonder how
> to expose them to JavaScript. I would also like to write a unit test
> that verifies that settings were passed correctly.
>
> I could use a HeaderContributor to inject raw JavaScript, but this
> doesn't seem to be very unit-testable. I could create a  which
> attributes/elements contain the settings, which seems to be more
> unit-testable.
>
> Thoughts?
>
> Thanks,
>
> Alec
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-- 
Fergal Keating
IT Senior Engineer
---
e. fergal.keat...@directski.com
p. NA
w. www.directski.com

Re: ObjectAutoCompleteBuilder in wicket 1.5.7 get is not a valid Serializable" error.

[Martin Grigorov]

This line says it all:

private java.lang.Object
org.apache.wicket.model.CompoundPropertyModel.target
[class=org.apache.wicket.quickstart.HomePage$SearchOptions] <-
field that is not serializable


HomePage$SearchOptions is not Serializable

On Wed, Aug 29, 2012 at 11:20 AM, Vignesh Palanisamy
 wrote:
> Hi martin,
>
>  Thanks for reply,
>
>  This is the log with exception stack trace:
>
>   ERROR - JavaSerializer - Error serializing object class
> org.apache.wicket.quickstart.HomePage [object=[Page class =
> org.apache.wicket.quickstart.HomePage, id = 0, render count = 1]]
> org.apache.wicket.util.io.SerializableChecker$WicketNotSerializableException:
> Unable to serialize class:
> org.apache.wicket.quickstart.HomePage$SearchOptions
> Field hierarchy is:
>   0 [class=org.apache.wicket.quickstart.HomePage, path=0]
> private java.lang.Object org.apache.wicket.MarkupContainer.children
> [class=[Ljava.lang.Object;]
>   private java.lang.Object org.apache.wicket.MarkupContainer.children[1]
> [class=org.apache.wicket.markup.html.form.Form, path=0:form]
> java.lang.Object org.apache.wicket.Component.data
> [class=org.apache.wicket.model.CompoundPropertyModel]
>   private java.lang.Object
> org.apache.wicket.model.CompoundPropertyModel.target
> [class=org.apache.wicket.quickstart.HomePage$SearchOptions] <- field
> that is not serializable
> at
> org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:395)
> at
> org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
> at
> org.apache.wicket.util.io.SerializableChecker.checkFields(SerializableChecker.java:655)
> at
> org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:578)
> at
> org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
> at
> org.apache.wicket.util.io.SerializableChecker.checkFields(SerializableChecker.java:655)
> at
> org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:578)
> at
> org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
> at
> org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:440)
> at
> org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
> at
> org.apache.wicket.util.io.SerializableChecker.checkFields(SerializableChecker.java:655)
> at
> org.apache.wicket.util.io.SerializableChecker.internalCheck(SerializableChecker.java:578)
> at
> org.apache.wicket.util.io.SerializableChecker.check(SerializableChecker.java:374)
> at
> org.apache.wicket.util.io.SerializableChecker.writeObjectOverride(SerializableChecker.java:724)
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
> at
> org.apache.wicket.serialize.java.JavaSerializer$CheckerObjectOutputStream.writeObjectOverride(JavaSerializer.java:258)
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
> at
> org.apache.wicket.serialize.java.JavaSerializer.serialize(JavaSerializer.java:77)
> at
> org.apache.wicket.pageStore.DefaultPageStore.serializePage(DefaultPageStore.java:368)
> at
> org.apache.wicket.pageStore.DefaultPageStore.storePage(DefaultPageStore.java:146)
> at
> org.apache.wicket.page.PageStoreManager$PersistentRequestAdapter.storeTouchedPages(PageStoreManager.java:383)
> at
> org.apache.wicket.page.RequestAdapter.commitRequest(RequestAdapter.java:171)
> at
> org.apache.wicket.page.AbstractPageManager.commitRequest(AbstractPageManager.java:94)
> at
> org.apache.wicket.page.PageManagerDecorator.commitRequest(PageManagerDecorator.java:68)
> at
> org.apache.wicket.page.PageAccessSynchronizer$2.commitRequest(PageAccessSynchronizer.java:281)
> at org.apache.wicket.Application$2.onDetach(Application.java:1598)
> at
> org.apache.wicket.request.cycle.RequestCycleListenerCollection$3.notify(RequestCycleListenerCollection.java:99)
> at
> org.apache.wicket.request.cycle.RequestCycleListenerCollection$3.notify(RequestCycleListenerCollection.java:97)
> at
> org.apache.wicket.util.listener.ListenerCollection$1.notify(ListenerCollection.java:119)
> at
> org.apache.wicket.util.listener.ListenerCollection.reversedNotify(ListenerCollection.java:143)
> at
> org.apache.wicket.util.listener.ListenerCollection.reversedNotifyIgnoringExceptions(ListenerCollection.java:113)
> at
> org.apache.wicket.request.cycle.RequestCycleListenerCollection.onDetach(RequestCycleListenerCollection.java:95)
> at
> org.apache.wicket.request.cycle.RequestCycle.onDetach(RequestCycle.java:603)
> at
> org.apache.wicket.request.cycle.RequestCycle.detach(RequestCycle.java:542)
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:287)
> at
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:

Re: Unable to get response page from PageRequestHandlerTracker

[James Eliyezar]

I second that Vineet.

On Wed, Aug 29, 2012 at 4:12 PM, vineet semwal wrote:

> passing Requestcycle is kind of useless.., PageRequestHandlerTracker
> can itself get the current requestcycle,i think separate methods like
> getLastHandler() and getFirstHandler() can be added , they can just
> delegate to the respectve getMethod(RequestCycle)
>
> On Wed, Aug 29, 2012 at 1:32 PM, Martin Grigorov 
> wrote:
> > Thanks !
> >
> > On Wed, Aug 29, 2012 at 10:00 AM, James Eliyezar 
> wrote:
> >> Updated the wiki "Request Cycle in Wicket
> >> 1.5<
> https://cwiki.apache.org/confluence/display/WICKET/RequestCycle+in+Wicket+1.5
> >
> >> "
> >>
> >> On Wed, Aug 29, 2012 at 3:31 PM, James Eliyezar 
> wrote:
> >>
> >>> That was fast Martin. I'm working on the wiki now.
> >>>
> >>>
> >>> On Wed, Aug 29, 2012 at 3:27 PM, Martin Grigorov  >wrote:
> >>>
> 
> 
> https://git-wip-us.apache.org/repos/asf/wicket/repo?p=wicket.git;a=commitdiff;h=a5a1fe98e3b76110c6827b5744bf83f45ab0aac4
> 
>  On Wed, Aug 29, 2012 at 9:19 AM, James Eliyezar 
>  wrote:
>  > I like that deal.. :-)
>  >
>  > On Wed, Aug 29, 2012 at 3:09 PM, Martin Grigorov <
> mgrigo...@apache.org
>  >wrote:
>  >
>  >> I'll improve the javadoc. You improve the wiki page ;-)
>  >>
>  >> On Wed, Aug 29, 2012 at 9:07 AM, James Eliyezar <
> ja...@mcruncher.com>
>  >> wrote:
>  >> > Thanks Martin for the info.
>  >> > A note in PageRequestHandlerTracker's javadoc can be very useful.
>  >> > And it will be great if this is reflected in the wiki page
> "Request
>  Cycle
>  >> > in wicket 1.5<
>  >> https://cwiki.apache.org/WICKET/requestcycle-in-wicket-15.html>
>  >> > ".
>  >> >
>  >> > On Wed, Aug 29, 2012 at 3:03 PM, Martin Grigorov <
>  mgrigo...@apache.org
>  >> >wrote:
>  >> >
>  >> >> Hi,
>  >> >>
>  >> >> Yes, you have to register it.
>  >> >> It is not registered by default because not everyone needs it.
>  >> >>
>  >> >> On Wed, Aug 29, 2012 at 9:01 AM, James Eliyezar <
>  ja...@mcruncher.com>
>  >> >> wrote:
>  >> >> > Guys,
>  >> >> >
>  >> >> > From the javadoc of IRequestCycleListener, I found that we
> have to
>  >> >> > explicitly register the implementations.
>  >> >> > I thought PageRequestHandlerTracker would have been
> registered by
>  >> default
>  >> >> > as that's from wicket.
>  >> >> > So, when I registered it manually, it worked as expected.
> This is
>  how
>  >> I
>  >> >> > registered it in the wicket application's "init" method.
>  >> >> >
>  >> >> > @Override
>  >> >> >> public void init()
>  >> >> >> {
>  >> >> >> super.init();
>  >> >> >> getRequestCycleListeners().add(new
>  >> PageRequestHandlerTracker());
>  >> >> >> }
>  >> >> >>
>  >> >> >
>  >> >> > On Wed, Aug 29, 2012 at 2:41 PM, James Eliyezar <
>  ja...@mcruncher.com>
>  >> >> wrote:
>  >> >> >
>  >> >> >> Should I register PageRequestHandlerTracker anywhere?
>  >> >> >>
>  >> >> >>
>  >> >> >> On Wed, Aug 29, 2012 at 2:40 PM, James Eliyezar <
>  ja...@mcruncher.com
>  >> >> >wrote:
>  >> >> >>
>  >> >> >>> Alright Paul.
>  >> >> >>>
>  >> >> >>> This is my code:
>  >> >> >>>
>  >> >> >>> public class HomePage extends WebPage
>  >> >>  {
>  >> >>  private static Logger logger =
>  >> >>  LoggerFactory.getLogger(HomePage.class);
>  >> >>  private static final long serialVersionUID = 1L;
>  >> >> 
>  >> >>  public HomePage(final PageParameters parameters)
>  >> >>  {
>  >> >>  add(new Label("version",
>  >> >>  getApplication().getFrameworkSettings().getVersion()));
>  >> >>  try {
>  >> >>  IPageRequestHandler lastHandler =
>  >> >> 
> PageRequestHandlerTracker.getLastHandler(RequestCycle.get());
>  >> >>  logger.debug("Last handler: {}", lastHandler);
>  >> >>  logger.debug("Requested page",
>  lastHandler.getPage());
>  >> >>  } catch (Exception ex) {
>  >> >>  logger.error("Error", ex);
>  >> >>  }
>  >> >>  }
>  >> >>  }
>  >> >> 
>  >> >> 
>  >> >> >>> This is the log with exception stack trace:
>  >> >> >>>
>  >> >> >>> [INFO] Started Jetty Server
>  >> >>  DEBUG - HomePage   - Last handler: null
>  >> >>  ERROR - DefaultExceptionMapper - Unexpected error
> occurred
>  >> >>  org.apache.wicket.WicketRuntimeException: Can't instantiate
>  page
>  >> using
>  >> >>  constructor 'public
>  >> >> 
>  >> >>
>  >>
> 
> org.apache.wicket.quickstart.HomePage(org.apache.wicket.request.mapper.parameter.PageParameters)'
> 

Re: Unable to get response page from PageRequestHandlerTracker

[vineet semwal]

passing Requestcycle is kind of useless.., PageRequestHandlerTracker
can itself get the current requestcycle,i think separate methods like
getLastHandler() and getFirstHandler() can be added , they can just
delegate to the respectve getMethod(RequestCycle)

On Wed, Aug 29, 2012 at 1:32 PM, Martin Grigorov  wrote:
> Thanks !
>
> On Wed, Aug 29, 2012 at 10:00 AM, James Eliyezar  wrote:
>> Updated the wiki "Request Cycle in Wicket
>> 1.5
>> "
>>
>> On Wed, Aug 29, 2012 at 3:31 PM, James Eliyezar  wrote:
>>
>>> That was fast Martin. I'm working on the wiki now.
>>>
>>>
>>> On Wed, Aug 29, 2012 at 3:27 PM, Martin Grigorov 
>>> wrote:
>>>

 https://git-wip-us.apache.org/repos/asf/wicket/repo?p=wicket.git;a=commitdiff;h=a5a1fe98e3b76110c6827b5744bf83f45ab0aac4

 On Wed, Aug 29, 2012 at 9:19 AM, James Eliyezar 
 wrote:
 > I like that deal.. :-)
 >
 > On Wed, Aug 29, 2012 at 3:09 PM, Martin Grigorov >>> >wrote:
 >
 >> I'll improve the javadoc. You improve the wiki page ;-)
 >>
 >> On Wed, Aug 29, 2012 at 9:07 AM, James Eliyezar 
 >> wrote:
 >> > Thanks Martin for the info.
 >> > A note in PageRequestHandlerTracker's javadoc can be very useful.
 >> > And it will be great if this is reflected in the wiki page "Request
 Cycle
 >> > in wicket 1.5<
 >> https://cwiki.apache.org/WICKET/requestcycle-in-wicket-15.html>
 >> > ".
 >> >
 >> > On Wed, Aug 29, 2012 at 3:03 PM, Martin Grigorov <
 mgrigo...@apache.org
 >> >wrote:
 >> >
 >> >> Hi,
 >> >>
 >> >> Yes, you have to register it.
 >> >> It is not registered by default because not everyone needs it.
 >> >>
 >> >> On Wed, Aug 29, 2012 at 9:01 AM, James Eliyezar <
 ja...@mcruncher.com>
 >> >> wrote:
 >> >> > Guys,
 >> >> >
 >> >> > From the javadoc of IRequestCycleListener, I found that we have to
 >> >> > explicitly register the implementations.
 >> >> > I thought PageRequestHandlerTracker would have been registered by
 >> default
 >> >> > as that's from wicket.
 >> >> > So, when I registered it manually, it worked as expected. This is
 how
 >> I
 >> >> > registered it in the wicket application's "init" method.
 >> >> >
 >> >> > @Override
 >> >> >> public void init()
 >> >> >> {
 >> >> >> super.init();
 >> >> >> getRequestCycleListeners().add(new
 >> PageRequestHandlerTracker());
 >> >> >> }
 >> >> >>
 >> >> >
 >> >> > On Wed, Aug 29, 2012 at 2:41 PM, James Eliyezar <
 ja...@mcruncher.com>
 >> >> wrote:
 >> >> >
 >> >> >> Should I register PageRequestHandlerTracker anywhere?
 >> >> >>
 >> >> >>
 >> >> >> On Wed, Aug 29, 2012 at 2:40 PM, James Eliyezar <
 ja...@mcruncher.com
 >> >> >wrote:
 >> >> >>
 >> >> >>> Alright Paul.
 >> >> >>>
 >> >> >>> This is my code:
 >> >> >>>
 >> >> >>> public class HomePage extends WebPage
 >> >>  {
 >> >>  private static Logger logger =
 >> >>  LoggerFactory.getLogger(HomePage.class);
 >> >>  private static final long serialVersionUID = 1L;
 >> >> 
 >> >>  public HomePage(final PageParameters parameters)
 >> >>  {
 >> >>  add(new Label("version",
 >> >>  getApplication().getFrameworkSettings().getVersion()));
 >> >>  try {
 >> >>  IPageRequestHandler lastHandler =
 >> >>  PageRequestHandlerTracker.getLastHandler(RequestCycle.get());
 >> >>  logger.debug("Last handler: {}", lastHandler);
 >> >>  logger.debug("Requested page",
 lastHandler.getPage());
 >> >>  } catch (Exception ex) {
 >> >>  logger.error("Error", ex);
 >> >>  }
 >> >>  }
 >> >>  }
 >> >> 
 >> >> 
 >> >> >>> This is the log with exception stack trace:
 >> >> >>>
 >> >> >>> [INFO] Started Jetty Server
 >> >>  DEBUG - HomePage   - Last handler: null
 >> >>  ERROR - DefaultExceptionMapper - Unexpected error occurred
 >> >>  org.apache.wicket.WicketRuntimeException: Can't instantiate
 page
 >> using
 >> >>  constructor 'public
 >> >> 
 >> >>
 >>
 org.apache.wicket.quickstart.HomePage(org.apache.wicket.request.mapper.parameter.PageParameters)'
 >> >>  and argument ''. Might be it doesn't exist, may be it is not
 >> visible
 >> >>  (public).
 >> >>  at
 >> >> 
 >> >>
 >>
 org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:193)
 >> >>  at
 >> >> 
 >> >>
 >>
 org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:76

Re: Unable to get response page from PageRequestHandlerTracker

[Martin Grigorov]

Thanks !

On Wed, Aug 29, 2012 at 10:00 AM, James Eliyezar  wrote:
> Updated the wiki "Request Cycle in Wicket
> 1.5
> "
>
> On Wed, Aug 29, 2012 at 3:31 PM, James Eliyezar  wrote:
>
>> That was fast Martin. I'm working on the wiki now.
>>
>>
>> On Wed, Aug 29, 2012 at 3:27 PM, Martin Grigorov wrote:
>>
>>>
>>> https://git-wip-us.apache.org/repos/asf/wicket/repo?p=wicket.git;a=commitdiff;h=a5a1fe98e3b76110c6827b5744bf83f45ab0aac4
>>>
>>> On Wed, Aug 29, 2012 at 9:19 AM, James Eliyezar 
>>> wrote:
>>> > I like that deal.. :-)
>>> >
>>> > On Wed, Aug 29, 2012 at 3:09 PM, Martin Grigorov >> >wrote:
>>> >
>>> >> I'll improve the javadoc. You improve the wiki page ;-)
>>> >>
>>> >> On Wed, Aug 29, 2012 at 9:07 AM, James Eliyezar 
>>> >> wrote:
>>> >> > Thanks Martin for the info.
>>> >> > A note in PageRequestHandlerTracker's javadoc can be very useful.
>>> >> > And it will be great if this is reflected in the wiki page "Request
>>> Cycle
>>> >> > in wicket 1.5<
>>> >> https://cwiki.apache.org/WICKET/requestcycle-in-wicket-15.html>
>>> >> > ".
>>> >> >
>>> >> > On Wed, Aug 29, 2012 at 3:03 PM, Martin Grigorov <
>>> mgrigo...@apache.org
>>> >> >wrote:
>>> >> >
>>> >> >> Hi,
>>> >> >>
>>> >> >> Yes, you have to register it.
>>> >> >> It is not registered by default because not everyone needs it.
>>> >> >>
>>> >> >> On Wed, Aug 29, 2012 at 9:01 AM, James Eliyezar <
>>> ja...@mcruncher.com>
>>> >> >> wrote:
>>> >> >> > Guys,
>>> >> >> >
>>> >> >> > From the javadoc of IRequestCycleListener, I found that we have to
>>> >> >> > explicitly register the implementations.
>>> >> >> > I thought PageRequestHandlerTracker would have been registered by
>>> >> default
>>> >> >> > as that's from wicket.
>>> >> >> > So, when I registered it manually, it worked as expected. This is
>>> how
>>> >> I
>>> >> >> > registered it in the wicket application's "init" method.
>>> >> >> >
>>> >> >> > @Override
>>> >> >> >> public void init()
>>> >> >> >> {
>>> >> >> >> super.init();
>>> >> >> >> getRequestCycleListeners().add(new
>>> >> PageRequestHandlerTracker());
>>> >> >> >> }
>>> >> >> >>
>>> >> >> >
>>> >> >> > On Wed, Aug 29, 2012 at 2:41 PM, James Eliyezar <
>>> ja...@mcruncher.com>
>>> >> >> wrote:
>>> >> >> >
>>> >> >> >> Should I register PageRequestHandlerTracker anywhere?
>>> >> >> >>
>>> >> >> >>
>>> >> >> >> On Wed, Aug 29, 2012 at 2:40 PM, James Eliyezar <
>>> ja...@mcruncher.com
>>> >> >> >wrote:
>>> >> >> >>
>>> >> >> >>> Alright Paul.
>>> >> >> >>>
>>> >> >> >>> This is my code:
>>> >> >> >>>
>>> >> >> >>> public class HomePage extends WebPage
>>> >> >>  {
>>> >> >>  private static Logger logger =
>>> >> >>  LoggerFactory.getLogger(HomePage.class);
>>> >> >>  private static final long serialVersionUID = 1L;
>>> >> >> 
>>> >> >>  public HomePage(final PageParameters parameters)
>>> >> >>  {
>>> >> >>  add(new Label("version",
>>> >> >>  getApplication().getFrameworkSettings().getVersion()));
>>> >> >>  try {
>>> >> >>  IPageRequestHandler lastHandler =
>>> >> >>  PageRequestHandlerTracker.getLastHandler(RequestCycle.get());
>>> >> >>  logger.debug("Last handler: {}", lastHandler);
>>> >> >>  logger.debug("Requested page",
>>> lastHandler.getPage());
>>> >> >>  } catch (Exception ex) {
>>> >> >>  logger.error("Error", ex);
>>> >> >>  }
>>> >> >>  }
>>> >> >>  }
>>> >> >> 
>>> >> >> 
>>> >> >> >>> This is the log with exception stack trace:
>>> >> >> >>>
>>> >> >> >>> [INFO] Started Jetty Server
>>> >> >>  DEBUG - HomePage   - Last handler: null
>>> >> >>  ERROR - DefaultExceptionMapper - Unexpected error occurred
>>> >> >>  org.apache.wicket.WicketRuntimeException: Can't instantiate
>>> page
>>> >> using
>>> >> >>  constructor 'public
>>> >> >> 
>>> >> >>
>>> >>
>>> org.apache.wicket.quickstart.HomePage(org.apache.wicket.request.mapper.parameter.PageParameters)'
>>> >> >>  and argument ''. Might be it doesn't exist, may be it is not
>>> >> visible
>>> >> >>  (public).
>>> >> >>  at
>>> >> >> 
>>> >> >>
>>> >>
>>> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:193)
>>> >> >>  at
>>> >> >> 
>>> >> >>
>>> >>
>>> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:76)
>>> >> >>  at
>>> >> >> 
>>> >> >>
>>> >>
>>> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:46)
>>> >> >>  at
>>> >> >> 
>>> >> >>
>>> >>
>>> org.apache.wicket.DefaultMapperContext.newPageInstance(DefaultMapperContext.java:103)
>>> >> >>  at
>>> >> >> 
>>> >> >>
>>> >>
>>> org.apache.wicket.request.handler.PageProvider.resolvePageInstance(PageProvider.java:274)
>>> >> >>  at

Re: Unable to get response page from PageRequestHandlerTracker

[James Eliyezar]

Updated the wiki "Request Cycle in Wicket
1.5
"

On Wed, Aug 29, 2012 at 3:31 PM, James Eliyezar  wrote:

> That was fast Martin. I'm working on the wiki now.
>
>
> On Wed, Aug 29, 2012 at 3:27 PM, Martin Grigorov wrote:
>
>>
>> https://git-wip-us.apache.org/repos/asf/wicket/repo?p=wicket.git;a=commitdiff;h=a5a1fe98e3b76110c6827b5744bf83f45ab0aac4
>>
>> On Wed, Aug 29, 2012 at 9:19 AM, James Eliyezar 
>> wrote:
>> > I like that deal.. :-)
>> >
>> > On Wed, Aug 29, 2012 at 3:09 PM, Martin Grigorov > >wrote:
>> >
>> >> I'll improve the javadoc. You improve the wiki page ;-)
>> >>
>> >> On Wed, Aug 29, 2012 at 9:07 AM, James Eliyezar 
>> >> wrote:
>> >> > Thanks Martin for the info.
>> >> > A note in PageRequestHandlerTracker's javadoc can be very useful.
>> >> > And it will be great if this is reflected in the wiki page "Request
>> Cycle
>> >> > in wicket 1.5<
>> >> https://cwiki.apache.org/WICKET/requestcycle-in-wicket-15.html>
>> >> > ".
>> >> >
>> >> > On Wed, Aug 29, 2012 at 3:03 PM, Martin Grigorov <
>> mgrigo...@apache.org
>> >> >wrote:
>> >> >
>> >> >> Hi,
>> >> >>
>> >> >> Yes, you have to register it.
>> >> >> It is not registered by default because not everyone needs it.
>> >> >>
>> >> >> On Wed, Aug 29, 2012 at 9:01 AM, James Eliyezar <
>> ja...@mcruncher.com>
>> >> >> wrote:
>> >> >> > Guys,
>> >> >> >
>> >> >> > From the javadoc of IRequestCycleListener, I found that we have to
>> >> >> > explicitly register the implementations.
>> >> >> > I thought PageRequestHandlerTracker would have been registered by
>> >> default
>> >> >> > as that's from wicket.
>> >> >> > So, when I registered it manually, it worked as expected. This is
>> how
>> >> I
>> >> >> > registered it in the wicket application's "init" method.
>> >> >> >
>> >> >> > @Override
>> >> >> >> public void init()
>> >> >> >> {
>> >> >> >> super.init();
>> >> >> >> getRequestCycleListeners().add(new
>> >> PageRequestHandlerTracker());
>> >> >> >> }
>> >> >> >>
>> >> >> >
>> >> >> > On Wed, Aug 29, 2012 at 2:41 PM, James Eliyezar <
>> ja...@mcruncher.com>
>> >> >> wrote:
>> >> >> >
>> >> >> >> Should I register PageRequestHandlerTracker anywhere?
>> >> >> >>
>> >> >> >>
>> >> >> >> On Wed, Aug 29, 2012 at 2:40 PM, James Eliyezar <
>> ja...@mcruncher.com
>> >> >> >wrote:
>> >> >> >>
>> >> >> >>> Alright Paul.
>> >> >> >>>
>> >> >> >>> This is my code:
>> >> >> >>>
>> >> >> >>> public class HomePage extends WebPage
>> >> >>  {
>> >> >>  private static Logger logger =
>> >> >>  LoggerFactory.getLogger(HomePage.class);
>> >> >>  private static final long serialVersionUID = 1L;
>> >> >> 
>> >> >>  public HomePage(final PageParameters parameters)
>> >> >>  {
>> >> >>  add(new Label("version",
>> >> >>  getApplication().getFrameworkSettings().getVersion()));
>> >> >>  try {
>> >> >>  IPageRequestHandler lastHandler =
>> >> >>  PageRequestHandlerTracker.getLastHandler(RequestCycle.get());
>> >> >>  logger.debug("Last handler: {}", lastHandler);
>> >> >>  logger.debug("Requested page",
>> lastHandler.getPage());
>> >> >>  } catch (Exception ex) {
>> >> >>  logger.error("Error", ex);
>> >> >>  }
>> >> >>  }
>> >> >>  }
>> >> >> 
>> >> >> 
>> >> >> >>> This is the log with exception stack trace:
>> >> >> >>>
>> >> >> >>> [INFO] Started Jetty Server
>> >> >>  DEBUG - HomePage   - Last handler: null
>> >> >>  ERROR - DefaultExceptionMapper - Unexpected error occurred
>> >> >>  org.apache.wicket.WicketRuntimeException: Can't instantiate
>> page
>> >> using
>> >> >>  constructor 'public
>> >> >> 
>> >> >>
>> >>
>> org.apache.wicket.quickstart.HomePage(org.apache.wicket.request.mapper.parameter.PageParameters)'
>> >> >>  and argument ''. Might be it doesn't exist, may be it is not
>> >> visible
>> >> >>  (public).
>> >> >>  at
>> >> >> 
>> >> >>
>> >>
>> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:193)
>> >> >>  at
>> >> >> 
>> >> >>
>> >>
>> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:76)
>> >> >>  at
>> >> >> 
>> >> >>
>> >>
>> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:46)
>> >> >>  at
>> >> >> 
>> >> >>
>> >>
>> org.apache.wicket.DefaultMapperContext.newPageInstance(DefaultMapperContext.java:103)
>> >> >>  at
>> >> >> 
>> >> >>
>> >>
>> org.apache.wicket.request.handler.PageProvider.resolvePageInstance(PageProvider.java:274)
>> >> >>  at
>> >> >> 
>> >> >>
>> >>
>> org.apache.wicket.request.handler.PageProvider.getPageInstance(PageProvider.java:165)
>> >> >>  at
>> >> >> 
>> >> >>
>> >>
>> org.apache.wicket.request.handler.render.PageR

Re: Unable to get response page from PageRequestHandlerTracker

[James Eliyezar]

That was fast Martin. I'm working on the wiki now.

On Wed, Aug 29, 2012 at 3:27 PM, Martin Grigorov wrote:

>
> https://git-wip-us.apache.org/repos/asf/wicket/repo?p=wicket.git;a=commitdiff;h=a5a1fe98e3b76110c6827b5744bf83f45ab0aac4
>
> On Wed, Aug 29, 2012 at 9:19 AM, James Eliyezar 
> wrote:
> > I like that deal.. :-)
> >
> > On Wed, Aug 29, 2012 at 3:09 PM, Martin Grigorov  >wrote:
> >
> >> I'll improve the javadoc. You improve the wiki page ;-)
> >>
> >> On Wed, Aug 29, 2012 at 9:07 AM, James Eliyezar 
> >> wrote:
> >> > Thanks Martin for the info.
> >> > A note in PageRequestHandlerTracker's javadoc can be very useful.
> >> > And it will be great if this is reflected in the wiki page "Request
> Cycle
> >> > in wicket 1.5<
> >> https://cwiki.apache.org/WICKET/requestcycle-in-wicket-15.html>
> >> > ".
> >> >
> >> > On Wed, Aug 29, 2012 at 3:03 PM, Martin Grigorov <
> mgrigo...@apache.org
> >> >wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> Yes, you have to register it.
> >> >> It is not registered by default because not everyone needs it.
> >> >>
> >> >> On Wed, Aug 29, 2012 at 9:01 AM, James Eliyezar  >
> >> >> wrote:
> >> >> > Guys,
> >> >> >
> >> >> > From the javadoc of IRequestCycleListener, I found that we have to
> >> >> > explicitly register the implementations.
> >> >> > I thought PageRequestHandlerTracker would have been registered by
> >> default
> >> >> > as that's from wicket.
> >> >> > So, when I registered it manually, it worked as expected. This is
> how
> >> I
> >> >> > registered it in the wicket application's "init" method.
> >> >> >
> >> >> > @Override
> >> >> >> public void init()
> >> >> >> {
> >> >> >> super.init();
> >> >> >> getRequestCycleListeners().add(new
> >> PageRequestHandlerTracker());
> >> >> >> }
> >> >> >>
> >> >> >
> >> >> > On Wed, Aug 29, 2012 at 2:41 PM, James Eliyezar <
> ja...@mcruncher.com>
> >> >> wrote:
> >> >> >
> >> >> >> Should I register PageRequestHandlerTracker anywhere?
> >> >> >>
> >> >> >>
> >> >> >> On Wed, Aug 29, 2012 at 2:40 PM, James Eliyezar <
> ja...@mcruncher.com
> >> >> >wrote:
> >> >> >>
> >> >> >>> Alright Paul.
> >> >> >>>
> >> >> >>> This is my code:
> >> >> >>>
> >> >> >>> public class HomePage extends WebPage
> >> >>  {
> >> >>  private static Logger logger =
> >> >>  LoggerFactory.getLogger(HomePage.class);
> >> >>  private static final long serialVersionUID = 1L;
> >> >> 
> >> >>  public HomePage(final PageParameters parameters)
> >> >>  {
> >> >>  add(new Label("version",
> >> >>  getApplication().getFrameworkSettings().getVersion()));
> >> >>  try {
> >> >>  IPageRequestHandler lastHandler =
> >> >>  PageRequestHandlerTracker.getLastHandler(RequestCycle.get());
> >> >>  logger.debug("Last handler: {}", lastHandler);
> >> >>  logger.debug("Requested page",
> lastHandler.getPage());
> >> >>  } catch (Exception ex) {
> >> >>  logger.error("Error", ex);
> >> >>  }
> >> >>  }
> >> >>  }
> >> >> 
> >> >> 
> >> >> >>> This is the log with exception stack trace:
> >> >> >>>
> >> >> >>> [INFO] Started Jetty Server
> >> >>  DEBUG - HomePage   - Last handler: null
> >> >>  ERROR - DefaultExceptionMapper - Unexpected error occurred
> >> >>  org.apache.wicket.WicketRuntimeException: Can't instantiate page
> >> using
> >> >>  constructor 'public
> >> >> 
> >> >>
> >>
> org.apache.wicket.quickstart.HomePage(org.apache.wicket.request.mapper.parameter.PageParameters)'
> >> >>  and argument ''. Might be it doesn't exist, may be it is not
> >> visible
> >> >>  (public).
> >> >>  at
> >> >> 
> >> >>
> >>
> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:193)
> >> >>  at
> >> >> 
> >> >>
> >>
> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:76)
> >> >>  at
> >> >> 
> >> >>
> >>
> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:46)
> >> >>  at
> >> >> 
> >> >>
> >>
> org.apache.wicket.DefaultMapperContext.newPageInstance(DefaultMapperContext.java:103)
> >> >>  at
> >> >> 
> >> >>
> >>
> org.apache.wicket.request.handler.PageProvider.resolvePageInstance(PageProvider.java:274)
> >> >>  at
> >> >> 
> >> >>
> >>
> org.apache.wicket.request.handler.PageProvider.getPageInstance(PageProvider.java:165)
> >> >>  at
> >> >> 
> >> >>
> >>
> org.apache.wicket.request.handler.render.PageRenderer.getPage(PageRenderer.java:78)
> >> >>  at
> >> >> 
> >> >>
> >>
> org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:93)
> >> >>  at
> >> >> 
> >> >>
> >>
> org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:237)
> >> >>  at
> >> >> 
> >> >>
> 

Re: Unable to get response page from PageRequestHandlerTracker

[Martin Grigorov]

https://git-wip-us.apache.org/repos/asf/wicket/repo?p=wicket.git;a=commitdiff;h=a5a1fe98e3b76110c6827b5744bf83f45ab0aac4

On Wed, Aug 29, 2012 at 9:19 AM, James Eliyezar  wrote:
> I like that deal.. :-)
>
> On Wed, Aug 29, 2012 at 3:09 PM, Martin Grigorov wrote:
>
>> I'll improve the javadoc. You improve the wiki page ;-)
>>
>> On Wed, Aug 29, 2012 at 9:07 AM, James Eliyezar 
>> wrote:
>> > Thanks Martin for the info.
>> > A note in PageRequestHandlerTracker's javadoc can be very useful.
>> > And it will be great if this is reflected in the wiki page "Request Cycle
>> > in wicket 1.5<
>> https://cwiki.apache.org/WICKET/requestcycle-in-wicket-15.html>
>> > ".
>> >
>> > On Wed, Aug 29, 2012 at 3:03 PM, Martin Grigorov > >wrote:
>> >
>> >> Hi,
>> >>
>> >> Yes, you have to register it.
>> >> It is not registered by default because not everyone needs it.
>> >>
>> >> On Wed, Aug 29, 2012 at 9:01 AM, James Eliyezar 
>> >> wrote:
>> >> > Guys,
>> >> >
>> >> > From the javadoc of IRequestCycleListener, I found that we have to
>> >> > explicitly register the implementations.
>> >> > I thought PageRequestHandlerTracker would have been registered by
>> default
>> >> > as that's from wicket.
>> >> > So, when I registered it manually, it worked as expected. This is how
>> I
>> >> > registered it in the wicket application's "init" method.
>> >> >
>> >> > @Override
>> >> >> public void init()
>> >> >> {
>> >> >> super.init();
>> >> >> getRequestCycleListeners().add(new
>> PageRequestHandlerTracker());
>> >> >> }
>> >> >>
>> >> >
>> >> > On Wed, Aug 29, 2012 at 2:41 PM, James Eliyezar 
>> >> wrote:
>> >> >
>> >> >> Should I register PageRequestHandlerTracker anywhere?
>> >> >>
>> >> >>
>> >> >> On Wed, Aug 29, 2012 at 2:40 PM, James Eliyezar > >> >wrote:
>> >> >>
>> >> >>> Alright Paul.
>> >> >>>
>> >> >>> This is my code:
>> >> >>>
>> >> >>> public class HomePage extends WebPage
>> >>  {
>> >>  private static Logger logger =
>> >>  LoggerFactory.getLogger(HomePage.class);
>> >>  private static final long serialVersionUID = 1L;
>> >> 
>> >>  public HomePage(final PageParameters parameters)
>> >>  {
>> >>  add(new Label("version",
>> >>  getApplication().getFrameworkSettings().getVersion()));
>> >>  try {
>> >>  IPageRequestHandler lastHandler =
>> >>  PageRequestHandlerTracker.getLastHandler(RequestCycle.get());
>> >>  logger.debug("Last handler: {}", lastHandler);
>> >>  logger.debug("Requested page", lastHandler.getPage());
>> >>  } catch (Exception ex) {
>> >>  logger.error("Error", ex);
>> >>  }
>> >>  }
>> >>  }
>> >> 
>> >> 
>> >> >>> This is the log with exception stack trace:
>> >> >>>
>> >> >>> [INFO] Started Jetty Server
>> >>  DEBUG - HomePage   - Last handler: null
>> >>  ERROR - DefaultExceptionMapper - Unexpected error occurred
>> >>  org.apache.wicket.WicketRuntimeException: Can't instantiate page
>> using
>> >>  constructor 'public
>> >> 
>> >>
>> org.apache.wicket.quickstart.HomePage(org.apache.wicket.request.mapper.parameter.PageParameters)'
>> >>  and argument ''. Might be it doesn't exist, may be it is not
>> visible
>> >>  (public).
>> >>  at
>> >> 
>> >>
>> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:193)
>> >>  at
>> >> 
>> >>
>> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:76)
>> >>  at
>> >> 
>> >>
>> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:46)
>> >>  at
>> >> 
>> >>
>> org.apache.wicket.DefaultMapperContext.newPageInstance(DefaultMapperContext.java:103)
>> >>  at
>> >> 
>> >>
>> org.apache.wicket.request.handler.PageProvider.resolvePageInstance(PageProvider.java:274)
>> >>  at
>> >> 
>> >>
>> org.apache.wicket.request.handler.PageProvider.getPageInstance(PageProvider.java:165)
>> >>  at
>> >> 
>> >>
>> org.apache.wicket.request.handler.render.PageRenderer.getPage(PageRenderer.java:78)
>> >>  at
>> >> 
>> >>
>> org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:93)
>> >>  at
>> >> 
>> >>
>> org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:237)
>> >>  at
>> >> 
>> >>
>> org.apache.wicket.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:167)
>> >>  at
>> >> 
>> >>
>> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:784)
>> >>  at
>> >> 
>> >>
>> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
>> >>  at
>> >> 
>> >>
>> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:255)
>> >>  at
>> 

Re: Unable to get response page from PageRequestHandlerTracker

[James Eliyezar]

I like that deal.. :-)

On Wed, Aug 29, 2012 at 3:09 PM, Martin Grigorov wrote:

> I'll improve the javadoc. You improve the wiki page ;-)
>
> On Wed, Aug 29, 2012 at 9:07 AM, James Eliyezar 
> wrote:
> > Thanks Martin for the info.
> > A note in PageRequestHandlerTracker's javadoc can be very useful.
> > And it will be great if this is reflected in the wiki page "Request Cycle
> > in wicket 1.5<
> https://cwiki.apache.org/WICKET/requestcycle-in-wicket-15.html>
> > ".
> >
> > On Wed, Aug 29, 2012 at 3:03 PM, Martin Grigorov  >wrote:
> >
> >> Hi,
> >>
> >> Yes, you have to register it.
> >> It is not registered by default because not everyone needs it.
> >>
> >> On Wed, Aug 29, 2012 at 9:01 AM, James Eliyezar 
> >> wrote:
> >> > Guys,
> >> >
> >> > From the javadoc of IRequestCycleListener, I found that we have to
> >> > explicitly register the implementations.
> >> > I thought PageRequestHandlerTracker would have been registered by
> default
> >> > as that's from wicket.
> >> > So, when I registered it manually, it worked as expected. This is how
> I
> >> > registered it in the wicket application's "init" method.
> >> >
> >> > @Override
> >> >> public void init()
> >> >> {
> >> >> super.init();
> >> >> getRequestCycleListeners().add(new
> PageRequestHandlerTracker());
> >> >> }
> >> >>
> >> >
> >> > On Wed, Aug 29, 2012 at 2:41 PM, James Eliyezar 
> >> wrote:
> >> >
> >> >> Should I register PageRequestHandlerTracker anywhere?
> >> >>
> >> >>
> >> >> On Wed, Aug 29, 2012 at 2:40 PM, James Eliyezar  >> >wrote:
> >> >>
> >> >>> Alright Paul.
> >> >>>
> >> >>> This is my code:
> >> >>>
> >> >>> public class HomePage extends WebPage
> >>  {
> >>  private static Logger logger =
> >>  LoggerFactory.getLogger(HomePage.class);
> >>  private static final long serialVersionUID = 1L;
> >> 
> >>  public HomePage(final PageParameters parameters)
> >>  {
> >>  add(new Label("version",
> >>  getApplication().getFrameworkSettings().getVersion()));
> >>  try {
> >>  IPageRequestHandler lastHandler =
> >>  PageRequestHandlerTracker.getLastHandler(RequestCycle.get());
> >>  logger.debug("Last handler: {}", lastHandler);
> >>  logger.debug("Requested page", lastHandler.getPage());
> >>  } catch (Exception ex) {
> >>  logger.error("Error", ex);
> >>  }
> >>  }
> >>  }
> >> 
> >> 
> >> >>> This is the log with exception stack trace:
> >> >>>
> >> >>> [INFO] Started Jetty Server
> >>  DEBUG - HomePage   - Last handler: null
> >>  ERROR - DefaultExceptionMapper - Unexpected error occurred
> >>  org.apache.wicket.WicketRuntimeException: Can't instantiate page
> using
> >>  constructor 'public
> >> 
> >>
> org.apache.wicket.quickstart.HomePage(org.apache.wicket.request.mapper.parameter.PageParameters)'
> >>  and argument ''. Might be it doesn't exist, may be it is not
> visible
> >>  (public).
> >>  at
> >> 
> >>
> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:193)
> >>  at
> >> 
> >>
> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:76)
> >>  at
> >> 
> >>
> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:46)
> >>  at
> >> 
> >>
> org.apache.wicket.DefaultMapperContext.newPageInstance(DefaultMapperContext.java:103)
> >>  at
> >> 
> >>
> org.apache.wicket.request.handler.PageProvider.resolvePageInstance(PageProvider.java:274)
> >>  at
> >> 
> >>
> org.apache.wicket.request.handler.PageProvider.getPageInstance(PageProvider.java:165)
> >>  at
> >> 
> >>
> org.apache.wicket.request.handler.render.PageRenderer.getPage(PageRenderer.java:78)
> >>  at
> >> 
> >>
> org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:93)
> >>  at
> >> 
> >>
> org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:237)
> >>  at
> >> 
> >>
> org.apache.wicket.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:167)
> >>  at
> >> 
> >>
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:784)
> >>  at
> >> 
> >>
> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
> >>  at
> >> 
> >>
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:255)
> >>  at
> >> 
> >>
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:212)
> >>  at
> >> 
> >>
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:283)
> >>  at
> >> 
> >>
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilt

Re: Unable to get response page from PageRequestHandlerTracker

[Martin Grigorov]

I'll improve the javadoc. You improve the wiki page ;-)

On Wed, Aug 29, 2012 at 9:07 AM, James Eliyezar  wrote:
> Thanks Martin for the info.
> A note in PageRequestHandlerTracker's javadoc can be very useful.
> And it will be great if this is reflected in the wiki page "Request Cycle
> in wicket 1.5
> ".
>
> On Wed, Aug 29, 2012 at 3:03 PM, Martin Grigorov wrote:
>
>> Hi,
>>
>> Yes, you have to register it.
>> It is not registered by default because not everyone needs it.
>>
>> On Wed, Aug 29, 2012 at 9:01 AM, James Eliyezar 
>> wrote:
>> > Guys,
>> >
>> > From the javadoc of IRequestCycleListener, I found that we have to
>> > explicitly register the implementations.
>> > I thought PageRequestHandlerTracker would have been registered by default
>> > as that's from wicket.
>> > So, when I registered it manually, it worked as expected. This is how I
>> > registered it in the wicket application's "init" method.
>> >
>> > @Override
>> >> public void init()
>> >> {
>> >> super.init();
>> >> getRequestCycleListeners().add(new PageRequestHandlerTracker());
>> >> }
>> >>
>> >
>> > On Wed, Aug 29, 2012 at 2:41 PM, James Eliyezar 
>> wrote:
>> >
>> >> Should I register PageRequestHandlerTracker anywhere?
>> >>
>> >>
>> >> On Wed, Aug 29, 2012 at 2:40 PM, James Eliyezar > >wrote:
>> >>
>> >>> Alright Paul.
>> >>>
>> >>> This is my code:
>> >>>
>> >>> public class HomePage extends WebPage
>>  {
>>  private static Logger logger =
>>  LoggerFactory.getLogger(HomePage.class);
>>  private static final long serialVersionUID = 1L;
>> 
>>  public HomePage(final PageParameters parameters)
>>  {
>>  add(new Label("version",
>>  getApplication().getFrameworkSettings().getVersion()));
>>  try {
>>  IPageRequestHandler lastHandler =
>>  PageRequestHandlerTracker.getLastHandler(RequestCycle.get());
>>  logger.debug("Last handler: {}", lastHandler);
>>  logger.debug("Requested page", lastHandler.getPage());
>>  } catch (Exception ex) {
>>  logger.error("Error", ex);
>>  }
>>  }
>>  }
>> 
>> 
>> >>> This is the log with exception stack trace:
>> >>>
>> >>> [INFO] Started Jetty Server
>>  DEBUG - HomePage   - Last handler: null
>>  ERROR - DefaultExceptionMapper - Unexpected error occurred
>>  org.apache.wicket.WicketRuntimeException: Can't instantiate page using
>>  constructor 'public
>> 
>> org.apache.wicket.quickstart.HomePage(org.apache.wicket.request.mapper.parameter.PageParameters)'
>>  and argument ''. Might be it doesn't exist, may be it is not visible
>>  (public).
>>  at
>> 
>> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:193)
>>  at
>> 
>> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:76)
>>  at
>> 
>> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:46)
>>  at
>> 
>> org.apache.wicket.DefaultMapperContext.newPageInstance(DefaultMapperContext.java:103)
>>  at
>> 
>> org.apache.wicket.request.handler.PageProvider.resolvePageInstance(PageProvider.java:274)
>>  at
>> 
>> org.apache.wicket.request.handler.PageProvider.getPageInstance(PageProvider.java:165)
>>  at
>> 
>> org.apache.wicket.request.handler.render.PageRenderer.getPage(PageRenderer.java:78)
>>  at
>> 
>> org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:93)
>>  at
>> 
>> org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:237)
>>  at
>> 
>> org.apache.wicket.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:167)
>>  at
>> 
>> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:784)
>>  at
>> 
>> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
>>  at
>> 
>> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:255)
>>  at
>> 
>> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:212)
>>  at
>> 
>> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:283)
>>  at
>> 
>> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:188)
>>  at
>> 
>> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:244)
>>  at
>> 
>> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1326)
>>  at
>> 
>> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:479)
>>  at
>> 
>> org.eclipse.jetty.server.handler

Re: Unable to get response page from PageRequestHandlerTracker

[James Eliyezar]

Thanks Martin for the info.
A note in PageRequestHandlerTracker's javadoc can be very useful.
And it will be great if this is reflected in the wiki page "Request Cycle
in wicket 1.5
".

On Wed, Aug 29, 2012 at 3:03 PM, Martin Grigorov wrote:

> Hi,
>
> Yes, you have to register it.
> It is not registered by default because not everyone needs it.
>
> On Wed, Aug 29, 2012 at 9:01 AM, James Eliyezar 
> wrote:
> > Guys,
> >
> > From the javadoc of IRequestCycleListener, I found that we have to
> > explicitly register the implementations.
> > I thought PageRequestHandlerTracker would have been registered by default
> > as that's from wicket.
> > So, when I registered it manually, it worked as expected. This is how I
> > registered it in the wicket application's "init" method.
> >
> > @Override
> >> public void init()
> >> {
> >> super.init();
> >> getRequestCycleListeners().add(new PageRequestHandlerTracker());
> >> }
> >>
> >
> > On Wed, Aug 29, 2012 at 2:41 PM, James Eliyezar 
> wrote:
> >
> >> Should I register PageRequestHandlerTracker anywhere?
> >>
> >>
> >> On Wed, Aug 29, 2012 at 2:40 PM, James Eliyezar  >wrote:
> >>
> >>> Alright Paul.
> >>>
> >>> This is my code:
> >>>
> >>> public class HomePage extends WebPage
>  {
>  private static Logger logger =
>  LoggerFactory.getLogger(HomePage.class);
>  private static final long serialVersionUID = 1L;
> 
>  public HomePage(final PageParameters parameters)
>  {
>  add(new Label("version",
>  getApplication().getFrameworkSettings().getVersion()));
>  try {
>  IPageRequestHandler lastHandler =
>  PageRequestHandlerTracker.getLastHandler(RequestCycle.get());
>  logger.debug("Last handler: {}", lastHandler);
>  logger.debug("Requested page", lastHandler.getPage());
>  } catch (Exception ex) {
>  logger.error("Error", ex);
>  }
>  }
>  }
> 
> 
> >>> This is the log with exception stack trace:
> >>>
> >>> [INFO] Started Jetty Server
>  DEBUG - HomePage   - Last handler: null
>  ERROR - DefaultExceptionMapper - Unexpected error occurred
>  org.apache.wicket.WicketRuntimeException: Can't instantiate page using
>  constructor 'public
> 
> org.apache.wicket.quickstart.HomePage(org.apache.wicket.request.mapper.parameter.PageParameters)'
>  and argument ''. Might be it doesn't exist, may be it is not visible
>  (public).
>  at
> 
> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:193)
>  at
> 
> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:76)
>  at
> 
> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:46)
>  at
> 
> org.apache.wicket.DefaultMapperContext.newPageInstance(DefaultMapperContext.java:103)
>  at
> 
> org.apache.wicket.request.handler.PageProvider.resolvePageInstance(PageProvider.java:274)
>  at
> 
> org.apache.wicket.request.handler.PageProvider.getPageInstance(PageProvider.java:165)
>  at
> 
> org.apache.wicket.request.handler.render.PageRenderer.getPage(PageRenderer.java:78)
>  at
> 
> org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:93)
>  at
> 
> org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:237)
>  at
> 
> org.apache.wicket.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:167)
>  at
> 
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:784)
>  at
> 
> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
>  at
> 
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:255)
>  at
> 
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:212)
>  at
> 
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:283)
>  at
> 
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:188)
>  at
> 
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:244)
>  at
> 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1326)
>  at
> 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:479)
>  at
> 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
>  at
> 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:520)
>  at
> 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
>  

Re: Unable to get response page from PageRequestHandlerTracker

[Martin Grigorov]

Hi,

Yes, you have to register it.
It is not registered by default because not everyone needs it.

On Wed, Aug 29, 2012 at 9:01 AM, James Eliyezar  wrote:
> Guys,
>
> From the javadoc of IRequestCycleListener, I found that we have to
> explicitly register the implementations.
> I thought PageRequestHandlerTracker would have been registered by default
> as that's from wicket.
> So, when I registered it manually, it worked as expected. This is how I
> registered it in the wicket application's "init" method.
>
> @Override
>> public void init()
>> {
>> super.init();
>> getRequestCycleListeners().add(new PageRequestHandlerTracker());
>> }
>>
>
> On Wed, Aug 29, 2012 at 2:41 PM, James Eliyezar  wrote:
>
>> Should I register PageRequestHandlerTracker anywhere?
>>
>>
>> On Wed, Aug 29, 2012 at 2:40 PM, James Eliyezar wrote:
>>
>>> Alright Paul.
>>>
>>> This is my code:
>>>
>>> public class HomePage extends WebPage
 {
 private static Logger logger =
 LoggerFactory.getLogger(HomePage.class);
 private static final long serialVersionUID = 1L;

 public HomePage(final PageParameters parameters)
 {
 add(new Label("version",
 getApplication().getFrameworkSettings().getVersion()));
 try {
 IPageRequestHandler lastHandler =
 PageRequestHandlerTracker.getLastHandler(RequestCycle.get());
 logger.debug("Last handler: {}", lastHandler);
 logger.debug("Requested page", lastHandler.getPage());
 } catch (Exception ex) {
 logger.error("Error", ex);
 }
 }
 }


>>> This is the log with exception stack trace:
>>>
>>> [INFO] Started Jetty Server
 DEBUG - HomePage   - Last handler: null
 ERROR - DefaultExceptionMapper - Unexpected error occurred
 org.apache.wicket.WicketRuntimeException: Can't instantiate page using
 constructor 'public
 org.apache.wicket.quickstart.HomePage(org.apache.wicket.request.mapper.parameter.PageParameters)'
 and argument ''. Might be it doesn't exist, may be it is not visible
 (public).
 at
 org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:193)
 at
 org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:76)
 at
 org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:46)
 at
 org.apache.wicket.DefaultMapperContext.newPageInstance(DefaultMapperContext.java:103)
 at
 org.apache.wicket.request.handler.PageProvider.resolvePageInstance(PageProvider.java:274)
 at
 org.apache.wicket.request.handler.PageProvider.getPageInstance(PageProvider.java:165)
 at
 org.apache.wicket.request.handler.render.PageRenderer.getPage(PageRenderer.java:78)
 at
 org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:93)
 at
 org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:237)
 at
 org.apache.wicket.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:167)
 at
 org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:784)
 at
 org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
 at
 org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:255)
 at
 org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:212)
 at
 org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:283)
 at
 org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:188)
 at
 org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:244)
 at
 org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1326)
 at
 org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:479)
 at
 org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
 at
 org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:520)
 at
 org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
 at
 org.eclipse.jetty.server.handler.ContextHandler.__doHandle(ContextHandler.java:940)
 at
 org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java)
 at
 org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:409)
 at
 org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
 at
 org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:874)
 at
 org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
  

Re: Unable to get response page from PageRequestHandlerTracker

[James Eliyezar]

Guys,

>From the javadoc of IRequestCycleListener, I found that we have to
explicitly register the implementations.
I thought PageRequestHandlerTracker would have been registered by default
as that's from wicket.
So, when I registered it manually, it worked as expected. This is how I
registered it in the wicket application's "init" method.

@Override
> public void init()
> {
> super.init();
> getRequestCycleListeners().add(new PageRequestHandlerTracker());
> }
>

On Wed, Aug 29, 2012 at 2:41 PM, James Eliyezar  wrote:

> Should I register PageRequestHandlerTracker anywhere?
>
>
> On Wed, Aug 29, 2012 at 2:40 PM, James Eliyezar wrote:
>
>> Alright Paul.
>>
>> This is my code:
>>
>> public class HomePage extends WebPage
>>> {
>>> private static Logger logger =
>>> LoggerFactory.getLogger(HomePage.class);
>>> private static final long serialVersionUID = 1L;
>>>
>>> public HomePage(final PageParameters parameters)
>>> {
>>> add(new Label("version",
>>> getApplication().getFrameworkSettings().getVersion()));
>>> try {
>>> IPageRequestHandler lastHandler =
>>> PageRequestHandlerTracker.getLastHandler(RequestCycle.get());
>>> logger.debug("Last handler: {}", lastHandler);
>>> logger.debug("Requested page", lastHandler.getPage());
>>> } catch (Exception ex) {
>>> logger.error("Error", ex);
>>> }
>>> }
>>> }
>>>
>>>
>> This is the log with exception stack trace:
>>
>> [INFO] Started Jetty Server
>>> DEBUG - HomePage   - Last handler: null
>>> ERROR - DefaultExceptionMapper - Unexpected error occurred
>>> org.apache.wicket.WicketRuntimeException: Can't instantiate page using
>>> constructor 'public
>>> org.apache.wicket.quickstart.HomePage(org.apache.wicket.request.mapper.parameter.PageParameters)'
>>> and argument ''. Might be it doesn't exist, may be it is not visible
>>> (public).
>>> at
>>> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:193)
>>> at
>>> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:76)
>>> at
>>> org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:46)
>>> at
>>> org.apache.wicket.DefaultMapperContext.newPageInstance(DefaultMapperContext.java:103)
>>> at
>>> org.apache.wicket.request.handler.PageProvider.resolvePageInstance(PageProvider.java:274)
>>> at
>>> org.apache.wicket.request.handler.PageProvider.getPageInstance(PageProvider.java:165)
>>> at
>>> org.apache.wicket.request.handler.render.PageRenderer.getPage(PageRenderer.java:78)
>>> at
>>> org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:93)
>>> at
>>> org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:237)
>>> at
>>> org.apache.wicket.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:167)
>>> at
>>> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:784)
>>> at
>>> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
>>> at
>>> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:255)
>>> at
>>> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:212)
>>> at
>>> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:283)
>>> at
>>> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:188)
>>> at
>>> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:244)
>>> at
>>> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1326)
>>> at
>>> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:479)
>>> at
>>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
>>> at
>>> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:520)
>>> at
>>> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
>>> at
>>> org.eclipse.jetty.server.handler.ContextHandler.__doHandle(ContextHandler.java:940)
>>> at
>>> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java)
>>> at
>>> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:409)
>>> at
>>> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
>>> at
>>> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:874)
>>> at
>>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
>>> at
>>> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:250)
>>> at
>>> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:149)
>>> at
>>> org.eclipse.jetty.server.handler.HandlerWrapper.handle

RE: Nested form submit problem

[Sandor Feher]

Paul Bors wrote
> 
> Must you really have a nested form here?
> 
I think yes. I tried to sketch what I need for better understanding. For
example there is a quiestionnarie has five questions. Every question has id
and max points can be given and so one. I store the result in a result table
and get the ids and max points from a param table. So I created a form for
buttons and as many nested forms as questions I have. Every questions has
it's own model because they will be stored in different records.
The main goal is to submit once and persist all of the nested models while
get value field validated at field level. The problem is that I can only
persist my models at nested form's level on onSubmit event while onSubmit
fires even I click on reset or delete or whatever on the parent form.
I hope it's more clear now and sorry for making noise. Please suggest what
could be the best approach to achieve this. 

TIA, Sandor


http://apache-wicket.1842946.n4.nabble.com/file/n4651589/modell_copy.png 



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Nested-form-submit-problem-tp4651565p4651589.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