[Wicket-user] Pushing data to the Ajax client in wicket?
Hi there, I am trying to push out events that contain the moving locations of a users buddies, so I can update the GMap on the page using plain JS and the GMarkerManager. Right now I am using Pushlet for this, but that has the disadvantage that it is not integrated into Wicket, and it uses a generic broadcast mechanism, much like JMS subscribing to topics from JS. Is there any way to get this functionality working using Wicket, e.g. the GMap not being reloaded, just moving the markers on a pull/push interval? Thanks for any hints! /peter - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Pushing data to the Ajax client in wicket?
On 3/6/07, Peter Neubauer [EMAIL PROTECTED] wrote: Hi there, I am trying to push out events that contain the moving locations of a users buddies, so I can update the GMap on the page using plain JS and the GMarkerManager. Right now I am using Pushlet for this, but that has the disadvantage that it is not integrated into Wicket, and it uses a generic broadcast mechanism, much like JMS subscribing to topics from JS. Is there any way to get this functionality working using Wicket, e.g. the GMap not being reloaded, just moving the markers on a pull/push interval? Thanks for any hints! I'm also in need of such things, and I've started a thread about that last week: http://www.nabble.com/server-side-triggered-page-refresh-%28aka-push%29-tf3321420.html#a9234009 As you see I'd like to implement two ways to do that, one simple purely wicket based, and another more scalable requiring dojo. In your case I don't know much about your map, but with the implementation I propose you can send javascript as you would on an AjaxRequestTarget, so I guess it should be ok. I already have an first implementation (the simple one, pure wicket), but last time I checked it wasn't working due to a bug in wicket (see WICKET-343). But if you want I can share this implementation with you (I think I will even create an issue in JIRA with the patch attached, even if it doesn't work with the wicket 1.x branch right now). - Xavier /peter - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] RequestCycle ThreadLocal
Why is there no set methods on the request cycle like there is for session and application? Yes, that is an interesting point. Just grew like that I guess. But having a set method wouldn't really help your case, right? It would help, because I have a Request Cycle container that keeps track of the current cycle. And I would be able to do RequestCycle.set so that Wicket is able to access the RequestCycle itself too. Could the Wicket team change RequestCycle so that either: 1) There is a public or protected static set method in RequestCycle 2) Make the ThreadLocal current inside RequestCycle protected Robert - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
[Wicket-user] Is Wicket like one thick template engine?
I feel Wicket like one thick template engine? such as smarty,velocity with thick business layer. the page object is just like something in common template engine.. do you agree with me?.. -- View this message in context: http://www.nabble.com/Is-Wicket-like-one-thick-template-engine--tf3354355.html#a9328724 Sent from the Wicket - User mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] URL problem in phonebook app
* John Patterson: OK, but the phone-book app is still broken in 2.0 due to this bug in WicketFilter.isWicketRequest () - at least it was a week ago when I wrote the initial email. Can anyone get the current phonebook app to work? I think when that bug is fixed my app would have worked. But now I have reverted to 1.3 anyway... Hello John, Did you file a JIRA issue for this? -- Jean-Baptiste Quenot aka John Banana Qwerty http://caraldi.com/jbq/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Is Wicket like one thick template engine?
They are nothing alike. Wicket parses your HTML template into a Java object tree, then renders the page by recursively rendering the page root, calling each object. Velocity copies the template, then does variable substitution, more like a mail merge. Brian On Mar 6, 2007, at 1:31 AM, Steven Zou wrote: I feel Wicket like one thick template engine? such as smarty,velocity with thick business layer. the page object is just like something in common template engine.. do you agree with me?.. -- View this message in context: http://www.nabble.com/Is-Wicket-like- one-thick-template-engine--tf3354355.html#a9328724 Sent from the Wicket - User mailing list archive at Nabble.com. -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php? page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Pushing data to the Ajax client in wicket?
* Xavier Hanin: As you see I'd like to implement two ways to do that, one simple purely wicket based, and another more scalable requiring dojo. In your case I don't know much about your map, but with the implementation I propose you can send javascript as you would on an AjaxRequestTarget, so I guess it should be ok. I already have an first implementation (the simple one, pure wicket), but last time I checked it wasn't working due to a bug in wicket (see WICKET-343). But if you want I can share this implementation with you (I think I will even create an issue in JIRA with the patch attached, even if it doesn't work with the wicket 1.x branch right now). Hi Xavier, Yes please put it in JIRA and Link this issue mentioning it's blocked by WICKET-343. Cheers, -- Jean-Baptiste Quenot aka John Banana Qwerty http://caraldi.com/jbq/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Pushing data to the Ajax client in wicket?
Hi, If you are using plain js on client side, I think cometd is perfect to you. With cometd you can publish in a channel an event on server side (CometdPublisher - wicket-contrib-Dojo). On your client you subcribe to a channel(CometdBehavior - wcd too) and when datas are published on server side, a js method in triggered (client side). This js method is what you want so it can contain code to update your GMap. Take a look at www.cometd.org and http://weblogs.java.net/blog/jfarcand/archive/2007/02/gcometd_introdu_1.html and in Wicket-contrib-dojo sources : https://svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-contrib-dojo/. I started to integrate it in wicket-contrib-dojo (CometdBehavior, CometdPublisher). But it is still under developpement, any contributions are welcome ;) I don't know xavier's pushing implementation but it can also feet to you need ;) Cheers -- Vincent Demay http://www.demay-fr.net/blog/ Xavier Hanin a écrit : On 3/6/07, *Peter Neubauer* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi there, I am trying to push out events that contain the moving locations of a users buddies, so I can update the GMap on the page using plain JS and the GMarkerManager. Right now I am using Pushlet for this, but that has the disadvantage that it is not integrated into Wicket, and it uses a generic broadcast mechanism, much like JMS subscribing to topics from JS. Is there any way to get this functionality working using Wicket, e.g. the GMap not being reloaded, just moving the markers on a pull/push interval? Thanks for any hints! I'm also in need of such things, and I've started a thread about that last week: http://www.nabble.com/server-side-triggered-page-refresh-%28aka-push%29-tf3321420.html#a9234009 As you see I'd like to implement two ways to do that, one simple purely wicket based, and another more scalable requiring dojo. In your case I don't know much about your map, but with the implementation I propose you can send javascript as you would on an AjaxRequestTarget, so I guess it should be ok. I already have an first implementation (the simple one, pure wicket), but last time I checked it wasn't working due to a bug in wicket (see WICKET-343). But if you want I can share this implementation with you (I think I will even create an issue in JIRA with the patch attached, even if it doesn't work with the wicket 1.x branch right now). - Xavier /peter - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net mailto:Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Pushing data to the Ajax client in wicket?
On 3/6/07, Vincent Demay [EMAIL PROTECTED] wrote: Hi, If you are using plain js on client side, I think cometd is perfect to you. With cometd you can publish in a channel an event on server side (CometdPublisher - wicket-contrib-Dojo). On your client you subcribe to a channel(CometdBehavior - wcd too) and when datas are published on server side, a js method in triggered (client side). This js method is what you want so it can contain code to update your GMap. Take a look at www.cometd.org and http://weblogs.java.net/blog/jfarcand/archive/2007/02/gcometd_introdu_1.htmland in Wicket-contrib-dojo sources : https://svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-contrib-dojo/. I started to integrate it in wicket-contrib-dojo (CometdBehavior, CometdPublisher). But it is still under developpement, any contributions are welcome ;) I don't know xavier's pushing implementation but it can also feet to you need ;) My implementation is very simple and less efficient than cometd. It's actually the client which is polling the server at a regular interval. The only advantage over a pure javascript solution is that it's pretty well integrated with wicket, so that you don't have to worry much about the implementation. I also plan to provide a cometd implementation, based on your work in WCD. But I need time to work on that, and for the moment I have other priorities. But I will create an issue with my push implementation attached in a moment, so that you can see if it can be of any use for you. - Xavier Cheers -- Vincent Demay http://www.demay-fr.net/blog/ Xavier Hanin a écrit : On 3/6/07, Peter Neubauer [EMAIL PROTECTED] wrote: Hi there, I am trying to push out events that contain the moving locations of a users buddies, so I can update the GMap on the page using plain JS and the GMarkerManager. Right now I am using Pushlet for this, but that has the disadvantage that it is not integrated into Wicket, and it uses a generic broadcast mechanism, much like JMS subscribing to topics from JS. Is there any way to get this functionality working using Wicket, e.g. the GMap not being reloaded, just moving the markers on a pull/push interval? Thanks for any hints! I'm also in need of such things, and I've started a thread about that last week: http://www.nabble.com/server-side-triggered-page-refresh-%28aka-push%29-tf3321420.html#a9234009 As you see I'd like to implement two ways to do that, one simple purely wicket based, and another more scalable requiring dojo. In your case I don't know much about your map, but with the implementation I propose you can send javascript as you would on an AjaxRequestTarget, so I guess it should be ok. I already have an first implementation (the simple one, pure wicket), but last time I checked it wasn't working due to a bug in wicket (see WICKET-343). But if you want I can share this implementation with you (I think I will even create an issue in JIRA with the patch attached, even if it doesn't work with the wicket 1.x branch right now). - Xavier /peter - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash
Re: [Wicket-user] Error with 1.2.5 and Spring
Got the same error On 3/5/07, Matt Welch [EMAIL PROTECTED] wrote: I'm only just now upgrading to Wicket 1.2.5 and I've run into an issue. I'm certain this is an problem on my side and not a bug because other people would have run into this and reported by now and I can't find any reports like this on the mailing list. I'm using Maven. I switched my three wicket dependencies (wicket, wicket-spring, and wicket-spring-annot) from version 1.2.4 to 1.2.5 and I'm now receiving an error. Everything compiles fine in my code, but when I start up jetty I see: -- java.lang.Error: Unresolved compilation problems: The import wicket.injection.IFieldValueFactory cannot be resolved IFieldValueFactory cannot be resolved to a type factory cannot be resolved IFieldValueFactory cannot be resolved to a type factory cannot be resolved at wicket.spring.injection.annot.AnnotSpringInjector.init(AnnotSpringInjector.java:4) at wicket.spring.injection.annot.SpringComponentInjector.init(SpringComponentInjector.java:96) at wicket.spring.injection.annot.SpringComponentInjector.init(SpringComponentInjector.java:68) at com.ptc.fusion.web.FusionWebApplication.init(FusionWebApplication.java:55) at wicket.protocol.http.WicketServlet.init(WicketServlet.java:299) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:442) at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:259) at org.mortbay.component.AbstractLifeCycle.start (AbstractLifeCycle.java:40) at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:593) at org.mortbay.jetty.servlet.Context.startContext(Context.java:139) at org.mortbay.jetty.webapp.WebAppContext.startContext (WebAppContext.java:1191) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:481) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:434) at org.mortbay.component.AbstractLifeCycle.start (AbstractLifeCycle.java:40) at org.mortbay.jetty.plugin.Jetty6PluginWebApplication.start(Jetty6PluginWebApplication.java:147) at org.mortbay.jetty.plugin.AbstractJettyRunMojo$1.changesDetected(AbstractJettyRunMojo.java :372) at org.mortbay.jetty.plugin.util.Scanner.run(Scanner.java:159) -- If I remove the following line in my WebAppliciation.init() method, everything starts up fine: addComponentInstantiationListener(new SpringComponentInjector(this)); Of course, when remove that, I can no longer inject Spring beans with the @SpringBean annotation. I'm a little stuck here. If I switch back to 1.2.4, it's all fine again. Any ideas? Matt - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
[Wicket-user] The type org.slf4j.Logger cannot be resolved
Hi, I'm setting up my environment to start Wicket development. I'm using Wicket-2.0-Snapshot. I'm getting the error: The type org.slf4j.Logger cannot be resolved. Is there any library dependency I'm missing on my classpath? I have commons-logging and log4j on my path. -- Wicket is Wicked - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] The type org.slf4j.Logger cannot be resolved
Ok, I've found the dependent library and everything is fine now. On 3/6/07, Udora [EMAIL PROTECTED] wrote: Hi, I'm setting up my environment to start Wicket development. I'm using Wicket-2.0-Snapshot. I'm getting the error: The type org.slf4j.Loggercannot be resolved. Is there any library dependency I'm missing on my classpath? I have commons-logging and log4j on my path. -- Wicket is Wicked -- Wicket is Wicked - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Pushing data to the Ajax client in wicket?
On 3/6/07, Xavier Hanin [EMAIL PROTECTED] wrote: On 3/6/07, Vincent Demay [EMAIL PROTECTED] wrote: Hi, If you are using plain js on client side, I think cometd is perfect to you. With cometd you can publish in a channel an event on server side (CometdPublisher - wicket-contrib-Dojo). On your client you subcribe to a channel(CometdBehavior - wcd too) and when datas are published on server side, a js method in triggered (client side). This js method is what you want so it can contain code to update your GMap. Take a look at www.cometd.org and http://weblogs.java.net/blog/jfarcand/archive/2007/02/gcometd_introdu_1.html and in Wicket-contrib-dojo sources : https://svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-contrib-dojo/. I started to integrate it in wicket-contrib-dojo (CometdBehavior, CometdPublisher). But it is still under developpement, any contributions are welcome ;) I don't know xavier's pushing implementation but it can also feet to you need ;) My implementation is very simple and less efficient than cometd. It's actually the client which is polling the server at a regular interval. The only advantage over a pure javascript solution is that it's pretty well integrated with wicket, so that you don't have to worry much about the implementation. I also plan to provide a cometd implementation, based on your work in WCD. But I need time to work on that, and for the moment I have other priorities. But I will create an issue with my push implementation attached in a moment, so that you can see if it can be of any use for you. Issue with patch here : https://issues.apache.org/jira/browse/WICKET-363 It seems to work properly now on wicket-1.x branch, maybe the blocking bug was fixed this week-end. - Xavier - Xavier Cheers -- Vincent Demay http://www.demay-fr.net/blog/ Xavier Hanin a écrit : On 3/6/07, Peter Neubauer [EMAIL PROTECTED] wrote: Hi there, I am trying to push out events that contain the moving locations of a users buddies, so I can update the GMap on the page using plain JS and the GMarkerManager. Right now I am using Pushlet for this, but that has the disadvantage that it is not integrated into Wicket, and it uses a generic broadcast mechanism, much like JMS subscribing to topics from JS. Is there any way to get this functionality working using Wicket, e.g. the GMap not being reloaded, just moving the markers on a pull/push interval? Thanks for any hints! I'm also in need of such things, and I've started a thread about that last week: http://www.nabble.com/server-side-triggered-page-refresh-%28aka-push%29-tf3321420.html#a9234009 As you see I'd like to implement two ways to do that, one simple purely wicket based, and another more scalable requiring dojo. In your case I don't know much about your map, but with the implementation I propose you can send javascript as you would on an AjaxRequestTarget, so I guess it should be ok. I already have an first implementation (the simple one, pure wicket), but last time I checked it wasn't working due to a bug in wicket (see WICKET-343). But if you want I can share this implementation with you (I think I will even create an issue in JIRA with the patch attached, even if it doesn't work with the wicket 1.x branch right now). - Xavier /peter - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Error with 1.2.5 and Spring
I ran into this too a while back, logged under https://issues.apache.org/jira/browse/WICKET-304 The maven wicket-spring-annot build in 1.2.5 is corrupted, either back to 1.2.4, or build your own 1.2.5 (or like me, move to 1.3 snapshots, if that is feasible) Johan Mats Norén wrote: Got the same error On 3/5/07, Matt Welch [EMAIL PROTECTED] wrote: I'm only just now upgrading to Wicket 1.2.5 and I've run into an issue. I'm certain this is an problem on my side and not a bug because other people would have run into this and reported by now and I can't find any reports like this on the mailing list. I'm using Maven. I switched my three wicket dependencies (wicket, wicket-spring, and wicket-spring-annot) from version 1.2.4 to 1.2.5 and I'm now receiving an error. Everything compiles fine in my code, but when I start up jetty I see: -- java.lang.Error: Unresolved compilation problems: The import wicket.injection.IFieldValueFactory cannot be resolved IFieldValueFactory cannot be resolved to a type factory cannot be resolved IFieldValueFactory cannot be resolved to a type factory cannot be resolved at wicket.spring.injection.annot.AnnotSpringInjector.init(AnnotSpringInjector.java:4) at wicket.spring.injection.annot.SpringComponentInjector.init(SpringComponentInjector.java:96) at wicket.spring.injection.annot.SpringComponentInjector.init(SpringComponentInjector.java:68) at com.ptc.fusion.web.FusionWebApplication.init(FusionWebApplication.java:55) at wicket.protocol.http.WicketServlet.init(WicketServlet.java:299) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:442) at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:259) at org.mortbay.component.AbstractLifeCycle.start (AbstractLifeCycle.java:40) at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:593) at org.mortbay.jetty.servlet.Context.startContext(Context.java:139) at org.mortbay.jetty.webapp.WebAppContext.startContext (WebAppContext.java:1191) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:481) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:434) at org.mortbay.component.AbstractLifeCycle.start (AbstractLifeCycle.java:40) at org.mortbay.jetty.plugin.Jetty6PluginWebApplication.start(Jetty6PluginWebApplication.java:147) at org.mortbay.jetty.plugin.AbstractJettyRunMojo$1.changesDetected(AbstractJettyRunMojo.java :372) at org.mortbay.jetty.plugin.util.Scanner.run(Scanner.java:159) -- If I remove the following line in my WebAppliciation.init() method, everything starts up fine: addComponentInstantiationListener(new SpringComponentInjector(this)); Of course, when remove that, I can no longer inject Spring beans with the @SpringBean annotation. I'm a little stuck here. If I switch back to 1.2.4, it's all fine again. Any ideas? Matt - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
[Wicket-user] Change Request (Re: dynamically (client) created form components)
below is a suggestion by me on how to handle repeating components created by javascript, especially for the case where several fields are involved. would love to get a comment on it thanks, ittay Ittay Dror wrote: i think this can be solved inside wicket quite easily: * FormComponent.getInputAsArray uses 'getRequest().getParameters(getInputName())'. instead, it would be 'getParent().getRequestParameters(this, getInputName())', * the default implementation of getRequestParameters(Component, String) in Component will be getRequest().getParameters(getInputName()) * In the above case, when creating a ListView, use a subclass that modifies getRequestParameters() so it returns the parameters from the nth occurrence of the parameters (the nth 'atext=xxacb=yy' segment) then, form components can be used as they are. ittay -- View this message in context: http://www.nabble.com/dynamically-%28client%29-created-form-components-tf3325801.html#a9332092 Sent from the Wicket - User mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Is Wicket like one thick template engine?
That's about right. But I would say Wicket associates Java objects with your markup (template is really not a very good word here precisely because people think of Velocity or Freemarker, but also because there isn't one markup file... a Wicket page is quite commonly a complex, recursive merge of some number of markup files associated with the component hierarchy through some concept of aggregation (for example, Panels) or inheritance (for example, Markup Inheritance)). Brian Topping wrote: They are nothing alike. Wicket parses your HTML template into a Java object tree, then renders the page by recursively rendering the page root, calling each object. Velocity copies the template, then does variable substitution, more like a mail merge. Brian On Mar 6, 2007, at 1:31 AM, Steven Zou wrote: I feel Wicket like one thick template engine? such as smarty,velocity with thick business layer. the page object is just like something in common template engine.. do you agree with me?.. -- View this message in context: http://www.nabble.com/Is-Wicket-like- one-thick-template-engine--tf3354355.html#a9328724 Sent from the Wicket - User mailing list archive at Nabble.com. -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php? page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/Is-Wicket-like-one-thick-template-engine--tf3354355.html#a9332571 Sent from the Wicket - User mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] dynamically (client) created form components
i don't really (have the time right now to) fully understand this thread, but at the risk of saying something obvious, i wanted to point out that although wicket components in a listview don't have unique names, they do have unique /paths/ because their parent container is named with the row number. Ittay Dror wrote: Ittay Dror wrote: b. have all repeating elements have the same name. the problem is that components won't be updated correctly if some fields do not appear, or i'll need to modify getInputAsArray for each (so as to look in the query string, not the parsed parameters), and give each an index. i'm looking for a better way. i think this can be solved inside wicket quite easily: * FormComponent.getInputAsArray uses 'getRequest().getParameters(getInputName())'. instead, it would be 'getParent().getRequestParameters(this, getInputName())', * the default implementation of getRequestParameters(Component, String) in Component will be getRequest().getParameters(getInputName()) * In the above case, when creating a ListView, use a subclass that modifies getRequestParameters() so it returns the parameters from the nth occurrence of the parameters (the nth 'atext=xxacb=yy' segment) then, form components can be used as they are. ittay -- View this message in context: http://www.nabble.com/dynamically-%28client%29-created-form-components-tf3325801.html#a9333058 Sent from the Wicket - User mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Questions about non-wicket ajax call to wicket component
Thanks very much. It's working now. Cheers, Michael Igor Vaynberg [EMAIL PROTECTED] wrote: see ComponentRequestTarget which will render a markup of a certain component only and RequestCycle.urlFor(Component,RequestInterface) which will create a url to any callback method on any component -igor On 3/5/07, Michael K [EMAIL PROTECTED] wrote: Hi, I got a problem when i tried to use yui-ext updateManager script to load wicket component via XHR. Here is what I 've done so far: I created a js script that contain a Yui-ext's Dialog panel and embedded into the header page. Next, I override Wicket.link's getOnClickScript(url) so that the onclick script will callback the yui-ext.updateManager script with a given url. Now, that works fine but my next challenge is to generate a url that points to a panel so that when the script make a request, wicket will response to that particular panel. My other solution is to load an entire page into IFramepageIFrame, but I prefer using divpanel/div. Any suggestion? Thanks, Michael - 8:00? 8:25? 8:40? Find a flick in no time with theYahoo! Search movie showtime shortcut. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Have a burning question? Go to Yahoo! Answers and get answers from real people who know.- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
[Wicket-user] Exception using @SpringBean and HibernateSessionFactory - wicket 1.3
Hi all,
we received the following exception within a WebPage using an injected
SpringBean - HibernateSessionFactory via sublassed LocalSessionFactoryBean :
ERROR - Objects : Error serializing object class
de.ponton.box.core.ui.detail.Detail [object=[Page class =
de.ponton.box.core.ui.detail.Detail, id = 0, version = 0]]
wicket.util.io.WicketSerializeableException: Error writing fields for
wicket.proxy.$Proxy7
de.ponton.box.core.ui.detail.Detail-sessionFactory
NOTE: if you feel Wicket is at fault with this exception, please report
to the mailing list. You can switch to JDK based serialization by
calling: wicket.util.lang.Objects.setObjectStreamFactory(new
IObjectStreamFactory.DefaultObjectStreamFactory()) e.g. in the init
method of your application
at
wicket.util.io.WicketObjectOutputStream.writeObjectOverride(WicketObjectOutputStream.java:806)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:298)
at
wicket.util.io.ClassStreamHandler$ObjectFieldAndIndex.writeField(ClassStreamHandler.java:860)
at
wicket.util.io.ClassStreamHandler.writeFields(ClassStreamHandler.java:387)
at
wicket.util.io.WicketObjectOutputStream.writeObjectOverride(WicketObjectOutputStream.java:779)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:298)
at wicket.util.lang.Objects.objectToByteArray(Objects.java:1102)
at
wicket.protocol.http.FilePageStore.serializePage(FilePageStore.java:408)
at wicket.protocol.http.FilePageStore.access$1500(FilePageStore.java:49)
at
wicket.protocol.http.FilePageStore$PageSerializingThread.run(FilePageStore.java:705)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
at
wicket.util.io.ClassStreamHandler.writeFields(ClassStreamHandler.java:397)
at
wicket.util.io.WicketObjectOutputStream.writeObjectOverride(WicketObjectOutputStream.java:779)
... 10 more
ERROR - FilePageStore$PageSerializingThread : Error in page save thread
java.lang.NullPointerException
at
wicket.protocol.http.FilePageStore.serializePage(FilePageStore.java:413)
at wicket.protocol.http.FilePageStore.access$1500(FilePageStore.java:49)
at
wicket.protocol.http.FilePageStore$PageSerializingThread.run(FilePageStore.java:705)
at java.lang.Thread.run(Thread.java:595)
shouldn't happen
Here is the applicationContextSnippet:
...
bean id=mergedSessionFactory
class=de.ponton.box.core.bootstrap.DynamicSessionFactoryBean
singleton=true
property name=dataSource
ref bean=dataSource /
/property
we are subclassing LocalSessionFactoryBean from spring:
...
public class DynamicSessionFactoryBean extends LocalSessionFactoryBean
{
...
and here is the code snippet:
@SpringBean
SessionFactory sessionFactory;
This has worked with Wicket 1.2.5...
Any ideas?
--
Best regards / Mit freundlichen Grüßen
Michel Wichers
_
Ponton Consulting GmbH voice: +49.40.69213-340
http://www.ponton-consulting.de/ fax:+49.40.69213-355
Dorotheenstrasse 60mobile: +49.175.566 9970
D-22301 Hamburgmailto:[EMAIL PROTECTED]
_
HRB 81480, AG Hamburg, Managing Director: Dr. Michael Merz
Ponton Consulting is a Member of C1 Group (www.c1-group.com)
_
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Pushing data to the Ajax client in wicket?
i am planning to build an abstraction for cometd support (jetty and tomcat now) inside wicket. So that it really works like a ajax behavior that has a constant open connection where that you can get and then write the components you need. I first need to build that we can release and get the page again (set the pagemap barrier and release it when in idle mode) If somebody has nice idea's/api for this please speak! johan On 3/6/07, Peter Neubauer [EMAIL PROTECTED] wrote: Hi there, I am trying to push out events that contain the moving locations of a users buddies, so I can update the GMap on the page using plain JS and the GMarkerManager. Right now I am using Pushlet for this, but that has the disadvantage that it is not integrated into Wicket, and it uses a generic broadcast mechanism, much like JMS subscribing to topics from JS. Is there any way to get this functionality working using Wicket, e.g. the GMap not being reloaded, just moving the markers on a pull/push interval? Thanks for any hints! /peter - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Pushing data to the Ajax client in wicket?
On 3/6/07, Johan Compagner [EMAIL PROTECTED] wrote: i am planning to build an abstraction for cometd support (jetty and tomcat now) inside wicket. So that it really works like a ajax behavior that has a constant open connection where that you can get and then write the components you need. Excellent news! I was planning to work on that too, but with far less experience than you have on wicket, so I'm happy you start. But if you need some help (at least for testing), feel free to ask. - Xavier I first need to build that we can release and get the page again (set the pagemap barrier and release it when in idle mode) If somebody has nice idea's/api for this please speak! johan On 3/6/07, Peter Neubauer [EMAIL PROTECTED] wrote: Hi there, I am trying to push out events that contain the moving locations of a users buddies, so I can update the GMap on the page using plain JS and the GMarkerManager. Right now I am using Pushlet for this, but that has the disadvantage that it is not integrated into Wicket, and it uses a generic broadcast mechanism, much like JMS subscribing to topics from JS. Is there any way to get this functionality working using Wicket, e.g. the GMap not being reloaded, just moving the markers on a pull/push interval? Thanks for any hints! /peter - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Exception using @SpringBean and HibernateSessionFactory - wicket 1.3
do like the message says:
You can switch to JDK based serialization by
calling: wicket.util.lang.Objects.setObjectStreamFactory(new
IObjectStreamFactory.DefaultObjectStreamFactory()) e.g. in the init
method of your application
i think there is a bug in our optimized serialization where it doesnt handle
proxies properly yet
-igor
On 3/6/07, Michel Wichers [EMAIL PROTECTED] wrote:
Hi all,
we received the following exception within a WebPage using an injected
SpringBean - HibernateSessionFactory via sublassed LocalSessionFactoryBean
:
ERROR - Objects : Error serializing object class
de.ponton.box.core.ui.detail.Detail [object=[Page class =
de.ponton.box.core.ui.detail.Detail, id = 0, version = 0]]
wicket.util.io.WicketSerializeableException: Error writing fields for
wicket.proxy.$Proxy7
de.ponton.box.core.ui.detail.Detail-sessionFactory
NOTE: if you feel Wicket is at fault with this exception, please report
to the mailing list. You can switch to JDK based serialization by
calling: wicket.util.lang.Objects.setObjectStreamFactory(new
IObjectStreamFactory.DefaultObjectStreamFactory()) e.g. in the init
method of your application
at
wicket.util.io.WicketObjectOutputStream.writeObjectOverride(
WicketObjectOutputStream.java:806)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:298)
at
wicket.util.io.ClassStreamHandler$ObjectFieldAndIndex.writeField(
ClassStreamHandler.java:860)
at
wicket.util.io.ClassStreamHandler.writeFields(ClassStreamHandler.java:387)
at
wicket.util.io.WicketObjectOutputStream.writeObjectOverride(
WicketObjectOutputStream.java:779)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:298)
at wicket.util.lang.Objects.objectToByteArray(Objects.java:1102)
at
wicket.protocol.http.FilePageStore.serializePage(FilePageStore.java:408)
at wicket.protocol.http.FilePageStore.access$1500(FilePageStore.java
:49)
at
wicket.protocol.http.FilePageStore$PageSerializingThread.run(
FilePageStore.java:705)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
at
wicket.util.io.ClassStreamHandler.writeFields(ClassStreamHandler.java:397)
at
wicket.util.io.WicketObjectOutputStream.writeObjectOverride(
WicketObjectOutputStream.java:779)
... 10 more
ERROR - FilePageStore$PageSerializingThread : Error in page save thread
java.lang.NullPointerException
at
wicket.protocol.http.FilePageStore.serializePage(FilePageStore.java:413)
at wicket.protocol.http.FilePageStore.access$1500(FilePageStore.java
:49)
at
wicket.protocol.http.FilePageStore$PageSerializingThread.run(
FilePageStore.java:705)
at java.lang.Thread.run(Thread.java:595)
shouldn't happen
Here is the applicationContextSnippet:
...
bean id=mergedSessionFactory
class=de.ponton.box.core.bootstrap.DynamicSessionFactoryBean
singleton=true
property name=dataSource
ref bean=dataSource /
/property
we are subclassing LocalSessionFactoryBean from spring:
...
public class DynamicSessionFactoryBean extends LocalSessionFactoryBean
{
...
and here is the code snippet:
@SpringBean
SessionFactory sessionFactory;
This has worked with Wicket 1.2.5...
Any ideas?
--
Best regards / Mit freundlichen Grüßen
Michel Wichers
_
Ponton Consulting GmbH voice: +49.40.69213-340
http://www.ponton-consulting.de/ fax:+49.40.69213-355
Dorotheenstrasse 60mobile: +49.175.566 9970
D-22301 Hamburgmailto:[EMAIL PROTECTED]
_
HRB 81480, AG Hamburg, Managing Director: Dr. Michael Merz
Ponton Consulting is a Member of C1 Group (www.c1-group.com)
_
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] How do I make CheckBoxMultipleChoice show horizontal instead of vertical?
On Monday, 05 March 2007 05:20 pm, Igor Vaynberg escreveu: well if you want it to be horizontal then you can do something like this: setprefix(div style=\float:left;\); setsuffix(/div); Thanks. I did a setSuffix( ), which seems to work fine. -igor On 3/5/07, Thomas R. Corbin [EMAIL PROTECTED] wrote: On Monday, 05 March 2007 04:22 pm, Igor Vaynberg escreveu: override getprefix/getsuffix to return whatever html you want Ok, sorry - but I'm not sure what html I want there. I'm more of a swing programmer than a web programmer. -igor On 3/5/07, Thomas R. Corbin [EMAIL PROTECTED] wrote: I know that must be a dumb question, but I just can't quite get it. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Pushing data to the Ajax client in wicket?
class NewChatMsgEvent implements ComentEvent {
...
}
final WebMarkupContainer chatwindow=new WebMarkupContainer(chatwindow);
chatwindow.add(new CometBehavior(NewChatMsgEvent.class) {
protected void onEvent(CometEvent e, ComentTarget t) {
t.addComponent(chatwindow);
}
}
form.add(new SendChatButton() {
public void onsubmit() {
getApplication().getCometBroadcaster().publish(new
NewChatMsgEvent());
}
}
something like that should do quiet nicely i think
the broadcaster then has to find all active pages that have a behavior that
subscribed to this event and trigger them.
-igor
On 3/6/07, Johan Compagner [EMAIL PROTECTED] wrote:
i am planning to build an abstraction for cometd support (jetty and tomcat
now)
inside wicket. So that it really works like a ajax behavior that has a
constant open connection
where that you can get and then write the components you need.
I first need to build that we can release and get the page again (set the
pagemap barrier and release it when in idle mode)
If somebody has nice idea's/api for this please speak!
johan
On 3/6/07, Peter Neubauer [EMAIL PROTECTED] wrote:
Hi there,
I am trying to push out events that contain the moving locations of a
users buddies, so I can update the GMap on the page using plain JS and
the GMarkerManager.
Right now I am using Pushlet for this, but that has the disadvantage
that it is not integrated into Wicket, and it uses a generic broadcast
mechanism, much like JMS subscribing to topics from JS.
Is there any way to get this functionality working using Wicket, e.g.
the GMap not being reloaded, just moving the markers on a pull/push
interval?
Thanks for any hints!
/peter
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
[Wicket-user] Question: Sometimes our web pages come back incomplete.
It seems as though some of the data just doesn't come back until we do a refresh. We're using wicket 1.2.5. We've got a form and then after the form we have a DefaultDataTable with some rows. Sometimes it seems like it stops drawing the page after part of the form, maybe after the second datepicker. Does this sound familiar? Do you have any suggestions? I am no wicket or web wizard, so any hints would be appreciated. Thanks. Title: Manage Interruptions From Date: To Date: Selected Incident: [selected contact] [table] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Question: Sometimes our web pages come back incomplete.
ive only heard of this happening when wicket pages were rendered inside sitemesh, is that what you are doing? -igor On 3/6/07, Thomas R. Corbin [EMAIL PROTECTED] wrote: It seems as though some of the data just doesn't come back until we do a refresh. We're using wicket 1.2.5. We've got a form and then after the form we have a DefaultDataTable with some rows. Sometimes it seems like it stops drawing the page after part of the form, maybe after the second datepicker. Does this sound familiar? Do you have any suggestions? I am no wicket or web wizard, so any hints would be appreciated. Thanks. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
[Wicket-user] automated response
Hi I will be away from the 7th March till 14th March, and will be back only on the 15th. If you have any urgent matters, please contact the following persons Technical issues: Ciek Yi ([EMAIL PROTECTED] / +60123260583) Other issues: Edwin Tay ([EMAIL PROTECTED] / +60123165148) Thank you. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Question: Sometimes our web pages come back incomplete.
On Tuesday, 06 March 2007 10:57 am, Igor Vaynberg escreveu: ive only heard of this happening when wicket pages were rendered inside sitemesh, is that what you are doing? Jeez. Yes! That's exactly what we're doing. We have been thinking of getting rid of sitemesh once we're totatlly off of webwork and onto wicket. Then we can just use wicket composition. I guess we need to accelerate that! Or is there some temporary solution? Thanks! Wow. -igor On 3/6/07, Thomas R. Corbin [EMAIL PROTECTED] wrote: It seems as though some of the data just doesn't come back until we do a refresh. We're using wicket 1.2.5. We've got a form and then after the form we have a DefaultDataTable with some rows. Sometimes it seems like it stops drawing the page after part of the form, maybe after the second datepicker. Does this sound familiar? Do you have any suggestions? I am no wicket or web wizard, so any hints would be appreciated. Thanks. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Question: Sometimes our web pages come back incomplete.
im not sure if a solution has been found. afaik its some weird bug in sitemesh. search the mailing list for sitemesh to see other threads -igor On 3/6/07, Thomas R. Corbin [EMAIL PROTECTED] wrote: On Tuesday, 06 March 2007 10:57 am, Igor Vaynberg escreveu: ive only heard of this happening when wicket pages were rendered inside sitemesh, is that what you are doing? Jeez. Yes! That's exactly what we're doing. We have been thinking of getting rid of sitemesh once we're totatlly off of webwork and onto wicket. Then we can just use wicket composition. I guess we need to accelerate that! Or is there some temporary solution? Thanks! Wow. -igor On 3/6/07, Thomas R. Corbin [EMAIL PROTECTED] wrote: It seems as though some of the data just doesn't come back until we do a refresh. We're using wicket 1.2.5. We've got a form and then after the form we have a DefaultDataTable with some rows. Sometimes it seems like it stops drawing the page after part of the form, maybe after the second datepicker. Does this sound familiar? Do you have any suggestions? I am no wicket or web wizard, so any hints would be appreciated. Thanks. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Question: Sometimes our web pages come back incomplete.
Switch the rendering from RENDER_TO_BUFFER to DIRECT_RENDER (or something similar) Martijn On 3/6/07, Igor Vaynberg [EMAIL PROTECTED] wrote: im not sure if a solution has been found. afaik its some weird bug in sitemesh. search the mailing list for sitemesh to see other threads -igor On 3/6/07, Thomas R. Corbin [EMAIL PROTECTED] wrote: On Tuesday, 06 March 2007 10:57 am, Igor Vaynberg escreveu: ive only heard of this happening when wicket pages were rendered inside sitemesh, is that what you are doing? Jeez. Yes! That's exactly what we're doing. We have been thinking of getting rid of sitemesh once we're totatlly off of webwork and onto wicket. Then we can just use wicket composition. I guess we need to accelerate that! Or is there some temporary solution? Thanks! Wow. -igor On 3/6/07, Thomas R. Corbin [EMAIL PROTECTED] wrote: It seems as though some of the data just doesn't come back until we do a refresh. We're using wicket 1.2.5. We've got a form and then after the form we have a DefaultDataTable with some rows. Sometimes it seems like it stops drawing the page after part of the form, maybe after the second datepicker. Does this sound familiar? Do you have any suggestions? I am no wicket or web wizard, so any hints would be appreciated. Thanks. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.5 will keep your server alive. Download Wicket now! http://wicketframework.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] RequestCycle ThreadLocal
itself too. Could the Wicket team change RequestCycle so that either: 1) There is a public or protected static set method in RequestCycle 2) Make the ThreadLocal current inside RequestCycle protected I'm ready to consider 1) if you can open up an issue for it. That way we can track progress and other team members can have their say on it. Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
[Wicket-user] Using the session
Would like some clarification on another seemingly confusing part of Wicket: using the Session. First, it looks as if I'm supposed to define my own session, which I guess I can do (wrapper around getAttribute and setAttribute). First, why? What's wrong with the default set/getAttribute(String, String) being public and saving to a Hash of some sort? Second, how do I set up Application to use this new custom Session of mine? Maybe the above is moot, here's my situation. I have a list of Users, individually selectable. I want, when a User is selected, to put that User object (hibernate Entity) or just it's Id into the session (something) for further use. Some pages can only be accessed when you've selected a User to use. Is there a right way of doing this? A wrong way? Thanks again. Jason - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
[Wicket-user] Wicket Spring Annotations
I'm trying out Wicket Spring Annotation Integration example and I'm getting this error at server startup 2007-03-06 13:32:29.030::WARN: failed example java.lang.Error: Unresolved compilation problems: The import wicket.injection.IFieldValueFactory cannot be resolved IFieldValueFactory cannot be resolved to a type factory cannot be resolved IFieldValueFactory cannot be resolved to a type factory cannot be resolved Can some tell me what I am missing? -- View this message in context: http://www.nabble.com/Wicket-Spring-Annotations-tf3357621.html#a9338799 Sent from the Wicket - User mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Wicket Spring Annotations
the released wicket-spring-annot jar is bad, rebuild it from source or use the one from 1.2.4 -igor On 3/6/07, jklcom99 [EMAIL PROTECTED] wrote: I'm trying out Wicket Spring Annotation Integration example and I'm getting this error at server startup 2007-03-06 13:32:29.030::WARN: failed example java.lang.Error: Unresolved compilation problems: The import wicket.injection.IFieldValueFactory cannot be resolved IFieldValueFactory cannot be resolved to a type factory cannot be resolved IFieldValueFactory cannot be resolved to a type factory cannot be resolved Can some tell me what I am missing? -- View this message in context: http://www.nabble.com/Wicket-Spring-Annotations-tf3357621.html#a9338799 Sent from the Wicket - User mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Using the session
First, it looks as if I'm supposed to define my own session You can, you don't have to. , which I guess I can do (wrapper around getAttribute and setAttribute). First, why? Because it is type safe. Instead of User u = (User)session.get(_theUser); you simply do User u = session.getUser(). This makes it obvious what can be in your session at any giving time, and refactoring etc will be easy. What's wrong with the default set/getAttribute(String, String) being public and saving to a Hash of some sort? If you want that, provide your own session and expose those methods yourself. We don't provide it because we think it is bad programming practice. Second, how do I set up Application to use this new custom Session of mine? override newSession and return your session object there. The method will be called by Wicket. Maybe the above is moot, here's my situation. I have a list of Users, individually selectable. I want, when a User is selected, to put that User object (hibernate Entity) or just it's Id into the session (something) for further use. Some pages can only be accessed when you've selected a User to use. Is there a right way of doing this? A wrong way? You could do that. Though it might be better if you made the contract of having a user more explicit e.g. by requiring it (or it's id) as a constructor argument in other pages or components. Your choice. Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Using the session
On 3/6/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
First, it looks as if I'm supposed to define my own session
You can, you don't have to.
, which I guess I
can do (wrapper around getAttribute and setAttribute). First, why?
Because it is type safe. Instead of User u =
(User)session.get(_theUser); you simply do User u =
session.getUser(). This makes it obvious what can be in your session
at any giving time, and refactoring etc will be easy.
What's
wrong with the default set/getAttribute(String, String) being public and
saving to a Hash of some sort?
If you want that, provide your own session and expose those methods
yourself. We don't provide it because we think it is bad programming
practice.
Second, how do I set up Application to use
this new custom Session of mine?
override newSession and return your session object there. The method
will be called by Wicket.
Maybe the above is moot, here's my situation. I have a list of Users,
individually selectable. I want, when a User is selected, to put that
User
object (hibernate Entity) or just it's Id into the session (something)
for
further use. Some pages can only be accessed when you've selected a User
to
use.
Is there a right way of doing this? A wrong way?
You could do that. Though it might be better if you made the contract
of having a user more explicit e.g. by requiring it (or it's id) as a
constructor argument in other pages or components. Your choice.
Eelco
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
So you're saying that I'm supposed to...
class MySession extends WebSession {
private User selectedUser;
public get/setUser() { ... }
}
And wicket will keep a single instance of this class in memory at all times,
so as not to lose my selected value? And how do I access my custom version
of the Session, from a Page, Component, etc, ((MySession)getSession())?
Jason
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Using the session
java 4: MySession mySession = (MySession)Session.get();
java5: MySession mySession = MySession.get();
(add a get() method on your MySession object)
johan
On 3/6/07, Jason Roelofs [EMAIL PROTECTED] wrote:
On 3/6/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
First, it looks as if I'm supposed to define my own session
You can, you don't have to.
, which I guess I
can do (wrapper around getAttribute and setAttribute). First, why?
Because it is type safe. Instead of User u =
(User)session.get(_theUser); you simply do User u =
session.getUser(). This makes it obvious what can be in your session
at any giving time, and refactoring etc will be easy.
What's
wrong with the default set/getAttribute(String, String) being public
and
saving to a Hash of some sort?
If you want that, provide your own session and expose those methods
yourself. We don't provide it because we think it is bad programming
practice.
Second, how do I set up Application to use
this new custom Session of mine?
override newSession and return your session object there. The method
will be called by Wicket.
Maybe the above is moot, here's my situation. I have a list of Users,
individually selectable. I want, when a User is selected, to put that
User
object (hibernate Entity) or just it's Id into the session (something)
for
further use. Some pages can only be accessed when you've selected a
User to
use.
Is there a right way of doing this? A wrong way?
You could do that. Though it might be better if you made the contract
of having a user more explicit e.g. by requiring it (or it's id) as a
constructor argument in other pages or components. Your choice.
Eelco
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
So you're saying that I'm supposed to...
class MySession extends WebSession {
private User selectedUser;
public get/setUser() { ... }
}
And wicket will keep a single instance of this class in memory at all
times, so as not to lose my selected value? And how do I access my custom
version of the Session, from a Page, Component, etc,
((MySession)getSession())?
Jason
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
[Wicket-user] Wicket 2 and Java SE 6
Dear wicket users, is there anybody out there who uses wicket with Java SE 6 / JEE 5? Any experiences, warnings, hints? What is the official status of Wicket 2.0 against Java SE 6? Stefan Lindner winmail.dat- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Error with 1.2.5 and Spring
Thanks guys. I'll build it and put it in our company's maven repo or consider moving to 1.3. Is there a maven repo housing the 1.3 snapshots by any chance? Matt On 3/6/07, Johan Karlberg [EMAIL PROTECTED] wrote: I ran into this too a while back, logged under https://issues.apache.org/jira/browse/WICKET-304 The maven wicket-spring-annot build in 1.2.5 is corrupted, either back to 1.2.4, or build your own 1.2.5 (or like me, move to 1.3 snapshots, if that is feasible) Johan Mats Norén wrote: Got the same error On 3/5/07, Matt Welch [EMAIL PROTECTED] wrote: I'm only just now upgrading to Wicket 1.2.5 and I've run into an issue. I'm certain this is an problem on my side and not a bug because other people would have run into this and reported by now and I can't find any reports like this on the mailing list. I'm using Maven. I switched my three wicket dependencies (wicket, wicket-spring, and wicket-spring-annot) from version 1.2.4 to 1.2.5 and I'm now receiving an error. Everything compiles fine in my code, but when I start up jetty I see: -- java.lang.Error: Unresolved compilation problems: The import wicket.injection.IFieldValueFactory cannot be resolved IFieldValueFactory cannot be resolved to a type factory cannot be resolved IFieldValueFactory cannot be resolved to a type factory cannot be resolved at wicket.spring.injection.annot.AnnotSpringInjector.init( AnnotSpringInjector.java:4) at wicket.spring.injection.annot.SpringComponentInjector.init( SpringComponentInjector.java:96) at wicket.spring.injection.annot.SpringComponentInjector.init( SpringComponentInjector.java:68) at com.ptc.fusion.web.FusionWebApplication.init(FusionWebApplication.java :55) at wicket.protocol.http.WicketServlet.init(WicketServlet.java:299) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java :442) at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:259) at org.mortbay.component.AbstractLifeCycle.start (AbstractLifeCycle.java:40) at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java :593) at org.mortbay.jetty.servlet.Context.startContext(Context.java:139) at org.mortbay.jetty.webapp.WebAppContext.startContext (WebAppContext.java:1191) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java :481) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:434) at org.mortbay.component.AbstractLifeCycle.start (AbstractLifeCycle.java:40) at org.mortbay.jetty.plugin.Jetty6PluginWebApplication.start( Jetty6PluginWebApplication.java:147) at org.mortbay.jetty.plugin.AbstractJettyRunMojo$1.changesDetected( AbstractJettyRunMojo.java :372) at org.mortbay.jetty.plugin.util.Scanner.run(Scanner.java:159) -- If I remove the following line in my WebAppliciation.init() method, everything starts up fine: addComponentInstantiationListener(new SpringComponentInjector(this)); Of course, when remove that, I can no longer inject Spring beans with the @SpringBean annotation. I'm a little stuck here. If I switch back to 1.2.4, it's all fine again. Any ideas? Matt - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Question: Sometimes our web pages come back incomplete.
On Tuesday, 06 March 2007 11:24 am, Martijn Dashorst escreveu: Switch the rendering from RENDER_TO_BUFFER to DIRECT_RENDER (or something similar) Thanks! I'll investigate that just until we get rid of it, since I like the way wicket works better, anyway. Martijn On 3/6/07, Igor Vaynberg [EMAIL PROTECTED] wrote: im not sure if a solution has been found. afaik its some weird bug in sitemesh. search the mailing list for sitemesh to see other threads -igor On 3/6/07, Thomas R. Corbin [EMAIL PROTECTED] wrote: On Tuesday, 06 March 2007 10:57 am, Igor Vaynberg escreveu: ive only heard of this happening when wicket pages were rendered inside sitemesh, is that what you are doing? Jeez. Yes! That's exactly what we're doing. We have been thinking of getting rid of sitemesh once we're totatlly off of webwork and onto wicket. Then we can just use wicket composition. I guess we need to accelerate that! Or is there some temporary solution? Thanks! Wow. -igor On 3/6/07, Thomas R. Corbin [EMAIL PROTECTED] wrote: It seems as though some of the data just doesn't come back until we do a refresh. We're using wicket 1.2.5. We've got a form and then after the form we have a DefaultDataTable with some rows. Sometimes it seems like it stops drawing the page after part of the form, maybe after the second datepicker. Does this sound familiar? Do you have any suggestions? I am no wicket or web wizard, so any hints would be appreciated. Thanks. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Wicket 2 and Java SE 6
On 3/6/07, Stefan Lindner [EMAIL PROTECTED] wrote: Dear wicket users, is there anybody out there who uses wicket with Java SE 6 / JEE 5? Any experiences, warnings, hints? What is the official status of Wicket 2.0 against Java SE 6? Faster with better GC, that's what Java SE is for Wicket. No differences for the rest (vs 5) :) Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Error with 1.2.5 and Spring
Sure there is. repository idWicket Snapshots/id urlhttp://wicketstuff.org/maven/repository/url snapshots enabledtrue/enabled /snapshots releases enabledfalse/enabled /releases /repository and wicket and friends with a new groupId groupIdorg.apache.wicket/groupId artifactIdwicket/artifactId Johan Matt Welch wrote: Thanks guys. I'll build it and put it in our company's maven repo or consider moving to 1.3. Is there a maven repo housing the 1.3 snapshots by any chance? Matt On 3/6/07, *Johan Karlberg* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I ran into this too a while back, logged under https://issues.apache.org/jira/browse/WICKET-304 The maven wicket-spring-annot build in 1.2.5 is corrupted, either back to 1.2.4, or build your own 1.2.5 (or like me, move to 1.3 snapshots, if that is feasible) Johan Mats Norén wrote: Got the same error On 3/5/07, Matt Welch [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I'm only just now upgrading to Wicket 1.2.5 and I've run into an issue. I'm certain this is an problem on my side and not a bug because other people would have run into this and reported by now and I can't find any reports like this on the mailing list. I'm using Maven. I switched my three wicket dependencies (wicket, wicket-spring, and wicket-spring-annot) from version 1.2.4 to 1.2.5 and I'm now receiving an error. Everything compiles fine in my code, but when I start up jetty I see: -- java.lang.Error: Unresolved compilation problems: The import wicket.injection.IFieldValueFactory cannot be resolved IFieldValueFactory cannot be resolved to a type factory cannot be resolved IFieldValueFactory cannot be resolved to a type factory cannot be resolved at wicket.spring.injection.annot.AnnotSpringInjector .init(AnnotSpringInjector.java:4) at wicket.spring.injection.annot.SpringComponentInjector.init(SpringComponentInjector.java:96) at wicket.spring.injection.annot.SpringComponentInjector .init(SpringComponentInjector.java:68) at com.ptc.fusion.web.FusionWebApplication.init(FusionWebApplication.java:55) at wicket.protocol.http.WicketServlet.init (WicketServlet.java:299) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java :442) at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:259) at org.mortbay.component.AbstractLifeCycle.start (AbstractLifeCycle.java:40) at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:593) at org.mortbay.jetty.servlet.Context.startContext(Context.java:139) at org.mortbay.jetty.webapp.WebAppContext.startContext (WebAppContext.java:1191) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:481) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:434) at org.mortbay.component.AbstractLifeCycle.start (AbstractLifeCycle.java:40) at org.mortbay.jetty.plugin.Jetty6PluginWebApplication.start(Jetty6PluginWebApplication.java:147) at org.mortbay.jetty.plugin.AbstractJettyRunMojo$1.changesDetected(AbstractJettyRunMojo.java :372) at org.mortbay.jetty.plugin.util.Scanner.run(Scanner.java:159) -- If I remove the following line in my WebAppliciation.init() method, everything starts up fine: addComponentInstantiationListener(new SpringComponentInjector(this)); Of course, when remove that, I can no longer inject Spring beans with the @SpringBean annotation. I'm a little stuck here. If I switch back to 1.2.4, it's all fine again. Any ideas? Matt - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
Re: [Wicket-user] Using the session
On 3/6/07, Eelco Hillenius [EMAIL PROTECTED] wrote: What's wrong with the default set/getAttribute(String, String) being public and saving to a Hash of some sort? If you want that, provide your own session and expose those methods yourself. We don't provide it because we think it is bad programming practice. Would you mine expounding on this a little more? This comes across to me as it's bad programming practice to follow paradigms set in place for the past 10+ years (Web session being a hash of strings at it's most basic implementation). In response to the topic at hand, I implemented what I posted earlier, it seems to work alright. Jason - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Using the session
On 3/6/07, Jason Roelofs [EMAIL PROTECTED] wrote: Would you mine expounding on this a little more? This comes across to me as it's bad programming practice to follow paradigms set in place for the past 10+ years (Web session being a hash of strings at it's most basic implementation). so why even look into wicket? why not use servlets directly? after all they have been around for 10+ years :) -igor - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
[Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
Hi, We (Wicket's developers) are having some discussion over 1.3 vs 2.0 and how difficult it is as a nun-funded project to spend so much time synchronizing the branches. A major issue in the discussion is that not everyone is convinced anymore that the constructor change in 2.0 is for the better. There are pros and cons for sure, but we want to get your opinion on this. Please help us out giving your opinion. We want to know: 1) Who uses 2.0 for serious projects? 2) What do you think of the constructor change? Do you prefer 1.3's add style or 2.0's style of passing in the parent construction time. 3) If we would ever backtrack on the constructor change (*if*, don't panic for now) how much trouble would that give you? Please don't be shy giving your opinion. This is an important issue in the future development of Wicket. Regards, Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Using the session
Would you mine expounding on this a little more? This comes across to me as it's bad programming practice to follow paradigms set in place for the past 10+ years (Web session being a hash of strings at it's most basic implementation). Exactly, that's what I'm saying! :) Much of what is wrong with web application framework today is that they do not support proper strongly typed object oriented development. In response to the topic at hand, I implemented what I posted earlier, it seems to work alright. Cool, Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
What's the advantage of the new code (no, I'm not currently using Wicket 2.0)? Is it processing performance? Memory usage? Is the framework code a lot less complex? A little less complex? []s Gus On 3/6/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Hi, We (Wicket's developers) are having some discussion over 1.3 vs 2.0 and how difficult it is as a nun-funded project to spend so much time synchronizing the branches. A major issue in the discussion is that not everyone is convinced anymore that the constructor change in 2.0 is for the better. There are pros and cons for sure, but we want to get your opinion on this. Please help us out giving your opinion. We want to know: 1) Who uses 2.0 for serious projects? 2) What do you think of the constructor change? Do you prefer 1.3's add style or 2.0's style of passing in the parent construction time. 3) If we would ever backtrack on the constructor change (*if*, don't panic for now) how much trouble would that give you? Please don't be shy giving your opinion. This is an important issue in the future development of Wicket. Regards, Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
On 3/6/07, Gustavo Hexsel [EMAIL PROTECTED] wrote: What's the advantage of the new code (no, I'm not currently using Wicket 2.0)? Is it processing performance? Memory usage? Is the framework code a lot less complex? A little less complex? Please see: http://cwiki.apache.org/WICKET/migrate-20.html#Migrate-2.0-Constructorchange And maybe Igor (and others?) can explain a bit about the pros and cons he experiences after developing two projects with it. Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
i would like to see a list of what we'd lose by not supporting the constructor change. i actually prefer the add() usage and always have. i just don't want us to forget why we originally wanted to make the constructor change. the only two things i can recall are: - better diagnostics, but i can't recall exactly /what/ diagnostics we thought we'd get - ability to make component init dependent on parental context. this might be either xml association or component data somehow. i can't think of any times i've been screaming to do this, but can anyone give some of the best examples so we can evaluate what we'd be losing here? Eelco Hillenius wrote: Hi, We (Wicket's developers) are having some discussion over 1.3 vs 2.0 and how difficult it is as a nun-funded project to spend so much time synchronizing the branches. A major issue in the discussion is that not everyone is convinced anymore that the constructor change in 2.0 is for the better. There are pros and cons for sure, but we want to get your opinion on this. Please help us out giving your opinion. We want to know: 1) Who uses 2.0 for serious projects? 2) What do you think of the constructor change? Do you prefer 1.3's add style or 2.0's style of passing in the parent construction time. 3) If we would ever backtrack on the constructor change (*if*, don't panic for now) how much trouble would that give you? Please don't be shy giving your opinion. This is an important issue in the future development of Wicket. Regards, Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/IMPORTANT%3A-your-opinion-on-the-constructor-change-in-2.0-tf3358738.html#a9342589 Sent from the Wicket - User mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
pros: * free to call any method in the constructor like getpage(), urlfor(), etc. * access to markup attributes in constructor as opposed to render time * fail at component instantiation time rather then render time if there is a hierarchy-java mismatch - so you get a java line-precise error as opposed to our error webpage cons: * code explosion 2.0: http://papernapkin.org/pastebin/view/4900 1.3: http://papernapkin.org/pastebin/view/4908 * hacks necessary for nontrivial components GridView.populate() http://papernapkin.org/pastebin/view/4902 notice fake1,fake2 parents necessary for child item instantiation and which are later removed * more limited in how the hierarchy is created since it MUST be created top-down * replacing components is less explicit. 1.3: a.replaceWith(new B()); 2.0: new B(a.getParent(), a.getId()); -igor On 3/6/07, Jonathan Locke [EMAIL PROTECTED] wrote: i would like to see a list of what we'd lose by not supporting the constructor change. i actually prefer the add() usage and always have. i just don't want us to forget why we originally wanted to make the constructor change. the only two things i can recall are: - better diagnostics, but i can't recall exactly /what/ diagnostics we thought we'd get - ability to make component init dependent on parental context. this might be either xml association or component data somehow. i can't think of any times i've been screaming to do this, but can anyone give some of the best examples so we can evaluate what we'd be losing here? Eelco Hillenius wrote: Hi, We (Wicket's developers) are having some discussion over 1.3 vs 2.0 and how difficult it is as a nun-funded project to spend so much time synchronizing the branches. A major issue in the discussion is that not everyone is convinced anymore that the constructor change in 2.0 is for the better. There are pros and cons for sure, but we want to get your opinion on this. Please help us out giving your opinion. We want to know: 1) Who uses 2.0 for serious projects? 2) What do you think of the constructor change? Do you prefer 1.3's add style or 2.0's style of passing in the parent construction time. 3) If we would ever backtrack on the constructor change (*if*, don't panic for now) how much trouble would that give you? Please don't be shy giving your opinion. This is an important issue in the future development of Wicket. Regards, Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/IMPORTANT%3A-your-opinion-on-the-constructor-change-in-2.0-tf3358738.html#a9342589 Sent from the Wicket - User mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
Why does code explosion happen as a consequence of the constructor change? Gili Igor Vaynberg wrote: pros: * free to call any method in the constructor like getpage(), urlfor(), etc. * access to markup attributes in constructor as opposed to render time * fail at component instantiation time rather then render time if there is a hierarchy-java mismatch - so you get a java line-precise error as opposed to our error webpage cons: * code explosion 2.0: http://papernapkin.org/pastebin/view/4900 1.3: http://papernapkin.org/pastebin/view/4908 http://papernapkin.org/pastebin/view/4908 * hacks necessary for nontrivial components GridView.populate() http://papernapkin.org/pastebin/view/4902 notice fake1,fake2 parents necessary for child item instantiation and which are later removed * more limited in how the hierarchy is created since it MUST be created top-down * replacing components is less explicit. 1.3: a.replaceWith(new B()); 2.0: new B(a.getParent(), a.getId()); -igor On 3/6/07, *Jonathan Locke* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: i would like to see a list of what we'd lose by not supporting the constructor change. i actually prefer the add() usage and always have. i just don't want us to forget why we originally wanted to make the constructor change. the only two things i can recall are: - better diagnostics, but i can't recall exactly /what/ diagnostics we thought we'd get - ability to make component init dependent on parental context. this might be either xml association or component data somehow. i can't think of any times i've been screaming to do this, but can anyone give some of the best examples so we can evaluate what we'd be losing here? Eelco Hillenius wrote: Hi, We (Wicket's developers) are having some discussion over 1.3 vs 2.0 and how difficult it is as a nun-funded project to spend so much time synchronizing the branches. A major issue in the discussion is that not everyone is convinced anymore that the constructor change in 2.0 is for the better. There are pros and cons for sure, but we want to get your opinion on this. Please help us out giving your opinion. We want to know: 1) Who uses 2.0 for serious projects? 2) What do you think of the constructor change? Do you prefer 1.3's add style or 2.0's style of passing in the parent construction time. 3) If we would ever backtrack on the constructor change (*if*, don't panic for now) how much trouble would that give you? Please don't be shy giving your opinion. This is an important issue in the future development of Wicket. Regards, Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net mailto:Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/IMPORTANT%3A-your-opinion-on-the-constructor-change-in-2.0-tf3358738.html#a9342589 http://www.nabble.com/IMPORTANT%3A-your-opinion-on-the-constructor-change-in-2.0-tf3358738.html#a9342589 Sent from the Wicket - User mailing list archive at Nabble.com http://Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net mailto:Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your
Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
just thinking out loud, there is no workaround for the constructor pros. are there any important things people really /need/ to get done that we're making impossible without the constructor change? i don't care to much about accessing markup attributes in the constructor because i don't care much about driving code from markup. but what about the others? are there any useful things we'd lose? i think i can live without the perfect error reporting as wicket error reporting seems good enough to me now. it's almost certainly not worth a code explosion to get this alone. jon igor.vaynberg wrote: pros: * free to call any method in the constructor like getpage(), urlfor(), etc. * access to markup attributes in constructor as opposed to render time * fail at component instantiation time rather then render time if there is a hierarchy-java mismatch - so you get a java line-precise error as opposed to our error webpage cons: * code explosion 2.0: http://papernapkin.org/pastebin/view/4900 1.3: http://papernapkin.org/pastebin/view/4908 * hacks necessary for nontrivial components GridView.populate() http://papernapkin.org/pastebin/view/4902 notice fake1,fake2 parents necessary for child item instantiation and which are later removed * more limited in how the hierarchy is created since it MUST be created top-down * replacing components is less explicit. 1.3: a.replaceWith(new B()); 2.0: new B(a.getParent(), a.getId()); -igor On 3/6/07, Jonathan Locke [EMAIL PROTECTED] wrote: i would like to see a list of what we'd lose by not supporting the constructor change. i actually prefer the add() usage and always have. i just don't want us to forget why we originally wanted to make the constructor change. the only two things i can recall are: - better diagnostics, but i can't recall exactly /what/ diagnostics we thought we'd get - ability to make component init dependent on parental context. this might be either xml association or component data somehow. i can't think of any times i've been screaming to do this, but can anyone give some of the best examples so we can evaluate what we'd be losing here? Eelco Hillenius wrote: Hi, We (Wicket's developers) are having some discussion over 1.3 vs 2.0 and how difficult it is as a nun-funded project to spend so much time synchronizing the branches. A major issue in the discussion is that not everyone is convinced anymore that the constructor change in 2.0 is for the better. There are pros and cons for sure, but we want to get your opinion on this. Please help us out giving your opinion. We want to know: 1) Who uses 2.0 for serious projects? 2) What do you think of the constructor change? Do you prefer 1.3's add style or 2.0's style of passing in the parent construction time. 3) If we would ever backtrack on the constructor change (*if*, don't panic for now) how much trouble would that give you? Please don't be shy giving your opinion. This is an important issue in the future development of Wicket. Regards, Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/IMPORTANT%3A-your-opinion-on-the-constructor-change-in-2.0-tf3358738.html#a9342589 Sent from the Wicket - User mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context:
Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
because the parent must be known at construction time and by YOU since YOU are the one calling new. so if there is an indirection somewhere like there is with the toolbars you have to use a factory in order to get the correct parent passed to you by the component at a later time. -igor On 3/6/07, cowwoc [EMAIL PROTECTED] wrote: Why does code explosion happen as a consequence of the constructor change? Gili Igor Vaynberg wrote: pros: * free to call any method in the constructor like getpage(), urlfor(), etc. * access to markup attributes in constructor as opposed to render time * fail at component instantiation time rather then render time if there is a hierarchy-java mismatch - so you get a java line-precise error as opposed to our error webpage cons: * code explosion 2.0: http://papernapkin.org/pastebin/view/4900 1.3: http://papernapkin.org/pastebin/view/4908 http://papernapkin.org/pastebin/view/4908 * hacks necessary for nontrivial components GridView.populate() http://papernapkin.org/pastebin/view/4902 notice fake1,fake2 parents necessary for child item instantiation and which are later removed * more limited in how the hierarchy is created since it MUST be created top-down * replacing components is less explicit. 1.3: a.replaceWith(new B()); 2.0: new B(a.getParent(), a.getId()); -igor On 3/6/07, *Jonathan Locke* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: i would like to see a list of what we'd lose by not supporting the constructor change. i actually prefer the add() usage and always have. i just don't want us to forget why we originally wanted to make the constructor change. the only two things i can recall are: - better diagnostics, but i can't recall exactly /what/ diagnostics we thought we'd get - ability to make component init dependent on parental context. this might be either xml association or component data somehow. i can't think of any times i've been screaming to do this, but can anyone give some of the best examples so we can evaluate what we'd be losing here? Eelco Hillenius wrote: Hi, We (Wicket's developers) are having some discussion over 1.3 vs 2.0 and how difficult it is as a nun-funded project to spend so much time synchronizing the branches. A major issue in the discussion is that not everyone is convinced anymore that the constructor change in 2.0 is for the better. There are pros and cons for sure, but we want to get your opinion on this. Please help us out giving your opinion. We want to know: 1) Who uses 2.0 for serious projects? 2) What do you think of the constructor change? Do you prefer 1.3 's add style or 2.0's style of passing in the parent construction time. 3) If we would ever backtrack on the constructor change (*if*, don't panic for now) how much trouble would that give you? Please don't be shy giving your opinion. This is an important issue in the future development of Wicket. Regards, Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net mailto:Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/IMPORTANT%3A-your-opinion-on-the-constructor-change-in-2.0-tf3358738.html#a9342589 http://www.nabble.com/IMPORTANT%3A-your-opinion-on-the-constructor-change-in-2.0-tf3358738.html#a9342589 Sent from the Wicket - User mailing list archive at Nabble.com http://Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net mailto:Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
well it is useful when constructing javascript behaviors because they can create urls to pass to javascript at construction time instead of doing it at a later point (onattach?). but it is mere convinience. -igor On 3/6/07, Jonathan Locke [EMAIL PROTECTED] wrote: just thinking out loud, there is no workaround for the constructor pros. are there any important things people really /need/ to get done that we're making impossible without the constructor change? i don't care to much about accessing markup attributes in the constructor because i don't care much about driving code from markup. but what about the others? are there any useful things we'd lose? i think i can live without the perfect error reporting as wicket error reporting seems good enough to me now. it's almost certainly not worth a code explosion to get this alone. jon igor.vaynberg wrote: pros: * free to call any method in the constructor like getpage(), urlfor(), etc. * access to markup attributes in constructor as opposed to render time * fail at component instantiation time rather then render time if there is a hierarchy-java mismatch - so you get a java line-precise error as opposed to our error webpage cons: * code explosion 2.0: http://papernapkin.org/pastebin/view/4900 1.3: http://papernapkin.org/pastebin/view/4908 * hacks necessary for nontrivial components GridView.populate() http://papernapkin.org/pastebin/view/4902 notice fake1,fake2 parents necessary for child item instantiation and which are later removed * more limited in how the hierarchy is created since it MUST be created top-down * replacing components is less explicit. 1.3: a.replaceWith(new B()); 2.0: new B(a.getParent(), a.getId()); -igor On 3/6/07, Jonathan Locke [EMAIL PROTECTED] wrote: i would like to see a list of what we'd lose by not supporting the constructor change. i actually prefer the add() usage and always have. i just don't want us to forget why we originally wanted to make the constructor change. the only two things i can recall are: - better diagnostics, but i can't recall exactly /what/ diagnostics we thought we'd get - ability to make component init dependent on parental context. this might be either xml association or component data somehow. i can't think of any times i've been screaming to do this, but can anyone give some of the best examples so we can evaluate what we'd be losing here? Eelco Hillenius wrote: Hi, We (Wicket's developers) are having some discussion over 1.3 vs 2.0 and how difficult it is as a nun-funded project to spend so much time synchronizing the branches. A major issue in the discussion is that not everyone is convinced anymore that the constructor change in 2.0 is for the better. There are pros and cons for sure, but we want to get your opinion on this. Please help us out giving your opinion. We want to know: 1) Who uses 2.0 for serious projects? 2) What do you think of the constructor change? Do you prefer 1.3's add style or 2.0's style of passing in the parent construction time. 3) If we would ever backtrack on the constructor change (*if*, don't panic for now) how much trouble would that give you? Please don't be shy giving your opinion. This is an important issue in the future development of Wicket. Regards, Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/IMPORTANT%3A-your-opinion-on-the-constructor-change-in-2.0-tf3358738.html#a9342589 Sent from the Wicket - User mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash
Re: [Wicket-user] Wicket Spring Annotations
Igor Vaynberg wrote: the released wicket-spring-annot jar is bad, rebuild it from source or use the one from 1.2.4 http://bzzt.net/~arnouten/wicket-spring-annot-1.2.5.jar seems to work fine - I believe I got it from wicketframework.org at some point. Arnout - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
i don't care to much about accessing markup attributes in the constructor because i don't care much about driving code from markup. If you create components that are based on or work together with Javascript components, this is a nice feature to have. Driving code from markup sounds more negative than it is, as when working with ajax and javascript, you *need* this, and the ability to do it at any time is nice. There are workarounds, and I found that in the end I'm often coupling such components on render time anyway (e.g. using header contributors with LoadableDetachableModels). Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
yeah, with our new headercontributor stuff some of these problems no longer matter -igor On 3/6/07, Eelco Hillenius [EMAIL PROTECTED] wrote: i don't care to much about accessing markup attributes in the constructor because i don't care much about driving code from markup. If you create components that are based on or work together with Javascript components, this is a nice feature to have. Driving code from markup sounds more negative than it is, as when working with ajax and javascript, you *need* this, and the ability to do it at any time is nice. There are workarounds, and I found that in the end I'm often coupling such components on render time anyway (e.g. using header contributors with LoadableDetachableModels). Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
The biggest problem I see is a matter of economics. Current applications can't be upgraded to the constructor change economically. Too much has to change to move in that direction. I do like the programming model, although I haven't used it in a production system (as I am doing with 1.x). Having the model changes in 1.x will result in a lot of work, but not nearly as much as the c'tor change. The api changes will be less intrusive as you'll likely have less custom models than components. Wicket 2.0 is a beast and hard to support, especially since to support software in a good way, you need to eat your own dog food. One other thing: moving to Apache usually requires you to move the code base into the org.apache namespace. We opted to do that for 2.x only, as the API is already broken. In the remote possibility of freezing further development on 2.x, we should see what we need to do in the org.apache realm for 1.x If/when we need to make a decision between 1.x and 2.x, I'd rather drop 2.x and continue with 1.x then drop 1.x in favor of 2.x. Martijn On 3/6/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Hi, We (Wicket's developers) are having some discussion over 1.3 vs 2.0 and how difficult it is as a nun-funded project to spend so much time synchronizing the branches. A major issue in the discussion is that not everyone is convinced anymore that the constructor change in 2.0 is for the better. There are pros and cons for sure, but we want to get your opinion on this. Please help us out giving your opinion. We want to know: 1) Who uses 2.0 for serious projects? 2) What do you think of the constructor change? Do you prefer 1.3's add style or 2.0's style of passing in the parent construction time. 3) If we would ever backtrack on the constructor change (*if*, don't panic for now) how much trouble would that give you? Please don't be shy giving your opinion. This is an important issue in the future development of Wicket. Regards, Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.5 will keep your server alive. Download Wicket now! http://wicketframework.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
On Mar 6, 2007, at 2:12 PM, Eelco Hillenius wrote: 1) Who uses 2.0 for serious projects? I'm hoping to roll my project out over the next few weeks, it uses 2.0. I don't have a lot of pages though, so porting wouldn't be a problem. 2) What do you think of the constructor change? Do you prefer 1.3's add style or 2.0's style of passing in the parent construction time. What about some hybrid of the two? My use case for this came yesterday, when I was wanting to add functionality for disabled option items in a DropDown. If I were to follow the pattern of creating all the constructor combinations for optional parameters, I would have had to add somewhere between 50-100% of the count of the constructors. IMHO, stuff like 'disabled' is secondary, and the meat of the component is the DropDown itself. This is to say I would not miss java line-precise errors for stuff that is considered secondary. (Ignore me if I am talking nonsense here...) 3) If we would ever backtrack on the constructor change (*if*, don't panic for now) how much trouble would that give you? It wouldn't be that big a deal for me. -b - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] IMPORTANT: your opinion on the constructor
To speak as an end-user: 1) Who uses 2.0 for serious projects? We use 2.0 in a serious project for mobile patient data acquisition. We plan the rollout for about next week (despite wicket 2.0 is not even in beta status). 2) What do you think of the constructor change? Do you prefer 1.3's We prefer the 2.0 constructor. At the first sight it looked a little bit strange. The 1.3 style felt much more java like, having an object and activationg a method of this object instead of just creating new objects with no anchor (no variable addressing the newly created object). But the discussion about the advantages was convincing and after using it for some months now, the top down style was very usefull. 3) If we would ever backtrack on the constructor change (*if*, don't panic for now) how much trouble would that give you? I don't believe that this would be a real problem. The task consists for changig changing new Component(this into this.add(new Component in most cases. But I was convinced of the advantages that the new constructor has and the question is now 1. Are the proposed advantages no longer advantages 2. Does the new constructor make anything impossible that was possible with the old style contructor? 3. What does the wicket 1.x users prevent to switch to the 2.0 style that goes beyond a simple syntax change? Stefan Lindner winmail.dat- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
Eelco Hillenius wrote: A major issue in the discussion is that not everyone is convinced anymore that the constructor change in 2.0 is for the better. There are pros and cons for sure, but we want to get your opinion on this. I'm a committer, but I'm also a user, and I feel pretty strongly about this on both fronts. Apologies that this is a bit long. I've tried to condense it a bit, but there are a lot of things to talk about. :-) The constructor change effectively means that for a big project you'll need to almost completely rewrite it to go from 1.x to 2.0 - there will be lots of fundamental logic changes. This seems misguided at best, for the following reasons... 1.x is not going to go away. With all the recent buzz, we now have an awful lot of 1.x users with growing code-bases (I'm one of them). Not providing all these users with a sensible upgrade path between versions is a big mistake, IMO. Users of Tapestry often complain that each big version is such a big API break that they effectively have to start from scratch each time. We surely don't want to make the same mistake? Because 1.x isn't going to go away, people will want bugs fixing and new features adding on that branch. 1.x isn't going to go into maintenance mode any time soon - we'll have to continue to support two very active branches for months and quite possibly years to come. Dividing effort and duplicating everything like this is a terrible waste of developer resources. I've no idea what quantitative impact it has/ will have, but I'd bet it's very large (25% or something). We're also less likely to attract people who want to work on the project either as core committers or JIRA patch providers if they need to effectively do their work and testing twice. The fork already annoys me no end, and I'd definitely be inclined to fix more bugs if it wasn't like that. If we have two active branches, they'll each be (on average) half as well tested in real world applications. This seems like a bad idea, for obvious reasons. Most developers seem to have live or near-production systems running on 1.3, so they are often scratching that itch first, and have limited time to forward port things to 2.0. This means that things lag a bit and make bug reporting and the like more of a hassle. I've lost track of the number of times someone has had to ask which branch are you using? in response to a bug report. I also sense that users are already getting frustrated with people saying things like ah, yes, that's fixed on the other branch. So why did we do the constructor refactor? The argument for javascript IDs seems reasonable, but I'd counter it with two things: - You can use a unique ID instead to get around the problem (in fact, maybe setOutputMarkupId() should use a globally unique ID by default rather than a path, so you don't even need to worry about this?). - If you do use the ID from the constructor that 2.0 makes possible, it will break if you do component replacement, because this will change. So really, you should be using the current approach of pulling the ID during the render or using a GUID anyway. So we're left with marginally nicer error reporting. Is this much of an improvement? Is our current reporting that deficient? Might there be another way of improving this similarly, but without the constructor change? Al - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] IMPORTANT: your opinion on the constructor
On 3/6/07, Stefan Lindner [EMAIL PROTECTED] wrote: To speak as an end-user: 2) What do you think of the constructor change? Do you prefer 1.3's We prefer the 2.0 constructor. what about it do you prefer? in most cases. But I was convinced of the advantages that the new constructor has and the question is now 1. Are the proposed advantages no longer advantages they still are, although less so with the new headercontributor stuff 2. Does the new constructor make anything impossible that was possible with the old style contructor? yes. it makes indirectly creating children more difficult. it also makes moving components very difficult. 3. What does the wicket 1.x users prevent to switch to the 2.0 style that goes beyond a simple syntax change? because the constructor is more limiting in the way you create hierarchies (see point 2) you need to rewrite parts of your code in a non-trivial manner going the other way 2.0-1.x should be trivial -igor Stefan Lindner - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
3) If we would ever backtrack on the constructor change (*if*, don't panic for now) how much trouble would that give you? I don't believe that this would be a real problem. The task consists for changig changing new Component(this into this.add(new Component in most cases. But I was convinced of the advantages that the new constructor has and the question is now 1. Are the proposed advantages no longer advantages Yes, they still are, though improved header contributions make that you don't often need the path at construction time, but instead can use a model for that. Also, I'd like to state again that for simple things, I like the more compact style of 2.0. And I actually like the automatic re-parenting that some others dislike. But a big problem is that some of the more dynamic things got more work/ uglier to implement. 2. Does the new constructor make anything impossible that was possible with the old style contructor? Some things. My biggest disappointment was that wizard steps can no longer be panels as well, but have to work with a factory pattern. So at least that component got uglier in 2.0. 3. What does the wicket 1.x users prevent to switch to the 2.0 style that goes beyond a simple syntax change? I think the big dividing line is where you primarily used components in a pretty straightforward manner, or whether you created lots of advanced custom components. If the latter is the case, upgrading or downgrading can be quite a bit of work. I think it goes too far to state that it concerns a full rewrite, but for a large project this certainly may make for a day or two excluding testing. Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] IMPORTANT: your opinion on the constructor
going the other way 2.0-1.x should be trivial This is true. At least it should be a lot easier. Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
code explosion? i count 5 chars less for every component create! ;) 1.3: container.add(new Child(id)); 2.0: new Child(container,id); johan :) On 3/6/07, Igor Vaynberg [EMAIL PROTECTED] wrote: pros: * free to call any method in the constructor like getpage(), urlfor(), etc. * access to markup attributes in constructor as opposed to render time * fail at component instantiation time rather then render time if there is a hierarchy-java mismatch - so you get a java line-precise error as opposed to our error webpage cons: * code explosion 2.0: http://papernapkin.org/pastebin/view/4900 1.3: http://papernapkin.org/pastebin/view/4908 * hacks necessary for nontrivial components GridView.populate() http://papernapkin.org/pastebin/view/4902 notice fake1,fake2 parents necessary for child item instantiation and which are later removed * more limited in how the hierarchy is created since it MUST be created top-down * replacing components is less explicit. 1.3: a.replaceWith(new B()); 2.0: new B(a.getParent(), a.getId()); -igor On 3/6/07, Jonathan Locke [EMAIL PROTECTED] wrote: i would like to see a list of what we'd lose by not supporting the constructor change. i actually prefer the add() usage and always have. i just don't want us to forget why we originally wanted to make the constructor change. the only two things i can recall are: - better diagnostics, but i can't recall exactly /what/ diagnostics we thought we'd get - ability to make component init dependent on parental context. this might be either xml association or component data somehow. i can't think of any times i've been screaming to do this, but can anyone give some of the best examples so we can evaluate what we'd be losing here? Eelco Hillenius wrote: Hi, We (Wicket's developers) are having some discussion over 1.3 vs 2.0 and how difficult it is as a nun-funded project to spend so much time synchronizing the branches. A major issue in the discussion is that not everyone is convinced anymore that the constructor change in 2.0 is for the better. There are pros and cons for sure, but we want to get your opinion on this. Please help us out giving your opinion. We want to know: 1) Who uses 2.0 for serious projects? 2) What do you think of the constructor change? Do you prefer 1.3's add style or 2.0's style of passing in the parent construction time. 3) If we would ever backtrack on the constructor change (*if*, don't panic for now) how much trouble would that give you? Please don't be shy giving your opinion. This is an important issue in the future development of Wicket. Regards, Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/IMPORTANT%3A-your-opinion-on-the-constructor-change-in-2.0-tf3358738.html#a9342589 Sent from the Wicket - User mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Exception using @SpringBean and HibernateSessionFactory - wicket 1.3
Can anybody make a quick unit test with such a class?
Anybody that encounters a specific class that should work but doesn't please
add a method to WicketOutputStreamTest
johan
On 3/6/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
do like the message says:
You can switch to JDK based serialization by
calling: wicket.util.lang.Objects.setObjectStreamFactory(new
IObjectStreamFactory.DefaultObjectStreamFactory()) e.g. in the init
method of your application
i think there is a bug in our optimized serialization where it doesnt
handle proxies properly yet
-igor
On 3/6/07, Michel Wichers [EMAIL PROTECTED] wrote:
Hi all,
we received the following exception within a WebPage using an injected
SpringBean - HibernateSessionFactory via sublassed
LocalSessionFactoryBean :
ERROR - Objects : Error serializing object class
de.ponton.box.core.ui.detail.Detail [object=[Page class =
de.ponton.box.core.ui.detail.Detail, id = 0, version = 0]]
wicket.util.io.WicketSerializeableException: Error writing fields for
wicket.proxy.$Proxy7
de.ponton.box.core.ui.detail.Detail-sessionFactory
NOTE: if you feel Wicket is at fault with this exception, please report
to the mailing list. You can switch to JDK based serialization by
calling: wicket.util.lang.Objects.setObjectStreamFactory (new
IObjectStreamFactory.DefaultObjectStreamFactory()) e.g. in the init
method of your application
at
wicket.util.io.WicketObjectOutputStream.writeObjectOverride(
WicketObjectOutputStream.java:806)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java
:298)
at
wicket.util.io.ClassStreamHandler$ObjectFieldAndIndex.writeField(
ClassStreamHandler.java:860)
at
wicket.util.io.ClassStreamHandler.writeFields (ClassStreamHandler.java
:387)
at
wicket.util.io.WicketObjectOutputStream.writeObjectOverride(
WicketObjectOutputStream.java:779)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java
:298)
at wicket.util.lang.Objects.objectToByteArray(Objects.java:1102)
at
wicket.protocol.http.FilePageStore.serializePage(FilePageStore.java:408)
at wicket.protocol.http.FilePageStore.access$1500(FilePageStore.java:49)
at
wicket.protocol.http.FilePageStore$PageSerializingThread.run(
FilePageStore.java:705)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
at
wicket.util.io.ClassStreamHandler.writeFields (ClassStreamHandler.java
:397)
at
wicket.util.io.WicketObjectOutputStream.writeObjectOverride(
WicketObjectOutputStream.java:779)
... 10 more
ERROR - FilePageStore$PageSerializingThread : Error in page save thread
java.lang.NullPointerException
at
wicket.protocol.http.FilePageStore.serializePage(FilePageStore.java:413)
at wicket.protocol.http.FilePageStore.access$1500(FilePageStore.java
:49)
at
wicket.protocol.http.FilePageStore$PageSerializingThread.run (
FilePageStore.java:705)
at java.lang.Thread.run(Thread.java:595)
shouldn't happen
Here is the applicationContextSnippet:
...
bean id=mergedSessionFactory
class= de.ponton.box.core.bootstrap.DynamicSessionFactoryBean
singleton=true
property name=dataSource
ref bean=dataSource /
/property
we are subclassing LocalSessionFactoryBean from spring:
...
public class DynamicSessionFactoryBean extends LocalSessionFactoryBean
{
...
and here is the code snippet:
@SpringBean
SessionFactory sessionFactory;
This has worked with Wicket 1.2.5...
Any ideas?
--
Best regards / Mit freundlichen Grüßen
Michel Wichers
_
Ponton Consulting GmbH voice: +49.40.69213-340
http://www.ponton-consulting.de/ fax:+49.40.69213-355
Dorotheenstrasse 60mobile: +49.175.566 9970
D-22301 Hamburgmailto:[EMAIL PROTECTED]
_
HRB 81480, AG Hamburg, Managing Director: Dr. Michael Merz
Ponton Consulting is a Member of C1 Group (www.c1-group.com)
_
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief
Re: [Wicket-user] StatelessForm and setRedirect(true) in the onSubmit method
yes a submit will always be redirected so what happens if you don't do
setRedirect(true)
are you then not getting that expired page??
does the onSubmit really be called? Or is that already the expired page?
johan
On 3/5/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
dont know if there is a problem with stateless pages and redirects, but
wicket's default redirect-to-buffer render strategy should already eliminate
that popup by performing a redirect
-igor
On 3/5/07, Matthew Kwong [EMAIL PROTECTED] wrote:
Hi guys,
I encountered a problem in the stateless form, which is in my login
page.
The form code is as below:
public final void onSubmit() {
// Get session info
DataStoreSession session = (DataStoreSession)getSession();
// Sign the user in
if (session.authenticate(username, password)) {
if (!continueToOriginalDestination()) {
setRedirect(true);
setResponsePage(new DataStoreTabbedPanelPage());
}
}
else {
error(getLocalizer().getString(loginError, this, Unable to
sign
you in));
}
}
DataStoreTabbedPanelPage is a stateful page with all the components and
panels. The session is also created after submit. However, when I click
other pages, it gives me Expired Page. The reason I want to redirect
because
when the user successfully login, and press F5, firefox gives them a
popup
for them to resubmit the form and create another session.
Is there any problem with the setRedirect(true) in stateless form?
Matthew Kwong
--
View this message in context:
http://www.nabble.com/StatelessForm-and-setRedirect%28true%29-in-the-onSubmit-method-tf3347688.html#a9308281
Sent from the Wicket - User mailing list archive at Nabble.com.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] NPE in Page#componentStateChanging
this is very strange because as far as i know that flag is only set inside
that if:
if (!getFlag(FLAG_NEW_VERSION)) -- this may return false?
{
// if we have no version manager
if (versionManager == null)
{
// then install a new version manager
versionManager = newVersionManager();
}
// start a new version
versionManager.beginVersion
(getRequest().mergeVersion());
setFlag(FLAG_NEW_VERSION, true);
}
But i guess versionManager is in some places set to null gain.. Is then that
flag not reset?
johan
On 3/5/07, Aaron Hiniker [EMAIL PROTECTED] wrote:
I ran this through my debugger, and my assumptions where correct. The
FLAG_NEW_VERSION flag is set while versionManager is null. I'm, looking
around and can't figure out the exact conditions that would cause this.
Any thoughts?
Aaron
Aaron Hiniker wrote:
Yeah, I know. But I'm not messing with any versioning settings (this is
just out-of-the-box ajax components and the like), so really there shouldn't
be any of these issues, correct? Here's mayTrackChangesFor() method, I've
added a comment regarding my thoughts as to what is causing this:
private final boolean mayTrackChangesFor(final Component component,
MarkupContainer parent)
{
// Auto components do not participate in versioning since they are
// added during the rendering phase (which is normally illegal).
if (component.isAuto() || (parent == null
!component.isVersioned())
|| (parent != null !parent.isVersioned()))
{
return false;
}
else
{
// the component is versioned... are we tracking changes at
all?
if (getFlag(FLAG_TRACK_CHANGES)) -- this returns true
{
// we are tracking changes... do we need to start new
version?
if (!getFlag(FLAG_NEW_VERSION)) -- this may return
false?
{
// if we have no version manager
if (versionManager == null)
{
// then install a new version manager
versionManager = newVersionManager();
}
// start a new version
versionManager.beginVersion
(getRequest().mergeVersion());
setFlag(FLAG_NEW_VERSION, true);
}
// this returns true, even though versionManager is not
set because of false check above
// return true as we are ready for versioning
return true;
}
// we are not tracking changes or the component not versioned
return false;
}
}
Should I specifically be setting versioning/non-versioning for components
to avoid this error?
Aaron
Johan Compagner wrote:
But if it is null then you could have a problem that things should be
versioned but arent..
So adding null checks is not the fix.
johan
On 3/2/07, Aaron HIniker [EMAIL PROTECTED] wrote:
That's why I was pointing at mayTrackChangesFor().. I looked at the
method and I can't see a loophole, but there must be one to generate an NPE,
correct?
When I implemented the not-null check, I noticed exceptions still being
thrown from 2 other methods (if you search Page.java for versionManager,
you can see where there is the assumption that mayTrackChangesFor() is
checked for 'true', yet versionManager is never initialized in other methods
as well. So after adding the null check to each of these methods, the
application is working fine. Thing is, I've only seen this exception when
dealing with ajax (default not versioned, right?).
I will try and run a debugger through mayTrackChangesFor() with my
current app, and see the logic flow and why versionManager is ending up
null.
Aaron
Johan Compagner wrote:
That is because the mayTrackChangesFor() method should only return true
when it makes a version manager. Why is that not the case?
If that method returns true the version manager can't be null because
the version info must be tracked.
johan
On 3/1/07, Aaron Hiniker [EMAIL PROTECTED] wrote:
I pulled the latest from trunk. And I am getting this NPE:
16:30:14,543 ERROR [STDERR] java.lang.NullPointerException
16:30:14,544 ERROR [STDERR] at
wicket.Page.componentStateChanging(Page.java:327)
16:30:14,545 ERROR [STDERR] at
wicket.Component.addStateChange(Component.java:2553)
16:30:14,545 ERROR [STDERR] at
wicket.Component.setModel(Component.java:2191)
16:30:14,545 ERROR [STDERR] at
wicket.MarkupContainer.setModel(MarkupContainer.java :596)
16:30:14,546 ERROR [STDERR] at
com.edicorp.erp.web.components.search.ProductSearchPanel.query(
ProductSearchPanel.java:144)
Re: [Wicket-user] Exception using @SpringBean and HibernateSessionFactory - wicket 1.3
Michel Wichers wrote: we received the following exception within a WebPage using an injected SpringBean - HibernateSessionFactory via sublassed LocalSessionFactoryBean : ... de.ponton.box.core.ui.detail.Detail-sessionFactory It looks to me like that class has a reference to sessionFactory. Needless to say, you shouldn't do that! You can't serialise your session factory - it has connections to the database, etc. So I don't think this is a bug in our serialization, but instead someone having a SessionFactory reference where they shouldn't. Al - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Exception using @SpringBean and HibernateSessionFactory - wicket 1.3
if its injected through @springbean its ok -igor On 3/6/07, Al Maw [EMAIL PROTECTED] wrote: Michel Wichers wrote: we received the following exception within a WebPage using an injected SpringBean - HibernateSessionFactory via sublassed LocalSessionFactoryBean : ... de.ponton.box.core.ui.detail.Detail-sessionFactory It looks to me like that class has a reference to sessionFactory. Needless to say, you shouldn't do that! You can't serialise your session factory - it has connections to the database, etc. So I don't think this is a bug in our serialization, but instead someone having a SessionFactory reference where they shouldn't. Al - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
[Wicket-user] pop window error
when i used a pop window or select open a new window for current link, some error happens it' seems I have to serializable PropertyDescProxy ? ERROR wicket.markup.html.WebPage - Page [Page class = com.toyshop.web.PayPage, id = 4] couldn't be cloned to move to another pagemap java.lang.ClassCastException: cannot assign instance of $Proxy10 to field com.toyshop.FormBuilder$PropertyDescProxy.desc of type com.toyshop.domain.PropertyDesc in instance of com.toyshop.FormBuilder$PropertyDescProxy at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamClass.java:2004) at java.io.ObjectStreamClass.setObjFieldValues(ObjectStreamClass.java:1184) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1914) 蒙 09:35:39 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] NPE in Page#componentStateChanging
Line #601 in Page.java is the only place where versionManager gets set
back to null from what I can tell..
// If we went all the way back to the
original page
if (page != null
page.getCurrentVersionNumber() == 0)
{
// remove version info
page.versionManager = null;
}
I am using bookmarkable pages, without an immediate redirect to a Page
instance, do bookmarkable pages stay on version 0 when invoking an ajax
component?
Or should this be set to a new instance of VersionManager instead of null?
Aaron
Johan Compagner wrote:
this is very strange because as far as i know that flag is only set
inside that if:
if (!getFlag(FLAG_NEW_VERSION)) -- this may return false?
{
// if we have no version manager
if (versionManager == null)
{
// then install a new version manager
versionManager = newVersionManager();
}
// start a new version
versionManager.beginVersion(getRequest().mergeVersion());
setFlag(FLAG_NEW_VERSION, true);
}
But i guess versionManager is in some places set to null gain.. Is
then that flag not reset?
johan
On 3/5/07, *Aaron Hiniker * [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
I ran this through my debugger, and my assumptions where correct.
The FLAG_NEW_VERSION flag is set while versionManager is null.
I'm, looking around and can't figure out the exact conditions that
would cause this.
Any thoughts?
Aaron
Aaron Hiniker wrote:
Yeah, I know. But I'm not messing with any versioning settings
(this is just out-of-the-box ajax components and the like), so
really there shouldn't be any of these issues, correct? Here's
mayTrackChangesFor() method, I've added a comment regarding my
thoughts as to what is causing this:
private final boolean mayTrackChangesFor(final Component
component, MarkupContainer parent)
{
// Auto components do not participate in versioning since
they are
// added during the rendering phase (which is normally
illegal).
if (component.isAuto() || (parent == null
!component.isVersioned())
|| (parent != null !parent.isVersioned()))
{
return false;
}
else
{
// the component is versioned... are we tracking
changes at all?
if (getFlag(FLAG_TRACK_CHANGES)) -- this returns true
{
// we are tracking changes... do we need to start
new version?
if (!getFlag(FLAG_NEW_VERSION)) -- this may
return false?
{
// if we have no version manager
if (versionManager == null)
{
// then install a new version manager
versionManager = newVersionManager();
}
// start a new version
versionManager.beginVersion(getRequest().mergeVersion());
setFlag(FLAG_NEW_VERSION, true);
}
// this returns true, even though versionManager
is not set because of false check above
// return true as we are ready for versioning
return true;
}
// we are not tracking changes or the component not
versioned
return false;
}
}
Should I specifically be setting versioning/non-versioning for
components to avoid this error?
Aaron
Johan Compagner wrote:
But if it is null then you could have a problem that things
should be versioned but arent..
So adding null checks is not the fix.
johan
On 3/2/07, * Aaron HIniker* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
That's why I was pointing at mayTrackChangesFor().. I
looked at the method and I can't see a loophole, but there
must be one to generate an NPE, correct?
When I implemented the not-null check, I noticed exceptions
still being thrown from 2 other methods (if you search
Page.java for versionManager, you can see where there is the
assumption that mayTrackChangesFor() is checked for 'true',
yet versionManager is never initialized in other methods as
well. So after adding the null check to each of these
methods, the application
[Wicket-user] how to set the readonly data in wicket form
When i set the html element to readonly or disabled , the wicket form cannot get the value of these specficed field. and I have control these fields accord to the different user. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] how to set the readonly data in wicket form
So you should set them only disabled according to specific user attributes. See wicket.authorization.Action.ENABLE for something that is useful in this context. Eelco On 3/6/07, tooy li(Gmail) [EMAIL PROTECTED] wrote: When i set the html element to readonly or disabled , the wicket form cannot get the value of these specficed field. and I have control these fields accord to the different user. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] how to set the readonly data in wicket form
Or more quick and dirty, override isEnabled of the components you target and let it return true or false depending on the current user. Eelco On 3/6/07, Eelco Hillenius [EMAIL PROTECTED] wrote: So you should set them only disabled according to specific user attributes. See wicket.authorization.Action.ENABLE for something that is useful in this context. Eelco On 3/6/07, tooy li(Gmail) [EMAIL PROTECTED] wrote: When i set the html element to readonly or disabled , the wicket form cannot get the value of these specficed field. and I have control these fields accord to the different user. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
well as long as there are workarounds, i'm fine with dropping the constructor change if everyone else seems to feel this way and there aren't any better arguments for it. Eelco Hillenius wrote: i don't care to much about accessing markup attributes in the constructor because i don't care much about driving code from markup. If you create components that are based on or work together with Javascript components, this is a nice feature to have. Driving code from markup sounds more negative than it is, as when working with ajax and javascript, you *need* this, and the ability to do it at any time is nice. There are workarounds, and I found that in the end I'm often coupling such components on render time anyway (e.g. using header contributors with LoadableDetachableModels). Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/IMPORTANT%3A-your-opinion-on-the-constructor-change-in-2.0-tf3358738.html#a9346362 Sent from the Wicket - User mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
Well, I'm not a core committer , so dont have enough vision to talk about the internal effects of the change, but as a user from the pre-1 versions of wicket till now(1.2.5), here are some humble opinions: pros: * free to call any method in the constructor like getpage(), urlfor(), etc. * access to markup attributes in constructor as opposed to render time I dont know why, but I've never felt any need for these two. Maybe I'm used to passing dependencies to child components, instead of letting them access the parent page. But these two have never been a problem for me . * fail at component instantiation time rather then render time if there is a hierarchy-java mismatch - so you get a java line-precise error as opposed to our error webpage In 80% of my usecases, I use the component as soon as I instantiate it, so this is really considered a minor improvement in my domain. cons: * code explosion 2.0: http://papernapkin.org/pastebin/view/4900 1.3: http://papernapkin.org/pastebin/view/4908 Now, I already preferred the add() method way over the new(parent,...) way, just because of clarity and maybe because I'm used to it. But this example is really frightening me. It's got way too complicated instead of simpler, and clean readable code is really REALLY important. Consider a newbie, looking for the first time at these two codes. Which one would be easier for him to understand ? * hacks necessary for nontrivial components GridView.populate() http://papernapkin.org/pastebin/view/4902 notice fake1,fake2 parents necessary for child item instantiation and which are later * more limited in how the hierarchy is created since it MUST be created top-down * replacing components is less explicit. 1.3: a.replaceWith(new B()); 2.0: new B(a.getParent(), a.getId()); again, code is getting uglier :-( Some other thoughts : * Converting 1.x code to 2.x is really really hard this way. If it would've been easier, I guess many users (including myself) would've started to use 2.x codebase right now. The amount of feedback and test you would get by that is enormous. But, considering how much code I have working with 1.x and how much pain it would have migrating to 2, I've left it out for my next project. * One of the best features I'm hoping for in 2.x is the Java 5 support, like covariant return types, Generics and stuff. Surely they would make my page's much cleaner and readable. But wicked is way too slow in adopting jdk5, and I see the problem is the enormous constructor change getting in its way. I cant estimate the amount of man-hour work needed to finish 2, but maybe a good 6 months is needed. Now that everybody is talking about the new features in Java 7, we still have to work with Java 1.4 style of code. Or maybe when 7 is out, we could finally use 5 ? ;-) As a user I'm very happy with the current features and possibilities in wicket, and am only waiting for the changes(stateless forms, page cache, ... ) in 1.3. My main dissatisfaction is some ugly code I'm forced to write which can be easily improved. Like I'm really sick of the casting and the always null parameter in : myObject = (MyObject) myModel.getObject(null); Just my 2c ! - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] NPE in Page#componentStateChanging
normally ajax shouldn't make a new version but in 1.3 we have also an ajax
version number beside the page version number.
But that the moment page.versionManager is set to null the flag should be
false at that time.
But if you have a quick test that exposes this null pointer please make an
issue and attach it.
On 3/7/07, Aaron HIniker [EMAIL PROTECTED] wrote:
Line #601 in Page.java is the only place where versionManager gets set
back to null from what I can tell..
// If we went all the way back to the
original page
if (page != null
page.getCurrentVersionNumber() == 0)
{
// remove version info
page.versionManager = null;
}
I am using bookmarkable pages, without an immediate redirect to a Page
instance, do bookmarkable pages stay on version 0 when invoking an ajax
component?
Or should this be set to a new instance of VersionManager instead of null?
Aaron
Johan Compagner wrote:
this is very strange because as far as i know that flag is only set inside
that if:
if (!getFlag(FLAG_NEW_VERSION)) -- this may return false?
{
// if we have no version manager
if (versionManager == null)
{
// then install a new version manager
versionManager = newVersionManager();
}
// start a new version
versionManager.beginVersion
(getRequest().mergeVersion());
setFlag(FLAG_NEW_VERSION, true);
}
But i guess versionManager is in some places set to null gain.. Is then
that flag not reset?
johan
On 3/5/07, Aaron Hiniker [EMAIL PROTECTED] wrote:
I ran this through my debugger, and my assumptions where correct. The
FLAG_NEW_VERSION flag is set while versionManager is null. I'm, looking
around and can't figure out the exact conditions that would cause this.
Any thoughts?
Aaron
Aaron Hiniker wrote:
Yeah, I know. But I'm not messing with any versioning settings (this
is just out-of-the-box ajax components and the like), so really there
shouldn't be any of these issues, correct? Here's mayTrackChangesFor()
method, I've added a comment regarding my thoughts as to what is causing
this:
private final boolean mayTrackChangesFor(final Component component,
MarkupContainer parent)
{
// Auto components do not participate in versioning since they
are
// added during the rendering phase (which is normally illegal).
if (component.isAuto() || (parent == null
!component.isVersioned())
|| (parent != null !parent.isVersioned()))
{
return false;
}
else
{
// the component is versioned... are we tracking changes at
all?
if (getFlag(FLAG_TRACK_CHANGES)) -- this returns true
{
// we are tracking changes... do we need to start new
version?
if (!getFlag(FLAG_NEW_VERSION)) -- this may return
false?
{
// if we have no version manager
if (versionManager == null)
{
// then install a new version manager
versionManager = newVersionManager();
}
// start a new version
versionManager.beginVersion
(getRequest().mergeVersion());
setFlag(FLAG_NEW_VERSION, true);
}
// this returns true, even though versionManager is not
set because of false check above
// return true as we are ready for versioning
return true;
}
// we are not tracking changes or the component not
versioned
return false;
}
}
Should I specifically be setting versioning/non-versioning for
components to avoid this error?
Aaron
Johan Compagner wrote:
But if it is null then you could have a problem that things should be
versioned but arent..
So adding null checks is not the fix.
johan
On 3/2/07, Aaron HIniker [EMAIL PROTECTED] wrote:
That's why I was pointing at mayTrackChangesFor().. I looked at the
method and I can't see a loophole, but there must be one to generate an NPE,
correct?
When I implemented the not-null check, I noticed exceptions still
being thrown from 2 other methods (if you search Page.java for
versionManager, you can see where there is the assumption that
mayTrackChangesFor() is checked for 'true', yet versionManager is never
initialized in other methods as well. So after adding the null check to
each of these methods, the application is working fine. Thing is, I've only
Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
As a user I'm very happy with the current features and possibilities in wicket, and am only waiting for the changes(stateless forms, Stateless pages, forms and links are already backported to 1.3! page cache, ... The SecondLevelCacheSessionStore? Already in 1.3 :) ) in 1.3. My main dissatisfaction is some ugly code I'm forced to write which can be easily improved. Like I'm really sick of the casting and the always null parameter in : myObject = (MyObject) myModel.getObject (null); Agreed. We've been talking about backporting 2.0's models. Mind you that the main pain point in this whole thing - besides maintaining two branches - is the constructor change, which we are starting to regret now. The model change definitively was for the better. Generics might be applied in a separate version. Just my 2c ! Thanks Iman! Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0
On 3/7/07, Eelco Hillenius [EMAIL PROTECTED] wrote: As a user I'm very happy with the current features and possibilities in wicket, and am only waiting for the changes(stateless forms, Stateless pages, forms and links are already backported to 1.3! page cache, ... The SecondLevelCacheSessionStore? Already in 1.3 :) Yes, that was my point. The only features I feel missing are the ones available in 1.3 (since I'm using 1.2.x right now) and the Java 5 features. ) in 1.3. My main dissatisfaction is some ugly code I'm forced to write which can be easily improved. Like I'm really sick of the casting and the always null parameter in : myObject = (MyObject) myModel.getObject (null); Agreed. We've been talking about backporting 2.0's models. Mind you that the main pain point in this whole thing - besides maintaining two branches - is the constructor change, which we are starting to regret now. The model change definitively was for the better. Generics might be applied in a separate version. So , I feel the trend is towards reversing the change ... heeheee ! ;-) Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] NPE in Page#componentStateChanging
I've experienced the exact same problem. You'll get this a lot when working
with ajax components. I've also reported this issue to the wicket 2 jira. If
you add if(versionManger != null) prior to the versionManager call you'll be
fine but that's probably an ugly hack. But it seem to work til they've
actually fixed it.
Aaron Hiniker-2 wrote:
I pulled the latest from trunk. And I am getting this NPE:
16:30:14,543 ERROR [STDERR] java.lang.NullPointerException
16:30:14,544 ERROR [STDERR] at
wicket.Page.componentStateChanging(Page.java:327)
16:30:14,545 ERROR [STDERR] at
wicket.Component.addStateChange(Component.java:2553)
16:30:14,545 ERROR [STDERR] at
wicket.Component.setModel(Component.java:2191)
16:30:14,545 ERROR [STDERR] at
wicket.MarkupContainer.setModel(MarkupContainer.java:596)
16:30:14,546 ERROR [STDERR] at
com.edicorp.erp.web.components.search.ProductSearchPanel.query(ProductSearchPanel.java:144)
16:30:14,546 ERROR [STDERR] at
com.edicorp.erp.web.components.search.ProductSearchPanel.onUpdate(ProductSearchPanel.java:109)
16:30:14,546 ERROR [STDERR] at
com.edicorp.erp.web.components.search.FilterPanel.fireOnChange(FilterPanel.java:74)
16:30:14,547 ERROR [STDERR] at
com.edicorp.erp.web.components.search.query.QueryPanel$QueryForm.onSubmit(QueryPanel.java:197)
16:30:14,547 ERROR [STDERR] at
wicket.markup.html.form.Form.delegateSubmit(Form.java:680)
16:30:14,547 ERROR [STDERR] at
wicket.markup.html.form.Form.onFormSubmitted(Form.java:396)
16:30:14,547 ERROR [STDERR] at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
I remember I was getting this NPE before, and I patched the source to
include this null check in Page.java:
final void componentStateChanging(final Component component,
Change change)
{
checkHierarchyChange(component);
dirty();
if (mayTrackChangesFor(component, null))
{
if ( versionManager != null )
versionManager.componentStateChanging(change);
}
}
It seems that everywhere else in Page.java there is a null check for
versionManager, except in this method. Not sure, but perhaps the
problem lies in the #mayTrackChangesFor() method, but in any case if I
add this null check my code runs fine.
Aaron
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
--
View this message in context:
http://www.nabble.com/NPE-in-Page-componentStateChanging-tf3330773.html#a9347814
Sent from the Wicket - User mailing list archive at Nabble.com.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Exception using @SpringBean and HibernateSessionFactory - wicket 1.3
Hi Igor,
using the default factory works ... however a fix would be great ;-)
Thanks for your help.
Regards,
Michel
Igor Vaynberg schrieb:
do like the message says:
You can switch to JDK based serialization by
calling: wicket.util.lang.Objects
.setObjectStreamFactory(new
IObjectStreamFactory.DefaultObjectStreamFactory()) e.g. in the init
method of your application
i think there is a bug in our optimized serialization where it doesnt
handle proxies properly yet
-igor
On 3/6/07, *Michel Wichers* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi all,
we received the following exception within a WebPage using an injected
SpringBean - HibernateSessionFactory via sublassed
LocalSessionFactoryBean :
ERROR - Objects : Error serializing object class
de.ponton.box.core.ui.detail.Detail [object=[Page class =
de.ponton.box.core.ui.detail.Detail, id = 0, version = 0]]
wicket.util.io.WicketSerializeableException: Error writing fields for
wicket.proxy.$Proxy7
de.ponton.box.core.ui.detail.Detail-sessionFactory
NOTE: if you feel Wicket is at fault with this exception, please
report
to the mailing list. You can switch to JDK based serialization by
calling: wicket.util.lang.Objects.setObjectStreamFactory (new
IObjectStreamFactory.DefaultObjectStreamFactory()) e.g. in the init
method of your application
at
wicket.util.io.WicketObjectOutputStream.writeObjectOverride(WicketObjectOutputStream.java:806)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:298)
at
wicket.util.io.ClassStreamHandler$ObjectFieldAndIndex.writeField(ClassStreamHandler.java:860)
at
wicket.util.io.ClassStreamHandler.writeFields
(ClassStreamHandler.java:387)
at
wicket.util.io.WicketObjectOutputStream.writeObjectOverride(WicketObjectOutputStream.java:779)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:298)
at wicket.util.lang.Objects.objectToByteArray(Objects.java:1102)
at
wicket.protocol.http.FilePageStore.serializePage(FilePageStore.java:408)
at
wicket.protocol.http.FilePageStore.access$1500(FilePageStore.java :49)
at
wicket.protocol.http.FilePageStore$PageSerializingThread.run(FilePageStore.java:705)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
at
wicket.util.io.ClassStreamHandler.writeFields
(ClassStreamHandler.java:397)
at
wicket.util.io.WicketObjectOutputStream.writeObjectOverride(WicketObjectOutputStream.java:779)
... 10 more
ERROR - FilePageStore$PageSerializingThread : Error in page save
thread
java.lang.NullPointerException
at
wicket.protocol.http.FilePageStore.serializePage(FilePageStore.java:413)
at
wicket.protocol.http.FilePageStore.access$1500(FilePageStore.java:49)
at
wicket.protocol.http.FilePageStore$PageSerializingThread.run
(FilePageStore.java:705)
at java.lang.Thread.run(Thread.java:595)
shouldn't happen
Here is the applicationContextSnippet:
...
bean id=mergedSessionFactory
class=
de.ponton.box.core.bootstrap.DynamicSessionFactoryBean
singleton=true
property name=dataSource
ref bean=dataSource /
/property
we are subclassing LocalSessionFactoryBean from spring:
...
public class DynamicSessionFactoryBean extends LocalSessionFactoryBean
{
...
and here is the code snippet:
@SpringBean
SessionFactory sessionFactory;
This has worked with Wicket 1.2.5...
Any ideas?
--
Best regards / Mit freundlichen Grüßen
Michel Wichers
_
Ponton Consulting GmbH voice: +49.40.69213-340
http://www.ponton-consulting.de/ fax:+49.40.69213-355
Dorotheenstrasse 60mobile: +49.175.566 9970
D-22301
Hamburgmailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
_
HRB 81480, AG Hamburg, Managing Director: Dr. Michael Merz
Ponton Consulting is a Member of C1 Group (www.c1-group.com
http://www.c1-group.com)
_
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to
share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
Re: [Wicket-user] Exception using @SpringBean and HibernateSessionFactory - wicket 1.3
create a jira issue and assign it to johan :)
-igor
On 3/6/07, Michel Wichers [EMAIL PROTECTED] wrote:
Hi Igor,
using the default factory works ... however a fix would be great ;-)
Thanks for your help.
Regards,
Michel
Igor Vaynberg schrieb:
do like the message says:
You can switch to JDK based serialization by
calling: wicket.util.lang.Objects
.setObjectStreamFactory(new
IObjectStreamFactory.DefaultObjectStreamFactory()) e.g. in the init
method of your application
i think there is a bug in our optimized serialization where it doesnt
handle proxies properly yet
-igor
On 3/6/07, *Michel Wichers* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi all,
we received the following exception within a WebPage using an
injected
SpringBean - HibernateSessionFactory via sublassed
LocalSessionFactoryBean :
ERROR - Objects : Error serializing object class
de.ponton.box.core.ui.detail.Detail [object=[Page class =
de.ponton.box.core.ui.detail.Detail, id = 0, version = 0]]
wicket.util.io.WicketSerializeableException: Error writing fields
for
wicket.proxy.$Proxy7
de.ponton.box.core.ui.detail.Detail-sessionFactory
NOTE: if you feel Wicket is at fault with this exception, please
report
to the mailing list. You can switch to JDK based serialization by
calling: wicket.util.lang.Objects.setObjectStreamFactory (new
IObjectStreamFactory.DefaultObjectStreamFactory()) e.g. in the init
method of your application
at
wicket.util.io.WicketObjectOutputStream.writeObjectOverride(
WicketObjectOutputStream.java:806)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:298)
at
wicket.util.io.ClassStreamHandler$ObjectFieldAndIndex.writeField(
ClassStreamHandler.java:860)
at
wicket.util.io.ClassStreamHandler.writeFields
(ClassStreamHandler.java:387)
at
wicket.util.io.WicketObjectOutputStream.writeObjectOverride(
WicketObjectOutputStream.java:779)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:298)
at wicket.util.lang.Objects.objectToByteArray(Objects.java:1102)
at
wicket.protocol.http.FilePageStore.serializePage(FilePageStore.java
:408)
at
wicket.protocol.http.FilePageStore.access$1500(FilePageStore.java:49)
at
wicket.protocol.http.FilePageStore$PageSerializingThread.run(
FilePageStore.java:705)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
at
wicket.util.io.ClassStreamHandler.writeFields
(ClassStreamHandler.java:397)
at
wicket.util.io.WicketObjectOutputStream.writeObjectOverride(
WicketObjectOutputStream.java:779)
... 10 more
ERROR - FilePageStore$PageSerializingThread : Error in page save
thread
java.lang.NullPointerException
at
wicket.protocol.http.FilePageStore.serializePage(FilePageStore.java
:413)
at
wicket.protocol.http.FilePageStore.access$1500(FilePageStore.java
:49)
at
wicket.protocol.http.FilePageStore$PageSerializingThread.run
(FilePageStore.java:705)
at java.lang.Thread.run(Thread.java:595)
shouldn't happen
Here is the applicationContextSnippet:
...
bean id=mergedSessionFactory
class=
de.ponton.box.core.bootstrap.DynamicSessionFactoryBean
singleton=true
property name=dataSource
ref bean=dataSource /
/property
we are subclassing LocalSessionFactoryBean from spring:
...
public class DynamicSessionFactoryBean extends
LocalSessionFactoryBean
{
...
and here is the code snippet:
@SpringBean
SessionFactory sessionFactory;
This has worked with Wicket 1.2.5...
Any ideas?
--
Best regards / Mit freundlichen Grüßen
Michel Wichers
_
Ponton Consulting GmbH voice: +49.40.69213-340
http://www.ponton-consulting.de/ fax:+49.40.69213-355
Dorotheenstrasse 60mobile: +49.175.566 9970
D-22301
Hamburgmailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
_
HRB 81480, AG Hamburg, Managing Director: Dr. Michael Merz
Ponton Consulting is a Member of C1 Group (www.c1-group.com
http://www.c1-group.com)
_
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to
share your
opinions on IT business topics through brief surveys-and earn cash
