JavaEEComponentInjector in Wicket 1.5

[msj121]

I am not sure if this is a bug or intentional. 

But seemingly
"getComponentInstantiationListeners().add((IComponentInstantiationListener)
new JavaEEComponentInjector(this));" No longer works in Wicket 1.5 (any
version I tried), but perfectly works in Wicket 1.4.5.

In Wicket 1.5 it states: "cannot access
org.apache.wicket.injection.ComponentInjector" I only changed the
version of wicket in my pom file


I will open a bug, but I have a feeling others ran into this, and I googled
for a solution (mostly people without wicket-ioc), but nothing yet, anyone
have any help or advice?

Matthew

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/JavaEEComponentInjector-in-Wicket-1-5-tp3426937p3426937.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: UploadProgressBar Possible Bug

[Pedro Santos]

we already have a quickstart :)
https://issues.apache.org/jira/browse/WICKET-3594

On Mon, Apr 4, 2011 at 6:10 PM,  wrote:

> The form does not process anything besides the file upload, and everything
> works fine until the UploadProgressBar is introduced (and yes I set
> mutlipart to true).  I will open a jira if/when time permits, if you have
> the appropriate credentials please create a jira on my behalf, I am not
> currently an account holder.
>
>
>
>
> From:   Pedro Santos 
> To: users@wicket.apache.org
> Date:   04/04/2011 04:59 PM
> Subject:Re: UploadProgressBar Possible Bug
>
>
>
> Please open a ticket, I will try to reproduce and upload a quickstart. I
> remember of it taking some time to be hidden, but just the time of form
> submit process (maybe your form do heavy processing, easily reproducible
> on
> quickstart).
>
> On Mon, Apr 4, 2011 at 12:43 PM,  wrote:
>
> > Sorry but I do not have the time/resources to create a quickstart (I
> don't
> > use Maven) but I wanted to alert the group to an issue I had in case
> > anyone wanted to test/fix it.
> >
> > Using the following;
> >
> > Wicket 1.4.16
> > UploadWebRequest in App object
> > Form with setMaxSize() (I'm using 1MB)
> > FileUploadField
> > AjaxSubmitButton
> > UploadProgressBar
> >
> > When the form max size exception is hit, the progress bar stays visible
> > and refreshes many times showing no progress, then eventually
> disappears.
> > If I manually call error on a component the form stops processing and
> the
> > progress bar disappears as expected.  I'm not sure if the bug is in the
> > progress bar or the form processing.  There also seems to be some
> > difference between Wicket 1.4.16 and 1.4.15.  Using 1.4.15 the progress
> > bar disappeared but the page continued to refresh repeatedly.  After
> > upgrading to 1.4.16 the progress bar remains visible and continues to
> > refresh erroneously.
> >
> >
> >
> > Notice: This communication, including any attachments, is intended
> solely
> > for the use of the individual or entity to which it is addressed. This
> > communication may contain information that is protected from disclosure
> > under State and/or Federal law. Please notify the sender immediately if
> > you have received this communication in error and delete this email from
> > your system. If you are not the intended recipient, you are requested
> not
> > to disclose, copy, distribute or take any action in reliance on the
> > contents of this information.
>
>
>
>
> --
> Pedro Henrique Oliveira dos Santos
>
>
>
>
>
> Notice: This communication, including any attachments, is intended solely
> for the use of the individual or entity to which it is addressed. This
> communication may contain information that is protected from disclosure
> under State and/or Federal law. Please notify the sender immediately if
> you have received this communication in error and delete this email from
> your system. If you are not the intended recipient, you are requested not
> to disclose, copy, distribute or take any action in reliance on the
> contents of this information.
>



-- 
Pedro Henrique Oliveira dos Santos

Re: UploadProgressBar Possible Bug

[MZemeck]

The form does not process anything besides the file upload, and everything 
works fine until the UploadProgressBar is introduced (and yes I set 
mutlipart to true).  I will open a jira if/when time permits, if you have 
the appropriate credentials please create a jira on my behalf, I am not 
currently an account holder.




From:   Pedro Santos 
To: users@wicket.apache.org
Date:   04/04/2011 04:59 PM
Subject:Re: UploadProgressBar Possible Bug



Please open a ticket, I will try to reproduce and upload a quickstart. I
remember of it taking some time to be hidden, but just the time of form
submit process (maybe your form do heavy processing, easily reproducible 
on
quickstart).

On Mon, Apr 4, 2011 at 12:43 PM,  wrote:

> Sorry but I do not have the time/resources to create a quickstart (I 
don't
> use Maven) but I wanted to alert the group to an issue I had in case
> anyone wanted to test/fix it.
>
> Using the following;
>
> Wicket 1.4.16
> UploadWebRequest in App object
> Form with setMaxSize() (I'm using 1MB)
> FileUploadField
> AjaxSubmitButton
> UploadProgressBar
>
> When the form max size exception is hit, the progress bar stays visible
> and refreshes many times showing no progress, then eventually 
disappears.
> If I manually call error on a component the form stops processing and 
the
> progress bar disappears as expected.  I'm not sure if the bug is in the
> progress bar or the form processing.  There also seems to be some
> difference between Wicket 1.4.16 and 1.4.15.  Using 1.4.15 the progress
> bar disappeared but the page continued to refresh repeatedly.  After
> upgrading to 1.4.16 the progress bar remains visible and continues to
> refresh erroneously.
>
>
>
> Notice: This communication, including any attachments, is intended 
solely
> for the use of the individual or entity to which it is addressed. This
> communication may contain information that is protected from disclosure
> under State and/or Federal law. Please notify the sender immediately if
> you have received this communication in error and delete this email from
> your system. If you are not the intended recipient, you are requested 
not
> to disclose, copy, distribute or take any action in reliance on the
> contents of this information.




-- 
Pedro Henrique Oliveira dos Santos





Notice: This communication, including any attachments, is intended solely 
for the use of the individual or entity to which it is addressed. This 
communication may contain information that is protected from disclosure 
under State and/or Federal law. Please notify the sender immediately if 
you have received this communication in error and delete this email from 
your system. If you are not the intended recipient, you are requested not 
to disclose, copy, distribute or take any action in reliance on the 
contents of this information.

Re: fter 1 minute the Pagemap null is still locked by: Thread[[ACTIVE]

[fachhoch]

please suggest me in case of datatable which uses   sortabledataprovider how 
can I  incorporate futuretask ?

please advice me.

for my thought I will have a panel which will hide its  datatable initially
and start a thread (futuretask) for loading data and will also have   
AjaxSelfUpdatingTimerBehavior   ,this behaviour will check every 5 seconds
to see the thread completed its job if so I will show the datatable and stop
the timer  , something like explained in this 

http://www.brimllc.com/2010/09/wicket-ajax-timer-for-legthy-operations-using-ajaxselfupdatingtimerbehavior/

but in case of datatable with sortable headers and pagination , when user
clicks on next page  (pagination )link ora sortable header  , how to
restart the timer and hide datatable  till thread completes  loading data?


--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/fter-1-minute-the-Pagemap-null-is-still-locked-by-Thread-ACTIVE-tp3423610p3426577.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: UploadProgressBar Possible Bug

[Pedro Santos]

Please open a ticket, I will try to reproduce and upload a quickstart. I
remember of it taking some time to be hidden, but just the time of form
submit process (maybe your form do heavy processing, easily reproducible on
quickstart).

On Mon, Apr 4, 2011 at 12:43 PM,  wrote:

> Sorry but I do not have the time/resources to create a quickstart (I don't
> use Maven) but I wanted to alert the group to an issue I had in case
> anyone wanted to test/fix it.
>
> Using the following;
>
> Wicket 1.4.16
> UploadWebRequest in App object
> Form with setMaxSize() (I'm using 1MB)
> FileUploadField
> AjaxSubmitButton
> UploadProgressBar
>
> When the form max size exception is hit, the progress bar stays visible
> and refreshes many times showing no progress, then eventually disappears.
> If I manually call error on a component the form stops processing and the
> progress bar disappears as expected.  I'm not sure if the bug is in the
> progress bar or the form processing.  There also seems to be some
> difference between Wicket 1.4.16 and 1.4.15.  Using 1.4.15 the progress
> bar disappeared but the page continued to refresh repeatedly.  After
> upgrading to 1.4.16 the progress bar remains visible and continues to
> refresh erroneously.
>
>
>
> Notice: This communication, including any attachments, is intended solely
> for the use of the individual or entity to which it is addressed. This
> communication may contain information that is protected from disclosure
> under State and/or Federal law. Please notify the sender immediately if
> you have received this communication in error and delete this email from
> your system. If you are not the intended recipient, you are requested not
> to disclose, copy, distribute or take any action in reliance on the
> contents of this information.




-- 
Pedro Henrique Oliveira dos Santos

RE: ModalWindow detach/serialize crashes wicket app

[Russell Morrisey]

Clint, Pedro,

Thank you both for your replies. Based on your comments, and from looking at a 
heap dump, I am thinking the problem may stem from an inner class created by 
our app's wicket Session. I have made the inner class static, so that it will 
no longer hold a reference to the Session. The inner class is a model which 
loads a reference to a User object.

Any hints on how to reproduce the problem, so I can prove it? I'm not clear on 
what triggers the serialization process that causes the error to be thrown.


RUSSELL E. MORRISEY
Programmer Analyst Professional
Mission Solutions Engineering, LLC

| russell.morri...@missionse.com | www.missionse.com
304 West Route 38, Moorestown, NJ 08057-3212

-Original Message-
From: Clint Checketts [mailto:checke...@gmail.com]
Sent: Friday, April 01, 2011 7:06 PM
To: users@wicket.apache.org
Subject: Re: ModalWindow detach/serialize crashes wicket app

Do you have a propetymodel with the session as its object?

On Friday, April 1, 2011, Pedro Santos  wrote:
> looks like your page is referencing session or pagemap somehow
>
> On Fri, Apr 1, 2011 at 4:15 PM, Russell Morrisey <
> russell.morri...@missionse.com> wrote:
>
>> Guys,
>>
>> I'm having an intermittent issue in development where use of a ModalWindow
>> on a page completely crashes wicket.
>>
>> I don't know of the ModalWindow is the root cause. I am hoping that someone
>> with intimate knowledge of wicket's page store can help me narrow it down.
>> Hints appreciated. =)
>>
>> The "X" button and other ajax controls within the ModalWindow's content
>> page stop responding to user input. When I try to hit the same bookmarkable
>> URL again for the containing page, wicket seems to have stopped running
>> entirely, and I get a Tomcat HTTP 404 error.
>>
>> The JVM outputs a StackOverflowError which looks like it happens during
>> page serialization.
>> Apr 1, 2011 2:53:14 PM org.apache.catalina.core.StandardWrapperValve invoke
>> SEVERE: Servlet.service() for servlet default threw exception
>> java.lang.StackOverflowError
>> The two blocks below occur multiple times, each, within a single trace:
>> ...
>>   at
>> org.apache.wicket.util.io.IObjectStreamFactory$DefaultObjectStreamFactory$2.writeObjectOverride(IObjectStreamFactory.java:121)
>>   at
>> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:322)
>>   at
>> org.apache.wicket.util.lang.Objects.objectToByteArray(Objects.java:1130)
>>   at
>> org.apache.wicket.protocol.http.pagestore.AbstractPageStore.serializePage(AbstractPageStore.java:203)
>>   at
>> org.apache.wicket.protocol.http.pagestore.DiskPageStore.prepareForSerialization(DiskPageStore.java:1190)
>>   at
>> org.apache.wicket.protocol.http.SecondLevelCacheSessionStore$SecondLevelCachePageMap.writeObject(SecondLevelCacheSessionStore.java:386)
>> ...
>>   at
>> org.apache.wicket.util.io.IObjectStreamFactory$DefaultObjectStreamFactory$2.writeObjectOverride(IObjectStreamFactory.java:121)
>>   at
>> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:322)
>>   at
>> org.apache.wicket.util.lang.Objects.objectToByteArray(Objects.java:1130)
>>   at
>> org.apache.wicket.protocol.http.pagestore.AbstractPageStore$PageSerializer.getPageReplacementObject(AbstractPageStore.java:288)
>>   at org.apache.wicket.Page.writeReplace(Page.java:1383)
>>
>> In our application's init() method, we have this setting:
>>
>> Objects.setObjectStreamFactory(null); // jdk serialization
>>
>> I have tried to reproduce the problem in a quickstart; but, I have not had
>> much luck, so far.
>>
>> We don't really have any custom code in our app that deals with object
>> serialization. Any help would be appreciated. We are currently using wicket
>> 1.4.9; if you guys think this might be fixed in a later version, we'd be
>> happy to upgrade. I searched briefly through the JIRA, and nothing popped
>> out at me.
>>
>> 
>>
>> RUSSELL E. MORRISEY
>> Programmer Analyst Professional
>> Mission Solutions Engineering, LLC
>>
>> | russell.morri...@missionse.com | www.missionse.com<
>> http://www.missionse.com/>
>> 304 West Route 38, Moorestown, NJ 08057-3212
>>
>>
>> 
>> This is a PRIVATE message. If you are not the intended recipient, please
>> delete without copying and kindly advise us by e-mail of the mistake in
>> delivery.
>> NOTE: Regardless of content, this e-mail shall not operate to bind MSE to
>> any order or other contract unless pursuant to explicit written agreement or
>> government initiative expressly permitting the use of e-mail for such
>> purpose.
>>
>
>
>
> --
> Pedro Henrique Oliveira dos Santos
>


This is a PRIVATE message. If you are not the intended recipient, please delete 
without copying and kindly advise us by e-mail of the mistake in delivery.
NOTE: Regardless of content, this e-mail shall not operate to bind MSE to any 
order or other contract unless pursuant to explicit written ag

Re: Page to select something and use the selection in another page

[James Carman]

I'm sure one of the core devs can slap me upside the head here and say
"why didn't you do it this way, doofus", but again I had a deadline
and I just needed to get it working.  By no means do I know each and
every bit of the framework, so sometimes I come up with something that
could have been better done with a built-in framework feature or two.
In short, there very well may be a built-in solution to this problem.
If there is, I don't know about it.  I do know there has been some
work done recently to introduce an event facility into the framework.

On Mon, Apr 4, 2011 at 1:24 PM, fernandospr  wrote:
> I guess this is a common functionality.
> It's weird it was not included as part of the framework, right?
>
>
>
> On Mon, Apr 4, 2011 at 2:19 PM, James Carman [via Apache Wicket] <
> ml-node+3426105-1808787178-210...@n4.nabble.com> wrote:
>
>> That was a tricky part, getting the selected or created value back to
>> the original page.  Perhaps it would have been better implemented with
>> an event-driven approach, but I just went with what I could get
>> working quickly.  I'm sure I could come up with something more elegant
>> if I had the time to ponder. :)
>>
>>
>> On Mon, Apr 4, 2011 at 1:08 PM, fernandospr <[hidden 
>> email]>
>> wrote:
>>
>> > Thanks James. I think I got it.
>> >
>> > I think the key part is this:
>> > ((FooSelectionListener) page).fooSelected(foo);
>> >
>> > I guess "page" is the page that starts the loop and is waiting for a
>> > selection, that is why it implements fooSelected.
>> >
>> > I think I'll implement something similar but instead of using a foo
>> object
>> > for fooSelected, I'll use an id. Then redirect to the original "page" and
>> my
>> > fooSelected would load it from the database.
>> >
>> > Though, I'm not sure if the original "page" would be automatically
>> refreshed
>> > with the selection.
>> >
>> > I will have to try.
>> >
>> > Thanks.
>> >
>> > --
>> > View this message in context:
>> http://apache-wicket.1842946.n4.nabble.com/Page-to-select-something-and-use-the-selection-in-another-page-tp3409591p3426075.html
>>
>> > Sent from the Users forum mailing list archive at Nabble.com.
>> >
>> > -
>> > To unsubscribe, e-mail: [hidden 
>> > email]
>> > For additional commands, e-mail: [hidden 
>> > email]
>> >
>> >
>>
>> -
>> To unsubscribe, e-mail: [hidden 
>> email]
>> For additional commands, e-mail: [hidden 
>> email]
>>
>>
>>
>> --
>>  If you reply to this email, your message will be added to the discussion
>> below:
>>
>> http://apache-wicket.1842946.n4.nabble.com/Page-to-select-something-and-use-the-selection-in-another-page-tp3409591p3426105.html
>>  To unsubscribe from Page to select something and use the selection in
>> another page, click 
>> here.
>>
>>
>
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/Page-to-select-something-and-use-the-selection-in-another-page-tp3409591p3426121.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 sessions vs Google App Engine read-only-mode. A hack.

[Per]

Hi there, fellow GAE lovers,

two App Engine maintenance windows are approaching (one is tomorrow, and the
other in 2 weeks)

Last time I got huge error messages, which also frustrated my customers. So
this time I wanted to be prepared. But since I started researching way too
late, and since I couldn't find any information about how to disable
sessions in Wicket easily, I decided to write my own hack for now. And from
what I can tell so far, it *should* work, fingers crossed :-)

Here's the write-up; if you run Wicket on GAE as well it could be
interesting for you too:
http://www.small-improvements.com/blog/technical/wicket-sessions-vs-app-engine-downtime/

But if there are better solutions please let me know!

Cheers,
Per


---
360 degree feedback and agile performance reviews
http://www.small-improvements.com


--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wicket-sessions-vs-Google-App-Engine-read-only-mode-A-hack-tp3426122p3426122.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 to select something and use the selection in another page

[fernandospr]

I guess this is a common functionality.
It's weird it was not included as part of the framework, right?



On Mon, Apr 4, 2011 at 2:19 PM, James Carman [via Apache Wicket] <
ml-node+3426105-1808787178-210...@n4.nabble.com> wrote:

> That was a tricky part, getting the selected or created value back to
> the original page.  Perhaps it would have been better implemented with
> an event-driven approach, but I just went with what I could get
> working quickly.  I'm sure I could come up with something more elegant
> if I had the time to ponder. :)
>
>
> On Mon, Apr 4, 2011 at 1:08 PM, fernandospr <[hidden 
> email]>
> wrote:
>
> > Thanks James. I think I got it.
> >
> > I think the key part is this:
> > ((FooSelectionListener) page).fooSelected(foo);
> >
> > I guess "page" is the page that starts the loop and is waiting for a
> > selection, that is why it implements fooSelected.
> >
> > I think I'll implement something similar but instead of using a foo
> object
> > for fooSelected, I'll use an id. Then redirect to the original "page" and
> my
> > fooSelected would load it from the database.
> >
> > Though, I'm not sure if the original "page" would be automatically
> refreshed
> > with the selection.
> >
> > I will have to try.
> >
> > Thanks.
> >
> > --
> > View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Page-to-select-something-and-use-the-selection-in-another-page-tp3409591p3426075.html
>
> > Sent from the Users forum mailing list archive at Nabble.com.
> >
> > -
> > To unsubscribe, e-mail: [hidden 
> > email]
> > For additional commands, e-mail: [hidden 
> > email]
> >
> >
>
> -
> To unsubscribe, e-mail: [hidden 
> email]
> For additional commands, e-mail: [hidden 
> email]
>
>
>
> --
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-wicket.1842946.n4.nabble.com/Page-to-select-something-and-use-the-selection-in-another-page-tp3409591p3426105.html
>  To unsubscribe from Page to select something and use the selection in
> another page, click 
> here.
>
>


--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Page-to-select-something-and-use-the-selection-in-another-page-tp3409591p3426121.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 to select something and use the selection in another page

[James Carman]

That was a tricky part, getting the selected or created value back to
the original page.  Perhaps it would have been better implemented with
an event-driven approach, but I just went with what I could get
working quickly.  I'm sure I could come up with something more elegant
if I had the time to ponder. :)


On Mon, Apr 4, 2011 at 1:08 PM, fernandospr  wrote:
> Thanks James. I think I got it.
>
> I think the key part is this:
> ((FooSelectionListener) page).fooSelected(foo);
>
> I guess "page" is the page that starts the loop and is waiting for a
> selection, that is why it implements fooSelected.
>
> I think I'll implement something similar but instead of using a foo object
> for fooSelected, I'll use an id. Then redirect to the original "page" and my
> fooSelected would load it from the database.
>
> Though, I'm not sure if the original "page" would be automatically refreshed
> with the selection.
>
> I will have to try.
>
> Thanks.
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/Page-to-select-something-and-use-the-selection-in-another-page-tp3409591p3426075.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

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

Re: Page to select something and use the selection in another page

[fernandospr]

Thanks James. I think I got it.

I think the key part is this:
((FooSelectionListener) page).fooSelected(foo); 

I guess "page" is the page that starts the loop and is waiting for a
selection, that is why it implements fooSelected.

I think I'll implement something similar but instead of using a foo object
for fooSelected, I'll use an id. Then redirect to the original "page" and my
fooSelected would load it from the database.

Though, I'm not sure if the original "page" would be automatically refreshed
with the selection.

I will have to try.

Thanks.

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Page-to-select-something-and-use-the-selection-in-another-page-tp3409591p3426075.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

UploadProgressBar Possible Bug

[MZemeck]

Sorry but I do not have the time/resources to create a quickstart (I don't 
use Maven) but I wanted to alert the group to an issue I had in case 
anyone wanted to test/fix it.

Using the following;

Wicket 1.4.16
UploadWebRequest in App object
Form with setMaxSize() (I'm using 1MB)
FileUploadField
AjaxSubmitButton
UploadProgressBar

When the form max size exception is hit, the progress bar stays visible 
and refreshes many times showing no progress, then eventually disappears. 
If I manually call error on a component the form stops processing and the 
progress bar disappears as expected.  I'm not sure if the bug is in the 
progress bar or the form processing.  There also seems to be some 
difference between Wicket 1.4.16 and 1.4.15.  Using 1.4.15 the progress 
bar disappeared but the page continued to refresh repeatedly.  After 
upgrading to 1.4.16 the progress bar remains visible and continues to 
refresh erroneously.



Notice: This communication, including any attachments, is intended solely 
for the use of the individual or entity to which it is addressed. This 
communication may contain information that is protected from disclosure 
under State and/or Federal law. Please notify the sender immediately if 
you have received this communication in error and delete this email from 
your system. If you are not the intended recipient, you are requested not 
to disclose, copy, distribute or take any action in reliance on the 
contents of this information.

Re: fter 1 minute the Pagemap null is still locked by: Thread[[ACTIVE]

[robert.mcguinness]

http://apache-wicket.1842946.n4.nabble.com/After-1-minute-the-Pagemap-null-is-still-locked-by-Thread-ACTIVE-tp3047890p3049862.html

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/fter-1-minute-the-Pagemap-null-is-still-locked-by-Thread-ACTIVE-tp3423610p3425308.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 For Mobile

[Pedro Santos]

I don't remember of Wicket JavaScript mobile compatibility thread. I tested
Wicket aplicaitons using AJAX on IE and Safari mobile versions, in both
works nice.

On Sun, Apr 3, 2011 at 11:33 AM, Ayodeji Aladejebi wrote:

> Hi,
> I like to find out the compatibility of wicket on mobile phones? especially
> the wicket javascript
> Have there been any publication or any project discussing wicket
> compatibility on Mobile Devices
>
> Thanks
>



-- 
Pedro Henrique Oliveira dos Santos

Re: fter 1 minute the Pagemap null is still locked by: Thread[[ACTIVE]

[fachhoch]

Thanks for the reply , I will use FutureTask  and can use  

future.isDone()


to check if the search is complete  and 

future.get()

to get the results.
In my case I use  AjaxFallbackDefaultDataTable  this uses a
SortableDataProvider.

Please advice me how to integrate future task and SortableDataProvider ?


--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/fter-1-minute-the-Pagemap-null-is-still-locked-by-Thread-ACTIVE-tp3423610p3425295.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: Strange behaviour in WicketTester when Ajax-clicking on a deselected checkbox

[Kent Tong]

I've got an AjaxCheckbox with a PropertyModel. When ajax-clicking in

> in WicketTester, when the model is true, everything works as expected
> but ajax-clicking it when the model is false doesn't result in a call
> of the model's setter even in onUpdate is executed (Breakpoints and
> jUnit-Asserts)

You may take a look at http://wicketpagetest.sourceforge.net which
supports true Ajax testing.

--
Kent Tong
Useful & FREE software at http://www2.cpttm.org.mo/cyberlab/freeware

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

Re: [VOTE] Behavior of CheckBox With Respect to setRequired(true)

[Kent Tong]

Hi,

As the guy who started that old thread and the old vote, I vote +1
for (2).

--
Kent Tong
Useful news for network admins at 
http://www2.cpttm.org.mo/cyberlab/netadmin-news


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

Re: Dynamic URL path

[Martin Grigorov]

mountPage("mountedPage/${dynamicPath}", SomePage.class)

Then in SomePage.java:

public SomePage(PageParameters params) {

  StringValue dynamic = params.get("dynamicPath");
}

On Mon, Apr 4, 2011 at 2:24 AM, Bruno Borges  wrote:

> Hi everyone,
>
>On Wicket 1.5, what is the best way to achieve this:
>
> http://localhost/mountedPage/dynamicPath
>
> And, within the page mounted at "mountedPage", retrieve the "dynamicPath"
> value ?
>
> Cheers,
>
> Bruno Borges
> www.brunoborges.com.br
> +55 21 76727099
>
> "The glory of great men should always be
> measured by the means they have used to
> acquire it."
>  - Francois de La Rochefoucauld
>



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