Re: [Wicket-user] header contribution ordering
I don't know if you still follow this thread. Maybe you're waiting for an alert. That's why I reply to one of your mails so that you are notified about the propose solution further down the thread. -- View this message in context: http://www.nabble.com/header-contribution-ordering-t1768566.html#a4896202 Sent from the Wicket - User forum at Nabble.com. ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] header contribution ordering
Well no. It would only solve my problem. How selfish of me to propose something like that ;-) I felt so sorry this morning that I have searched for a real solution to Michaels problem, and guess what I found it. All that needs to be done is add something similar to this at the end of the child page constructor: add(HeaderContributor.forCss(MyChildPage.class, MyChildCSS.css)); I have tested it and the result is that the link to MyChildCSS.css is the very last item in the head of the rendered page. And it even can be used to solve my case :-) The limitation is that it only works for Wicket 1.2. It should also be possible for the other versions but then Michael should have a look at Eelco's blog about header contributions: http://chillenious.wordpress.com/2006/05/03/wicket-header-contributions-with-behaviors/ -- View this message in context: http://www.nabble.com/header-contribution-ordering-t1768566.html#a4878920 Sent from the Wicket - User forum at Nabble.com. ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] header contribution ordering
I ran into a similar problem and my workaround was to use the id attribute for overwriting a style.But that is not a clean solution since it makes the CSS files very hard to read and you don't always have full control of the id attribute value. Maybe we need an extra optional wicket tag to indicate the position where we want the wicket:head stuff to be inserted. That way we can link our stylesheet after this tag so that we can easily overwrite any style of any of the children. So this would be something like: html head title wicket:id=titleMy Template/title wicket:headers/ link href=/myStyle.css type=text/css rel=stylesheet/ /head /html -- View this message in context: http://www.nabble.com/header-contribution-ordering-t1768566.html#a4867200 Sent from the Wicket - User forum at Nabble.com. ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] EJB3 Lazy Loading (was Seam-like solution for Wicket + EJB3?)
We have planned to look at this issue because we also want to use a pure EJB3 implementation. But there are some other issues with the EJB3 specification that makes it almost useless for production applications: - it does not have a simple solution for value converters, so converting for instance a DB char to a Java boolean cannot be done out of the box. - the EJBQL language does not even implement the complete SQL99 standard. One of the important things it misses is a join on sub queries. The solution to this issue might be to use an extended persistence context. Somewhere you must be able to set the PersistenceContextType to EXTENDED. In that case the Entity Beans are not detached when the transaction is closed. You should read chaper 3.3 and chapter 5.7 of the 'Enterprise JavaBeans 3.0, Final Release specification' for more information. I don't have any experience with it so I'm not sure if it has some drawbacks that makes it useless in a Wicket world. -- View this message in context: http://www.nabble.com/EJB3+Lazy+Loading+%28was+%22Seam-like+solution+for+Wicket+%2B+EJB3-%22%29-t1715549.html#a4659930 Sent from the Wicket - User forum at Nabble.com. --- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnkkid=107521bid=248729dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] onkeydown or onkeyup
Hi, In fact we should never do an ajax submit on the 'onkeydown' event. 'onkeydown' is a typical event that is only very usefull on the client and I think that it's main purpose was to allow the cancellation of a key stroke. You can interprete it more like a 'beforekey' event. I don't think there is a usecase where you really want to use the onkeydown event, except maybe in the event that you want to hold down your key and that each character is submitted to the server. But then I think that this should never be allowed because somebody might just bring your server down. But if you really want to support the onkeydown event then it should be done the way it is done in wicket.extensions.ajax.markup.html.autocomplete.wicket-autocomplete.js. in there the value of the field is retrieved by using it's ID and not by passing a reference. In that case it seems that all characters are sent to the server even when using the 'onkeydown' event. But this behaviour could not be the same on all browsers. (I only tested it with Firefox) Byeee... -- View this message in context: http://www.nabble.com/onkeydown-or-onkeyup-t1506344.html#a4097293 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
[Wicket-user] ajax behavior NotSerializable exception
Hi,
I'm currently developing an ajax search text field that updates a DataView.
I have encountered 2 blocking issues which, I think, might be bugs, but it
could also just be me doing something wrong ;-) (I have created 2 separate
messages)
Following code causes a NotSerializable exception:
AjaxFormComponentUpdatingBehavior ajaxBehavior = new
AjaxFormComponentUpdatingBehavior(onkeydown) {
private static final long serialVersionUID =
6734232774096304005L;
@Override
protected void onUpdate(AjaxRequestTarget target) {
target.addComponent(myComponent);
}
};
ajaxBehavior.setThrottleDelay(Duration.ONE_SECOND);
The problem is the 'setThrottleDelay' method. This method creates an
instance of the 'wicket.ajax.AjaxEventBehavior$ThrottlingSettings' class.
This inner class however is not serializable and I guess that when the
component is put on the session, Glassfish throws the NotSerializable
exception.
Byeee...
--
View this message in context:
http://www.nabble.com/ajax-behavior-NotSerializable-exception-t1504611.html#a4079785
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
[Wicket-user] onkeydown or onkeyup
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] immediate redirect?
In wicket 1.2 you just have to add this line of code: throw new RestartResponseAtInterceptPageException(YourFancyErrorPage.class); I'm not sure if this one will work with wicket version prior to 1.2, but then it might be worth the upgrade ;-) -- View this message in context: http://www.nabble.com/immediate-redirect--t1448808.html#a3915673 Sent from the Wicket - User forum at Nabble.com. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
[Wicket-user] DatePickerSettings not closing inputstream
Hi, Everytime I start my Wicket application, I see a warning in the Glassfish log file: Input stream has been finalized or forced closed without being explicitly closed; stream instantiation reported in following stack trace java.lang.Throwable at com.sun.enterprise.loader.EJBClassLoader$SentinelInputStream.init(EJBClassLoader.java:1096) at com.sun.enterprise.loader.EJBClassLoader$InternalJarURLConnection.getInputStream(EJBClassLoader.java:1189) at java.net.URL.openStream(URL.java:1007) at java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:1161) at com.sun.enterprise.loader.EJBClassLoader.getResourceAsStream(EJBClassLoader.java:755) at java.lang.Class.getResourceAsStream(Class.java:1998) at wicket.extensions.markup.html.datepicker.DatePickerSettings.clinit(DatePickerSettings.java:52) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:164) at wicket.extensions.markup.html.datepicker.DatePickerComponentInitializer.class$(DatePickerComponentInitializer.java:110) at wicket.extensions.markup.html.datepicker.DatePickerComponentInitializer.init(DatePickerComponentInitializer.java:130) at wicket.extensions.Initializer.init(Initializer.java:39) at wicket.Application.initialize(Application.java:653) at wicket.Application.initializeComponents(Application.java:718) at wicket.Application.initializeComponents(Application.java:695) at wicket.protocol.http.WicketServlet.init(WicketServlet.java:287) This exception seems to be related to the fact that the inputstream is not explicitly closed when reading the dateformats.properties file in the DatePickerSettings class. This is not a real bug but I like to have clean log files ;-) Byeee... -- View this message in context: http://www.nabble.com/DatePickerSettings-not-closing-inputstream-t1443016.html#a3896735 Sent from the Wicket - User forum at Nabble.com. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
