date:20060425

override configureResponseOn 4/25/06, lu dongping [EMAIL PROTECTED] wrote:
I now need to expire the page at once,so users can not click back button again.thanks!

Re: [Wicket-user] Is there an easy way to Prevent Caching and Expire HTML content imediately

2006-04-25 Thread Eelco Hillenius

The page or the session?

If you don't want to support the back button for a page, just override
isVersioned and return false. The effect is that the URL stays the
same, so the back button will take users to the page they were before
that.

To invalidate a session, call Session.invalidate().

Eelco

On 4/25/06, lu dongping [EMAIL PROTECTED] wrote:
 I now need to expire the page at once,
 so users can not click back button again.
 thanks!



---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] UML diagram?

2006-04-25 Thread Alexandre Bairos

A good catch is to show the framework concepts, showing hot and frozen spots. For each concept, a wiki node.On 4/24/06, Stefan Kanev 
[EMAIL PROTECTED] wrote:HiDon't you think that an UML diagram for the basic objects in wicket would be useful for newbies to the frameworks (shows the complete) picture and for all users, where it can serve as a quick reference. Since such a diagram is not present, I'm willing to put up one. What do you think should be included in it?
Stefan

[Wicket-user] AJAX: updating a label by klicking a check box

2006-04-25 Thread Stefan Lindner

Dear wicket supporters,

I am looking for some hints for the following: I have a form containing
a check box. This form uses AJAX to submit the check box value after
klicking it. Not I want to update a label on the page when the check box
is klicked. I found the ajax with prototype - Ajax example using
prototype.js example that does something similar. But I found no way to
manipulate the on click script for the check box.


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] AJAX: updating a label by klicking a check box

this is trivial to do if you want to use wicket's ajax support instead of the prorotype.js. in fact there are plenty examples in wicket-examples/ajax that will give you a clue.basically...call setOutputMarkupId(true) on the label.
use AjaxCheckBox and in onclick() add the label to the AjaxTargetthats it.-IgorOn 4/25/06, Stefan Lindner 
[EMAIL PROTECTED] wrote:Dear wicket supporters,I am looking for some hints for the following: I have a form containing
a check box. This form uses AJAX to submit the check box value afterklicking it. Not I want to update a label on the page when the check boxis klicked. I found the ajax with prototype - Ajax example using
prototype.js example that does something similar. But I found no way tomanipulate the on click script for the check box.---Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easierDownload IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmdlnkkid0709bid3057dat1642___Wicket-user mailing listWicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

[Wicket-user] RE: Removing a Validator

2006-04-25 Thread Andrew Strickland

My apologies for leaving all that reply text in my last response.  Hopefully it 
doesn't confuse anyone too much.
 
Andy
winmail.dat

Re: [Wicket-user] Removing a Validator

How would you remove the validator? Would you do it by index or by instance? Its not very clean either way. Check out IFormValidator, I think it fits your usecase better then an IValidator.-Igor
On 4/25/06, Andrew Strickland [EMAIL PROTECTED] wrote:
Was the capability added in 1.2 to remove Validators from a component?If not, are there any plans to add such a capability?When doing dynamic forms it is a huge convenience to be able to add and remove validators based on a user selection on another field in the form.
An example: on my project some fields are required or not depending on the classification of the system.During account creation the user has the ability to choose which classification they are requesting their account be created for.If they choose the more restrictive classification and then change their mind and switch to the less restrictive some of the fields that I added a validator to will now STILL have the RequiredValidator even though it is no longer a required field, and I have no way of removing the validator.
Andy

[Wicket-user] GridView option?

2006-04-25 Thread Frank Silbermann









On each page of a GridView
(Wicket Extensions 1.2) the elements enter the grid in row-order, from top to
bottom. Is there a way to have the DataProvider populate the grid in column-order  filling
one column from top to bottom before moving onto the next column to the right?



If not, maybe this could be considered a
feature request.

[Wicket-user] onkeydown or onkeyup

2006-04-25 Thread Davy De Durpel


Hi,

I finally managed to get my own search text field working but I think I
might have found a bug in one of the wicket examples.

The problem is related to the behavior of the 'onkeydown' event.  Whenever I
press a key, only the previous key presses are submitted and not the current
one.  (ex. when my field contains 'dumm' and I press the 'y' then only
'dumm' will be submitted)  This seems to be the default behaviour of (all?)
browsers because the onkeydown event allows you to cancel a keypress, so
that in that case your field isn't updated.  This means that I should use
the 'onkeyup' event.  In that case everything works as it should.

But the 'Ajax - BuiltIn - Form' example uses the 'onkeydown' event.  You can
clearly see the problem when you enter something in the 'Email' field.  The
message that is displayed in the FeedBackPanel never displays the last
character that has been entered.

Replacing it with the 'onkeyup' event should fix it.

byeee...
--
View this message in context: 
http://www.nabble.com/onkeydown-or-onkeyup-t1506344.html#a4085010
Sent from the Wicket - User forum at Nabble.com.



---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] GridView option?

if you want column-major form you will have to rewrite gridview, it is not that simple because html is row-major. so to do column-major you will have to buffer output somewhere, you cant just stream it like gridview works now.
-IgorOn 4/25/06, Frank Silbermann [EMAIL PROTECTED] wrote:



















On each page of a GridView
(Wicket Extensions 1.2) the elements enter the grid in row-order, from top to
bottom. Is there a way to have the DataProvider populate the grid in column-order – filling
one column from top to bottom before moving onto the next column to the right?



If not, maybe this could be considered a
feature request.

Re: [Wicket-user] onkeydown or onkeyup

fixed, thanks-IgorOn 4/25/06, Davy De Durpel [EMAIL PROTECTED] wrote:
Hi,I finally managed to get my own search text field working but I think Imight have found a bug in one of the wicket examples.The problem is related to the behavior of the 'onkeydown' event.Whenever I
press a key, only the previous key presses are submitted and not the currentone.(ex. when my field contains 'dumm' and I press the 'y' then only'dumm' will be submitted)This seems to be the default behaviour of (all?)
browsers because the onkeydown event allows you to cancel a keypress, sothat in that case your field isn't updated.This means that I should usethe 'onkeyup' event.In that case everything works as it should.
But the 'Ajax - BuiltIn - Form' example uses the 'onkeydown' event.You canclearly see the problem when you enter something in the 'Email' field.Themessage that is displayed in the FeedBackPanel never displays the last
character that has been entered.Replacing it with the 'onkeyup' event should fix it.byeee...--View this message in context: 
http://www.nabble.com/onkeydown-or-onkeyup-t1506344.html#a4085010Sent from the Wicket - User forum at Nabble.com.---
Using Tomcat but need to do more? Need to support web services, security?Get stuff done quickly with pre-integrated technology to make your job easierDownload IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___
Wicket-user mailing listWicket-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wicket-user

[Wicket-user] when to initialize a ListChoice model

I have a page that has several ListChoices and their model lists are reloaded on every page view. I need to initialize the lists before any events are processed, because the AbstractSingleSelectChoice.convertValue requires the model list to be non null. 
I want to dereference the model list in the onDetach callback, not to hold the data in the session, and the list needs to be reloaded the next time anyhow. Which callback should I use for the purpose? - onAttach is called after events are processed.
Thanks,Yuri

Re: [Wicket-user] when to initialize a ListChoice model

use a detachable model. look into LoadableDetachableModel, that one might be the easiest to use in this usecase.-IgorOn 4/25/06, Yuri Magrisso
 [EMAIL PROTECTED] wrote:
I have a page that has several ListChoices and their model lists are reloaded on every page view. I need to initialize the lists before any events are processed, because the AbstractSingleSelectChoice.convertValue requires the model list to be non null. 
I want to dereference the model list in the onDetach callback, not to hold the data in the session, and the list needs to be reloaded the next time anyhow. Which callback should I use for the purpose? - onAttach is called after events are processed.
Thanks,Yuri

Re: [Wicket-user] onkeydown or onkeyup

just a remark: what happens if i hold down the key?i do get this then:dummyyy(there is no key up..)On 4/25/06, 
Igor Vaynberg [EMAIL PROTECTED] wrote:
fixed, thanks-Igor
On 4/25/06, Davy De Durpel [EMAIL PROTECTED] wrote:

Hi,I finally managed to get my own search text field working but I think Imight have found a bug in one of the wicket examples.The problem is related to the behavior of the 'onkeydown' event.Whenever I
press a key, only the previous key presses are submitted and not the currentone.(ex. when my field contains 'dumm' and I press the 'y' then only'dumm' will be submitted)This seems to be the default behaviour of (all?)
browsers because the onkeydown event allows you to cancel a keypress, sothat in that case your field isn't updated.This means that I should usethe 'onkeyup' event.In that case everything works as it should.
But the 'Ajax - BuiltIn - Form' example uses the 'onkeydown' event.You canclearly see the problem when you enter something in the 'Email' field.Themessage that is displayed in the FeedBackPanel never displays the last
character that has been entered.Replacing it with the 'onkeyup' event should fix it.byeee...--View this message in context: 

http://www.nabble.com/onkeydown-or-onkeyup-t1506344.html#a4085010Sent from the Wicket - User forum at Nabble.com
.---
Using Tomcat but need to do more? Need to support web services, security?Get stuff done quickly with pre-integrated technology to make your job easierDownload IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing listWicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

[Wicket-user] RE: Removing a Validator

2006-04-25 Thread Andrew Strickland




My first thought was the component would have a Map of validators that you storeby a validator name...that way you could add or remove like remove( IValidator.getName() )...also that way you could never end up with more than one of the same type of Validator on any given component.

AndyHow would you remove the validator? Would you do it by index or by instance?Its not very clean either way. Check out IFormValidator, I think it fitsyour usecase better then an IValidator.-IgorOn 4/25/06, Andrew Strickland [EMAIL PROTECTED] wrote: Was the capability added in 1.2 to remove Validators from a component? I=f not, are there any plans to add such a capability? When doing dynamic forms it is a huge convenience to be able to add and remove validators based on a user selection on another field in the form. An example: on my project some fields are required or not depending on th=e classification of the system. During account creation the user has the ability to choose which classification they are requesting their account =be created for. If they choose the more restrictive classification and then change their mind and switch to the less restrictive some of the fields t=hat I added a validator to will now STILL have the RequiredValidator even tho=ugh it is no longer a required field, and I have no way of removing the validator. Andy

[Wicket-user] Ajax field level validation

2006-04-25 Thread Jeff Lin

I was wondering if there is a good Wicket example of field level  
validation. I am currently using the regular feedback panel for  
validation and messages, but I would rather do onBlur() validation  
that marks the field and focusses the cursor on the invalid field.  
Does wicket have any of these capabilities built in? Are there any  
good examples of this?


Thanks in advance,
Jeff



---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] button as a link with additional onClick

protected String getOnClickScript() { String wicketScript=super.getOnClickScript(); return if (!alert('blah')) return false; +wicketScript;}-Igor
On 4/25/06, Rüdiger Schulz [EMAIL PROTECTED] wrote:
Hello all,I want to use a button which is specified by a Link in java. Thisworks fine, my onClik() method of the link is executed.Now I want to prepend a onClick-_javascript_, asking for confirmation
via window.confirm(), and not executing the Wicket generated_javascript_ if cancel is clicked.My problem is, I don't get my _javascript_ prepended.When I override getOnClickScript(), the Wicket-generated JS is
discarded.When I use an (Simple)AttributeModifier or AttributeAppender, my_javascript_ is put into another onClick attribute of the button tag,and it never gets executed.Is there a way to put my custom script before the Wicket script? Or
should I simply look for another solution (like an image linkor sth like that)?--greetings from Berlin,Rüdiger Schulz---Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easierDownload IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmdlnkkid0709bid3057dat1642___Wicket-user mailing listWicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] onkeydown or onkeyup

good, i think in this case we shouldnt make an ajax call until you release a key.-IgorOn 4/25/06, Johan Compagner 
[EMAIL PROTECTED] wrote:just a remark: what happens if i hold down the key?
i do get this then:dummyyy(there is no key up..)
On 4/25/06, 
Igor Vaynberg [EMAIL PROTECTED] wrote:

fixed, thanks-Igor
On 4/25/06, Davy De Durpel [EMAIL PROTECTED] wrote:


Hi,I finally managed to get my own search text field working but I think Imight have found a bug in one of the wicket examples.The problem is related to the behavior of the 'onkeydown' event.Whenever I
press a key, only the previous key presses are submitted and not the currentone.(ex. when my field contains 'dumm' and I press the 'y' then only'dumm' will be submitted)This seems to be the default behaviour of (all?)
browsers because the onkeydown event allows you to cancel a keypress, sothat in that case your field isn't updated.This means that I should usethe 'onkeyup' event.In that case everything works as it should.
But the 'Ajax - BuiltIn - Form' example uses the 'onkeydown' event.You canclearly see the problem when you enter something in the 'Email' field.Themessage that is displayed in the FeedBackPanel never displays the last
character that has been entered.Replacing it with the 'onkeyup' event should fix it.byeee...--View this message in context: 


http://www.nabble.com/onkeydown-or-onkeyup-t1506344.html#a4085010Sent from the Wicket - User forum at Nabble.com

.---
Using Tomcat but need to do more? Need to support web services, security?Get stuff done quickly with pre-integrated technology to make your job easierDownload IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing listWicket-user@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Ajax field level validation

the pieces are all there, its up to you to figure out how to put them together.if you want to highlight the field you need to add an attribute modifier that adds some css class if the component is invalid or highlights by other means
the ajax target can accept a _javascript_ that you want evaluated on the client side via addJavascript call, you can use that to focus on the invalid componentand then there are of course the ajaxified form component and form validating behaviors
you can package all the functionality above into your own behavior.hope this gets you started-IgorOn 4/25/06, Jeff Lin 
[EMAIL PROTECTED] wrote:I was wondering if there is a good Wicket example of field level
validation. I am currently using the regular feedback panel forvalidation and messages, but I would rather do onBlur() validationthat marks the field and focusses the cursor on the invalid field.Does wicket have any of these capabilities built in? Are there any
good examples of this?Thanks in advance,Jeff---Using Tomcat but need to do more? Need to support web services, security?Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimohttp://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___Wicket-user mailing listWicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] RE: Removing a Validator

but once you introduce the map you introduce the ambiguity of evaluation order as well and it makes things more complex to manage.also once you allow removal you alse need to allow insertion. it keeps getting messier and messier for the end user.
you can also potentially do what you want by overriding isrequired(), but you cannot then use the model of the component it depends on, only its input value.i think a IFormValidator which delegates to a few IValidator is the cleanest way to go, but thats just my two cents.
-IgorOn 4/25/06, Andrew Strickland [EMAIL PROTECTED] wrote:



My first thought was the component would have a Map of validators that you storeby a validator name...that way you could add or remove like remove( IValidator.getName() )...also that way you could never end up with more than one of the same type of Validator on any given component.


AndyHow would you remove the validator? Would you do it by index or by instance?Its not very clean either way. Check out IFormValidator, I think it fits
your usecase better then an IValidator.-IgorOn 4/25/06, Andrew Strickland 
[EMAIL PROTECTED] wrote: Was the capability added in 1.2 to remove Validators from a component? I=f
 not, are there any plans to add such a capability? When doing dynamic forms it is a huge convenience to be able to add and remove validators based on a user selection on another field in the form.
 An example: on my project some fields are required or not depending on th=e classification of the system. During account creation the user has the
 ability to choose which classification they are requesting their account =be created for. If they choose the more restrictive classification and then change their mind and switch to the less restrictive some of the fields t=
hat I added a validator to will now STILL have the RequiredValidator even tho=ugh it is no longer a required field, and I have no way of removing the
 validator. Andy

[Wicket-user] Re: AJAX: updating a label by klicking a check box

2006-04-25 Thread Stefan Lindner

Thank You Igor,

this works very well!

Stefan Lindner

--
Visionet GmbH, Am Weichselgarten 7, 91058 Erlangen
Tel.: (09131)691-230, FAX: (09131)691-111
E-Mail: mailto:[EMAIL PROTECTED], Internet:
http://www.visionet.de


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

[Wicket-user] when to initialize a ListChoice model

I have a page that has several ListChoices and their model lists are reloaded on every page view.I need to initialize the lists before any events are processed, because the AbstractSingleSelectChoice.convertValue requires the model list to be non null.
I want to dereference the model list in the onDetach callback, not to hold the data in the session, and the list needs to be reloaded the next time anyhow. Which callback should I use for the purpose? - onAttach is called after events are processed.
Thanks,Yuri

[Wicket-user] images sizes

2006-04-25 Thread Alexander Lohse


Hi,

I know this is slightly off-topic, but I wonder if anyone ever solved  
this:
I have a gallery application that takes a directory and reads out all  
the images.(Actually I use two directories, one for thumbnails and  
one for the hires version).
I use PopupSettings to open a new window with the appropriate size  
for the hires image.
As I am coming from PHP I am used to a very quick function-call to  
find the size of an image. In Java I have to read the whole image  
into memory, which takes very long in terms of request-time.


I tried Jimi/ImageIO and even Swing-ImageIcon.

e.g.

BufferedImage image = null;
try {
image = ImageIO.read(new File(localHiresPath.toString 
()));

} catch (IOException exc) {

}

   if (image != null) {

ImageModel model = new ImageModel();
model.setHeight(image.getHeight());
model.setWidth(image.getWidth());

}


Is there any better/fast way to achive this? Maybe some nice wicket  
functionality?


Thank you for any help.

Alex




---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

[Wicket-user] Free Maven2 book

2006-04-25 Thread Gwyn Evans

Just as an aside, if there's anyone out there who's interested in
Maven2, (which is the Wicket-standard build method), there's a very
useful free eBook available from
http://www.mergere.com/m2book_download.jsp

/Gwyn


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] proposal: internationalization project

2006-04-25 Thread Bruno Borges

Just tell me the directions and let me do pt_BR. :)Regards,Bruno BorgesOn 4/24/06, Eelco Hillenius 
[EMAIL PROTECTED] wrote:On 4/23/06, Iman Rahmatizadeh 
[EMAIL PROTECTED] wrote: I'm ready for Persian/Farsi (fa_IR). Just asking, would it be a good idea to let wicket automatically set the page direction (ltr or rtl) based on the locale ?
I have no experience with that, so I wouldn't know. Which is exactlywhy we should startup such a project :)Eelco Iman ---
 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1
 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/wicket-user---Using Tomcat but need to do more? Need to support web services, security?Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimohttp://sel.as-us.falkag.net/sel?cmdlnkkid0709bid3057dat1642
___Wicket-user mailing listWicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user-- Bruno Borges[EMAIL PROTECTED]Sun Certified Java Programmer for 
1.4Sun Certified Web Component Developer for 1.4

Re: [Wicket-user] when to initialize a ListChoice model

Thanks for the quick answer! That worked greatOn 4/25/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
use a detachable model. look into LoadableDetachableModel, that one might be the easiest to use in this usecase.
-IgorOn 4/25/06, 
Yuri Magrisso
 [EMAIL PROTECTED] wrote:

I have a page that has several ListChoices and their model lists are reloaded on every page view. I need to initialize the lists before any events are processed, because the AbstractSingleSelectChoice.convertValue requires the model list to be non null. 
I want to dereference the model list in the onDetach callback, not to hold the data in the session, and the list needs to be reloaded the next time anyhow. Which callback should I use for the purpose? - onAttach is called after events are processed.
Thanks,Yuri

[Wicket-user] Re: when to initialize a ListChoice model

sorry for the double postOn 4/25/06, Yuri Magrisso [EMAIL PROTECTED] wrote:
I have a page that has several ListChoices and their model lists are reloaded on every page view.I need to initialize the lists before any events are processed, because the AbstractSingleSelectChoice.convertValue
 requires the model list to be non null.
I want to dereference the model list in the onDetach callback, not to hold the data in the session, and the list needs to be reloaded the next time anyhow. Which callback should I use for the purpose? - onAttach is called after events are processed.
Thanks,Yuri

Re: [Wicket-user] images sizes

2006-04-25 Thread Timo Stamm


Alexander Lohse schrieb:
As I am coming from PHP I am used to a very quick function-call to find 
the size of an image. In Java I have to read the whole image into 
memory, which takes very long in terms of request-time.


You don't have to read the entire image. The dimensions are usually 
embedded in some meta-data section, so it is not necessary to decode the 
entire image just to get the dimensions.


This is how you get the dimensions from image files:

ImageInputStream i = ImageIO.createImageInputStream(new 
FileInputStream(file));

try {
   IteratorImageReader r = ImageIO.getImageReaders(i);
   if (r.hasNext()) {
  ImageReader reader = r.next();
  reader.setInput(i, true);
  width = reader.getWidth(0);
  height = reader.getHeight(0);
  formatName = reader.getFormatName().toLowerCase();
  reader.dispose();
   }
} finally {
   i.close();
}


HTH,
Timo


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

RE: [Wicket-user] RE: Removing a Validator

2006-04-25 Thread Roan O'Sullivan

Hi Igor, 
 
I have this same requirement, also in the context of dynamic forms. 
 
I think a simple #removeAllValidators() would do the trick without introducing 
ambiguity or any additional complexity. In v1.1.1 I end up reconstructing the 
component when, for example, I need to remove a TypeValidator. This can be a 
real pain. 
 
Haven't had a chance to check out IFormValidator, and it may do what I require. 
However, I don't see how a #removeAllValidators() could hurt either :).
 
Thanks, 
 
Roan



From: [EMAIL PROTECTED] on behalf of Igor Vaynberg
Sent: Tue 4/25/2006 2:09 PM
To: wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] RE: Removing a Validator


but once you introduce the map you introduce the ambiguity of evaluation order 
as well and it makes things more complex to manage.

also once you allow removal you alse need to allow insertion. it keeps getting 
messier and messier for the end user. 

you can also potentially do what you want by overriding isrequired(), but you 
cannot then use the model of the component it depends on, only its input value.

i think a IFormValidator which delegates to a few IValidator is the cleanest 
way to go, but thats just my two cents. 

-Igor



On 4/25/06, Andrew Strickland [EMAIL PROTECTED] wrote: 

My first thought was the component would have a Map of validators that 
you store by a validator name...that way you could add or remove like remove( 
IValidator.getName() )...also that way you could never end up with more than 
one of the same type of Validator on any given component. 
 
Andy


How would you remove the validator? Would you do it by index or by 
instance?
Its not very clean either way. Check out IFormValidator, I think it 
fits 
your usecase better then an IValidator.

-Igor


On 4/25/06, Andrew Strickland  [EMAIL PROTECTED] mailto:[EMAIL 
PROTECTED]  wrote:


 Was the capability added in 1.2 to remove Validators from a 
component?  I=
f

 not, are there any plans to add such a capability?

 When doing dynamic forms it is a huge convenience to be able to add 
and
 remove validators based on a user selection on another field in the 
form. 


 An example: on my project some fields are required or not depending 
on th=
e

 classification of the system.  During account creation the user has 
the 
 ability to choose which classification they are requesting their 
account =
be
 created for.  If they choose the more restrictive classification and 
then

 change their mind and switch to the less restrictive some of the 
fields t= 
hat
 I added a validator to will now STILL have the RequiredValidator even 
tho=
ugh

 it is no longer a required field, and I have no way of removing the 
 validator.

 Andy


winmail.dat

Re: [Wicket-user] RE: Removing a Validator

i get the feeling this is all revolving around requiredvalidator right?-IgorOn 4/25/06, Roan O'Sullivan 
[EMAIL PROTECTED] wrote:Hi Igor,I have this same requirement, also in the context of dynamic forms.
I think a simple #removeAllValidators() would do the trick without introducing ambiguity or any additional complexity. In v1.1.1 I end up reconstructing the component when, for example, I need to remove a TypeValidator. This can be a real pain.
Haven't had a chance to check out IFormValidator, and it may do what I require. However, I don't see how a #removeAllValidators() could hurt either :).Thanks,Roan
From: [EMAIL PROTECTED] on behalf of Igor VaynbergSent: Tue 4/25/2006 2:09 PMTo: 
wicket-user@lists.sourceforge.netSubject: Re: [Wicket-user] RE: Removing a Validatorbut once you introduce the map you introduce the ambiguity of evaluation order as well and it makes things more complex to manage.
also once you allow removal you alse need to allow insertion. it keeps getting messier and messier for the end user.you can also potentially do what you want by overriding isrequired(), but you cannot then use the model of the component it depends on, only its input value.
i think a IFormValidator which delegates to a few IValidator is the cleanest way to go, but thats just my two cents.-IgorOn 4/25/06, Andrew Strickland 
[EMAIL PROTECTED] wrote:My first thought was the component would have a Map of validators that you store by a validator name...that way you could add or remove like remove( IValidator.getName
() )...also that way you could never end up with more than one of the same type of Validator on any given component.AndyHow would you remove the validator? Would you do it by index or by instance?
Its not very clean either way. Check out IFormValidator, I think it fitsyour usecase better then an IValidator.-IgorOn 4/25/06, Andrew Strickland  
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]  wrote:
 Was the capability added in 1.2 to remove Validators from a component?I=f not, are there any plans to add such a capability? When doing dynamic forms it is a huge convenience to be able to add and
 remove validators based on a user selection on another field in the form. An example: on my project some fields are required or not depending on th=e
 classification of the system.During account creation the user has the ability to choose which classification they are requesting their account =be created for.If they choose the more restrictive classification and then
 change their mind and switch to the less restrictive some of the fields t=hat I added a validator to will now STILL have the RequiredValidator even tho=ugh
 it is no longer a required field, and I have no way of removing the validator. Andy

Re: [Wicket-user] RE: Removing a Validator

MyCompoundValidator compound = new MyCompoundValidatior();compound.add(XXXValidatior);compound.add(YYYValidator);compound.validate(){iterator.next().validate()}component.add(compound);
compound.remove(xxx);johanOn 4/25/06, Roan O'Sullivan [EMAIL PROTECTED]
 wrote:Hi Igor,I have this same requirement, also in the context of dynamic forms.
I think a simple #removeAllValidators() would do the trick without introducing ambiguity or any additional complexity. In v1.1.1 I end up reconstructing the component when, for example, I need to remove a TypeValidator. This can be a real pain.
Haven't had a chance to check out IFormValidator, and it may do what I require. However, I don't see how a #removeAllValidators() could hurt either :).Thanks,Roan
From: [EMAIL PROTECTED] on behalf of Igor VaynbergSent: Tue 4/25/2006 2:09 PMTo: 
wicket-user@lists.sourceforge.netSubject: Re: [Wicket-user] RE: Removing a Validatorbut once you introduce the map you introduce the ambiguity of evaluation order as well and it makes things more complex to manage.
also once you allow removal you alse need to allow insertion. it keeps getting messier and messier for the end user.you can also potentially do what you want by overriding isrequired(), but you cannot then use the model of the component it depends on, only its input value.
i think a IFormValidator which delegates to a few IValidator is the cleanest way to go, but thats just my two cents.-IgorOn 4/25/06, Andrew Strickland 
[EMAIL PROTECTED] wrote:My first thought was the component would have a Map of validators that you store by a validator name...that way you could add or remove like remove( IValidator.getName
() )...also that way you could never end up with more than one of the same type of Validator on any given component.AndyHow would you remove the validator? Would you do it by index or by instance?
Its not very clean either way. Check out IFormValidator, I think it fitsyour usecase better then an IValidator.-IgorOn 4/25/06, Andrew Strickland  
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]  wrote:
 Was the capability added in 1.2 to remove Validators from a component?I=f not, are there any plans to add such a capability? When doing dynamic forms it is a huge convenience to be able to add and
 remove validators based on a user selection on another field in the form. An example: on my project some fields are required or not depending on th=e
 classification of the system.During account creation the user has the ability to choose which classification they are requesting their account =be created for.If they choose the more restrictive classification and then
 change their mind and switch to the less restrictive some of the fields t=hat I added a validator to will now STILL have the RequiredValidator even tho=ugh
 it is no longer a required field, and I have no way of removing the validator. Andy

Re: [Wicket-user] RE: Removing a Validator

yep, there is certainly that.-IgorOn 4/25/06, Johan Compagner [EMAIL PROTECTED] wrote:
MyCompoundValidator compound = new MyCompoundValidatior();
compound.add(XXXValidatior);compound.add(YYYValidator);compound.validate(){iterator.next().validate()}component.add(compound);
compound.remove(xxx);johan
On 4/25/06, Roan O'Sullivan [EMAIL PROTECTED]
 wrote:
Hi Igor,I have this same requirement, also in the context of dynamic forms.
I think a simple #removeAllValidators() would do the trick without introducing ambiguity or any additional complexity. In v1.1.1 I end up reconstructing the component when, for example, I need to remove a TypeValidator. This can be a real pain.
Haven't had a chance to check out IFormValidator, and it may do what I require. However, I don't see how a #removeAllValidators() could hurt either :).Thanks,Roan
From: [EMAIL PROTECTED] on behalf of Igor VaynbergSent: Tue 4/25/2006 2:09 PM
To: 
wicket-user@lists.sourceforge.netSubject: Re: [Wicket-user] RE: Removing a Validatorbut once you introduce the map you introduce the ambiguity of evaluation order as well and it makes things more complex to manage.
also once you allow removal you alse need to allow insertion. it keeps getting messier and messier for the end user.you can also potentially do what you want by overriding isrequired(), but you cannot then use the model of the component it depends on, only its input value.
i think a IFormValidator which delegates to a few IValidator is the cleanest way to go, but thats just my two cents.-IgorOn 4/25/06, Andrew Strickland 

[EMAIL PROTECTED] wrote:My first thought was the component would have a Map of validators that you store by a validator name...that way you could add or remove like remove( IValidator.getName

() )...also that way you could never end up with more than one of the same type of Validator on any given component.AndyHow would you remove the validator? Would you do it by index or by instance?
Its not very clean either way. Check out IFormValidator, I think it fitsyour usecase better then an IValidator.-IgorOn 4/25/06, Andrew Strickland  
[EMAIL PROTECTED] mailto:
[EMAIL PROTECTED]  wrote:
 Was the capability added in 1.2 to remove Validators from a component?I=f not, are there any plans to add such a capability? When doing dynamic forms it is a huge convenience to be able to add and
 remove validators based on a user selection on another field in the form. An example: on my project some fields are required or not depending on th=e

 classification of the system.During account creation the user has the ability to choose which classification they are requesting their account =be created for.If they choose the more restrictive classification and then
 change their mind and switch to the less restrictive some of the fields t=hat I added a validator to will now STILL have the RequiredValidator even tho=ugh

 it is no longer a required field, and I have no way of removing the validator. Andy

RE: [Wicket-user] RE: Removing a Validator

2006-04-25 Thread Roan O'Sullivan

Not necessarily. TypeValidator, RequiredValidator, PatternValidator ... I may 
add any type of Validator, and then remove them (my workaround for the lack of 
support for removing validators in 1.1.1 is to instantiate an entirely new 
component) and add different ones in response to user events. 
 
- Roan



From: [EMAIL PROTECTED] on behalf of Igor Vaynberg
Sent: Tue 4/25/2006 5:29 PM
To: wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] RE: Removing a Validator


i get the feeling this is all revolving around requiredvalidator right?

-Igor



On 4/25/06, Roan O'Sullivan  [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]  
wrote: 

Hi Igor,

I have this same requirement, also in the context of dynamic forms. 

I think a simple #removeAllValidators() would do the trick without 
introducing ambiguity or any additional complexity. In v1.1.1 I end up 
reconstructing the component when, for example, I need to remove a 
TypeValidator. This can be a real pain. 

Haven't had a chance to check out IFormValidator, and it may do what I 
require. However, I don't see how a #removeAllValidators() could hurt either :).

Thanks,

Roan

 

From: [EMAIL PROTECTED] on behalf of Igor Vaynberg
Sent: Tue 4/25/2006 2:09 PM
To: wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] RE: Removing a Validator


but once you introduce the map you introduce the ambiguity of 
evaluation order as well and it makes things more complex to manage. 

also once you allow removal you alse need to allow insertion. it keeps 
getting messier and messier for the end user.

you can also potentially do what you want by overriding isrequired(), 
but you cannot then use the model of the component it depends on, only its 
input value. 

i think a IFormValidator which delegates to a few IValidator is the 
cleanest way to go, but thats just my two cents.

-Igor



On 4/25/06, Andrew Strickland  [EMAIL PROTECTED] mailto:[EMAIL 
PROTECTED]  wrote:

My first thought was the component would have a Map of 
validators that you store by a validator name...that way you could add or 
remove like remove( IValidator.getName () )...also that way you could never end 
up with more than one of the same type of Validator on any given component.

Andy


How would you remove the validator? Would you do it by index 
or by instance? 
Its not very clean either way. Check out IFormValidator, I 
think it fits
your usecase better then an IValidator.

-Igor


On 4/25/06, Andrew Strickland  [EMAIL PROTECTED] 
mailto:[EMAIL PROTECTED]  wrote:


 Was the capability added in 1.2 to remove Validators from a 
component?  I=
f

 not, are there any plans to add such a capability?

 When doing dynamic forms it is a huge convenience to be able 
to add and 
 remove validators based on a user selection on another field 
in the form.


 An example: on my project some fields are required or not 
depending on th=
e

 classification of the system.  During account creation the 
user has the
 ability to choose which classification they are requesting 
their account =
be
 created for.  If they choose the more restrictive 
classification and then 

 change their mind and switch to the less restrictive some of 
the fields t=
hat
 I added a validator to will now STILL have the 
RequiredValidator even tho=
ugh

 it is no longer a required field, and I have no way of 
removing the
 validator.

 Andy






winmail.dat

Re: [Wicket-user] images sizes

2006-04-25 Thread Alexander Lohse


Hi Timo,

thank you very much. This was exactly what I needed! :-)

Alex


Alexander Lohse schrieb:
As I am coming from PHP I am used to a very quick function-call to  
find the size of an image. In Java I have to read the whole image  
into memory, which takes very long in terms of request-time.


You don't have to read the entire image. The dimensions are usually  
embedded in some meta-data section, so it is not necessary to  
decode the entire image just to get the dimensions.


This is how you get the dimensions from image files:

ImageInputStream i = ImageIO.createImageInputStream(new  
FileInputStream(file));

try {
   IteratorImageReader r = ImageIO.getImageReaders(i);
   if (r.hasNext()) {
  ImageReader reader = r.next();
  reader.setInput(i, true);
  width = reader.getWidth(0);
  height = reader.getHeight(0);
  formatName = reader.getFormatName().toLowerCase();
  reader.dispose();
   }
} finally {
   i.close();
}


HTH,
Timo





---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] RE: Removing a Validator

Type and Required validators are gone in 1.2they are now just setType() and setRequired() johanOn 4/25/06, Roan O'Sullivan 
[EMAIL PROTECTED] wrote:Not necessarily. TypeValidator, RequiredValidator, PatternValidator ... I may add any type of Validator, and then remove them (my workaround for the lack of support for removing validators in 
1.1.1 is to instantiate an entirely new component) and add different ones in response to user events.- RoanFrom: 
[EMAIL PROTECTED] on behalf of Igor VaynbergSent: Tue 4/25/2006 5:29 PMTo: wicket-user@lists.sourceforge.netSubject: Re: [Wicket-user] RE: Removing a Validator
i get the feeling this is all revolving around requiredvalidator right?-IgorOn 4/25/06, Roan O'Sullivan  [EMAIL PROTECTED]
 mailto:[EMAIL PROTECTED]  wrote:Hi Igor,I have this same requirement, also in the context of dynamic forms.
I think a simple #removeAllValidators() would do the trick without introducing ambiguity or any additional complexity. In v1.1.1 I end up reconstructing the component when, for example, I need to remove a TypeValidator. This can be a real pain.
Haven't had a chance to check out IFormValidator, and it may do what I require. However, I don't see how a #removeAllValidators() could hurt either :).Thanks,Roan
From: [EMAIL PROTECTED] on behalf of Igor VaynbergSent: Tue 4/25/2006 2:09 PMTo: 
wicket-user@lists.sourceforge.netSubject: Re: [Wicket-user] RE: Removing a Validatorbut once you introduce the map you introduce the ambiguity of evaluation order as well and it makes things more complex to manage.
also once you allow removal you alse need to allow insertion. it keeps getting messier and messier for the end user.you can also potentially do what you want by overriding isrequired(), but you cannot then use the model of the component it depends on, only its input value.
i think a IFormValidator which delegates to a few IValidator is the cleanest way to go, but thats just my two cents.-IgorOn 4/25/06, Andrew Strickland  
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]  wrote:My first thought was the component would have a Map of validators that you store by a validator name...that way you could add or remove like remove( 
IValidator.getName () )...also that way you could never end up with more than one of the same type of Validator on any given component.AndyHow would you remove the validator? Would you do it by index or by instance?
Its not very clean either way. Check out IFormValidator, I think it fitsyour usecase better then an IValidator.-IgorOn 4/25/06, Andrew Strickland  
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]  wrote:
 Was the capability added in 1.2 to remove Validators from a component?I=f not, are there any plans to add such a capability?
 When doing dynamic forms it is a huge convenience to be able to add and remove validators based on a user selection on another field in the form.
 An example: on my project some fields are required or not depending on th=e classification of the system.During account creation the user has the
 ability to choose which classification they are requesting their account =be created for.If they choose the more restrictive classification and then
 change their mind and switch to the less restrictive some of the fields t=hat I added a validator to will now STILL have the RequiredValidator even tho=
ugh it is no longer a required field, and I have no way of removing the validator. Andy

[Wicket-user] Howto override destroy() in WebApplication class???

2006-04-25 Thread Marty Backe

I've decided to build a project at work, based on Wicket. So no doubt this
is a newbie question. Any help would be appreciated. Hopefully it's a
simple question to answer.

In my WebApplication based class, I setup my database, etc. in the init()
method. I'd like to shutdown the database when the servlet is destroyed
(I'm deploying in Tomcat), so my first thought would be to override
destroy(), but this isn't an available method of WebApplication.

What's the recommended approach?

Along the same lines, I had also wanted to throw a ServletException if I
couldn't setup the database in init(), but that's not available to me
either.


Thanks much for any guidance.

Marty Backe







---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Howto override destroy() in WebApplication class???

i just checked in a destroy() method you can override on the application.as far as the servletexception i dont think this is proper to throw from the application because application is not a servlet. who is to say application is even backed by a servlet.
-IgorOn 4/25/06, Marty Backe [EMAIL PROTECTED] wrote:
I've decided to build a project at work, based on Wicket. So no doubt thisis a newbie question. Any help would be appreciated. Hopefully it's asimple question to answer.In my WebApplication based class, I setup my database, etc. in the init()
method. I'd like to shutdown the database when the servlet is destroyed(I'm deploying in Tomcat), so my first thought would be to overridedestroy(), but this isn't an available method of WebApplication.
What's the recommended approach?Along the same lines, I had also wanted to throw a ServletException if Icouldn't setup the database in init(), but that's not available to meeither.Thanks much for any guidance.
Marty Backe---Using Tomcat but need to do more? Need to support web services, security?Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimohttp://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___Wicket-user mailing listWicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Howto override destroy() in WebApplication class???

2006-04-25 Thread Marty Backe


Thanks for the quick reply.

Regarding the Exception. What would be the recommended approach for 
cases where init() is not able to complete successfully? In my case 
init() might fail because the database can't be started (bad 
configuration, etc.). With a Servlet I can throw a ServletException and 
the container (Tomcat) will stop the application. What should a 
WebApplication do?



Thanks,

Marty

Igor Vaynberg wrote:

i just checked in a destroy() method you can override on the application.

as far as the servletexception i dont think this is proper to throw 
from the application because application is not a servlet. who is to 
say application is even backed by a servlet.


-Igor


On 4/25/06, *Marty Backe* [EMAIL PROTECTED] 
mailto:[EMAIL PROTECTED] wrote:


I've decided to build a project at work, based on Wicket. So no
doubt this
is a newbie question. Any help would be appreciated. Hopefully it's a
simple question to answer.

In my WebApplication based class, I setup my database, etc. in the
init()
method. I'd like to shutdown the database when the servlet is
destroyed
(I'm deploying in Tomcat), so my first thought would be to override
destroy(), but this isn't an available method of WebApplication.

What's the recommended approach?

Along the same lines, I had also wanted to throw a
ServletException if I
couldn't setup the database in init(), but that's not available to me
either.


Thanks much for any guidance.

Marty Backe







---
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your
job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
mailto:Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user





--


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Howto override destroy() in WebApplication class???

tomcat will also stop the application if a runtimeexception is thrown from servlet's init. so you can just throw any runtime exception and you are set.-IgorOn 4/25/06,
Marty Backe [EMAIL PROTECTED] wrote:
Thanks for the quick reply.Regarding the Exception. What would be the recommended approach forcases where init() is not able to complete successfully? In my caseinit() might fail because the database can't be started (bad
configuration, etc.). With a Servlet I can throw a ServletException andthe container (Tomcat) will stop the application. What should aWebApplication do?Thanks,MartyIgor Vaynberg wrote:
i just checked in a destroy() method you can override on the application. as far as the servletexception i dont think this is proper to throw from the application because application is not a servlet. who is to
say application is even backed by a servlet. -Igor On 4/25/06, *Marty Backe* [EMAIL PROTECTED] mailto:
[EMAIL PROTECTED] wrote: I've decided to build a project at work, based on Wicket. So no doubt this is a newbie question. Any help would be appreciated. Hopefully it's a
simple question to answer. In my WebApplication based class, I setup my database, etc. in the init() method. I'd like to shutdown the database when the servlet is
destroyed (I'm deploying in Tomcat), so my first thought would be to override destroy(), but this isn't an available method of WebApplication. What's the recommended approach?
Along the same lines, I had also wanted to throw a ServletException if I couldn't setup the database in init(), but that's not available to me either.
Thanks much for any guidance. Marty Backe --- Using Tomcat but need to do more? Need to support web services,
security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list
Wicket-user@lists.sourceforge.net mailto:Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user-Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easierDownload IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___Wicket-user mailing list
Wicket-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wicket-user

[Wicket-user] Any news on JSR-168 portlet support?

2006-04-25 Thread Vince Marco

I haven't been actively following this mailing list and I'm a bit  
confused about JSR-168 support.  The 1.2 documentation lists JSR-168  
support, but I see some evidence (or a lack of evidence) that it is  
in the RC2.  Is it being yanked from 1.2?


Vince



---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Any news on JSR-168 portlet support?

yeah, we are yanking it. martijn can you update our roadmap please. maybe 2.0 will have it.the main block is that none of the core developer team are familiar/have any experience with the spec. so if you or anyone else wants to help in this area we would welcome the support. otherwise it will have to wait until one of us has the time to learn the spec.
-IgorOn 4/25/06, Vince Marco [EMAIL PROTECTED] wrote:
I haven't been actively following this mailing list and I'm a bitconfused about JSR-168 support.The 1.2 documentation lists JSR-168support, but I see some evidence (or a lack of evidence) that it isin the RC2.Is it being yanked from 
1.2?Vince---Using Tomcat but need to do more? Need to support web services, security?Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimohttp://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___Wicket-user mailing listWicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

[Wicket-user] Wicket design questions

2006-04-25 Thread Aaron Hiniker





I am just curious,

Why was it chosen to pass the ID to the constructor of a component vs the add() method of the container??

ie: 

// doesn't this make the MyComponent code less-cohesive to the heirarchy?
container.add( myComponentID, new MyComponent( new MyModel() ) ); 

This seems cleaner to me as the component should not need to be aware of how it's being wired to the heirarchy, and passing the id to the constructor now requires us to construct all of our components with an ID, when the ID is only used (from the end-user's point-of-view) in referencing the component within the heirarchy. Having to implement default constructors to satisfy the ID gets tedious.. and then when you start to nest components together, you end up hitting walls (well, I have since I'm new to Wicket):



//*** component A ***//

wicket:panel
 span wicket:id=listOfB
 Here is a ComponentB: span wicket:id=componentB/br/
 /span
/wicket:panel


ComponentA extends Panel
{
 public ComponentA( String id, List ComponentB  list )
 {
	super( id );
	add( new ListView( listOfB, list ) )
	{
 	public void populateItem( ListItem item )
		{
			item.add( (Component)item.getModelObject() );
		}
	}
 ... 
 }
}



//*** component B ***//

wicket:panel
	This is a component!
/wicket:panel

ComponentB extends Panel
{
 public ComponentB( String id )
 {
 super( id );
 }
}


Now, to wire it all together: we would do:


// MyPage //

ComponentB[] components = new ComponentB[] { new ComponentB( componentB ), new ComponentB( componentB ) };
ComponentA compA = new ComponentA( componentA, Arrays.toList( components ) );
add( compA );





As you can see, if build your components in this manner (passing components to another component), you must make sure you get the ID name correct, when really ComponentB should be wired into the heirarchy by ComponentA. 
You *could* hardcode super( componentB ) into ComponentB's constructor, but now if you want to use ComponentB somewhere else, you are forced to use componentB in your markup.

Using a different technique, we could do this:





//*** component A ***//

wicket:panel
 span wicket:id=listOfB
 Here is a ComponentB: span wicket:id=componentB/
 /span
/wicket:panel


ComponentA extends Panel
{
 public ComponentA( List ComponentB  list )
 {
	add( listOfB, new ListView( list ) )
	{
 	public void populateItem( ListItem item )
		{
			item.add( componentB, (Component)item.getModelObject() );
		}
	}
 ... 
 }
}




//*** component B ***//

wicket:panel
	This is a component!
/wicket:panel

ComponentB extends Panel
{
 // we don't need to call the default constructor anymore!! (unless we want to pass IModel)
}


Now, to wire it all together: we would do:


//*** MyPage //

ComponentB[] components = new ComponentB[] { new ComponentB(), new ComponentB() };
ComponentA compA = new ComponentA( Arrays.toList( components ) );
add( componentA, compA );



So am I even approaching this problem correctly? Is there good reason to construct components with an ID rather than specify the ID in container.add() ??

Re: [Wicket-user] Wicket design questions

you are not approaching the problem properly, at least not from compositing perspective. you would not create arrays of components to populate the listview, you would forward the listview's abstract callback to the panel, after all what if the listview is pageable?
abstract ComponentA extends Panel{ public ComponentA( String id ) {	super( id );	add( new ListView( listOfB, list ) )	{
 	public void populateItem( ListItem item )		{			populateMyItem(item, componentB);		}	} ...  }
protected abstract populateMyItem(ListItem item, String componentId);}ComponentA a=new ComponentA(a) {
 populateMyItem(ListItem item, String componentId) { add(new ComponentB(componentId));
 }};
add(a);in 1.3 we will remove the add() call and require the parent in the constructor next to id instead - might seem even more inconvinient from your pov. this will give us a lot more features such as:
components will have access to their attributes/markup in the constructorline precise errors for hierarchy inconsistencies at component creation time instead of render timeand a lot more, there was a long discussion on this or the devel list a while back if you want to dig around.
-Igor

Re: [Wicket-user] Question about localizing strings with .properties files

2006-04-25 Thread Ari Suutari


Hi,


What i (and presumably Ari) wanted tried to achieve, is to have some
style-specific bundle wich only contains some keys with style-specific
values and thus not having to maintain a bunch of property files if we
add another key, eventhough it's value would be the same across all styles.

But since this behaviour is *not* how java usually deals with
.properties, i'm not sure if this is a bug.


   I think that this is the way how java handles ResourceBundles: lookup
   falls back to parent bundle if key is not found. Because of this I assumed
   that wicket's .properties would work same way.

   Ari S.



---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

[Wicket-user] wicket hangs in Session.getPage (causes tomcat to run out of threads !)

2006-04-25 Thread Ari Suutari


Hi,

We have been preparing one part of our wicket application to production use. 
In testing there have been multple cases where whole application stops working and
I think that we have now isolated to reason for this. 


One of my collegues noticed that there is a message on tomcat's log file:

Apr 22, 2006 9:00:01 PM org.apache.tomcat.util.threads.ThreadPool logFull
SEVERE: All threads (150) are currently busy, waiting. Increase 
maxThreads (150) or check the servlet status


As 150 should be more than enough for current environment, he did some further
research on issue, which shows that problem is related to case where end-user
clicks a link on page before the page has completely rendered (users just do
it and I think that it cannot be changed :-). 


When a link is clicked on page which hasn't fully rendered yet, following 
exception occurs:

java.lang.NullPointerException
at wicket.PageMap.removeEntry(PageMap.java:335)
at wicket.PageMap.access(PageMap.java:628)
at wicket.PageMap.get(PageMap.java:459)
at wicket.Session.getPage(Session.java:395)
at 
wicket.request.compound.DefaultRequestTargetResolverStrategy.resolveRenderedPage(DefaultRequestTargetResolverStrategy.java:149)
at 
wicket.request.compound.DefaultRequestTargetResolverStrategy.resolve(DefaultRequestTargetResolverStrategy.java:92)
at 
wicket.request.compound.AbstractCompoundRequestCycleProcessor.resolve(AbstractCompoundRequestCycleProcessor.java:48)
at wicket.RequestCycle.step(RequestCycle.java:942)
at wicket.RequestCycle.steps(RequestCycle.java:1034)
at wicket.RequestCycle.request(RequestCycle.java:453)
at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:215)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)


This wouldn't be a problem otherwise, but it seems that wicket does not recover
from this situation, as the thread in tomcat is left waiting for like this:

Name: http-80-Processor22
State: WAITING on [EMAIL PROTECTED]
Total blocked: 7  Total waited: 5

Stack trace: 
java.lang.Object.wait(Native Method)

java.lang.Object.wait(Object.java:474)
wicket.Session.getPage(Session.java:386)
wicket.request.compound.DefaultRequestTargetResolverStrategy.resolveRenderedPage(DefaultRequestTargetResolverStrategy.java:149)
wicket.request.compound.DefaultRequestTargetResolverStrategy.resolve(DefaultRequestTargetResolverStrategy.java:92)
wicket.request.compound.AbstractCompoundRequestCycleProcessor.resolve(AbstractCompoundRequestCycleProcessor.java:48)
wicket.RequestCycle.step(RequestCycle.java:942)
wicket.RequestCycle.steps(RequestCycle.java:1034)
wicket.RequestCycle.request(RequestCycle.java:453)
wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:215)
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

The thread just sits there forever so tomcat creates a new thread to serve next 
thread and
if the user does similar things again we run out of threads.

This is occurring on wicket 1.2 rc2 and it is rather serious issue for us since 
I cannot figure any workaround for this.


   Ari S.



---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] wicket hangs in Session.getPage (causes tomcat to run out of threads !)