Re: Always serialize pages for debug purposes

[James Carman]

The only problem with having to look at the console is that sometimes
other logging can make that stuff fly by.  And, if you're not watching
it, it's not obvious there's a problem.  Perhaps a better solution
might be to check serializability using a unit test rather than by
exercising the pages manually.

On Mon, Aug 11, 2008 at 6:18 PM, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> well, then check who removed them and ask them why they did that...
>
> personally i dont mind looking into the console, but thats just me...
>
> -igor
>
> On Mon, Aug 11, 2008 at 2:10 PM, James Carman
> <[EMAIL PROTECTED]> wrote:
>> But, it's in a separate thread, right?  So, you'll have to look for
>> error messages in a log file (or console window).  Would a more
>> drastic response (error in the browser) be more appropriate during
>> development?
>>
>> On Mon, Aug 11, 2008 at 11:34 AM, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
>>> with the default diskstore pages are always serialized...
>>>
>>> -igor
>>>
>>> On Mon, Aug 11, 2008 at 8:23 AM, Thomas Mäder <[EMAIL PROTECTED]> wrote:
 Ah bugger! That was most convenient! I'd be very much in favor of it's
 making a comeback

 Thomas

 On Mon, Aug 11, 2008 at 4:56 PM, Jonas <[EMAIL PROTECTED]> wrote:

> It seems this feature was removed, but there's some javadoc
> left in org.apache.wicket.settings.IDebugSettings:
> [quote]
> serializeSessionAttributes (defaults to true in development
> mode) - Causes the framework
>  * to serialize any attribute put into session - this helps find Not
> Serializable errors early
> [/quote]
>
> On Mon, Aug 11, 2008 at 3:30 PM, Thomas Mäder <[EMAIL PROTECTED]>
> wrote:
> > Yeah, but wasn't there "official" support for that? And if not, wouldn't
> > this be useful for debug?
> >
> > Thomas
> >
> > 2008/8/11 Uwe Schäfer <[EMAIL PROTECTED]>
> >
> >> Thomas Mäder schrieb:
> >>
> >>
> >>  I seem to remember that there was a way to force Wicket to always
> >>> serialize
> >>> pages on detach in order to make sure every page is serializable 
> >>> during
> >>> development. Can someone please point me to the FM so I can read it?
> >>> Searching Nabble & Google didn't turn up anything.
> >>>
> >>
> >> one guy once posted this one:
> >>
> >>
> >> 
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Always serialize pages for debug purposes

[Igor Vaynberg]

well, then check who removed them and ask them why they did that...

personally i dont mind looking into the console, but thats just me...

-igor

On Mon, Aug 11, 2008 at 2:10 PM, James Carman
<[EMAIL PROTECTED]> wrote:
> But, it's in a separate thread, right?  So, you'll have to look for
> error messages in a log file (or console window).  Would a more
> drastic response (error in the browser) be more appropriate during
> development?
>
> On Mon, Aug 11, 2008 at 11:34 AM, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
>> with the default diskstore pages are always serialized...
>>
>> -igor
>>
>> On Mon, Aug 11, 2008 at 8:23 AM, Thomas Mäder <[EMAIL PROTECTED]> wrote:
>>> Ah bugger! That was most convenient! I'd be very much in favor of it's
>>> making a comeback
>>>
>>> Thomas
>>>
>>> On Mon, Aug 11, 2008 at 4:56 PM, Jonas <[EMAIL PROTECTED]> wrote:
>>>
 It seems this feature was removed, but there's some javadoc
 left in org.apache.wicket.settings.IDebugSettings:
 [quote]
 serializeSessionAttributes (defaults to true in development
 mode) - Causes the framework
  * to serialize any attribute put into session - this helps find Not
 Serializable errors early
 [/quote]

 On Mon, Aug 11, 2008 at 3:30 PM, Thomas Mäder <[EMAIL PROTECTED]>
 wrote:
 > Yeah, but wasn't there "official" support for that? And if not, wouldn't
 > this be useful for debug?
 >
 > Thomas
 >
 > 2008/8/11 Uwe Schäfer <[EMAIL PROTECTED]>
 >
 >> Thomas Mäder schrieb:
 >>
 >>
 >>  I seem to remember that there was a way to force Wicket to always
 >>> serialize
 >>> pages on detach in order to make sure every page is serializable during
 >>> development. Can someone please point me to the FM so I can read it?
 >>> Searching Nabble & Google didn't turn up anything.
 >>>
 >>
 >> one guy once posted this one:
 >>
 >>
 >> 
 >

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


>>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Feedback messages disappearing before display

[Matej Knopp]

If you want to show messages on another page you need to use session
feedback messages (getSession().info)

-Matej

On Mon, Aug 11, 2008 at 9:47 PM, insom <[EMAIL PROTECTED]> wrote:
>
> I have a submit button that adds a message to my FeedbackPanel, like so:
>
> if (isTestPassed()) {
>...
> } else {
>setResponsePage(TestPage.class);
>info("You didn't pass the test...");
> }
>
> However, when the browser gets to the TestPage, it doesn't display any
> messages. I stepped through the process in Eclipse. Running
> getSession().getFeedbackMesages() in the debugger shows that the message did
> get registered. However, when it gets to line 1367 in RequestCycle (Wicket
> 1.3.4), the message is removed. Here is the relevant code from RequestCycle:
>
> 1361  finally
> 1362{
> 1363// set step manually to clean up
> 1364currentStep = DETACH_REQUEST;
> 1365
> 1366// clean up the request
> 1367detach();  <-- This is where the message disappears
> 1368
> 1369// set step manually to done
> 1370currentStep = DONE;
> 1371}
>
> I have no idea what to do to fix this. Any suggestions?
> --
> View this message in context: 
> http://www.nabble.com/Feedback-messages-disappearing-before-display-tp18932342p18932342.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Feedback messages disappearing before display

[insom]

That solved it. I'm surprised -- considering that the original
getSession().getFeedbackMessages() showed the message, I had assumed that it
was being attached to the session. I guess I still have a lot to learn :)
Thanks for your help.


Matej Knopp-2 wrote:
> 
> If you want to show messages on another page you need to use session
> feedback messages (getSession().info)
> 
> -Matej
> 

-- 
View this message in context: 
http://www.nabble.com/Feedback-messages-disappearing-before-display-tp18932342p18933971.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Always serialize pages for debug purposes

[James Carman]

But, it's in a separate thread, right?  So, you'll have to look for
error messages in a log file (or console window).  Would a more
drastic response (error in the browser) be more appropriate during
development?

On Mon, Aug 11, 2008 at 11:34 AM, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> with the default diskstore pages are always serialized...
>
> -igor
>
> On Mon, Aug 11, 2008 at 8:23 AM, Thomas Mäder <[EMAIL PROTECTED]> wrote:
>> Ah bugger! That was most convenient! I'd be very much in favor of it's
>> making a comeback
>>
>> Thomas
>>
>> On Mon, Aug 11, 2008 at 4:56 PM, Jonas <[EMAIL PROTECTED]> wrote:
>>
>>> It seems this feature was removed, but there's some javadoc
>>> left in org.apache.wicket.settings.IDebugSettings:
>>> [quote]
>>> serializeSessionAttributes (defaults to true in development
>>> mode) - Causes the framework
>>>  * to serialize any attribute put into session - this helps find Not
>>> Serializable errors early
>>> [/quote]
>>>
>>> On Mon, Aug 11, 2008 at 3:30 PM, Thomas Mäder <[EMAIL PROTECTED]>
>>> wrote:
>>> > Yeah, but wasn't there "official" support for that? And if not, wouldn't
>>> > this be useful for debug?
>>> >
>>> > Thomas
>>> >
>>> > 2008/8/11 Uwe Schäfer <[EMAIL PROTECTED]>
>>> >
>>> >> Thomas Mäder schrieb:
>>> >>
>>> >>
>>> >>  I seem to remember that there was a way to force Wicket to always
>>> >>> serialize
>>> >>> pages on detach in order to make sure every page is serializable during
>>> >>> development. Can someone please point me to the FM so I can read it?
>>> >>> Searching Nabble & Google didn't turn up anything.
>>> >>>
>>> >>
>>> >> one guy once posted this one:
>>> >>
>>> >>
>>> >> 
>>> >
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Feedback messages disappearing before display

[Matej Knopp]

If you want to show messages on another page you need to use session
feedback messages (getSession().info)

-Matej

On Mon, Aug 11, 2008 at 9:47 PM, insom <[EMAIL PROTECTED]> wrote:
>
> I have a submit button that adds a message to my FeedbackPanel, like so:
>
> if (isTestPassed()) {
>...
> } else {
>setResponsePage(TestPage.class);
>info("You didn't pass the test...");
> }
>
> However, when the browser gets to the TestPage, it doesn't display any
> messages. I stepped through the process in Eclipse. Running
> getSession().getFeedbackMesages() in the debugger shows that the message did
> get registered. However, when it gets to line 1367 in RequestCycle (Wicket
> 1.3.4), the message is removed. Here is the relevant code from RequestCycle:
>
> 1361  finally
> 1362{
> 1363// set step manually to clean up
> 1364currentStep = DETACH_REQUEST;
> 1365
> 1366// clean up the request
> 1367detach();  <-- This is where the message disappears
> 1368
> 1369// set step manually to done
> 1370currentStep = DONE;
> 1371}
>
> I have no idea what to do to fix this. Any suggestions?
> --
> View this message in context: 
> http://www.nabble.com/Feedback-messages-disappearing-before-display-tp18932342p18932342.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Feedback messages disappearing before display

[Matej Knopp]

If you want to show messages on another page you need to use session
feedback messages (getSession().info)

-Matej

On Mon, Aug 11, 2008 at 9:47 PM, insom <[EMAIL PROTECTED]> wrote:
>
> I have a submit button that adds a message to my FeedbackPanel, like so:
>
> if (isTestPassed()) {
>...
> } else {
>setResponsePage(TestPage.class);
>info("You didn't pass the test...");
> }
>
> However, when the browser gets to the TestPage, it doesn't display any
> messages. I stepped through the process in Eclipse. Running
> getSession().getFeedbackMesages() in the debugger shows that the message did
> get registered. However, when it gets to line 1367 in RequestCycle (Wicket
> 1.3.4), the message is removed. Here is the relevant code from RequestCycle:
>
> 1361  finally
> 1362{
> 1363// set step manually to clean up
> 1364currentStep = DETACH_REQUEST;
> 1365
> 1366// clean up the request
> 1367detach();  <-- This is where the message disappears
> 1368
> 1369// set step manually to done
> 1370currentStep = DONE;
> 1371}
>
> I have no idea what to do to fix this. Any suggestions?
> --
> View this message in context: 
> http://www.nabble.com/Feedback-messages-disappearing-before-display-tp18932342p18932342.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Feedback messages disappearing before display

[insom]

I tried to follow your suggestions, but it is still not displaying messages
in the panel.


nanotech wrote:
> 
> I believe you want to display the feedback message in "TestPage".
> 

Yes, that's correct. TestPage extends BaseTemplate, which contains this:

BaseTemplate.java:
MessagePanel messagePanel = new MessagePanel("messages"){
private static final long serialVersionUID = 1L;
public boolean isVisible()
{
return anyMessage();
}
}; 
add(messagePanel);  

BaseTemplate.html:
This is
the spot for error/info messages
This is where TestPage is included

MessagePanel trivially extends FeedbackPanel:

MessagePanel.java:
public abstract class MessagePanel extends FeedbackPanel
{
public MessagePanel(final String id)
{
super(id);  
}
}


nanotech wrote:
> 
> If so, do something like this:
> 1. make sure you have feedback panel added on the page where you will be
> landing after redirect.
> 

If I understand Wicket inheritance, that is taken care of with what I showed
above.


nanotech wrote:
> 
> 2. Then you can get hold of the feedback panel in the current page like
> shown below:
> 
> FeedbackPanel feedback = (FeedbackPanel)
> responsePage.get("responsePage-feedbackPanel");
> getSession().info("You pased the test");
> 

Here's how I tried to implement your advice. I wasn't clear on what you
meant by "responsePage.get("responsePage-feedbackPanel")", so I tried
instantiating TestPage for that, as you can see below. I'm afraid it didn't
work, though:

if (isTestPassed()) {
  ...
} else {
TestPage testPage = new TestPage();
MessagePanel feedback = (MessagePanel)testPage.get("messages"); 
info("You didn't pass the test...");
setResponsePage(TestPage.class);
}

Can you tell me what I'm doing wrong? Thanks for your time and help.
-- 
View this message in context: 
http://www.nabble.com/Feedback-messages-disappearing-before-display-tp18932342p18933293.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: In memoriam: Maurice Marrink

[insom]

Let me publicly express my thanks for his work as well. While I'm new to
Wicket, I've seen Maurice's name often in the message archives. He responded
to requests for help quickly, effectively, and kindly. I have been deeply
impressed during my experience with Wicket, as much due to the quality of
the people running the project as to the quality of the framework itself.
Maurice especially represented the spirit of wisdom and service that I've
seen throughout the project.
-- 
View this message in context: 
http://www.nabble.com/In-memoriam%3A-Maurice-Marrink-tp18813746p18932705.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Feedback messages disappearing before display

[nanotech]

Hi,

I believe you want to display the feedback message in "TestPage". If so,
do something like this:
1. make sure you have feedback panel added on the page where you will be
landing after redirect.
2. Then you can get hold of the feedback panel in the current page like
shown below:

FeedbackPanel feedback = (FeedbackPanel)
responsePage.get("responsePage-feedbackPanel");
getSession().info("You pased the test");

So your code would look like:
if (isTestPassed()) {
...
} else 
{
// response Page is the page where you will be going. In your case TestPage.
FeedbackPanel feedback = (FeedbackPanel)
responsePage.get("responsePage-feedbackPanel");
getSession().info("You did not pass the test");
setResponsePage(TestPage.class);
}



insom wrote:
> 
> I have a submit button that adds a message to my FeedbackPanel, like so:
> 
> if (isTestPassed()) {
>   ...
> } else {
>   setResponsePage(TestPage.class);
>   info("You didn't pass the test...");
> }
> 
> However, when the browser gets to the TestPage, it doesn't display any
> messages. I stepped through the process in Eclipse. Running
> getSession().getFeedbackMesages() in the debugger shows that the message
> did get registered. However, when it gets to line 1367 in RequestCycle
> (Wicket 1.3.4), the message is removed. Here is the relevant code from
> RequestCycle:
> 
> 1361  finally
> 1362  {
> 1363  // set step manually to clean up
> 1364  currentStep = DETACH_REQUEST;
> 1365  
> 1366  // clean up the request
> 1367  detach();  <-- This is where the message 
> disappears
> 1368  
> 1369  // set step manually to done
> 1370  currentStep = DONE;
> 1371  }
> 
> I have no idea what to do to fix this. Any suggestions?
> 

-- 
View this message in context: 
http://www.nabble.com/Feedback-messages-disappearing-before-display-tp18932342p18932704.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wicket 1.4m3 - AjaxButton, AjaxSubmitLink in ModalWindow in IE 7 Problem ?

[Martijn Dashorst]

also, don't use a submit button with wicket:id "submit"

Martijn

On Mon, Aug 11, 2008 at 9:57 PM, FakeBoy <[EMAIL PROTECTED]> wrote:
>
> Hi, I GOT IT 
> I found the problem. The Problem was in the TextField with wicket id "id".
> When you want to safetly use ajax submit components (AjaxButton,
> AjaxSubmitLink) your form components (TextFiels etc.) CAN NOT have wicket id
> "id", because ajax submit stop work in IE. For example:
> form.add(new TextField("id",...)) -> cause in IE Ajax Submit Problem
>
> I hope that it helps you, if you will have same problems like I had
> :thinking:
>
> Dave
>
>
>
> FakeBoy wrote:
>>
>> Thanks for your interest :)
>> I tried to isolate problem, because I use it in some context of my
>> application. I made small fake startup project only with only necessary
>> classes and this problem hasn't occured. So everything works fine. But I
>> made only simple dummy modal window with no listeners and other features.
>> Now I will try make it more complex step by step and I will try recognize,
>> when it will stop working. If I detect something, let you know.
>> Thanks one more for your help ;)
>>
>> Dave
>>
>>
>> kag1526 wrote:
>>>
>>> I just tested my app in IE 7 since I also have a ModalWindow with an
>>> AjaxSubmitLink that submits my form and closes the window and mine worked
>>> fine. sorry I can't help with a solution but I can tell you that it is
>>> possible to make work.
>>>
>>>
>>>
>>> FakeBoy wrote:

 Hi,
 I tried to submit form from ModalWindow with AjaxButton or
 AjaxSubmitLink.
 In Firefox, Opera, Safari everything works fine, but in IE 7 doesn't.
 No onSubmit or onError method is fired after button or link cliked in IE
 7.
 I used WICKET DEBUG console and after clik on Button or Link i see
 message:
 INFO: Ajax POST stopped because of precondition check,
 url:?wicket:interface=modal-dialog-pagemap:0:form:testLink1::IActivePageBehaviorListener:0:&wicket:ignoreIfNotActive=true
 What doe's it mean? It's wicket problem or I did something wrong?
 Thanks a lot for your soon reply.


>>>
>>>
>>
>>
>
> --
> View this message in context: 
> http://www.nabble.com/Wicket-1.4m3---AjaxButton%2C-AjaxSubmitLink-in-ModalWindow-in-IE-7-Problem---tp18912755p18932529.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wicket 1.4m3 - AjaxButton, AjaxSubmitLink in ModalWindow in IE 7 Problem ?

[FakeBoy]

Hi, I GOT IT 
I found the problem. The Problem was in the TextField with wicket id "id".
When you want to safetly use ajax submit components (AjaxButton,
AjaxSubmitLink) your form components (TextFiels etc.) CAN NOT have wicket id
"id", because ajax submit stop work in IE. For example:
form.add(new TextField("id",...)) -> cause in IE Ajax Submit Problem

I hope that it helps you, if you will have same problems like I had
:thinking:

Dave



FakeBoy wrote:
> 
> Thanks for your interest :)
> I tried to isolate problem, because I use it in some context of my
> application. I made small fake startup project only with only necessary
> classes and this problem hasn't occured. So everything works fine. But I
> made only simple dummy modal window with no listeners and other features.
> Now I will try make it more complex step by step and I will try recognize,
> when it will stop working. If I detect something, let you know.
> Thanks one more for your help ;)
> 
> Dave
> 
> 
> kag1526 wrote:
>> 
>> I just tested my app in IE 7 since I also have a ModalWindow with an
>> AjaxSubmitLink that submits my form and closes the window and mine worked
>> fine. sorry I can't help with a solution but I can tell you that it is
>> possible to make work.
>> 
>> 
>> 
>> FakeBoy wrote:
>>> 
>>> Hi,
>>> I tried to submit form from ModalWindow with AjaxButton or
>>> AjaxSubmitLink.
>>> In Firefox, Opera, Safari everything works fine, but in IE 7 doesn't.
>>> No onSubmit or onError method is fired after button or link cliked in IE
>>> 7.
>>> I used WICKET DEBUG console and after clik on Button or Link i see
>>> message:
>>> INFO: Ajax POST stopped because of precondition check,
>>> url:?wicket:interface=modal-dialog-pagemap:0:form:testLink1::IActivePageBehaviorListener:0:&wicket:ignoreIfNotActive=true
>>> What doe's it mean? It's wicket problem or I did something wrong? 
>>> Thanks a lot for your soon reply.
>>> 
>>> 
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Wicket-1.4m3---AjaxButton%2C-AjaxSubmitLink-in-ModalWindow-in-IE-7-Problem---tp18912755p18932529.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: In memoriam: Maurice Marrink

[Nino Saturnino Martinez Vazquez Wael]

Yes, very sad. I had the pleasure of chatting and mailing with him a 
couple of times, and was looking very much forward to getting 
annotations into the Wicket security framework. This is truly a loss for 
the Wicket community:(


RIP Maurice.

greeklinux wrote:

That is very sad.

Maurice, RIP



Martijn Dashorst-4 wrote:
  

It is with great sadness that we must report the staggering loss of our
good friend and colleague, Maurice Marrink. Maurice died in a car crash
last friday.

Maurice was a dear co-worker, project member and good friend. He was
always enthusiastic, willing to lend a hand and above all friendly.
Coming from the northern parts of the Netherlands, Maurice could be
quite stubborn at times–a trait that is invaluable working as a software
engineer, especially when working in a group of strong minded people.

Maurice was a great asset to the Wicket community since Wicket became
open source. The Wicket team was fortunate to have Maurice on board
since last March. He was committed to the continued success of Wicket
and the Apache community as a whole.

Maurice has guided students that created the initial Wicket Dojo
integration (Wicket 1.1 timeframe, before Wicket Ajax). He put a lot of
effort into creating two security frameworks for Wicket, with the latest
and greatest open sourced: the Wicket Security framework (aka
Swarm/Wasp). He had many good ideas on the future of Wicket and
integrating his projects into our core distribution.

Within Topicus he was one of the pillars of our company–professionally,
and even more important: culturally. He was always organizing and
attending social events, nerd nights, cart challenges and board gaming
evenings. Just two weeks ago he was our hero when he arranged tickets
for a pre-screening of Batman: The dark knight at our local IMax
theatre.

Maurice, we miss you. All our thoughts and good wishes are with you and
your loved ones. May your soul find peace.

- the Wicket crew.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






  


--
-Wicket for love

Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Feedback messages disappearing before display

[insom]

I have a submit button that adds a message to my FeedbackPanel, like so:

if (isTestPassed()) {
...
} else {
setResponsePage(TestPage.class);
info("You didn't pass the test...");
}

However, when the browser gets to the TestPage, it doesn't display any
messages. I stepped through the process in Eclipse. Running
getSession().getFeedbackMesages() in the debugger shows that the message did
get registered. However, when it gets to line 1367 in RequestCycle (Wicket
1.3.4), the message is removed. Here is the relevant code from RequestCycle:

1361  finally
1362{
1363// set step manually to clean up
1364currentStep = DETACH_REQUEST;
1365  
1366// clean up the request
1367detach();  <-- This is where the message disappears
1368  
1369// set step manually to done
1370currentStep = DONE;
1371}

I have no idea what to do to fix this. Any suggestions?
-- 
View this message in context: 
http://www.nabble.com/Feedback-messages-disappearing-before-display-tp18932342p18932342.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How to not reload page when switching tabs in TabbedPanel.

[kag1526]

I have gotten the search tab to work by making the class that creates the tab
panel have a class variable called searchPanel that holds the panel that the
getPanel() method returns, (I create it the first time the tab is selected
and then just return it each time after that) I might have to go with a more
complicated method for the detail tabs but wanted to post this in case
anyone else was looking for a way to keep the state of tabs when switching
between them.



igor.vaynberg wrote:
> 
> you need to do this on model-level, not component level. there have
> been threads on the mailing list about background tasks, even
> search-result specific threads. search the list.
> 
> -igor
> 
> On Mon, Aug 11, 2008 at 9:47 AM, kag1526 <[EMAIL PROTECTED]> wrote:
>>
>> I have a TabbedPanel where the first tab is a search screen where you can
>> search the database and then click on a row to open detailed information
>> about that row in another tab. Some of the searches can take a long time
>> in
>> the database so I need the search results to stay in the search tab even
>> if
>> the user moves to another tab and then back again, is there anyway to
>> accomplish this?
>>
>> The methods I have though of are:
>> 1) Making the searchTabPanel a singleton, which might work for this, but
>> there is also a treeTable in the detailed tabs and I would like whatever
>> nodes are collasped or expanded to also be persistant, although if this
>> is
>> the best way to go I'll do that for the searchTab and either try to find
>> another way or do without for the detailed tabs.
>>
>> 2) Keeping a list of the panels in the overall page class then just
>> before
>> switching tabs saving the panel and if the panel already exists for the
>> new
>> tab using that panel instead of a new one, however there isn't a method
>> that
>> will allow you to do something just before a tab is changed, it must have
>> been gwt where I saw that. (I built this same application in gwt earlier
>> so
>> I get them confused from time to time.
>>
>> Does anyone know of any other ways that might work for keeping the pages
>> persistant while changing tabs?
>> --
>> View this message in context:
>> http://www.nabble.com/How-to-not-reload-page-when-switching-tabs-in-TabbedPanel.-tp18929550p18929550.html
>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-to-not-reload-page-when-switching-tabs-in-TabbedPanel.-tp18929550p18932094.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wicket 1.4m3 - AjaxButton, AjaxSubmitLink in ModalWindow in IE 7 Problem ?

[FakeBoy]

Thanks for your interest :)
I tried to isolate problem, because I use it in some context of my
application. I made small fake startup project only with only necessary
classes and this problem hasn't occured. So everything works fine. But I
made only simple dummy modal window with no listeners and other features.
Now I will try make it more complex step by step and I will try recognize,
when it will stop working. If I detect something, let you know.
Thanks one more for your help ;)

Dave


kag1526 wrote:
> 
> I just tested my app in IE 7 since I also have a ModalWindow with an
> AjaxSubmitLink that submits my form and closes the window and mine worked
> fine. sorry I can't help with a solution but I can tell you that it is
> possible to make work.
> 
> 
> 
> FakeBoy wrote:
>> 
>> Hi,
>> I tried to submit form from ModalWindow with AjaxButton or
>> AjaxSubmitLink.
>> In Firefox, Opera, Safari everything works fine, but in IE 7 doesn't.
>> No onSubmit or onError method is fired after button or link cliked in IE
>> 7.
>> I used WICKET DEBUG console and after clik on Button or Link i see
>> message:
>> INFO: Ajax POST stopped because of precondition check,
>> url:?wicket:interface=modal-dialog-pagemap:0:form:testLink1::IActivePageBehaviorListener:0:&wicket:ignoreIfNotActive=true
>> What doe's it mean? It's wicket problem or I did something wrong? 
>> Thanks a lot for your soon reply.
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Wicket-1.4m3---AjaxButton%2C-AjaxSubmitLink-in-ModalWindow-in-IE-7-Problem---tp18912755p18931673.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Images not caching in browser

[jchappelle]

That was it. There was a no-cache header being sent to the browser from
tomcat. I'll post my findings for anyone else that is having the same
problem.

I used a tool called fiddler to examine the headers that were being sent
down. You can get it here: http://www.fiddler2.com/fiddler2/

After that we found this post that was very helpful:

http://www.symphonious.net/2007/06/19/caching-in-tomcat/

Basically our server had basic authentication set up in tomcat. So the
change we made in server.xml was this:



Also for the Context element we had to set the path="/mypath". 

I hope this helps someone in the future. Thanks for your help.

Josh
-- 
View this message in context: 
http://www.nabble.com/Images-not-caching-in-browser-tp18901385p18931041.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Any wicketstuff.org site admins around?

[David Nedrow]

It doesn't look as though there is any way to send a message to the  
site admins listed on the Wicket Stuff site.


The web server is not setting the correct mime-type for .war files.

If any of the admins see this, could you add something like the  
following (assuming Apache httpd)...


AddType application/octet-stream .war

-David

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How to not reload page when switching tabs in TabbedPanel.

[Igor Vaynberg]

you need to do this on model-level, not component level. there have
been threads on the mailing list about background tasks, even
search-result specific threads. search the list.

-igor

On Mon, Aug 11, 2008 at 9:47 AM, kag1526 <[EMAIL PROTECTED]> wrote:
>
> I have a TabbedPanel where the first tab is a search screen where you can
> search the database and then click on a row to open detailed information
> about that row in another tab. Some of the searches can take a long time in
> the database so I need the search results to stay in the search tab even if
> the user moves to another tab and then back again, is there anyway to
> accomplish this?
>
> The methods I have though of are:
> 1) Making the searchTabPanel a singleton, which might work for this, but
> there is also a treeTable in the detailed tabs and I would like whatever
> nodes are collasped or expanded to also be persistant, although if this is
> the best way to go I'll do that for the searchTab and either try to find
> another way or do without for the detailed tabs.
>
> 2) Keeping a list of the panels in the overall page class then just before
> switching tabs saving the panel and if the panel already exists for the new
> tab using that panel instead of a new one, however there isn't a method that
> will allow you to do something just before a tab is changed, it must have
> been gwt where I saw that. (I built this same application in gwt earlier so
> I get them confused from time to time.
>
> Does anyone know of any other ways that might work for keeping the pages
> persistant while changing tabs?
> --
> View this message in context: 
> http://www.nabble.com/How-to-not-reload-page-when-switching-tabs-in-TabbedPanel.-tp18929550p18929550.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Multiple instances of pages and spring integration

[Igor Vaynberg]

On Mon, Aug 11, 2008 at 9:40 AM, Lorenzo Bolzani <[EMAIL PROTECTED]> wrote:
> So you are saying that wicket does not provide a standard way for page
> configuration.
> So I'll develop a custom solution based on spring or on property files.

there is no one-way-fits-all way of configuring pages, this is too
application specific for us to provide anything.

>> there is no need for a framework to provide anything special for such
>> a usecase, it is just java...
>
> Even I18N is "just java", you could write the wicket code yourself if
> you should. But I chose to use wicket just not to have to.
> I think configurability is a very common requirement for any web
> framework (even servlets had this). Even a simple solution based on
> property files

ok, thats done... getString("key") will read the .properties files...

> or, for example, a complete integration with Spring
> would be useful.

yeah, that would be awesome. and what about all those pesky users we
have who do not use spring?

-igor


>
>
> Thanks, bye
>
> Lorenzo
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

How to not reload page when switching tabs in TabbedPanel.

[kag1526]

I have a TabbedPanel where the first tab is a search screen where you can
search the database and then click on a row to open detailed information
about that row in another tab. Some of the searches can take a long time in
the database so I need the search results to stay in the search tab even if
the user moves to another tab and then back again, is there anyway to
accomplish this? 

The methods I have though of are:
1) Making the searchTabPanel a singleton, which might work for this, but
there is also a treeTable in the detailed tabs and I would like whatever
nodes are collasped or expanded to also be persistant, although if this is
the best way to go I'll do that for the searchTab and either try to find
another way or do without for the detailed tabs.

2) Keeping a list of the panels in the overall page class then just before
switching tabs saving the panel and if the panel already exists for the new
tab using that panel instead of a new one, however there isn't a method that
will allow you to do something just before a tab is changed, it must have
been gwt where I saw that. (I built this same application in gwt earlier so
I get them confused from time to time.

Does anyone know of any other ways that might work for keeping the pages
persistant while changing tabs?
-- 
View this message in context: 
http://www.nabble.com/How-to-not-reload-page-when-switching-tabs-in-TabbedPanel.-tp18929550p18929550.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Multiple instances of pages and spring integration

[Lorenzo Bolzani]

2008/8/11 Igor Vaynberg <[EMAIL PROTECTED]>:
> then have your page look it up itself from the spring context using
> some registry
>
> class mypage extends webpage {
>  @SpringBean private PageConfigRegistry registry;
>
>  public mypage() {
>mydata data=(mydata)registry.getdatafor(getclass());
>// do whatever with data
>
>// ^ or put that lookup into your base page so page just has to
> call getConfigData()
>  }
> }
>

So you are saying that wicket does not provide a standard way for page
configuration.
So I'll develop a custom solution based on spring or on property files.

> there is no need for a framework to provide anything special for such
> a usecase, it is just java...

Even I18N is "just java", you could write the wicket code yourself if
you should. But I chose to use wicket just not to have to.
I think configurability is a very common requirement for any web
framework (even servlets had this). Even a simple solution based on
property files or, for example, a complete integration with Spring
would be useful.


Thanks, bye

Lorenzo

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Easier way to accomplish setResponsePage(Class, PageParameters)

[Ryan O'Hara]

We are trying to figure out the best way to make our URLs portable.   
Currently, we mount a QueryStringUrlEncodingStrategy in our  
application class.  Then, in the beginning of the page's constructor,  
page parameters are mapped to instance variables.  Then, when the  
form button is clicked, a map of parameters is created to pass to  
setResponsePage(Class, PageParameters).  It seems like mapping the  
parameters to variables and creating a map of parameters to  
setResponsePage() can be avoided by using setResponsePage(this.getPage 
()), but the URL produced is not portable.  Having to map parameters  
to instance variables and maintain a map to pass in is high  
maintenance.  Is there a better way to do this?  Thanks for the help.


Ryan

public Search(PageParameters params) {
//TODO:
//it would be nice if this could be done automatically...
//if there are parameters, map them to instance variables
if (params.size() > 0) {
setSourceSelection(params.getString("source"));
setPosition(params.getString("position"));
setSizeStart(params.getString("sizeStart"));
setSizeEnd(params.getString("sizeEnd"));
setSnpStart(params.getString("snpStart"));
setSnpEnd(params.getString("snpEnd"));
setSortorderSelection(params.getString("sortorder"));
setVariationTypeSelection(params.getString 
("variationType"));


if (params.getInt("pagesize", -1) != -1) {
setPagesize(params.getInt("pagesize"));
}

//populate the result list now that the instance
//variables have been set
try {
resultlist = annotatedQuery.getAnnotations 
(getSourceSelection(), getPosition(), getSizeStart(), getSizeEnd(),  
getSnpStart(), getSnpEnd(), getSortorderSelection(),  
getVariationTypeSelection());

} catch (CnvException e) {
e.printStackTrace();
error(e.getMessage());
}
}

//submit button
Button asl = new Button("submit") {
public void onSubmit() {
try {
//TODO:
//it would be nice if we could make the url of
//setresponsepage(this.getPage()) to look nice
//as it would handle all of the parameter  
business.. ugh

HashMap params = new HashMap();
params.put("source", getSourceSelection());
params.put("position", getPosition());
params.put("sortorder", getSortorderSelection());
params.put("variationType",  
getVariationTypeSelection());

if (getSizeStart() != null) {
params.put("sizeStart", getSizeStart());
}
if (getSizeEnd() != null) {
params.put("sizeEnd", getSizeEnd());
}
if (getSnpStart() != null) {
params.put("snpStart", getSnpStart());
}
if (getSnpEnd() != null) {
params.put("snpEnd", getSnpEnd());
}
setPagesize((Integer) results_page.getModelObject 
());

params.put("pagesize", getPagesize().toString());

System.out.println(getSortorderSelection());
setResponsePage(Search.class, new PageParameters 
(params));

} catch (Exception e) {
error(e.getMessage());
}
}
};

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Comparing JSF and Wicket

[Peter Thomas]

On Thu, Aug 7, 2008 at 12:24 PM, nlif <[EMAIL PROTECTED]> wrote:

>
> Peter,
>
> Actually, when I said I googled a bit and found some material, I was in
> fact
> referring to your blog post and the slides :) This is very useful
> information, and your comparison was done, IMHO, very fairly and
> skillfully.
> However, as I said, this is from 2006, and I figured things may have
> changed. Obviously, Wicket has matured and improved, but for all I know -
> so
> did JSF probably.
>
> Are you still up-to-date with JSF nowadays? Would you still hold to the
> same
> opinion based on current offering of both frameworks?
>
> Thanks,
> Naaman
>
>
Naaman,

Sorry for replying a little late.  Actually the comparison you are referring
to was done in mid 2007 not 2006 - so I don't think it is *that* out of
date.  I still do try to keep track of JSF but not hands-on.  With respect
to the JSF 1.1 code in the blog-post (which is a very simple example), I am
not aware of anything new in JSF 1.2 that would improve any particular
aspect.  There were a few pro-JSF comments saying that Facelets would
address the lack of "previewability", and it is true that I stuck to core
JSF for the comparison.

Facelets and today Spring WebFlow appear to offer some respite from what
many see as significant limitations in the spec - but if you choose to go
down that path, one of the main arguments for using JSF does not hold good
anymore.  Which is of course, the tired old argument that "JSF is a
standard".  So if you look beyond the core spec - you now have a big choice
to make, for instance do you want to go the Sun / Facelets way, the JBoss
Seam way, the Spring way or the high-way.  This is what JSF advocates
cunningly refer to as an "ecosystem".

As an example of where the current version of the spec has limitations - JSF
1.X was obviously drafted in an age where Ajax was unheard of.  The pro-JSF
arguments with respect to Ajax are that JSF is designed for extension and
you just have to hook into the life-cycle phases etc.  To me this honestly
sounds more like a workaround, and there are comments on the above mentioned
blog post that speak of javascript library collisions when you mix
components from multiple JSF vendors.  Let me just say that in over one and
half years of developing (at least three different applications) with
Wicket, I am yet to see a situation where the stuff I want to do in Ajax is
restricted in any way by the framework design or anything like that.
Seriously.

Coming to JSF 2.0 it is anybody's guess as to when that community process
(read: design-by-committee) will get over and when usable implementations
will start appearing.  Life is too short and I prefer being intensely
productive rather than waiting for a promised spec and enduring the pain and
sleepless nights while the "ecosystem" stabilizes.

Generally specifications like JSF gravitate towards a "least common
denominator" approach.  I'm not saying that there is no place for standards,
but especially when building user interfaces, you will agree that every
client is different and demands a different approach.  One thing that even
JSF advocates will admit is that it is hard to create custom components.  So
if you hit a wall and find that an existing JSF component needs to be
tweaked for your project, you are at the mercy of the component vendor or
you have to customize the component yourself.  JSF makes an IMHO flawed
assumption that the committee has done the Big Design Up Front to cover all
use cases and context variations.  Case in point: just take this example of
a simple autocomplete component [1].  Look at all the possible attributes
that this component supports.  To me, this smells strongly of YAGNI [2].

Thanks,

Peter.

[1] https://blueprints.dev.java.net/complib/v2/auto-complete.html
[2] http://en.wikipedia.org/wiki/You_Ain%27t_Gonna_Need_It


ptrthomas wrote:
>
> Hi,
>
> Here is a list of bullet points I compiled on "JSF when compared with
> Wicket":
>
> – Not really OO components, more of XML tags than Java
> – Added complexity of JSF-EL and mixing JSP-EL if applicable
> – faces-config.xml : synchronize multiple files for navigation,
> page-centric, string expressions not type-safe
> – Poor separation of concerns / "preview-ability" (in core JSF spec)
> – General consensus that for practical use you have to supplement with
> non-standard extensions -e.g. Facelets, Spring WebFlow etc.
> – Hard to unit test
> – Hard to debug / step-through
> – More dependence on tooling / IDE support
> – Mixing components from multiple vendors problematic especially with AJAX
> – Generated HTML is typically verbose
> – Creating custom components is much harder
> – Slow evolution as it is a specification, now JSF 2.0 is being discussed…
>
> I had this as a back-up slide in a presentation recently (which I ended up
> having to use because of all the questions :)  You can find the
> presentation
> here if you are interested, it is more to do with comparing Wicket with
> ac

Re: PageParameters

[Brill Pappin]

Oh I wouldn't take out the convenience methods... but the base should  
not be  :)


Start with  then add any convenience methods from there.
I agree that manual conversion would be a bit of a pain, but most  
people would only do it once if that was the only option (however its  
not, so you don't need to discard anything).


- Brill


On 11-Aug-08, at 11:33 AM, Igor Vaynberg wrote:


then, unfortunately, you have to perform the conversion yourself all
the time, which is quiet annoying.

-igor

On Mon, Aug 11, 2008 at 8:24 AM, Brill Pappin <[EMAIL PROTECTED]> wrote:

ok... that make sense to me.
The primary then should be  but maybe overload it  
so that

nothing legacy breaks.

I think the  will help, but I also think that being  
specific
about what it holds is important... otherwise its trying to be "too  
smart"

and I might get a string representation that I don't want... if it's
explicitly  then you always know exactly what is  
going

in/out.

IMO.

- Brill Pappin


On 11-Aug-08, at 11:07 AM, Igor Vaynberg wrote:


wicket provides convinience methods for working with strings, eg a
method to automatically convert a string to an int so you dont have
to. likewise it will automatically convert all objects you put  
into it

to a string.

-igor

On Mon, Aug 11, 2008 at 7:36 AM, Lutz Müller <[EMAIL PROTECTED] 
>

wrote:


Thats what I was thinking, too, when I read Uwes post. I did not  
look at
Wicket 1.4 yet, but had assumed that PageParameters should always  
be

String to
String maps, because this is what they are in HTTP.
But then again, wicket is not strictly HTTP, and when you look at  
the

javadoc
comment for PageParameters (at least in 1.3) it explicitly states  
that
PageParameters might be used with other protocols. Maybe this is  
the

reason
why.

Lutz

On Monday 11 August 2008 02:33:56 Brill Pappin wrote:


I agree on the generics front... however are not the params  
supposed

to be strings?
or do they represent request parameters as well as page  
attributes?


If they are representing both, maybe they should be separated.

- Brill

On 8-Aug-08, at 12:59 PM, Uwe Schäfer wrote:


ok, maybe there was too much K and V in my last mail ;)

I´ll try another way round:

wouldn´t it be nice to be able to use smth like that ?

Map map =...
PageParameters p = new PageParameters(map);

So if you agree, please switch from

public PageParameters(final Map parameterMap)
to
public PageParameters(final Map parameterMap)

thx, uwe

--

THOMAS DAILY GmbH
Adlerstraße 19
79098 Freiburg
Deutschland
T  + 49 761 3 85 59 0
F  + 49 761 3 85 59 550
E  [EMAIL PROTECTED]
www.thomas-daily.de

Geschäftsführer/Managing Directors:
Wendy Thomas, Susanne Larbig
Handelsregister Freiburg i.Br., HRB 3947

Registrieren Sie sich unter http://morningnews.thomas-daily.de  
für
die kostenfreien TD Morning News, eine Auswahl aktueller Themen  
des

Tages morgens um 9:00 in Ihrer Mailbox.

Hinweis: Der Redaktionsschluss für unsere TD Morning News ist
täglich um 8:30 Uhr. Es werden vorrangig Informationen
berücksichtigt, die nach 16:00 Uhr des Vortages eingegangen sind.
Die Email-Adresse unserer Redaktion lautet [EMAIL PROTECTED] 
.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Always serialize pages for debug purposes

[Igor Vaynberg]

with the default diskstore pages are always serialized...

-igor

On Mon, Aug 11, 2008 at 8:23 AM, Thomas Mäder <[EMAIL PROTECTED]> wrote:
> Ah bugger! That was most convenient! I'd be very much in favor of it's
> making a comeback
>
> Thomas
>
> On Mon, Aug 11, 2008 at 4:56 PM, Jonas <[EMAIL PROTECTED]> wrote:
>
>> It seems this feature was removed, but there's some javadoc
>> left in org.apache.wicket.settings.IDebugSettings:
>> [quote]
>> serializeSessionAttributes (defaults to true in development
>> mode) - Causes the framework
>>  * to serialize any attribute put into session - this helps find Not
>> Serializable errors early
>> [/quote]
>>
>> On Mon, Aug 11, 2008 at 3:30 PM, Thomas Mäder <[EMAIL PROTECTED]>
>> wrote:
>> > Yeah, but wasn't there "official" support for that? And if not, wouldn't
>> > this be useful for debug?
>> >
>> > Thomas
>> >
>> > 2008/8/11 Uwe Schäfer <[EMAIL PROTECTED]>
>> >
>> >> Thomas Mäder schrieb:
>> >>
>> >>
>> >>  I seem to remember that there was a way to force Wicket to always
>> >>> serialize
>> >>> pages on detach in order to make sure every page is serializable during
>> >>> development. Can someone please point me to the FM so I can read it?
>> >>> Searching Nabble & Google didn't turn up anything.
>> >>>
>> >>
>> >> one guy once posted this one:
>> >>
>> >>
>> >> 
>> >
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: PageParameters

[Igor Vaynberg]

then, unfortunately, you have to perform the conversion yourself all
the time, which is quiet annoying.

-igor

On Mon, Aug 11, 2008 at 8:24 AM, Brill Pappin <[EMAIL PROTECTED]> wrote:
> ok... that make sense to me.
> The primary then should be  but maybe overload it so that
> nothing legacy breaks.
>
> I think the  will help, but I also think that being specific
> about what it holds is important... otherwise its trying to be "too smart"
> and I might get a string representation that I don't want... if it's
> explicitly  then you always know exactly what is going
> in/out.
>
> IMO.
>
> - Brill Pappin
>
>
> On 11-Aug-08, at 11:07 AM, Igor Vaynberg wrote:
>
>> wicket provides convinience methods for working with strings, eg a
>> method to automatically convert a string to an int so you dont have
>> to. likewise it will automatically convert all objects you put into it
>> to a string.
>>
>> -igor
>>
>> On Mon, Aug 11, 2008 at 7:36 AM, Lutz Müller <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> Thats what I was thinking, too, when I read Uwes post. I did not look at
>>> Wicket 1.4 yet, but had assumed that PageParameters should always be
>>> String to
>>> String maps, because this is what they are in HTTP.
>>> But then again, wicket is not strictly HTTP, and when you look at the
>>> javadoc
>>> comment for PageParameters (at least in 1.3) it explicitly states that
>>> PageParameters might be used with other protocols. Maybe this is the
>>> reason
>>> why.
>>>
>>> Lutz
>>>
>>> On Monday 11 August 2008 02:33:56 Brill Pappin wrote:

 I agree on the generics front... however are not the params supposed
 to be strings?
 or do they represent request parameters as well as page attributes?

 If they are representing both, maybe they should be separated.

 - Brill

 On 8-Aug-08, at 12:59 PM, Uwe Schäfer wrote:
>
> ok, maybe there was too much K and V in my last mail ;)
>
> I´ll try another way round:
>
> wouldn´t it be nice to be able to use smth like that ?
>
> Map map =...
> PageParameters p = new PageParameters(map);
>
> So if you agree, please switch from
>
> public PageParameters(final Map parameterMap)
> to
> public PageParameters(final Map parameterMap)
>
> thx, uwe
>
> --
>
> THOMAS DAILY GmbH
> Adlerstraße 19
> 79098 Freiburg
> Deutschland
> T  + 49 761 3 85 59 0
> F  + 49 761 3 85 59 550
> E  [EMAIL PROTECTED]
> www.thomas-daily.de
>
> Geschäftsführer/Managing Directors:
> Wendy Thomas, Susanne Larbig
> Handelsregister Freiburg i.Br., HRB 3947
>
> Registrieren Sie sich unter http://morningnews.thomas-daily.de für
> die kostenfreien TD Morning News, eine Auswahl aktueller Themen des
> Tages morgens um 9:00 in Ihrer Mailbox.
>
> Hinweis: Der Redaktionsschluss für unsere TD Morning News ist
> täglich um 8:30 Uhr. Es werden vorrangig Informationen
> berücksichtigt, die nach 16:00 Uhr des Vortages eingegangen sind.
> Die Email-Adresse unserer Redaktion lautet [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: PageParameters

[Brill Pappin]

ok... that make sense to me.
The primary then should be  but maybe overload it so  
that nothing legacy breaks.


I think the  will help, but I also think that being  
specific about what it holds is important... otherwise its trying to  
be "too smart" and I might get a string representation that I don't  
want... if it's explicitly  then you always know  
exactly what is going in/out.


IMO.

- Brill Pappin


On 11-Aug-08, at 11:07 AM, Igor Vaynberg wrote:


wicket provides convinience methods for working with strings, eg a
method to automatically convert a string to an int so you dont have
to. likewise it will automatically convert all objects you put into it
to a string.

-igor

On Mon, Aug 11, 2008 at 7:36 AM, Lutz Müller  
<[EMAIL PROTECTED]> wrote:
Thats what I was thinking, too, when I read Uwes post. I did not  
look at
Wicket 1.4 yet, but had assumed that PageParameters should always  
be String to

String maps, because this is what they are in HTTP.
But then again, wicket is not strictly HTTP, and when you look at  
the javadoc
comment for PageParameters (at least in 1.3) it explicitly states  
that
PageParameters might be used with other protocols. Maybe this is  
the reason

why.

Lutz

On Monday 11 August 2008 02:33:56 Brill Pappin wrote:

I agree on the generics front... however are not the params supposed
to be strings?
or do they represent request parameters as well as page attributes?

If they are representing both, maybe they should be separated.

- Brill

On 8-Aug-08, at 12:59 PM, Uwe Schäfer wrote:

ok, maybe there was too much K and V in my last mail ;)

I´ll try another way round:

wouldn´t it be nice to be able to use smth like that ?

Map map =...
PageParameters p = new PageParameters(map);

So if you agree, please switch from

public PageParameters(final Map parameterMap)
to
public PageParameters(final Map parameterMap)

thx, uwe

--

THOMAS DAILY GmbH
Adlerstraße 19
79098 Freiburg
Deutschland
T  + 49 761 3 85 59 0
F  + 49 761 3 85 59 550
E  [EMAIL PROTECTED]
www.thomas-daily.de

Geschäftsführer/Managing Directors:
Wendy Thomas, Susanne Larbig
Handelsregister Freiburg i.Br., HRB 3947

Registrieren Sie sich unter http://morningnews.thomas-daily.de für
die kostenfreien TD Morning News, eine Auswahl aktueller Themen des
Tages morgens um 9:00 in Ihrer Mailbox.

Hinweis: Der Redaktionsschluss für unsere TD Morning News ist
täglich um 8:30 Uhr. Es werden vorrangig Informationen
berücksichtigt, die nach 16:00 Uhr des Vortages eingegangen sind.
Die Email-Adresse unserer Redaktion lautet [EMAIL PROTECTED] 
.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Always serialize pages for debug purposes

[Thomas Mäder]

Ah bugger! That was most convenient! I'd be very much in favor of it's
making a comeback

Thomas

On Mon, Aug 11, 2008 at 4:56 PM, Jonas <[EMAIL PROTECTED]> wrote:

> It seems this feature was removed, but there's some javadoc
> left in org.apache.wicket.settings.IDebugSettings:
> [quote]
> serializeSessionAttributes (defaults to true in development
> mode) - Causes the framework
>  * to serialize any attribute put into session - this helps find Not
> Serializable errors early
> [/quote]
>
> On Mon, Aug 11, 2008 at 3:30 PM, Thomas Mäder <[EMAIL PROTECTED]>
> wrote:
> > Yeah, but wasn't there "official" support for that? And if not, wouldn't
> > this be useful for debug?
> >
> > Thomas
> >
> > 2008/8/11 Uwe Schäfer <[EMAIL PROTECTED]>
> >
> >> Thomas Mäder schrieb:
> >>
> >>
> >>  I seem to remember that there was a way to force Wicket to always
> >>> serialize
> >>> pages on detach in order to make sure every page is serializable during
> >>> development. Can someone please point me to the FM so I can read it?
> >>> Searching Nabble & Google didn't turn up anything.
> >>>
> >>
> >> one guy once posted this one:
> >>
> >>
> >> 
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Handling runtime exceptions in ajax request

[Daniel Stoch]

Hi,

In Wicket by default IRequestCycleProcessor.respond(RuntimeException,
RequestCycle) method is called to handle runtime exceptions. In
AbstractRequestCycleProcessor this method throws
RestartResponseException (or RestartResponseAtInterceptPageException)
and then the other page is shown (eg. ExceptionErrorPage or other page
specified in RequestCycle.onRuntimeException()).

In ajax requests I want to avoid loading another page when runtime
exception is thrown. I want to show a proper exception message within
the current page.
I have prepared a small draft solution how to do this (by extending
AjaxRequestTarget and WebRequestCycleProcessor classes), but firstly I
want to ask you is it any "standard" way to handle runtime exception
within ajax request, without rendering another page?

--
Daniel

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Customizing treeTable.

[Matej Knopp]

Hi,

with current layout it is not possible for the TreeTable to have
variable row height.

-Matej

On Mon, Aug 11, 2008 at 2:13 PM, kag1526 <[EMAIL PROTECTED]> wrote:
>
> I am using a tree table to display data from a database, however some of the
> rows in the tree table needs to have multiple values that I would like to be
> displayed in the same cell on multiple lines like:
>
> Name   | ABC
> 
> Variant names   | ABC corp
>  | ABC corporation
> 
>
> To do this I extended PropertyRenderableColumn to make a PropertyMultiLine
> column that simply has a MultiLineLabel instead of a plain label and set the
> overflow to scroll so that the cell will scroll if the list is really long.
> This causes the correct data to be displayed in the fields however the row
> height doesn't expand so in IE you will only see the first company and then
> have a tiny scroll bar to see the others, and in firefox it adds an extra
> new line to the beginning and end of the list so all I see is the very top
> of the letters (I also don't get the scroll bars but I'll deal with that
> later)
>
> To extend the table row I tried changing the css height value of div.row and
> of div.a_ but neither worked, from the html the structure of the table seems
> to be:
>
> 
>   
>   
>  
>   
>
>
>
>   
> 
>   
> My text here 
>   
>
>
>
>
>   
>   
>  
> 
>
> Any other ideas on how I might get the row height larger?
>
>
>
> --
> View this message in context: 
> http://www.nabble.com/Customizing-treeTable.-tp18924644p18924644.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Multiple instances of pages and spring integration

[Igor Vaynberg]

then have your page look it up itself from the spring context using
some registry

class mypage extends webpage {
  @SpringBean private PageConfigRegistry registry;

  public mypage() {
mydata data=(mydata)registry.getdatafor(getclass());
// do whatever with data

// ^ or put that lookup into your base page so page just has to
call getConfigData()
  }
}

there is no need for a framework to provide anything special for such
a usecase, it is just java...

-igor

On Mon, Aug 11, 2008 at 6:46 AM, Lorenzo Bolzani <[EMAIL PROTECTED]> wrote:
> Hi Michael, the point is that this is not a user provided parameter
> but a "server-side" page configuration parameter.
>
> In this specific case I need to tell the page how often it should
> auto-refresh. So it is not something that should be passed in from the
> client over the url but something defined at the application startup.
> If my page requires three config parameters I do not want to have to
> provide these on every link to this page.
>
> Am I missing something?
>
> Bye
>
> Lorenzo
>
> 2008/8/11 Michael Sparer <[EMAIL PROTECTED]>:
>>
>> I'd say Igor's suggestion is a solution rather than workaround. There's just
>> no point in configuring pages by means of XML or - worse - even a spring
>> config. Passing in page specific parameters is exactly the way to go.
>>
>>> I tryed to pass in these parameters as PageParameters but in this way
>>> I have to convert this from String to Integer to use it and in every
>>> call to the page I have to provide these parameters.
>>
>> I don't get it. Parsing a String with Integer.parse shouldn't be considered
>> as a bad hack or a problem - as far as i know you can even use
>> params.getInt("foobar"). and you're also free to do your custom stuff if a
>> param isn't provided. or am i misunderstanding something?
>>
>> regards,
>> Michael
>>
>>
>> Lorenzo Bolzani wrote:
>>>
>>> Hi Igor, I tried your suggestion and it works but looks like a
>>> workaround more than a solution.
>>>
>>> I have many pages that need some configuration. This is server side
>>> configuration, for example how often a page should refresh itself.
>>> I tryed to pass in these parameters as PageParameters but in this way
>>> I have to convert this from String to Integer to use it and in every
>>> call to the page I have to provide these parameters. At the same time
>>> I do not have an easy place to put this page configuration params. I
>>> think I can define a PageParameters bean for each page inside spring
>>> but looks like a bad hack and this won't solve all the problems.
>>>
>>> I expect page configuration to be a very common problem so I think
>>> there should be a simple/standard approach for this or just some best
>>> practices about this.
>>>
>>> Thanks, bye
>>>
>>>
>>> Lorenzo
>>>
>>>
>>> 2008/8/6 Igor Vaynberg <[EMAIL PROTECTED]>:
 well normally you would just do

 class monitorpage extends webpage {
  public monitorpage(string deviceid) {
 .. do whatever with deviceid
  }
 }

 if you need your pages to be bookmarkable then just use

 class monitorpage extends webpage {
  public monitorpage(pageparameters params) {
string deviceid=params.get("0");
   }
 }

 and mount the page with mount("/device",new
 indexedurlcodingstrategy(monitorpage.class));
 then the urls are /device/deviceid

 -igor

 On Wed, Aug 6, 2008 at 10:48 AM, Lorenzo Bolzani <[EMAIL PROTECTED]>
 wrote:
> Hi all, I have a page to monitor the status of a remote device.
> The page just stay there and refresh automatically to display the actual
> state.
>
> The problem is that I need to have to distinct pages to monitor two
> distinct devices.
>
> My ideal approach would be to define two pages in spring, something like
> this
>
> 
>
>
> 
>
> 
>
>
> 
>
> but I know that Wicket is not going to look for this pages in my
> spring-config file.
>
> In other words I need two instances of the same page configured in two
> different ways.
> Is this possibile? How can I pass in the parameters (with or without
> spring)? I found nothing about this in the docs.
> In this way I could pass in the ref name (device1 or device2) and make
> it work with an explicit spring context lookup (no injection).
>
> The @SpringBean annotation works but in this specific case it is not
> usable because of the two different parameters.
>
> Thanks for any suggestions.
>
>
> Bye
>
> Lorenzo
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, 

Re: PageParameters

[Igor Vaynberg]

wicket provides convinience methods for working with strings, eg a
method to automatically convert a string to an int so you dont have
to. likewise it will automatically convert all objects you put into it
to a string.

-igor

On Mon, Aug 11, 2008 at 7:36 AM, Lutz Müller <[EMAIL PROTECTED]> wrote:
> Thats what I was thinking, too, when I read Uwes post. I did not look at
> Wicket 1.4 yet, but had assumed that PageParameters should always be String to
> String maps, because this is what they are in HTTP.
> But then again, wicket is not strictly HTTP, and when you look at the javadoc
> comment for PageParameters (at least in 1.3) it explicitly states that
> PageParameters might be used with other protocols. Maybe this is the reason
> why.
>
> Lutz
>
> On Monday 11 August 2008 02:33:56 Brill Pappin wrote:
>> I agree on the generics front... however are not the params supposed
>> to be strings?
>> or do they represent request parameters as well as page attributes?
>>
>> If they are representing both, maybe they should be separated.
>>
>> - Brill
>>
>> On 8-Aug-08, at 12:59 PM, Uwe Schäfer wrote:
>> > ok, maybe there was too much K and V in my last mail ;)
>> >
>> > I´ll try another way round:
>> >
>> > wouldn´t it be nice to be able to use smth like that ?
>> >
>> > Map map =...
>> > PageParameters p = new PageParameters(map);
>> >
>> > So if you agree, please switch from
>> >
>> > public PageParameters(final Map parameterMap)
>> > to
>> > public PageParameters(final Map parameterMap)
>> >
>> > thx, uwe
>> >
>> > --
>> >
>> > THOMAS DAILY GmbH
>> > Adlerstraße 19
>> > 79098 Freiburg
>> > Deutschland
>> > T  + 49 761 3 85 59 0
>> > F  + 49 761 3 85 59 550
>> > E  [EMAIL PROTECTED]
>> > www.thomas-daily.de
>> >
>> > Geschäftsführer/Managing Directors:
>> > Wendy Thomas, Susanne Larbig
>> > Handelsregister Freiburg i.Br., HRB 3947
>> >
>> > Registrieren Sie sich unter http://morningnews.thomas-daily.de für
>> > die kostenfreien TD Morning News, eine Auswahl aktueller Themen des
>> > Tages morgens um 9:00 in Ihrer Mailbox.
>> >
>> > Hinweis: Der Redaktionsschluss für unsere TD Morning News ist
>> > täglich um 8:30 Uhr. Es werden vorrangig Informationen
>> > berücksichtigt, die nach 16:00 Uhr des Vortages eingegangen sind.
>> > Die Email-Adresse unserer Redaktion lautet [EMAIL PROTECTED]
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: how to test multiple submits on the form

[Igor Vaynberg]

add button's name attribute to the post params

iirc buttonname.x=2&buttonname.y=2 will do

-igor

On Mon, Aug 11, 2008 at 12:18 AM, ElSe <[EMAIL PROTECTED]> wrote:
>
> Hi, all!
>
> I have a question regarding the load testing of the Wicket application.
>
> I have used this article
> http://cwiki.apache.org/WICKET/multiple-submit-buttons.html to create the
> form in my application. All works well. But now I have to organize load
> testing of my application.
>
> I have read this article -
> http://cwiki.apache.org/WICKET/wicket-and-jmeter-with-regular-expressions.html
> began to write test plan and suddenly met the problem: I can't write regular
> expression to submit form to the server. It is  easy when there is one
> submit button but what should I do if there are several of them? I don't
> know how to "press" one definite button.
>
> I think that the problem comes to following: I don't understand how Wicket
> does determine what button was pressed. When any submit button is pressed
> the url seems to be the same - something like this:
> http:?wicket:interface=:1:::IFormSubmitListener::.
>
> May be I'm wrong and didn't notice some important detail?
>
> Could anybody clear this situation for me?
>
> Best regards,
> Elena.
> --
> View this message in context: 
> http://www.nabble.com/how-to-test-multiple-submits-on-the-form-tp18921170p18921170.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wicket 1.4m3 - AjaxButton, AjaxSubmitLink in ModalWindow in IE 7 Problem ?

[kag1526]

I just tested my app in IE 7 since I also have a ModalWindow with an
AjaxSubmitLink that submits my form and closes the window and mine worked
fine. sorry I can't help with a solution but I can tell you that it is
possible to make work.



FakeBoy wrote:
> 
> Hi,
> I tried to submit form from ModalWindow with AjaxButton or AjaxSubmitLink.
> In Firefox, Opera, Safari everything works fine, but in IE 7 doesn't.
> No onSubmit or onError method is fired after button or link cliked in IE
> 7.
> I used WICKET DEBUG console and after clik on Button or Link i see
> message:
> INFO: Ajax POST stopped because of precondition check,
> url:?wicket:interface=modal-dialog-pagemap:0:form:testLink1::IActivePageBehaviorListener:0:&wicket:ignoreIfNotActive=true
> What doe's it mean? It's wicket problem or I did something wrong? 
> Thanks a lot for your soon reply.
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Wicket-1.4m3---AjaxButton%2C-AjaxSubmitLink-in-ModalWindow-in-IE-7-Problem---tp18912755p18927552.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Always serialize pages for debug purposes

[Jonas]

It seems this feature was removed, but there's some javadoc
left in org.apache.wicket.settings.IDebugSettings:
[quote]
serializeSessionAttributes (defaults to true in development
mode) - Causes the framework
 * to serialize any attribute put into session - this helps find Not
Serializable errors early
[/quote]

On Mon, Aug 11, 2008 at 3:30 PM, Thomas Mäder <[EMAIL PROTECTED]> wrote:
> Yeah, but wasn't there "official" support for that? And if not, wouldn't
> this be useful for debug?
>
> Thomas
>
> 2008/8/11 Uwe Schäfer <[EMAIL PROTECTED]>
>
>> Thomas Mäder schrieb:
>>
>>
>>  I seem to remember that there was a way to force Wicket to always
>>> serialize
>>> pages on detach in order to make sure every page is serializable during
>>> development. Can someone please point me to the FM so I can read it?
>>> Searching Nabble & Google didn't turn up anything.
>>>
>>
>> one guy once posted this one:
>>
>>
>> 
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: PageParameters

[Lutz Müller]

Thats what I was thinking, too, when I read Uwes post. I did not look at 
Wicket 1.4 yet, but had assumed that PageParameters should always be String to 
String maps, because this is what they are in HTTP.
But then again, wicket is not strictly HTTP, and when you look at the javadoc 
comment for PageParameters (at least in 1.3) it explicitly states that  
PageParameters might be used with other protocols. Maybe this is the reason 
why.

Lutz

On Monday 11 August 2008 02:33:56 Brill Pappin wrote:
> I agree on the generics front... however are not the params supposed
> to be strings?
> or do they represent request parameters as well as page attributes?
>
> If they are representing both, maybe they should be separated.
>
> - Brill
>
> On 8-Aug-08, at 12:59 PM, Uwe Schäfer wrote:
> > ok, maybe there was too much K and V in my last mail ;)
> >
> > I´ll try another way round:
> >
> > wouldn´t it be nice to be able to use smth like that ?
> >
> > Map map =...
> > PageParameters p = new PageParameters(map);
> >
> > So if you agree, please switch from
> >
> > public PageParameters(final Map parameterMap)
> > to
> > public PageParameters(final Map parameterMap)
> >
> > thx, uwe
> >
> > --
> >
> > THOMAS DAILY GmbH
> > Adlerstraße 19
> > 79098 Freiburg
> > Deutschland
> > T  + 49 761 3 85 59 0
> > F  + 49 761 3 85 59 550
> > E  [EMAIL PROTECTED]
> > www.thomas-daily.de
> >
> > Geschäftsführer/Managing Directors:
> > Wendy Thomas, Susanne Larbig
> > Handelsregister Freiburg i.Br., HRB 3947
> >
> > Registrieren Sie sich unter http://morningnews.thomas-daily.de für
> > die kostenfreien TD Morning News, eine Auswahl aktueller Themen des
> > Tages morgens um 9:00 in Ihrer Mailbox.
> >
> > Hinweis: Der Redaktionsschluss für unsere TD Morning News ist
> > täglich um 8:30 Uhr. Es werden vorrangig Informationen
> > berücksichtigt, die nach 16:00 Uhr des Vortages eingegangen sind.
> > Die Email-Adresse unserer Redaktion lautet [EMAIL PROTECTED]
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

Re: Multiple instances of pages and spring integration

[Michael Sparer]

Well if it's no dynamic parameter but a static one, different for each page
... why not subclassing a basepage with changed attributes?

If the only problem you see is a missing overview, i.e. you'd like to
control the different values at one place, you should consider setting the
properties e.g. in the application ...

regards
Michael


Lorenzo Bolzani wrote:
> 
> Hi Michael, the point is that this is not a user provided parameter
> but a "server-side" page configuration parameter.
> 
> In this specific case I need to tell the page how often it should
> auto-refresh. So it is not something that should be passed in from the
> client over the url but something defined at the application startup.
> If my page requires three config parameters I do not want to have to
> provide these on every link to this page.
> 
> Am I missing something?
> 
> Bye
> 
> Lorenzo
> 
> 2008/8/11 Michael Sparer <[EMAIL PROTECTED]>:
>>
>> I'd say Igor's suggestion is a solution rather than workaround. There's
>> just
>> no point in configuring pages by means of XML or - worse - even a spring
>> config. Passing in page specific parameters is exactly the way to go.
>>
>>> I tryed to pass in these parameters as PageParameters but in this way
>>> I have to convert this from String to Integer to use it and in every
>>> call to the page I have to provide these parameters.
>>
>> I don't get it. Parsing a String with Integer.parse shouldn't be
>> considered
>> as a bad hack or a problem - as far as i know you can even use
>> params.getInt("foobar"). and you're also free to do your custom stuff if
>> a
>> param isn't provided. or am i misunderstanding something?
>>
>> regards,
>> Michael
>>
>>
>> Lorenzo Bolzani wrote:
>>>
>>> Hi Igor, I tried your suggestion and it works but looks like a
>>> workaround more than a solution.
>>>
>>> I have many pages that need some configuration. This is server side
>>> configuration, for example how often a page should refresh itself.
>>> I tryed to pass in these parameters as PageParameters but in this way
>>> I have to convert this from String to Integer to use it and in every
>>> call to the page I have to provide these parameters. At the same time
>>> I do not have an easy place to put this page configuration params. I
>>> think I can define a PageParameters bean for each page inside spring
>>> but looks like a bad hack and this won't solve all the problems.
>>>
>>> I expect page configuration to be a very common problem so I think
>>> there should be a simple/standard approach for this or just some best
>>> practices about this.
>>>
>>> Thanks, bye
>>>
>>>
>>> Lorenzo
>>>
>>>
>>> 2008/8/6 Igor Vaynberg <[EMAIL PROTECTED]>:
 well normally you would just do

 class monitorpage extends webpage {
  public monitorpage(string deviceid) {
 .. do whatever with deviceid
  }
 }

 if you need your pages to be bookmarkable then just use

 class monitorpage extends webpage {
  public monitorpage(pageparameters params) {
string deviceid=params.get("0");
   }
 }

 and mount the page with mount("/device",new
 indexedurlcodingstrategy(monitorpage.class));
 then the urls are /device/deviceid

 -igor

 On Wed, Aug 6, 2008 at 10:48 AM, Lorenzo Bolzani <[EMAIL PROTECTED]>
 wrote:
> Hi all, I have a page to monitor the status of a remote device.
> The page just stay there and refresh automatically to display the
> actual
> state.
>
> The problem is that I need to have to distinct pages to monitor two
> distinct devices.
>
> My ideal approach would be to define two pages in spring, something
> like
> this
>
> 
>
>
> 
>
> 
>
>
> 
>
> but I know that Wicket is not going to look for this pages in my
> spring-config file.
>
> In other words I need two instances of the same page configured in two
> different ways.
> Is this possibile? How can I pass in the parameters (with or without
> spring)? I found nothing about this in the docs.
> In this way I could pass in the ref name (device1 or device2) and make
> it work with an explicit spring context lookup (no injection).
>
> The @SpringBean annotation works but in this specific case it is not
> usable because of the two different parameters.
>
> Thanks for any suggestions.
>
>
> Bye
>
> Lorenzo
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


>>>
>>>
>>>
>>> --
>>> It has to start somewhere, It has to start sometime.
>>> What better place than here, what better tim

Re: Multiple instances of pages and spring integration

[Lorenzo Bolzani]

Hi Michael, the point is that this is not a user provided parameter
but a "server-side" page configuration parameter.

In this specific case I need to tell the page how often it should
auto-refresh. So it is not something that should be passed in from the
client over the url but something defined at the application startup.
If my page requires three config parameters I do not want to have to
provide these on every link to this page.

Am I missing something?

Bye

Lorenzo

2008/8/11 Michael Sparer <[EMAIL PROTECTED]>:
>
> I'd say Igor's suggestion is a solution rather than workaround. There's just
> no point in configuring pages by means of XML or - worse - even a spring
> config. Passing in page specific parameters is exactly the way to go.
>
>> I tryed to pass in these parameters as PageParameters but in this way
>> I have to convert this from String to Integer to use it and in every
>> call to the page I have to provide these parameters.
>
> I don't get it. Parsing a String with Integer.parse shouldn't be considered
> as a bad hack or a problem - as far as i know you can even use
> params.getInt("foobar"). and you're also free to do your custom stuff if a
> param isn't provided. or am i misunderstanding something?
>
> regards,
> Michael
>
>
> Lorenzo Bolzani wrote:
>>
>> Hi Igor, I tried your suggestion and it works but looks like a
>> workaround more than a solution.
>>
>> I have many pages that need some configuration. This is server side
>> configuration, for example how often a page should refresh itself.
>> I tryed to pass in these parameters as PageParameters but in this way
>> I have to convert this from String to Integer to use it and in every
>> call to the page I have to provide these parameters. At the same time
>> I do not have an easy place to put this page configuration params. I
>> think I can define a PageParameters bean for each page inside spring
>> but looks like a bad hack and this won't solve all the problems.
>>
>> I expect page configuration to be a very common problem so I think
>> there should be a simple/standard approach for this or just some best
>> practices about this.
>>
>> Thanks, bye
>>
>>
>> Lorenzo
>>
>>
>> 2008/8/6 Igor Vaynberg <[EMAIL PROTECTED]>:
>>> well normally you would just do
>>>
>>> class monitorpage extends webpage {
>>>  public monitorpage(string deviceid) {
>>> .. do whatever with deviceid
>>>  }
>>> }
>>>
>>> if you need your pages to be bookmarkable then just use
>>>
>>> class monitorpage extends webpage {
>>>  public monitorpage(pageparameters params) {
>>>string deviceid=params.get("0");
>>>   }
>>> }
>>>
>>> and mount the page with mount("/device",new
>>> indexedurlcodingstrategy(monitorpage.class));
>>> then the urls are /device/deviceid
>>>
>>> -igor
>>>
>>> On Wed, Aug 6, 2008 at 10:48 AM, Lorenzo Bolzani <[EMAIL PROTECTED]>
>>> wrote:
 Hi all, I have a page to monitor the status of a remote device.
 The page just stay there and refresh automatically to display the actual
 state.

 The problem is that I need to have to distinct pages to monitor two
 distinct devices.

 My ideal approach would be to define two pages in spring, something like
 this

 


 

 


 

 but I know that Wicket is not going to look for this pages in my
 spring-config file.

 In other words I need two instances of the same page configured in two
 different ways.
 Is this possibile? How can I pass in the parameters (with or without
 spring)? I found nothing about this in the docs.
 In this way I could pass in the ref name (device1 or device2) and make
 it work with an explicit spring context lookup (no injection).

 The @SpringBean annotation works but in this specific case it is not
 usable because of the two different parameters.

 Thanks for any suggestions.


 Bye

 Lorenzo

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>>
>>
>> --
>> It has to start somewhere, It has to start sometime.
>> What better place than here, what better time than now?
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>
>
> -
> Michael Sparer
> http://talk-on-tech.blogspot.com
> --
> View this message in context: 
> http://www.nabble.com/Multiple-instances-of-pages-and-spring-integration-tp18856317p18924320.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -
> To

Re: Always serialize pages for debug purposes

[Thomas Mäder]

Yeah, but wasn't there "official" support for that? And if not, wouldn't
this be useful for debug?

Thomas

2008/8/11 Uwe Schäfer <[EMAIL PROTECTED]>

> Thomas Mäder schrieb:
>
>
>  I seem to remember that there was a way to force Wicket to always
>> serialize
>> pages on detach in order to make sure every page is serializable during
>> development. Can someone please point me to the FM so I can read it?
>> Searching Nabble & Google didn't turn up anything.
>>
>
> one guy once posted this one:
>
>
> 

Re: Always serialize pages for debug purposes

[Uwe Schäfer]

Thomas Mäder schrieb:


I seem to remember that there was a way to force Wicket to always serialize
pages on detach in order to make sure every page is serializable during
development. Can someone please point me to the FM so I can read it?
Searching Nabble & Google didn't turn up anything.


one guy once posted this one:

class PickyHttpSessionStore extends HttpSessionStore
{
/**
 * @param application
 */
public PickyHttpSessionStore(final Application application)
{
super(application);
}

@Override
public void setAttribute(final Request request, final String 
name, final Object value)

{
try
{
ByteArrayOutputStream baos = new ByteArrayOutputStream();
ObjectOutputStream stream = new ObjectOutputStream(baos);
stream.writeObject(value);
stream.close();

super.setAttribute(request, name, value);
}
catch (Throwable exception)
{
String s = "Unable to serialize value: " + 
value.toString();

System.err.println(s);
System.err.println(exception);
throw new RuntimeException(s, exception);
}

}
}

--

THOMAS DAILY GmbH
Adlerstraße 19
79098 Freiburg
Deutschland
T  + 49 761 3 85 59 0
F  + 49 761 3 85 59 550
E  [EMAIL PROTECTED]
www.thomas-daily.de

Geschäftsführer/Managing Directors:
Wendy Thomas, Susanne Larbig
Handelsregister Freiburg i.Br., HRB 3947

Registrieren Sie sich unter http://morningnews.thomas-daily.de für die 
kostenfreien TD Morning News, eine Auswahl aktueller Themen des Tages 
morgens um 9:00 in Ihrer Mailbox.


Hinweis: Der Redaktionsschluss für unsere TD Morning News ist täglich um 
8:30 Uhr. Es werden vorrangig Informationen berücksichtigt, die nach 
16:00 Uhr des Vortages eingegangen sind. Die Email-Adresse unserer 
Redaktion lautet [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Customizing treeTable.

[kag1526]

I am using a tree table to display data from a database, however some of the
rows in the tree table needs to have multiple values that I would like to be
displayed in the same cell on multiple lines like:

Name   | ABC

Variant names   | ABC corp
  | ABC corporation


To do this I extended PropertyRenderableColumn to make a PropertyMultiLine
column that simply has a MultiLineLabel instead of a plain label and set the
overflow to scroll so that the cell will scroll if the list is really long.
This causes the correct data to be displayed in the fields however the row
height doesn't expand so in IE you will only see the first company and then
have a tiny scroll bar to see the others, and in firefox it adds an extra
new line to the beginning and end of the list so all I see is the very top
of the letters (I also don't get the scroll bars but I'll deal with that
later)

To extend the table row I tried changing the css height value of div.row and
of div.a_ but neither worked, from the html the structure of the table seems
to be:

 
   
   
  
   

 
  
   

   
 My text here 
   
  
   
 

   
   
  


Any other ideas on how I might get the row height larger?   
 


-- 
View this message in context: 
http://www.nabble.com/Customizing-treeTable.-tp18924644p18924644.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Multiple instances of pages and spring integration

[Michael Sparer]

I'd say Igor's suggestion is a solution rather than workaround. There's just
no point in configuring pages by means of XML or - worse - even a spring
config. Passing in page specific parameters is exactly the way to go.

> I tryed to pass in these parameters as PageParameters but in this way
> I have to convert this from String to Integer to use it and in every
> call to the page I have to provide these parameters.

I don't get it. Parsing a String with Integer.parse shouldn't be considered
as a bad hack or a problem - as far as i know you can even use
params.getInt("foobar"). and you're also free to do your custom stuff if a
param isn't provided. or am i misunderstanding something?

regards, 
Michael


Lorenzo Bolzani wrote:
> 
> Hi Igor, I tried your suggestion and it works but looks like a
> workaround more than a solution.
> 
> I have many pages that need some configuration. This is server side
> configuration, for example how often a page should refresh itself.
> I tryed to pass in these parameters as PageParameters but in this way
> I have to convert this from String to Integer to use it and in every
> call to the page I have to provide these parameters. At the same time
> I do not have an easy place to put this page configuration params. I
> think I can define a PageParameters bean for each page inside spring
> but looks like a bad hack and this won't solve all the problems.
> 
> I expect page configuration to be a very common problem so I think
> there should be a simple/standard approach for this or just some best
> practices about this.
> 
> Thanks, bye
> 
> 
> Lorenzo
> 
> 
> 2008/8/6 Igor Vaynberg <[EMAIL PROTECTED]>:
>> well normally you would just do
>>
>> class monitorpage extends webpage {
>>  public monitorpage(string deviceid) {
>> .. do whatever with deviceid
>>  }
>> }
>>
>> if you need your pages to be bookmarkable then just use
>>
>> class monitorpage extends webpage {
>>  public monitorpage(pageparameters params) {
>>string deviceid=params.get("0");
>>   }
>> }
>>
>> and mount the page with mount("/device",new
>> indexedurlcodingstrategy(monitorpage.class));
>> then the urls are /device/deviceid
>>
>> -igor
>>
>> On Wed, Aug 6, 2008 at 10:48 AM, Lorenzo Bolzani <[EMAIL PROTECTED]>
>> wrote:
>>> Hi all, I have a page to monitor the status of a remote device.
>>> The page just stay there and refresh automatically to display the actual
>>> state.
>>>
>>> The problem is that I need to have to distinct pages to monitor two
>>> distinct devices.
>>>
>>> My ideal approach would be to define two pages in spring, something like
>>> this
>>>
>>> 
>>>
>>>
>>> 
>>>
>>> 
>>>
>>>
>>> 
>>>
>>> but I know that Wicket is not going to look for this pages in my
>>> spring-config file.
>>>
>>> In other words I need two instances of the same page configured in two
>>> different ways.
>>> Is this possibile? How can I pass in the parameters (with or without
>>> spring)? I found nothing about this in the docs.
>>> In this way I could pass in the ref name (device1 or device2) and make
>>> it work with an explicit spring context lookup (no injection).
>>>
>>> The @SpringBean annotation works but in this specific case it is not
>>> usable because of the two different parameters.
>>>
>>> Thanks for any suggestions.
>>>
>>>
>>> Bye
>>>
>>> Lorenzo
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 
> 
> -- 
> It has to start somewhere, It has to start sometime.
> What better place than here, what better time than now?
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 


-
Michael Sparer
http://talk-on-tech.blogspot.com
-- 
View this message in context: 
http://www.nabble.com/Multiple-instances-of-pages-and-spring-integration-tp18856317p18924320.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Always serialize pages for debug purposes

[Thomas Mäder]

Hi Guys,

I seem to remember that there was a way to force Wicket to always serialize
pages on detach in order to make sure every page is serializable during
development. Can someone please point me to the FM so I can read it?
Searching Nabble & Google didn't turn up anything.

this is 1.3.3

Thomas

Re: tinymce ajax submit

[sander v F]

For a project I also needed a AjaxSubmitLink to submit the tinyMce data, so
i've searched for a solution and found it at
http://dwairi.blogspot.com/2006/12/tinymce-ajax.html
The solution is to add "tinyMCE.triggerSave(true,true);" to the onclick of
the ajax button/link before the wicket code is called.

I made a nice Wicket AttributeModifier (TinyMceAjaxSubmitModifier) which can
be added to the ajax button/link and I also made a TinyMceAjaxButton and
TinyMceAjaxSubmitLink for easier use.

These component are added to the wicket-contrib-tinymce project.



2008/2/19 Igor Vaynberg <[EMAIL PROTECTED]>

> tinymce replaces the textarea with an iframe. after that it installs
> an onsubmit hook to detect when the form is submitted and does the
> opposite. since you are submitting via ajax form's onsubmit() is never
> called and so tinymce doesnt replace the iframe with a textarea piror
> tp submit. you need to look at what that callback calls and call it
> yourself
>
> -igor
>
> On Feb 19, 2008 2:55 AM, Benjamin Ernst <[EMAIL PROTECTED]> wrote:
> > Hi Marc,
> >
> > I have the same problem. When i am submitting a textarea with a
> > TinyMCEBehavior the model of the textarea does not get updated.
> > I am interested in your solution, but I do not understand it.
> >
> > It would be nice if you (or anyone else) could explain it for me.
> >
> > Thanks in advance,
> > Benjamin
> >
> > 2007/11/19, godin <[EMAIL PROTECTED]>:
> >
> > >
> > > godin a écrit :
> > > > Frank Bille a écrit :
> > > >> Hi,
> > > >>
> > > >> Do you have problems with it?
> > > >>
> > > >>
> > > >
> > > > yes , the submit work half a time 
> > > > i will investigate it more
> > >
> > >
> > > Ok find a workaround,
> > > pb on mozilla, use a decorator
> > > super.decorateScript("tinyMCE.triggerSave(true,
> > > true);"+script+"tinyMCE.idCounter=0;");
> > >
> > > regards marc
> > > Wicket rocks !
> > > >> I tried it over a year ago, and as far as I remember there was
> > > >> nothing to
> > > >> it. That was Wicket 1.2.3 and tinymce from back then.
> > > >>
> > > >> Frank
> > > >>
> > > >> On Nov 16, 2007 5:24 PM, godin <[EMAIL PROTECTED]> wrote:
> > > >>
> > > >>
> > > >>> Hi,
> > > >>> doe somebody manage to make tinymce work with an ajax submit button
> > > >>> regards
> > > >>> Marc
> > > >>>
> > > >>>
> -
> > > >>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > >>> For additional commands, e-mail: [EMAIL PROTECTED]
> > > >>>
> > > >>>
> > > >>>
> > > >>
> > > >>
> > > >
> > > > -
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

RE: Strange AjaxFormComponentUpdatingBehavior with Internet Explorer

[Kai Mütz]

Can anyone helb with the above issue?

Kai Mütz  wrote:
> BTW, whilw checking the checkbox the AJAX Debug window says:
>
> Info: Set focus on required
>
>
> That's all.
>
>
> 2008/8/8 Kai Mütz <[EMAIL PROTECTED]>
>
> Hi,
>
> I have 2 form components in a form. A checkbox and a dropdownchoice.
> The dropdownchoice should depend on the checkbox, as it is enabled if
> the checkbox is checked and disabled if the checkbox is not checked.
>
> Thus I have added a AjaxFormComponentUpdatingBehavior:
>
> final CheckBox required = new CheckBox("required", new
> PropertyModel(project, "required"));
> add(required);
> final DropDownChoice officer = new DropDownChoice("officer", new
> PropertyModel(project, "officer"), users, true);
> add(officer);
> officer.setOutputMarkupId(true);
> officer.setEnabled(project.isRequired());
> required.add(new AjaxFormComponentUpdatingBehavior("onchange") {
>protected void onUpdate(final AjaxRequestTarget target) {
>officer.setEnabled((Boolean)
>required.getModelObject()); if (!officer.isEnabled()) {
>officer.setModelObject(null);
>}
>target.addComponent(officer);
>}
> });
>
>
> This works fine withe Firefox. With IE7 (and IE6) the dropdownchoice
> is not updated until clicking on the it. Example:
>
> - Checkbox is unchecked and dropdownchoice is disabled by default
> - Check the checkbox -> nothing happens, dropdownchoice is still
> disabled (in IE)
> - Clicking on dropdownchoice -> dropdownchoice is enabled
> - Uncheck the checkbox -> nothing happens, dropdownchoice is still
> enabled (in IE)
> - Clicking on dropdownchoice -> dropdownchoice is disabled
>
>
> Can anybody help?
>
> Cheers, Kai


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Multiple instances of pages and spring integration

[Lorenzo Bolzani]

Hi Igor, I tried your suggestion and it works but looks like a
workaround more than a solution.

I have many pages that need some configuration. This is server side
configuration, for example how often a page should refresh itself.
I tryed to pass in these parameters as PageParameters but in this way
I have to convert this from String to Integer to use it and in every
call to the page I have to provide these parameters. At the same time
I do not have an easy place to put this page configuration params. I
think I can define a PageParameters bean for each page inside spring
but looks like a bad hack and this won't solve all the problems.

I expect page configuration to be a very common problem so I think
there should be a simple/standard approach for this or just some best
practices about this.

Thanks, bye


Lorenzo


2008/8/6 Igor Vaynberg <[EMAIL PROTECTED]>:
> well normally you would just do
>
> class monitorpage extends webpage {
>  public monitorpage(string deviceid) {
> .. do whatever with deviceid
>  }
> }
>
> if you need your pages to be bookmarkable then just use
>
> class monitorpage extends webpage {
>  public monitorpage(pageparameters params) {
>string deviceid=params.get("0");
>   }
> }
>
> and mount the page with mount("/device",new
> indexedurlcodingstrategy(monitorpage.class));
> then the urls are /device/deviceid
>
> -igor
>
> On Wed, Aug 6, 2008 at 10:48 AM, Lorenzo Bolzani <[EMAIL PROTECTED]> wrote:
>> Hi all, I have a page to monitor the status of a remote device.
>> The page just stay there and refresh automatically to display the actual 
>> state.
>>
>> The problem is that I need to have to distinct pages to monitor two
>> distinct devices.
>>
>> My ideal approach would be to define two pages in spring, something like this
>>
>> 
>>
>>
>> 
>>
>> 
>>
>>
>> 
>>
>> but I know that Wicket is not going to look for this pages in my
>> spring-config file.
>>
>> In other words I need two instances of the same page configured in two
>> different ways.
>> Is this possibile? How can I pass in the parameters (with or without
>> spring)? I found nothing about this in the docs.
>> In this way I could pass in the ref name (device1 or device2) and make
>> it work with an explicit spring context lookup (no injection).
>>
>> The @SpringBean annotation works but in this specific case it is not
>> usable because of the two different parameters.
>>
>> Thanks for any suggestions.
>>
>>
>> Bye
>>
>> Lorenzo
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
It has to start somewhere, It has to start sometime.
What better place than here, what better time than now?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ListView in Forms

[Markus Haspl]

hi,

thanks. this works :-)

avajon

On Sat, Aug 9, 2008 at 1:11 AM, brian.diekelman <[EMAIL PROTECTED]> wrote:

>
>
> There are a few things going on here... try this and see if it does what
> you
> want it to do.  If so reply back and I'll explain what the underlying issue
> was:
>
> TextField propertiesName = new TextField("name",new
> PropertyModel(pluginProperties, "name"));
> TextField propertiesValue = new TextField("value",new
> PropertyModel(pluginProperties, "value"));
> CheckBox propertiesDefault = new CheckBox("defaultProperty",new
> PropertyModel(pluginProperties, "defaultProperty"));
>
>
> Markus Haspl wrote:
> >
> > no, there aren't any errors.
> >
> > but i don't understand why i have to use propertiesName.getModelObject();
> > in
> > the onSubmit() method. Because there may be hundrets of propertiesName in
> > the ListView/Form.
> >
> > Would it be better to make a Forms in a ListView? But then i need for
> > every
> > Form a submit-button. that wouldn't be so nice...
> >
> > thanks
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/ListView-in-Forms-tp18852263p18900382.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Extending BrowserInfoForm

[Federico Fanton]

On Fri, 8 Aug 2008 08:29:37 -0700
[EMAIL PROTECTED] wrote:

> should be fine

Done, https://issues.apache.org/jira/browse/WICKET-1786
Thanks!


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

how to test multiple submits on the form

[ElSe]

Hi, all!

I have a question regarding the load testing of the Wicket application.

I have used this article
http://cwiki.apache.org/WICKET/multiple-submit-buttons.html to create the
form in my application. All works well. But now I have to organize load
testing of my application.

I have read this article -
http://cwiki.apache.org/WICKET/wicket-and-jmeter-with-regular-expressions.html 
began to write test plan and suddenly met the problem: I can't write regular
expression to submit form to the server. It is  easy when there is one
submit button but what should I do if there are several of them? I don't
know how to "press" one definite button.

I think that the problem comes to following: I don't understand how Wicket
does determine what button was pressed. When any submit button is pressed
the url seems to be the same - something like this:
http:?wicket:interface=:1:::IFormSubmitListener::.
 

May be I'm wrong and didn't notice some important detail?

Could anybody clear this situation for me?

Best regards,
Elena.
-- 
View this message in context: 
http://www.nabble.com/how-to-test-multiple-submits-on-the-form-tp18921170p18921170.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]