Re: Upgrade to 6.5.0
You're sure the application class is com.myApp.myAppApp? Looks like an accidental duplication of myApp. Sven On 01/26/2013 11:36 PM, Stephen Walsh wrote: Caused by: java.lang.ClassNotFoundException: com.myApp.myAppApp from [Module deployment.myApp- - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: [6.0] CouldNotLockPageException
Better find out why it takes that long and try to make the request processing faster. On Sat, Jan 26, 2013 at 9:21 PM, Pierre Goupil goupilpie...@gmail.comwrote: Thanks a lot, it works! Cheers, Pierre On Sat, Jan 26, 2013 at 7:00 PM, Sven Meier s...@meiers.net wrote: You can adjust IRequestCycleSettings#**setTimeout(). Sven On 01/26/2013 06:03 PM, Pierre Goupil wrote: Good afternoon, When debugging through my Wicket code, I often get this exception: CouldNotLockPageException: Could not lock page 1. Attempt lasted 1 minute Is there anything I can do to rise up this timeout, please? Regards, Pierre Goupil --**--**- To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Parce que c'est la nuit qu'il est beau de croire à la lumière. Edmond Rostand -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com http://jweekend.com/
Re: Load Image in IE fails
Try the solution explained at http://markmail.org/thread/5sbhcqbjxxb7arwy On Sat, Jan 26, 2013 at 8:44 PM, Satrix satrix...@gmail.com wrote: Hi, Im using 1.5.8 Wicket version and IE 9. Regards -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Load-Image-in-IE-fails-tp4655776p4655780.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com http://jweekend.com/
Re: [6.0] CouldNotLockPageException
As I said, it's only when using (Eclipse) debugger. When I go from methods to breakpoints and back again, only one minute is a bit short. But with Sven's solution, I have what I need. Cheers, men! Pierre On Sun, Jan 27, 2013 at 12:35 PM, Martin Grigorov mgrigo...@apache.orgwrote: Better find out why it takes that long and try to make the request processing faster. On Sat, Jan 26, 2013 at 9:21 PM, Pierre Goupil goupilpie...@gmail.com wrote: Thanks a lot, it works! Cheers, Pierre On Sat, Jan 26, 2013 at 7:00 PM, Sven Meier s...@meiers.net wrote: You can adjust IRequestCycleSettings#**setTimeout(). Sven On 01/26/2013 06:03 PM, Pierre Goupil wrote: Good afternoon, When debugging through my Wicket code, I often get this exception: CouldNotLockPageException: Could not lock page 1. Attempt lasted 1 minute Is there anything I can do to rise up this timeout, please? Regards, Pierre Goupil --**--**- To unsubscribe, e-mail: users-unsubscribe@wicket.**apache.org users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Parce que c'est la nuit qu'il est beau de croire à la lumière. Edmond Rostand -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com http://jweekend.com/ -- Parce que c'est la nuit qu'il est beau de croire à la lumière. Edmond Rostand
Preventing inner form processing?
Hi all,
I have an inner form, and I would like this inner form to not being
processed when the parent form is submitted, like described here:
https://cwiki.apache.org/WICKET/conditional-validation.html
The problem, in my case, is that this inner-form is posted with
'wicketSubmitFormById', so do I not have any submitting button and
#findSubmittingButton naturally returns null.
But as I am processing the form using an IFormSubmitter, I would like to
write something that could looks like this (in my inner form):
public boolean processChildren()
{
IFormSubmitter submitter = this.getFormSubmitter(); //!\\
return submitter != null submitter.getForm() == this;
}
But I do not have any equivalent for #getFormSubmitter()...
Any ideas?
Thanks in advance,
Sebastien.
Re: Upgrade to 6.5.0
I did a find and replace to remove the app name. That was an oversight. __ Stephen Walsh | http://connectwithawalsh.com On Jan 27, 2013, at 5:07, Sven Meier s...@meiers.net wrote: You're sure the application class is com.myApp.myAppApp? Looks like an accidental duplication of myApp. Sven On 01/26/2013 11:36 PM, Stephen Walsh wrote: Caused by: java.lang.ClassNotFoundException: com.myApp.myAppApp from [Module deployment.myApp- - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Upgrade to 6.5.0
Here was the original error: 16:29:29,557 INFO [org.jboss.as.repository] (management-handler-thread - 8) JBAS014900: Content added at location /usr/share/jboss-as-7.1.1.Final/standalone/data/content/2c/fd9a0ad0a567de3c4bfde63b541413297ba7f5/content 16:29:29,617 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of campingawaits-1.0-SNAPSHOT.war 16:29:30,433 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/campingawaits-1.0-SNAPSHOT]] (MSC service thread 1-3) Exception starting filter wicket.campingawaits: org.apache.wicket.WicketRuntimeException: Unable to create application of class com.campingawaits.CampingAwaitsApp at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:86) [wicket-core-6.5.0.jar:6.5.0] at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:50) [wicket-core-6.5.0.jar:6.5.0] at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:370) [wicket-core-6.5.0.jar:6.5.0] at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:336) [wicket-core-6.5.0.jar:6.5.0] at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:447) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3269) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3865) [jbossweb-7.0.13.Final.jar:] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_37] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_37] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37] Caused by: java.lang.ClassNotFoundException: com.campingawaits.CampingAwaitsApp from [Module deployment.campingawaits-1.0-SNAPSHOT.war:main from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) at java.lang.Class.forName0(Native Method) [classes.jar:1.6.0_37] at java.lang.Class.forName(Class.java:247) [classes.jar:1.6.0_37] at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:72) [wicket-core-6.5.0.jar:6.5.0] ... 12 more 16:29:30,469 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-3) Error filterStart 16:29:30,470 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-3) Context [/campingawaits-1.0-SNAPSHOT] startup failed due to previous errors 16:29:30,471 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC1: Failed to start service jboss.web.deployment.default-host./campingawaits-1.0-SNAPSHOT: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./campingawaits-1.0-SNAPSHOT: JBAS018040: Failed to start context at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_37] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_37] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37] 16:29:30,765 INFO [org.jboss.as.server] (management-handler-thread - 8) JBAS018562: Redeployed campingawaits-1.0-SNAPSHOT.war 16:29:30,766 INFO [org.jboss.as.controller] (management-handler-thread - 8) JBAS014774: Service status report JBAS014777: Services which failed to
[ANNOUNCE] WicketStuff 1.5.9.1 is released
Hello, WicketStuff Core projects version 1.5.9.1 have been released and shortly will be available at Maven Central repository. They are built against Apache Wicket 1.5.9. The changelog is: Martin Grigorov (4): Merge pull request #167 from fieona/core-1.5.x Merge pull request #168 from fieona/core-1.5.x Merge pull request #181 from bitstorm/core-1.5.x Merge pull request #136 from jesselong/core-1.5.x Sofie Muys (3): moved jwicket to wicket 1.5, jdk 1.6 + made sure it compiles. Fixed errors and warnings Added idea config dir to gitignore Martin Tzvetanov Grigorov (2): Upgrade to newer maven-compiler-plugin for faster compiling. Fix a typo Release Wicket Stuff 1.5.9.1 bitstorm (2): Fixed image upload plugin for 1.5 branch ...missing css Jesse Long (1): Add ReferenceLoadableDetachableModel - a LoadableDetachableModel that uses a reference (think PK) to the object to load it. Michael Mosmann (1): maven dependency fix The projects can be retrieved from Maven like this: dependency groupIdorg.wicketstuff/groupId artifactIdwicketstuff-progressbar/artifactId version1.5.9.1/version /dependency The release tag is here: https://github.com/wicketstuff/core/tree/wicketstuff-core-1.5.9.1 Issues can be reported here: https://github.com/wicketstuff/core/issues The Project Wiki is available here: https://github.com/wicketstuff/core/wiki The WicketStuff team!
Re: Upgrade to 6.5.0
Also, it seems like this might be a deployment issue, but I'm not sure. I'm using mvn package jboss-as:deploy to get my package into jboss, and after rolling back to 6.0.0, I'm still having the same issue 09:45:27,020 INFO [org.jboss.as.repository] (management-handler-thread - 1) JBAS014900: Content added at location /usr/share/jboss-as-7.1.1.Final/standalone/data/content/a2/dffcda3610a8edc34edcd11ac16fc22eed4591/content 09:45:27,057 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of campingawaits-1.0-SNAPSHOT.war 09:45:27,948 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/campingawaits-1.0-SNAPSHOT]] (MSC service thread 1-3) Exception starting filter wicket.campingawaits: org.apache.wicket.WicketRuntimeException: Unable to create application of class com.campingawaits.CampingAwaitsApp at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:86) [wicket-core-6.0.0.jar:6.0.0] at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:50) [wicket-core-6.0.0.jar:6.0.0] at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:339) [wicket-core-6.0.0.jar:6.0.0] at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:314) [wicket-core-6.0.0.jar:6.0.0] at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:447) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3269) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3865) [jbossweb-7.0.13.Final.jar:] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_37] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_37] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37] Caused by: java.lang.ClassNotFoundException: com.campingawaits.CampingAwaitsApp from [Module deployment.campingawaits-1.0-SNAPSHOT.war:main from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) at java.lang.Class.forName0(Native Method) [classes.jar:1.6.0_37] at java.lang.Class.forName(Class.java:247) [classes.jar:1.6.0_37] at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:72) [wicket-core-6.0.0.jar:6.0.0] ... 12 more 09:45:27,959 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-3) Error filterStart 09:45:27,960 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-3) Context [/campingawaits-1.0-SNAPSHOT] startup failed due to previous errors 09:45:28,111 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC1: Failed to start service jboss.web.deployment.default-host./campingawaits-1.0-SNAPSHOT: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./campingawaits-1.0-SNAPSHOT: JBAS018040: Failed to start context at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_37] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_37] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37] 09:45:28,146 INFO [org.jboss.as.server] (management-handler-thread - 1) JBAS018562: Redeployed
Re: Upgrade to 6.5.0
I'm using the default web.xml. I've never touched it since I've started, but here it is: ?xml version=1.0 encoding=ISO-8859-1? web-app xmlns=http://java.sun.com/xml/ns/javaee; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd; version=2.5 display-namecampingawaits/display-name !-- There are three means to configure Wickets configuration mode and they are tested in the order given. 1) A system property: -Dwicket.configuration 2) servlet specific init-param 3) context specific context-param The value might be either development (reloading when templates change) or deployment. If no configuration is found, development is the default. -- filter filter-namewicket.campingawaits/filter-name filter-classorg.apache.wicket.protocol.http.WicketFilter/filter-class init-param param-nameapplicationClassName/param-name param-valuecom.campingawaits.CampingAwaitsApp/param-value /init-param /filter filter-mapping filter-namewicket.campingawaits/filter-name url-pattern/*/url-pattern /filter-mapping /web-app I ran mvn clean and it was successful. WEB-INF, does have the classes folders and my classes that have been built. I'm not sure what you mean by your last question. I'm on a Mac and using Terminal, Maven, and the j-boss maven plugin to deploy to my jboss install. Update to the above. I ran into the same issue, but now jboss won't even start. I've got a few away from desk items, so I'll have to check this when I get back and after a clean jboss install. Thanks for the help thus far. ___ Stephen Walsh | http://connectwithawalsh.com On Sun, Jan 27, 2013 at 9:52 AM, Stephen Walsh step...@connectwithawalsh.com wrote: Also, it seems like this might be a deployment issue, but I'm not sure. I'm using mvn package jboss-as:deploy to get my package into jboss, and after rolling back to 6.0.0, I'm still having the same issue 09:45:27,020 INFO [org.jboss.as.repository] (management-handler-thread - 1) JBAS014900: Content added at location /usr/share/jboss-as-7.1.1.Final/standalone/data/content/a2/dffcda3610a8edc34edcd11ac16fc22eed4591/content 09:45:27,057 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of campingawaits-1.0-SNAPSHOT.war 09:45:27,948 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/campingawaits-1.0-SNAPSHOT]] (MSC service thread 1-3) Exception starting filter wicket.campingawaits: org.apache.wicket.WicketRuntimeException: Unable to create application of class com.campingawaits.CampingAwaitsApp at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication( ContextParamWebApplicationFactory.java:86) [wicket-core-6.0.0.jar:6.0.0] at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication( ContextParamWebApplicationFactory.java:50) [wicket-core-6.0.0.jar:6.0.0] at org.apache.wicket.protocol.http.WicketFilter.init( WicketFilter.java:339) [wicket-core-6.0.0.jar:6.0.0] at org.apache.wicket.protocol.http.WicketFilter.init( WicketFilter.java:314) [wicket-core-6.0.0.jar:6.0.0] at org.apache.catalina.core.ApplicationFilterConfig.getFilter( ApplicationFilterConfig.java:447) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContext.filterStart( StandardContext.java:3269) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContext.start( StandardContext.java:3865) [jbossweb-7.0.13.Final.jar:] at org.jboss.as.web.deployment.WebDeploymentService.start( WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService( ServiceControllerImpl.java:1811) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run( ServiceControllerImpl.java:1746) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( ThreadPoolExecutor.java:886) [classes.jar:1.6.0_37] at java.util.concurrent.ThreadPoolExecutor$Worker.run( ThreadPoolExecutor.java:908) [classes.jar:1.6.0_37] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37] Caused by: java.lang.ClassNotFoundException: com.campingawaits.CampingAwaitsApp from [Module deployment.campingawaits-1.0-SNAPSHOT.war:main from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass( ModuleClassLoader.java:190) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked( ConcurrentClassLoader.java:468) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked( ConcurrentClassLoader.java:456) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked( ConcurrentClassLoader.java:423) at org.jboss.modules.ConcurrentClassLoader.performLoadClass( ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass( ConcurrentClassLoader.java:120)
ResizableBehavior multiple resizable panels on a page
I have multiple panels on a page, each once constructed as follows:
* public EditableQuestionPanel(String id, final QuestionBaseWebModel
questionBaseWebModel, final TemplateWebModel templateWebModel, final
QuestionEditPanel panel) {*
*super(id);*
*Options options = new Options();*
*options.set(minWidth, 350);*
*options.set(minHeight, 85);*
*add(new ResizableBehavior(#resizable,options));*
Here is the HTML for each panel.
*wicket:panel*
*div id=resizable class=ui-widget-content*
*div class=question wicket:id=holder*
*a href=# wicket:id=editor*
*div id=label wicket:id=questionDisplayPanel*
*/div*
*/a*
* span wicket:id=navpanel/span*
*/div*
*/div*
*/wicket:panel*
I want them each to be resizable but only the first panel ever is.
I am using wicket-jquery-ui. Any idea what I am doing wrong here. Do I have
to give each pane a unique html id attribute?
Pieter
Re: Upgrade to 6.5.0
Well, I got a clean install of jboss and used the web interface to add my war to the deployment area. When I tried to enable it, I got the same errors as below. So I'm still not up and running with either 6.0.0 or 6.5.0. :( On Jan 27, 2013, at 10:03 AM, Stephen Walsh step...@connectwithawalsh.com wrote: I'm using the default web.xml. I've never touched it since I've started, but here it is: ?xml version=1.0 encoding=ISO-8859-1? web-app xmlns=http://java.sun.com/xml/ns/javaee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd; version=2.5 display-namecampingawaits/display-name !-- There are three means to configure Wickets configuration mode and they are tested in the order given. 1) A system property: -Dwicket.configuration 2) servlet specific init-param 3) context specific context-param The value might be either development (reloading when templates change) or deployment. If no configuration is found, development is the default. -- filter filter-namewicket.campingawaits/filter-name filter-classorg.apache.wicket.protocol.http.WicketFilter/filter-class init-param param-nameapplicationClassName/param-name param-valuecom.campingawaits.CampingAwaitsApp/param-value /init-param /filter filter-mapping filter-namewicket.campingawaits/filter-name url-pattern/*/url-pattern /filter-mapping /web-app I ran mvn clean and it was successful. WEB-INF, does have the classes folders and my classes that have been built. I'm not sure what you mean by your last question. I'm on a Mac and using Terminal, Maven, and the j-boss maven plugin to deploy to my jboss install. Update to the above. I ran into the same issue, but now jboss won't even start. I've got a few away from desk items, so I'll have to check this when I get back and after a clean jboss install. Thanks for the help thus far. ___ Stephen Walsh | http://connectwithawalsh.com On Sun, Jan 27, 2013 at 9:52 AM, Stephen Walsh step...@connectwithawalsh.com wrote: Also, it seems like this might be a deployment issue, but I'm not sure. I'm using mvn package jboss-as:deploy to get my package into jboss, and after rolling back to 6.0.0, I'm still having the same issue 09:45:27,020 INFO [org.jboss.as.repository] (management-handler-thread - 1) JBAS014900: Content added at location /usr/share/jboss-as-7.1.1.Final/standalone/data/content/a2/dffcda3610a8edc34edcd11ac16fc22eed4591/content 09:45:27,057 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of campingawaits-1.0-SNAPSHOT.war 09:45:27,948 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/campingawaits-1.0-SNAPSHOT]] (MSC service thread 1-3) Exception starting filter wicket.campingawaits: org.apache.wicket.WicketRuntimeException: Unable to create application of class com.campingawaits.CampingAwaitsApp at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:86) [wicket-core-6.0.0.jar:6.0.0] at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:50) [wicket-core-6.0.0.jar:6.0.0] at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:339) [wicket-core-6.0.0.jar:6.0.0] at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:314) [wicket-core-6.0.0.jar:6.0.0] at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:447) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3269) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3865) [jbossweb-7.0.13.Final.jar:] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_37] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_37] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37] Caused by:
Re: ResizableBehavior multiple resizable panels on a page
Hi Pieter,
If you have multiple panel, they all have the same html-id (#resizable).
(and so jquery statement $(#resizable) will only take the first one)
What you need is to have different (rendered) html ids for each panels. So,
you can simply do:
add(new ResizableBehavior(# + this.setOutputMarkupId(true).getMarkupId(),
options));
Which can be shortened as:
add(new ResizableBehavior(JQueryWidget.getSelector(this), options));
Hope this helps,
Sebastien.
On Sun, Jan 27, 2013 at 5:19 PM, Pieter Claassen pie...@musmato.com wrote:
I have multiple panels on a page, each once constructed as follows:
* public EditableQuestionPanel(String id, final QuestionBaseWebModel
questionBaseWebModel, final TemplateWebModel templateWebModel, final
QuestionEditPanel panel) {*
*super(id);*
*Options options = new Options();*
*options.set(minWidth, 350);*
*options.set(minHeight, 85);*
*add(new ResizableBehavior(#resizable,options));*
Here is the HTML for each panel.
*wicket:panel*
*div id=resizable class=ui-widget-content*
*div class=question wicket:id=holder*
*a href=# wicket:id=editor*
*div id=label wicket:id=questionDisplayPanel*
*/div*
*/a*
* span wicket:id=navpanel/span*
*/div*
*/div*
*/wicket:panel*
I want them each to be resizable but only the first panel ever is.
I am using wicket-jquery-ui. Any idea what I am doing wrong here. Do I have
to give each pane a unique html id attribute?
Pieter
Re: Upgrade to 6.5.0
I think that Sven has right about war duplication. Jboss maven plugin has 3 goals to manage deployments: deploy, redeploy, undeploy. If you use only deploy goal, jboss could leave some trashes in deployment location. So if you reinstall JBoss, the old configuration files could still be on your disc. You should remove this folders (temp, works etc) - I don't know where this files are located on mac. Fast check: Download fresh zipped installation from JBoss site (http://www.jboss.org/jbossas/downloads) and unzip it, copy war into %JBOSS%/standalone/deployments and run it %JBOSS%/run/stanalone Can you publish also the com.campingawaits.CampingAwaitsApp class? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Upgrade-to-6-5-0-tp4655782p4655802.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Upgrade to 6.5.0
I'll have to double check on this for sure when I get home, but a simple
JBOSS question. I can't just run mvn package jboss-as:deploy over and over
again? This has seemed to work for months up until this point. Obviously
I need to discontinue if it's not good practice; I just didn't know any
better. I'll try again when I get home. I'm on a different computer
that's out of sync with my code at home.
Here's the class:
package com.campingawaits;
import org.apache.wicket.Page;
import org.apache.wicket.Session;
import org.apache.wicket.authorization.IAuthorizationStrategy;
import
org.apache.wicket.authorization.strategies.page.SimplePageAuthorizationStrategy;
import org.apache.wicket.protocol.http.WebApplication;
import org.apache.wicket.request.Request;
import org.apache.wicket.request.Response;
import org.apache.wicket.settings.IRequestCycleSettings.RenderStrategy;
import com.campingawaits.auth.AuthenticatedWebPage;
import com.campingawaits.auth.CampingAwaitsSession;
import com.campingawaits.auth.SignIn;
import com.campingawaits.base.About;
import com.campingawaits.base.Blog;
import com.campingawaits.base.ContactUs;
import com.campingawaits.base.Index;
import com.campingawaits.blog.BlogDetails;
/**
* Application object for your web application. If you want to run this
application without deploying, run the Start class.
*
* @see com.campingawaits.Start#main(String[])
*/
public class CampingAwaitsApplication extends WebApplication
{
/**
* Contstruct
*/
public CampingAwaitsApplication()
{
}
/**
* @see org.apache.wicket.Application#getHomePage()
*/
@Override
public Class? extends Page getHomePage() {
return Index.class;
}
/**
* @see
org.apache.wicket.protocol.http.WebApplication#newSession(org.apache.wicket.request.Request,
* org.apache.wicket.request.Response)
*/
@Override
public Session newSession(Request request, Response response)
{
return new CampingAwaitsSession(request);
}
/**
* @see org.apache.wicket.Application#init()
*/
@Override
public void init() {
super.init();
getResourceSettings().setThrowExceptionOnMissingResource(false);
getRequestCycleSettings().setRenderStrategy(RenderStrategy.REDIRECT_TO_RENDER);
IAuthorizationStrategy authorizationStrategy = new
SimplePageAuthorizationStrategy(
AuthenticatedWebPage.class, SignIn.class) {
@Override
protected boolean isAuthorized() {
return (((CampingAwaitsSession)Session.get()).isSignedIn());
}
};
getSecuritySettings().setAuthorizationStrategy(authorizationStrategy);
/*mountPage(/, Index.class);*/
mountPage(/news, Blog.class);
mountPage(/news/${id}, BlogDetails.class);
mountPage(/contact, ContactUs.class);
mountPage(/about, About.class);
}
}
___
Stephen Walsh | http://connectwithawalsh.com
On Sun, Jan 27, 2013 at 10:38 AM, procrastinative.developer
procrastinative.develo...@gmail.com wrote:
I think that Sven has right about war duplication. Jboss maven plugin has 3
goals to manage deployments: deploy, redeploy, undeploy. If you use only
deploy goal, jboss could leave some trashes in deployment location.
So if you reinstall JBoss, the old configuration files could still be on
your disc. You should remove this folders (temp, works etc) - I don't know
where this files are located on mac.
Fast check: Download fresh zipped installation from JBoss site
(http://www.jboss.org/jbossas/downloads) and unzip it, copy war into
%JBOSS%/standalone/deployments and run it %JBOSS%/run/stanalone
Can you publish also the com.campingawaits.CampingAwaitsApp class?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Upgrade-to-6-5-0-tp4655782p4655802.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: ResizableBehavior multiple resizable panels on a page
Thanks, that did the job.
Pieter
On Sun, Jan 27, 2013 at 5:35 PM, Sebastien seb...@gmail.com wrote:
Hi Pieter,
If you have multiple panel, they all have the same html-id (#resizable).
(and so jquery statement $(#resizable) will only take the first one)
What you need is to have different (rendered) html ids for each panels. So,
you can simply do:
add(new ResizableBehavior(# + this.setOutputMarkupId(true).getMarkupId(),
options));
Which can be shortened as:
add(new ResizableBehavior(JQueryWidget.getSelector(this), options));
Hope this helps,
Sebastien.
On Sun, Jan 27, 2013 at 5:19 PM, Pieter Claassen pie...@musmato.com
wrote:
I have multiple panels on a page, each once constructed as follows:
* public EditableQuestionPanel(String id, final QuestionBaseWebModel
questionBaseWebModel, final TemplateWebModel templateWebModel, final
QuestionEditPanel panel) {*
*super(id);*
*Options options = new Options();*
*options.set(minWidth, 350);*
*options.set(minHeight, 85);*
*add(new ResizableBehavior(#resizable,options));*
Here is the HTML for each panel.
*wicket:panel*
*div id=resizable class=ui-widget-content*
*div class=question wicket:id=holder*
*a href=# wicket:id=editor*
*div id=label wicket:id=questionDisplayPanel*
*/div*
*/a*
* span wicket:id=navpanel/span*
*/div*
*/div*
*/wicket:panel*
I want them each to be resizable but only the first panel ever is.
I am using wicket-jquery-ui. Any idea what I am doing wrong here. Do I
have
to give each pane a unique html id attribute?
Pieter
--
- - - - - - - - - - - - - - - - - - - -
Pieter Claassen
Musmato B.V.
e: pieter.claas...@musmato.com
t: +31 877 848259
w: http://musmato.com
- - - - - - - - - - - - - - - - - - - -
Re: Upgrade to 6.5.0
Just to clarify, the class is not out of sync, the applications (Eclipse,
JBOSS, etc.)
___
Stephen Walsh | http://connectwithawalsh.com
On Sun, Jan 27, 2013 at 11:46 AM, Stephen Walsh
step...@connectwithawalsh.com wrote:
I'll have to double check on this for sure when I get home, but a simple
JBOSS question. I can't just run mvn package jboss-as:deploy over and
over again? This has seemed to work for months up until this point.
Obviously I need to discontinue if it's not good practice; I just didn't
know any better. I'll try again when I get home. I'm on a different
computer that's out of sync with my code at home.
Here's the class:
package com.campingawaits;
import org.apache.wicket.Page;
import org.apache.wicket.Session;
import org.apache.wicket.authorization.IAuthorizationStrategy;
import
org.apache.wicket.authorization.strategies.page.SimplePageAuthorizationStrategy;
import org.apache.wicket.protocol.http.WebApplication;
import org.apache.wicket.request.Request;
import org.apache.wicket.request.Response;
import org.apache.wicket.settings.IRequestCycleSettings.RenderStrategy;
import com.campingawaits.auth.AuthenticatedWebPage;
import com.campingawaits.auth.CampingAwaitsSession;
import com.campingawaits.auth.SignIn;
import com.campingawaits.base.About;
import com.campingawaits.base.Blog;
import com.campingawaits.base.ContactUs;
import com.campingawaits.base.Index;
import com.campingawaits.blog.BlogDetails;
/**
* Application object for your web application. If you want to run this
application without deploying, run the Start class.
*
* @see com.campingawaits.Start#main(String[])
*/
public class CampingAwaitsApplication extends WebApplication
{
/**
* Contstruct
*/
public CampingAwaitsApplication()
{
}
/**
* @see org.apache.wicket.Application#getHomePage()
*/
@Override
public Class? extends Page getHomePage() {
return Index.class;
}
/**
* @see
org.apache.wicket.protocol.http.WebApplication#newSession(org.apache.wicket.request.Request,
* org.apache.wicket.request.Response)
*/
@Override
public Session newSession(Request request, Response response)
{
return new CampingAwaitsSession(request);
}
/**
* @see org.apache.wicket.Application#init()
*/
@Override
public void init() {
super.init();
getResourceSettings().setThrowExceptionOnMissingResource(false);
getRequestCycleSettings().setRenderStrategy(RenderStrategy.REDIRECT_TO_RENDER);
IAuthorizationStrategy authorizationStrategy = new
SimplePageAuthorizationStrategy(
AuthenticatedWebPage.class, SignIn.class) {
@Override
protected boolean isAuthorized() {
return (((CampingAwaitsSession)Session.get()).isSignedIn());
}
};
getSecuritySettings().setAuthorizationStrategy(authorizationStrategy);
/*mountPage(/, Index.class);*/
mountPage(/news, Blog.class);
mountPage(/news/${id}, BlogDetails.class);
mountPage(/contact, ContactUs.class);
mountPage(/about, About.class);
}
}
___
Stephen Walsh | http://connectwithawalsh.com
On Sun, Jan 27, 2013 at 10:38 AM, procrastinative.developer
procrastinative.develo...@gmail.com wrote:
I think that Sven has right about war duplication. Jboss maven plugin has
3
goals to manage deployments: deploy, redeploy, undeploy. If you use only
deploy goal, jboss could leave some trashes in deployment location.
So if you reinstall JBoss, the old configuration files could still be on
your disc. You should remove this folders (temp, works etc) - I don't know
where this files are located on mac.
Fast check: Download fresh zipped installation from JBoss site
(http://www.jboss.org/jbossas/downloads) and unzip it, copy war into
%JBOSS%/standalone/deployments and run it %JBOSS%/run/stanalone
Can you publish also the com.campingawaits.CampingAwaitsApp class?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Upgrade-to-6-5-0-tp4655782p4655802.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Upgrade to 6.5.0
Got it working now. I think I had some stuff that was keeping the new install of JBOSS from actually being uninstalled. Thanks for the help. Now to figure out why Maven keeps building with Java 1.5 instead of 1.6. ___ Stephen Walsh | http://connectwithawalsh.com On Sun, Jan 27, 2013 at 12:08 PM, procrastinative.developer procrastinative.develo...@gmail.com wrote: if this fix help you can use JBoss maven plugin in old way. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Upgrade-to-6-5-0-tp4655782p4655809.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
JQuery - best practice
This is a general best practice question. I am using wicket-jquery-ui because I don't seem to be able to find a resizable panel in the internal wicket ajax widgets. 1. Is there no problem loading new jquery libraries over the wicket implementation? What is best practice? 2. I am looking for a way to get the resized panels' x and y size parameters into my wicket code? Any suggestions how to do this? Thanks, Pieter - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: JQuery - best practice
Hi, On Mon, Jan 28, 2013 at 7:45 AM, Pieter Claassen pie...@musmato.com wrote: This is a general best practice question. I am using wicket-jquery-ui because I don't seem to be able to find a resizable panel in the internal wicket ajax widgets. 1. Is there no problem loading new jquery libraries over the wicket implementation? What is best practice? Look at the existing jquery integrations and see what people do? 2. I am looking for a way to get the resized panels' x and y size parameters into my wicket code? Any suggestions how to do this? You have to: 1-Hook onto the client side events triggered by resize and use Wicket.AJA.get/post to stream back the parameters. 2-Attach and AJAX behavior at server side component and on respond get and parse those parameter. Examples? https://github.com/WiQuery/wiquery/blob/master/wiquery-jquery-ui/src/main/java/org/odlabs/wiquery/ui/slider/AjaxSlider.java https://github.com/WiQuery/wiquery/blob/master/wiquery-jquery-ui/src/main/java/org/odlabs/wiquery/ui/tabs/Tabs.java or event better https://github.com/WiQuery/wiquery/blob/master/wiquery-jquery-ui/src/main/java/org/odlabs/wiquery/ui/resizable/ResizableBehavior.java wihc already have that functionality (see AjaxResizeCallback) Thanks, Pieter - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Regards - Ernesto Reinaldo Barreiro Antilia Soft http://antiliasoft.com/ http://antiliasoft.com/antilia
Re: [6.0] weird exception about super.onBeforeRender()
Hi,
Put a breakpoint at org.apache.wicket.Component#internalBeforeRender, in
the second 'if' clause that throws this exception. This way you can see
details about the problematic component - like its type, its id, its
parents, etc. This way you should be able to identify which parent class
doesn't call super.onBeforeRender()
On Sun, Jan 27, 2013 at 5:53 PM, Pierre Goupil goupilpie...@gmail.comwrote:
Good afternoon,
In my project I got this exception from times to times:
Last cause: org.apache.wicket.Component has not been properly rendered.
Something in the hierarchy of blah.ExternalImage has not called
super.onBeforeRender() in the override of onBeforeRender() method
WicketMessage: Error attaching this container for rendering:
[WebMarkupContainer [Component id = wrapper]]
This occurs during an Ajax update.
What puzzles me is:
- that it doesn't occur every time, only now and then
- and that I never override onBeforeRender() in my code, neither in
ExternalImage
nor everywhere else.
Here is my code for ExternalImage, just in case:
public class ExternalImage extends WebComponent
{
private static final long serialVersionUID = 1L;
public ExternalImage(final String id, final String imageUrl)
{
super(id);
this.add(AttributeModifier.replace(src, new ModelString(imageUrl)));
this.setVisible(!((imageUrl == null) || imageUrl.equals()));
}
@Override
protected void onComponentTag(final ComponentTag tag)
{
super.onComponentTag(tag);
this.checkComponentTag(tag, img);
}
}
Regarding my wrapper component ([Component id = wrapper] in the exception),
it's pretty straightforward:
final WebMarkupContainer wrapper = new WebMarkupContainer(wrapper);
wrapper.setMarkupId(wrapper + item.getIndex());
wrapper.setOutputMarkupId(true);
I've googled around without any success, so if anyone has an idea, I'd be
more than happy! :-)
Regards,
Pierre Goupil
--
Parce que c'est la nuit qu'il est beau de croire à la lumière.
Edmond Rostand
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com http://jweekend.com/
Re: Preventing inner form processing?
Hi,
The signature of this method is (Wicket 1.5.x and earlier) :
function wicketSubmitFormById(formId, url, submitButton,
successHandler, failureHandler, precondition, channel)
i.e. there is a way to specify the submitting button. If you use the
inputName of a button from the outer form then it should do exactly what
you need.
On Sun, Jan 27, 2013 at 3:28 PM, Sebastien seb...@gmail.com wrote:
Hi all,
I have an inner form, and I would like this inner form to not being
processed when the parent form is submitted, like described here:
https://cwiki.apache.org/WICKET/conditional-validation.html
The problem, in my case, is that this inner-form is posted with
'wicketSubmitFormById', so do I not have any submitting button and
#findSubmittingButton naturally returns null.
But as I am processing the form using an IFormSubmitter, I would like to
write something that could looks like this (in my inner form):
public boolean processChildren()
{
IFormSubmitter submitter = this.getFormSubmitter(); //!\\
return submitter != null submitter.getForm() == this;
}
But I do not have any equivalent for #getFormSubmitter()...
Any ideas?
Thanks in advance,
Sebastien.
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com http://jweekend.com/
