Re: congrats to inmethod
On Sat, May 30, 2009 at 1:36 AM, Cristi Manole cristiman...@gmail.com wrote: I was trying to see if the inmethod site still links the (best) wicket data/tree table (although i knew it's been moved to wicket-stuff) and I stumbled on the new site. The site looks great and so does the service. Congrats to Matej... Igor (brix in action) ?... and best of luck with it. Why didn't you guys promote it here? http://www.inmethod.com lack of time? :) -Matej -- Cristi Manole Nova Creator Software www.novacreator.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: DropDownChoices: How to force a selection.
It should work with the value in your model. In your case something like
selectedDistrito.setSelectedChoice(1);
Rob
On 5/30/09 3:02 AM, Marco Santos wrote:
Here is the creation of the DDC:
private void buildDistritosComboBox() {
DistritosModel distritosModel = new DistritosModel();
SelectedChoice selectedDistrito = new SelectedChoice();//A class
with a variable selectedChoice and it getter and setter
DropDownChoice distritosDDC = new DropDownChoice(distritos, new
PropertyModel(selectedDistrito, selectedChoice), distritosModel);
distritosDDC.setOutputMarkupId(true);
distritosDDC.setRequired(true);
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Restarting AjaxLazyLoadingPanel
We use AjaxLazyLoadingPanel, and want to be able to trigger the
process of showing the indicator, and requesting the panels contents
with a separate Ajax request, after the first complete render has
finished. I.e. do the whole process over and over, without having to
reload the entire page.
I came up with this, which I was surprised actually worked first
try :) gotta love Wicket.
But perhaps there's a better way to do it ? A simpler way? Something
I'm missing? I tried simply replacing the lazy loading panel with a
new instance of one but that didn't seem to have an effect - I think
the magic is in the adding a new AbstractAjaxBehaviour on each request.
import org.apache.wicket.Component;
import org.apache.wicket.ajax.AbstractDefaultAjaxBehavior;
import org.apache.wicket.ajax.AjaxRequestTarget;
import org.apache.wicket.extensions.ajax.markup.html.AjaxLazyLoadPanel;
import org.apache.wicket.markup.html.IHeaderResponse;
/**
* An {...@link AjaxLazyLoadPanel} extension which allows it to
* {...@link #restart(AjaxRequestTarget)} the process of showing the
loading
* indicator, then load it's contents using a separate Ajax request.
*
* @author Antony Stubbs
*/
abstract public class ReloadingAjaxLazyPanel extends AjaxLazyLoadPanel {
private static final long serialVersionUID = 1L;
public ReloadingAjaxLazyPanel(String id) {
super( id );
}
/**
* Causes the {...@link AjaxLazyLoadPanel} to re-display the loading
indicator,
* then in a seperate ajax request, get it's contents.
*
* @param target
*/
public void restart(AjaxRequestTarget target) {
target.addComponent( this );
// replace panel contents with loading icon
Component loadingComponent = getLoadingComponent( content );
this.replace( loadingComponent );
// add ajax behaviour to install call back
loadingComponent.add( new AbstractDefaultAjaxBehavior() {
private static final long serialVersionUID = 1L;
@Override
protected void respond(AjaxRequestTarget target) {
Component component =
ReloadingAjaxLazyPanel.this.getLazyLoadComponent( content );
ReloadingAjaxLazyPanel
.this.replace( component.setRenderBodyOnly( true ) );
target.addComponent( ReloadingAjaxLazyPanel.this );
// setState((byte)2);
}
@Override
public void renderHead(IHeaderResponse response) {
super.renderHead( response );
response.renderOnDomReadyJavascript( getCallbackScript().toString() );
}
} );
}
}
As you can see, there is duplication from AjaxLazyLoadingPanel - which
would need re-factoring in order to remove. - no problem there.
But also, because the setState method is private, I can't use that
state system.
Regards,
Antony Stubbs,
NZ
http://friendfeed.com/astubbs
localisation - specify fallback locale
I would like to keep all our languages in specific files
*_lang.properties - and not have a *.properties file - i.e.
mypanel_en.prop
mypanel_nl.prop
and not have a mypanel.prop. and if someone comes to the site with fr
as their locale, is there already an option for me to specify that the
fallback locale should be nl? (yes, i know about the
mypanel.properties being the default - but it doesnt seem right to me
to not specify the language of that file in the file name).
Or do I need to
application.init() {
getresourcesettings().setlocalizer(...);
}
?
Regards,
Antony Stubbs,
NZ
http://friendfeed.com/astubbs
Re: localisation - specify fallback locale
Ok, answered my own question:
ComponentStringResourceLoader dutchFallbackResourceLoader =
new ComponentStringResourceLoader(){
@Override
public String loadStringResource(Class? clazz, String
key, Locale locale, String style) {
return super.loadStringResource( clazz, key, new
Locale(nl), style );
}
};
getResourceSettings
().addStringResourceLoader( dutchFallbackResourceLoader );
You could also implement a getFallbackLocale() for your application
class if you tended to change it.
So - when using this you don't need a *.prop file - instead you can
have a _en and a _nl and then specify nl as your 'fallback' locale.
Regards,
Antony Stubbs,
NZ
http://friendfeed.com/astubbs
On 30/05/2009, at 11:44 PM, Antony Stubbs wrote:
I would like to keep all our languages in specific files
*_lang.properties - and not have a *.properties file - i.e.
mypanel_en.prop
mypanel_nl.prop
and not have a mypanel.prop. and if someone comes to the site with
fr as their locale, is there already an option for me to specify
that the fallback locale should be nl? (yes, i know about the
mypanel.properties being the default - but it doesnt seem right to
me to not specify the language of that file in the file name).
Or do I need to
application.init() {
getresourcesettings().setlocalizer(...);
}
?
Regards,
Antony Stubbs,
NZ
http://friendfeed.com/astubbs
Re: Wicket Quickstart vs WIA eclipse projects: why so different?
Something that may be worth trying is mvn jetty:run-exploded On Fri, May 29, 2009 at 6:10 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote: like i said, the best way is to right click the Start class and do run as java application. you can, of course, do it any other way you like - including installing jetty eclipse launcher plugin. -igor On Fri, May 29, 2009 at 3:17 PM, David Brown dbr...@sexingtechnologies.com wrote: Hello Igor, thanks for the reply. Can I just ignore the QuickStart embedded jetty and install jetty on Eclipse then do a run-as without any issues? Please advise, David. - Original Message - From: Igor Vaynberg igor.vaynb...@gmail.com To: users@wicket.apache.org Cc: david da...@davidwbrown.name Sent: Friday, May 29, 2009 4:51:02 PM GMT -06:00 US/Canada Central Subject: Re: Wicket Quickstart vs WIA eclipse projects: why so different? why dont you just start the project from eclipse directly using the Start class, that way you get debug and hotswap - which should be the real student's dream :) -igor On Fri, May 29, 2009 at 2:53 PM, David Brown dbr...@sexingtechnologies.com wrote: Hello Martin, Jeremy, dev, gurus, users and mortals. I have just finished ch. 13 of the WIA.pdf. I have followed closely the reading using the wicket-in-action eclipse project. I have the wicket-in-action running under the: mvn jetty:run. The wicket-in-action project is redeployed every 60 seconds (a student's dream). After finishing the 13th chapter I decided to leave the nest for the 1.4rc QuickStart. The new QuickStart project expanded and imported into the Eclipse workspace no-problemo. The mystery is what am I doing wrong to get the automatic 60 second re-deploy. As it stands now I have to kill jetty, mvn package and then restart jetty (mvn jetty:run). I have pasted in the: ** context-param param-nameconfiguration/param-name param-valuedevelopment/param-value /context-param ** from the wicket-in-action web.xml but no change. The Windows cmd console shows the usual Wicket WARNING: running in development mode. I plan to use the wicket-in-action almost verbatim including the Hibernate DAO for my current gig. It is probably only a few weeks before they start holding my feet to the fire. Please advise, David. - 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 - 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: Wicket Quickstart vs WIA eclipse projects: why so different?
For what its worth, I run a few Wicket 1.4x projects as within Eclipse/m2plugin and pages, etc refresh just fine. I use the Run/Debug Configurations and create a Maven application and then select the jetty plugin, correct workspace and jetty:run command. There are also Jetty options you can include directly in the POM file that define how and when Jetty should regularly will scan the deployed files ... restarting Jetty if changes detected. What I've described is too different mechanisms for picking up changes ... is that what you're asking for? -Luther On Sat, May 30, 2009 at 7:53 AM, Ben Tilford bentilf...@gmail.com wrote: Something that may be worth trying is mvn jetty:run-exploded On Fri, May 29, 2009 at 6:10 PM, Igor Vaynberg igor.vaynb...@gmail.com wrote: like i said, the best way is to right click the Start class and do run as java application. you can, of course, do it any other way you like - including installing jetty eclipse launcher plugin. -igor On Fri, May 29, 2009 at 3:17 PM, David Brown dbr...@sexingtechnologies.com wrote: Hello Igor, thanks for the reply. Can I just ignore the QuickStart embedded jetty and install jetty on Eclipse then do a run-as without any issues? Please advise, David. - Original Message - From: Igor Vaynberg igor.vaynb...@gmail.com To: users@wicket.apache.org Cc: david da...@davidwbrown.name Sent: Friday, May 29, 2009 4:51:02 PM GMT -06:00 US/Canada Central Subject: Re: Wicket Quickstart vs WIA eclipse projects: why so different? why dont you just start the project from eclipse directly using the Start class, that way you get debug and hotswap - which should be the real student's dream :) -igor On Fri, May 29, 2009 at 2:53 PM, David Brown dbr...@sexingtechnologies.com wrote: Hello Martin, Jeremy, dev, gurus, users and mortals. I have just finished ch. 13 of the WIA.pdf. I have followed closely the reading using the wicket-in-action eclipse project. I have the wicket-in-action running under the: mvn jetty:run. The wicket-in-action project is redeployed every 60 seconds (a student's dream). After finishing the 13th chapter I decided to leave the nest for the 1.4rc QuickStart. The new QuickStart project expanded and imported into the Eclipse workspace no-problemo. The mystery is what am I doing wrong to get the automatic 60 second re-deploy. As it stands now I have to kill jetty, mvn package and then restart jetty (mvn jetty:run). I have pasted in the: ** context-param param-nameconfiguration/param-name param-valuedevelopment/param-value /context-param ** from the wicket-in-action web.xml but no change. The Windows cmd console shows the usual Wicket WARNING: running in development mode. I plan to use the wicket-in-action almost verbatim including the Hibernate DAO for my current gig. It is probably only a few weeks before they start holding my feet to the fire. Please advise, David. - 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 - 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: OutOfMemory on certain combinations of controls
Please file a jira issue and Attach the quickstart. Saves a lot of hunting. Use the power of jira! Martijn On Friday, May 29, 2009, Flavius flav...@silverlion.com wrote: I put a quickstart build up at http://silverlion.com/tmp2/OutOfMemory.zip. Just unzip it, change to that dir and run mvn jetty:run and go to http://localhost:8080/OutOfMemory It has just one page, one modal window, one border, and one panel. The steps to repro this are there on the home page. Thanks for your help, Igor. igor.vaynberg wrote: there is too much going on in the sample you posted. if you want you can create a quickstart with the minimal amount of code necessary to reproduce this and i will take a look. -igor On Thu, May 28, 2009 at 2:12 PM, Flavius flav...@silverlion.com wrote: The sample I posted only has the single page with a link to the ModalWindow. The modal window keeps a reference to the ModalWindow param passed in to the constructor. That's only used to close the window when the AjaxRequestTarget is passed from the AjaxLink. When the OnChangeAjaxBehavior#onUpdate fires, it's rebuilding the repeating view and adding the WebMarkupContainer wrapper to the AjaxRequestTarget. So it's not keeping any references that I see. igor.vaynberg wrote: make sure you dont keep page references across pages. that may be it. -igor -- View this message in context: http://www.nabble.com/OutOfMemory-on-certain-combinations-of-controls-tp23750424p23770219.html Sent from the Wicket - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/OutOfMemory-on-certain-combinations-of-controls-tp23750424p23786803.html Sent from the Wicket - User 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 -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Error filterStart -- how to know what caused tomcat start failure?
Hello, I am in the process of learning Wicket and testing different things. One of the biggest problems so far is that when starting Tomcat, I often get the following error message: SEVERE: Error filterStart AND Tomcat gives no detail what cuased the problem Any way I can make Tomcat produce more information about the cause of the failure? Thanks!!! - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Error filterStart -- how to know what caused tomcat start failure?
I guess this isn't wicket specific. goggle on your error and you may get information on how to solve this. -- View this message in context: http://www.nabble.com/Error-filterStarthow-to-know-what-caused-tomcat-start-failure--tp23794740p23794783.html Sent from the Wicket - User 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: Wicket Quickstart vs WIA eclipse projects: why so different?
Hello Igor, thanks. I had to create an Eclipse Run/Launch property as the Run as is not available on right click (but it works). The only issue now is the corresponding HTML page cannot be found. I have seen this before on this ML but I can no longer find the reference. Apparently, Eclipse properties limits copying .HTML files with the classes. I have not found how or where to change this. Any and all feedback welcomed. Regards, David. Igor Vaynberg wrote .. like i said, the best way is to right click the Start class and do run as java application. you can, of course, do it any other way you like - including installing jetty eclipse launcher plugin. -igor On Fri, May 29, 2009 at 3:17 PM, David Brown dbr...@sexingtechnologies.com wrote: Hello Igor, thanks for the reply. Can I just ignore the QuickStart embedded jetty and install jetty on Eclipse then do a run-as without any issues? Please advise, David. - Original Message - From: Igor Vaynberg igor.vaynb...@gmail.com To: users@wicket.apache.org Cc: david da...@davidwbrown.name Sent: Friday, May 29, 2009 4:51:02 PM GMT -06:00 US/Canada Central Subject: Re: Wicket Quickstart vs WIA eclipse projects: why so different? why dont you just start the project from eclipse directly using the Start class, that way you get debug and hotswap - which should be the real student's dream :) -igor On Fri, May 29, 2009 at 2:53 PM, David Brown dbr...@sexingtechnologies.com wrote: Hello Martin, Jeremy, dev, gurus, users and mortals. I have just finished ch. 13 of the WIA.pdf. I have followed closely the reading using the wicket-in-action eclipse project. I have the wicket-in-action running under the: mvn jetty:run. The wicket-in-action project is redeployed every 60 seconds (a student's dream). After finishing the 13th chapter I decided to leave the nest for the 1.4rc QuickStart. The new QuickStart project expanded and imported into the Eclipse workspace no-problemo. The mystery is what am I doing wrong to get the automatic 60 second re-deploy. As it stands now I have to kill jetty, mvn package and then restart jetty (mvn jetty:run). I have pasted in the: ** context-param param-nameconfiguration/param-name param-valuedevelopment/param-value /context-param ** from the wicket-in-action web.xml but no change. The Windows cmd console shows the usual Wicket WARNING: running in development mode. I plan to use the wicket-in-action almost verbatim including the Hibernate DAO for my current gig. It is probably only a few weeks before they start holding my feet to the fire. Please advise, David. - 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 - 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Error filterStart -- how to know what caused tomcat start failure?
I googled a lot but failed to find satisfactory answers. I just find a way to make tomcat to produce more error info than simply May 30, 2009 12:06:57 PM org.apache.catalina.core.StandardContext start SEVERE: Error filterStart May 30, 2009 12:06:57 PM org.apache.catalina.core.StandardContext start SEVERE: Context [/wic] startup failed due to previous errors I am learning from the book Wicket in Action. The funny thing is that the new stuff is no problem, but the tomcat error is. --- On Sat, 5/30/09, Mathias Nilsson wicket.program...@gmail.com wrote: From: Mathias Nilsson wicket.program...@gmail.com Subject: Re: Error filterStart -- how to know what caused tomcat start failure? To: users@wicket.apache.org Date: Saturday, May 30, 2009, 12:07 PM I guess this isn't wicket specific. goggle on your error and you may get information on how to solve this. -- View this message in context: http://www.nabble.com/Error-filterStarthow-to-know-what-caused-tomcat-start-failure--tp23794740p23794783.html Sent from the Wicket - User 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Error filterStart -- how to know what caused tomcat start failure?
Have you tried this with a jetty server? If you are using maven then this will help you. http://wicket.apache.org/quickstart.html http://wicket.apache.org/quickstart.html are you using windows, mac, linux? -- View this message in context: http://www.nabble.com/Error-filterStarthow-to-know-what-caused-tomcat-start-failure--tp23794740p23794900.html Sent from the Wicket - User 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: Error filterStart -- how to know what caused tomcat start failure?
There are also other tomcat logs, have you looked into them? I found an cause of this error in other log, but I do not remember which one was that. Vitek David Chang wrote: I googled a lot but failed to find satisfactory answers. I just find a way to make tomcat to produce more error info than simply May 30, 2009 12:06:57 PM org.apache.catalina.core.StandardContext start SEVERE: Error filterStart May 30, 2009 12:06:57 PM org.apache.catalina.core.StandardContext start SEVERE: Context [/wic] startup failed due to previous errors I am learning from the book Wicket in Action. The funny thing is that the new stuff is no problem, but the tomcat error is. --- On Sat, 5/30/09, Mathias Nilsson wicket.program...@gmail.com wrote: From: Mathias Nilsson wicket.program...@gmail.com Subject: Re: Error filterStart -- how to know what caused tomcat start failure? To: users@wicket.apache.org Date: Saturday, May 30, 2009, 12:07 PM I guess this isn't wicket specific. goggle on your error and you may get information on how to solve this. -- View this message in context: http://www.nabble.com/Error-filterStarthow-to-know-what-caused-tomcat-start-failure--tp23794740p23794783.html Sent from the Wicket - User 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 - 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: Wicket Quickstart vs WIA eclipse projects: why so different?
Check project's sources (Project - Properties - Build path - Sources) and remove the excludes El sáb, 30-05-2009 a las 11:08 -0500, da...@davidwbrown.name escribió: Hello Igor, thanks. I had to create an Eclipse Run/Launch property as the Run as is not available on right click (but it works). The only issue now is the corresponding HTML page cannot be found. I have seen this before on this ML but I can no longer find the reference. Apparently, Eclipse properties limits copying .HTML files with the classes. I have not found how or where to change this. Any and all feedback welcomed. Regards, David. Igor Vaynberg wrote .. like i said, the best way is to right click the Start class and do run as java application. you can, of course, do it any other way you like - including installing jetty eclipse launcher plugin. -igor On Fri, May 29, 2009 at 3:17 PM, David Brown dbr...@sexingtechnologies.com wrote: Hello Igor, thanks for the reply. Can I just ignore the QuickStart embedded jetty and install jetty on Eclipse then do a run-as without any issues? Please advise, David. - Original Message - From: Igor Vaynberg igor.vaynb...@gmail.com To: users@wicket.apache.org Cc: david da...@davidwbrown.name Sent: Friday, May 29, 2009 4:51:02 PM GMT -06:00 US/Canada Central Subject: Re: Wicket Quickstart vs WIA eclipse projects: why so different? why dont you just start the project from eclipse directly using the Start class, that way you get debug and hotswap - which should be the real student's dream :) -igor On Fri, May 29, 2009 at 2:53 PM, David Brown dbr...@sexingtechnologies.com wrote: Hello Martin, Jeremy, dev, gurus, users and mortals. I have just finished ch. 13 of the WIA.pdf. I have followed closely the reading using the wicket-in-action eclipse project. I have the wicket-in-action running under the: mvn jetty:run. The wicket-in-action project is redeployed every 60 seconds (a student's dream). After finishing the 13th chapter I decided to leave the nest for the 1.4rc QuickStart. The new QuickStart project expanded and imported into the Eclipse workspace no-problemo. The mystery is what am I doing wrong to get the automatic 60 second re-deploy. As it stands now I have to kill jetty, mvn package and then restart jetty (mvn jetty:run). I have pasted in the: ** context-param param-nameconfiguration/param-name param-valuedevelopment/param-value /context-param ** from the wicket-in-action web.xml but no change. The Windows cmd console shows the usual Wicket WARNING: running in development mode. I plan to use the wicket-in-action almost verbatim including the Hibernate DAO for my current gig. It is probably only a few weeks before they start holding my feet to the fire. Please advise, David. - 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 - 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 - 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
Help debugging why a component is not showing up...
Hello- I am pulling my hair out trying to figure out why a component is not showing up within a page. When I run the app from eclipse in development or deployment mode, it shows up just fine. When I build a package run that... no luck. However it does include javascript libraries added from the (not visible) components. Is there an easy way to debug the component hierarchy on the page? Perhaps some way to dump the current page tree to text or something? Any pointers would be great! thanks ryan - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Help debugging why a component is not showing up...
Ryan, Is PageView what you're looking for? Regards - Cemal http://jWeekend.com jWeekend ryantxu wrote: Hello- I am pulling my hair out trying to figure out why a component is not showing up within a page. When I run the app from eclipse in development or deployment mode, it shows up just fine. When I build a package run that... no luck. However it does include javascript libraries added from the (not visible) components. Is there an easy way to debug the component hierarchy on the page? Perhaps some way to dump the current page tree to text or something? Any pointers would be great! thanks ryan - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- View this message in context: http://www.nabble.com/Help-debugging-why-a-component-is-not-showing-up...-tp23796086p23796445.html Sent from the Wicket - User 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: CheckGroup and AjaxPagingNavigator
you need to change the links to be ajaxsubmitlinks instead of just ajaxlinks, there are factory methods on the navigator. -igor On Fri, May 29, 2009 at 5:18 PM, Julian Sinai jsi...@yahoo.com wrote: I'm having trouble with my usage of CheckGroup and AjaxPagingNavigator. If the user checks one or more checkboxes on one page of my data table, then navigates to the next page, the choices on the first page are forgotten. In my application, they need to be remembered. This was not a problem before I switched to Ajax paging navigation. If someone can help, I'd appreciate it. Thanks, Julian More detail: I'm using the DataView/IDataProvider pattern for my data table. I'm using CheckGroup, Check, and CheckGroupSelector for the checkboxes in my data table. - 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: Restarting AjaxLazyLoadingPanel
you can just replace the entire panel with a new instance.
-igor
On Sat, May 30, 2009 at 3:11 AM, Antony Stubbs antony.stu...@gmail.com wrote:
We use AjaxLazyLoadingPanel, and want to be able to trigger the process of
showing the indicator, and requesting the panels contents with a separate
Ajax request, after the first complete render has finished. I.e. do the
whole process over and over, without having to reload the entire page.
I came up with this, which I was surprised actually worked first try :)
gotta love Wicket.
But perhaps there's a better way to do it ? A simpler way? Something I'm
missing? I tried simply replacing the lazy loading panel with a new instance
of one but that didn't seem to have an effect - I think the magic is in the
adding a new AbstractAjaxBehaviour on each request.
import org.apache.wicket.Component;
import org.apache.wicket.ajax.AbstractDefaultAjaxBehavior;
import org.apache.wicket.ajax.AjaxRequestTarget;
import org.apache.wicket.extensions.ajax.markup.html.AjaxLazyLoadPanel;
import org.apache.wicket.markup.html.IHeaderResponse;
/**
* An {...@link AjaxLazyLoadPanel} extension which allows it to
* {...@link #restart(AjaxRequestTarget)} the process of showing the loading
* indicator, then load it's contents using a separate Ajax request.
*
* @author Antony Stubbs
*/
abstract public class ReloadingAjaxLazyPanel extends AjaxLazyLoadPanel {
private static final long serialVersionUID = 1L;
public ReloadingAjaxLazyPanel(String id) {
super( id );
}
/**
* Causes the {...@link AjaxLazyLoadPanel} to re-display the loading
indicator,
* then in a seperate ajax request, get it's contents.
*
* @param target
*/
public void restart(AjaxRequestTarget target) {
target.addComponent( this );
// replace panel contents with loading icon
Component loadingComponent = getLoadingComponent( content );
this.replace( loadingComponent );
// add ajax behaviour to install call back
loadingComponent.add( new AbstractDefaultAjaxBehavior() {
private static final long serialVersionUID = 1L;
�...@override
protected void respond(AjaxRequestTarget target) {
Component component =
ReloadingAjaxLazyPanel.this.getLazyLoadComponent( content );
ReloadingAjaxLazyPanel.this.replace(
component.setRenderBodyOnly( true ) );
target.addComponent( ReloadingAjaxLazyPanel.this );
// setState((byte)2);
}
�...@override
public void renderHead(IHeaderResponse response) {
super.renderHead( response );
response.renderOnDomReadyJavascript(
getCallbackScript().toString() );
}
} );
}
}
As you can see, there is duplication from AjaxLazyLoadingPanel - which would
need re-factoring in order to remove. - no problem there.
But also, because the setState method is private, I can't use that state
system.
Regards,
Antony Stubbs,
NZ
http://friendfeed.com/astubbs
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: OutOfMemory on certain combinations of controls
the problem is the page inside the modal window has a reference to the outer page - you pass the modal window which has an anonymous close callback which keeps a reference to the page. so you keep serializing the entire page with every ajax request as part of the current page. you dont need the reference to the modalwindow, you can use ModalWindow.closeCurrent() to close it. -igor On Fri, May 29, 2009 at 1:45 PM, Flavius flav...@silverlion.com wrote: I put a quickstart build up at http://silverlion.com/tmp2/OutOfMemory.zip. Just unzip it, change to that dir and run mvn jetty:run and go to http://localhost:8080/OutOfMemory It has just one page, one modal window, one border, and one panel. The steps to repro this are there on the home page. Thanks for your help, Igor. igor.vaynberg wrote: there is too much going on in the sample you posted. if you want you can create a quickstart with the minimal amount of code necessary to reproduce this and i will take a look. -igor On Thu, May 28, 2009 at 2:12 PM, Flavius flav...@silverlion.com wrote: The sample I posted only has the single page with a link to the ModalWindow. The modal window keeps a reference to the ModalWindow param passed in to the constructor. That's only used to close the window when the AjaxRequestTarget is passed from the AjaxLink. When the OnChangeAjaxBehavior#onUpdate fires, it's rebuilding the repeating view and adding the WebMarkupContainer wrapper to the AjaxRequestTarget. So it's not keeping any references that I see. igor.vaynberg wrote: make sure you dont keep page references across pages. that may be it. -igor -- View this message in context: http://www.nabble.com/OutOfMemory-on-certain-combinations-of-controls-tp23750424p23770219.html Sent from the Wicket - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/OutOfMemory-on-certain-combinations-of-controls-tp23750424p23786803.html Sent from the Wicket - User 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Error filterStart -- how to know what caused tomcat start failure?
Vitek, you are right. Under tomcat\logs directory, one type of logs called localhost contains more info than what tomcat start screen reveals. Thanks for the pointer. --- On Sat, 5/30/09, Vit Rozkovec rozkovec...@email.cz wrote: From: Vit Rozkovec rozkovec...@email.cz Subject: Re: Error filterStart -- how to know what caused tomcat start failure? To: users@wicket.apache.org Date: Saturday, May 30, 2009, 12:24 PM There are also other tomcat logs, have you looked into them? I found an cause of this error in other log, but I do not remember which one was that. Vitek David Chang wrote: I googled a lot but failed to find satisfactory answers. I just find a way to make tomcat to produce more error info than simply May 30, 2009 12:06:57 PM org.apache.catalina.core.StandardContext start SEVERE: Error filterStart May 30, 2009 12:06:57 PM org.apache.catalina.core.StandardContext start SEVERE: Context [/wic] startup failed due to previous errors I am learning from the book Wicket in Action. The funny thing is that the new stuff is no problem, but the tomcat error is. --- On Sat, 5/30/09, Mathias Nilsson wicket.program...@gmail.com wrote: From: Mathias Nilsson wicket.program...@gmail.com Subject: Re: Error filterStart -- how to know what caused tomcat start failure? To: users@wicket.apache.org Date: Saturday, May 30, 2009, 12:07 PM I guess this isn't wicket specific. goggle on your error and you may get information on how to solve this. -- View this message in context: http://www.nabble.com/Error-filterStarthow-to-know-what-caused-tomcat-start-failure--tp23794740p23794783.html Sent from the Wicket - User 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 - 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket Quickstart vs WIA eclipse projects: why so different?
Hello Luther, thanks for the informative and speedy reply. I'm going to take things one-step-at-a-time. So far, Igor is right about running the Start.class (as found in the test-classes directory). The only issue now is the Eclipse bug-a-boo about not copying the .HTML files along with the .CLASS files. See RuntimeException included below. As soon as I learn how to turn off the filter I will try your way if this fails. Yes, I am basically looking for anyway of speeding up the: edit, build, deploy cycle. Directly deploying .WAR files is OK once but since I'm trying to develop something for work I'm running out of time quickly. Thanks and regards, David. - Original Message - From: Luther Baker lutherba...@gmail.com To: users@wicket.apache.org Sent: Saturday, May 30, 2009 9:36:55 AM GMT -06:00 US/Canada Central Subject: Re: Wicket Quickstart vs WIA eclipse projects: why so different? For what its worth, I run a few Wicket 1.4x projects as within Eclipse/m2plugin and pages, etc refresh just fine. I use the Run/Debug Configurations and create a Maven application and then select the jetty plugin, correct workspace and jetty:run command. There are also Jetty options you can include directly in the POM file that define how and when Jetty should regularly will scan the deployed files ... restarting Jetty if changes detected. What I've described is too different mechanisms for picking up changes ... is that what you're asking for? -Luther On Sat, May 30, 2009 at 7:53 AM, Ben Tilford bentilf...@gmail.com wrote: Something that may be worth trying is mvn jetty:run-exploded On Fri, May 29, 2009 at 6:10 PM, Igor Vaynberg igor.vaynb...@gmail.com wrote: like i said, the best way is to right click the Start class and do run as java application. you can, of course, do it any other way you like - including installing jetty eclipse launcher plugin. -igor On Fri, May 29, 2009 at 3:17 PM, David Brown dbr...@sexingtechnologies.com wrote: Hello Igor, thanks for the reply. Can I just ignore the QuickStart embedded jetty and install jetty on Eclipse then do a run-as without any issues? Please advise, David. - Original Message - From: Igor Vaynberg igor.vaynb...@gmail.com To: users@wicket.apache.org Cc: david da...@davidwbrown.name Sent: Friday, May 29, 2009 4:51:02 PM GMT -06:00 US/Canada Central Subject: Re: Wicket Quickstart vs WIA eclipse projects: why so different? why dont you just start the project from eclipse directly using the Start class, that way you get debug and hotswap - which should be the real student's dream :) -igor On Fri, May 29, 2009 at 2:53 PM, David Brown dbr...@sexingtechnologies.com wrote: Hello Martin, Jeremy, dev, gurus, users and mortals. I have just finished ch. 13 of the WIA.pdf. I have followed closely the reading using the wicket-in-action eclipse project. I have the wicket-in-action running under the: mvn jetty:run. The wicket-in-action project is redeployed every 60 seconds (a student's dream). After finishing the 13th chapter I decided to leave the nest for the 1.4rc QuickStart. The new QuickStart project expanded and imported into the Eclipse workspace no-problemo. The mystery is what am I doing wrong to get the automatic 60 second re-deploy. As it stands now I have to kill jetty, mvn package and then restart jetty (mvn jetty:run). I have pasted in the: ** context-param param-nameconfiguration/param-name param-valuedevelopment/param-value /context-param ** from the wicket-in-action web.xml but no change. The Windows cmd console shows the usual Wicket WARNING: running in development mode. I plan to use the wicket-in-action almost verbatim including the Hibernate DAO for my current gig. It is probably only a few weeks before they start holding my feet to the fire. Please advise, David. - 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 - 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail:
Re: Wicket Quickstart vs WIA eclipse projects: why so different?
window/preferences/compiler/building - remove *.html from output folder/filtered resources -igor On Sat, May 30, 2009 at 2:09 PM, David Brown dbr...@sexingtechnologies.com wrote: Hello Luther, thanks for the informative and speedy reply. I'm going to take things one-step-at-a-time. So far, Igor is right about running the Start.class (as found in the test-classes directory). The only issue now is the Eclipse bug-a-boo about not copying the .HTML files along with the .CLASS files. See RuntimeException included below. As soon as I learn how to turn off the filter I will try your way if this fails. Yes, I am basically looking for anyway of speeding up the: edit, build, deploy cycle. Directly deploying .WAR files is OK once but since I'm trying to develop something for work I'm running out of time quickly. Thanks and regards, David. - Original Message - From: Luther Baker lutherba...@gmail.com To: users@wicket.apache.org Sent: Saturday, May 30, 2009 9:36:55 AM GMT -06:00 US/Canada Central Subject: Re: Wicket Quickstart vs WIA eclipse projects: why so different? For what its worth, I run a few Wicket 1.4x projects as within Eclipse/m2plugin and pages, etc refresh just fine. I use the Run/Debug Configurations and create a Maven application and then select the jetty plugin, correct workspace and jetty:run command. There are also Jetty options you can include directly in the POM file that define how and when Jetty should regularly will scan the deployed files ... restarting Jetty if changes detected. What I've described is too different mechanisms for picking up changes ... is that what you're asking for? -Luther On Sat, May 30, 2009 at 7:53 AM, Ben Tilford bentilf...@gmail.com wrote: Something that may be worth trying is mvn jetty:run-exploded On Fri, May 29, 2009 at 6:10 PM, Igor Vaynberg igor.vaynb...@gmail.com wrote: like i said, the best way is to right click the Start class and do run as java application. you can, of course, do it any other way you like - including installing jetty eclipse launcher plugin. -igor On Fri, May 29, 2009 at 3:17 PM, David Brown dbr...@sexingtechnologies.com wrote: Hello Igor, thanks for the reply. Can I just ignore the QuickStart embedded jetty and install jetty on Eclipse then do a run-as without any issues? Please advise, David. - Original Message - From: Igor Vaynberg igor.vaynb...@gmail.com To: users@wicket.apache.org Cc: david da...@davidwbrown.name Sent: Friday, May 29, 2009 4:51:02 PM GMT -06:00 US/Canada Central Subject: Re: Wicket Quickstart vs WIA eclipse projects: why so different? why dont you just start the project from eclipse directly using the Start class, that way you get debug and hotswap - which should be the real student's dream :) -igor On Fri, May 29, 2009 at 2:53 PM, David Brown dbr...@sexingtechnologies.com wrote: Hello Martin, Jeremy, dev, gurus, users and mortals. I have just finished ch. 13 of the WIA.pdf. I have followed closely the reading using the wicket-in-action eclipse project. I have the wicket-in-action running under the: mvn jetty:run. The wicket-in-action project is redeployed every 60 seconds (a student's dream). After finishing the 13th chapter I decided to leave the nest for the 1.4rc QuickStart. The new QuickStart project expanded and imported into the Eclipse workspace no-problemo. The mystery is what am I doing wrong to get the automatic 60 second re-deploy. As it stands now I have to kill jetty, mvn package and then restart jetty (mvn jetty:run). I have pasted in the: ** context-param param-nameconfiguration/param-name param-valuedevelopment/param-value /context-param ** from the wicket-in-action web.xml but no change. The Windows cmd console shows the usual Wicket WARNING: running in development mode. I plan to use the wicket-in-action almost verbatim including the Hibernate DAO for my current gig. It is probably only a few weeks before they start holding my feet to the fire. Please advise, David. - 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 - 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,
Re: Restarting AjaxLazyLoadingPanel
Yeah that's what I thought. And I tried it, but visually nothing
happened. I'll give it another shot.
Sent from my iPhone
http://friendfeed.com/astubbs
On 31/05/2009, at 7:15 AM, Igor Vaynberg igor.vaynb...@gmail.com
wrote:
you can just replace the entire panel with a new instance.
-igor
On Sat, May 30, 2009 at 3:11 AM, Antony Stubbs antony.stu...@gmail.com
wrote:
We use AjaxLazyLoadingPanel, and want to be able to trigger the
process of
showing the indicator, and requesting the panels contents with a
separate
Ajax request, after the first complete render has finished. I.e. do
the
whole process over and over, without having to reload the entire
page.
I came up with this, which I was surprised actually worked first
try :)
gotta love Wicket.
But perhaps there's a better way to do it ? A simpler way?
Something I'm
missing? I tried simply replacing the lazy loading panel with a new
instance
of one but that didn't seem to have an effect - I think the magic
is in the
adding a new AbstractAjaxBehaviour on each request.
import org.apache.wicket.Component;
import org.apache.wicket.ajax.AbstractDefaultAjaxBehavior;
import org.apache.wicket.ajax.AjaxRequestTarget;
import
org.apache.wicket.extensions.ajax.markup.html.AjaxLazyLoadPanel;
import org.apache.wicket.markup.html.IHeaderResponse;
/**
* An {...@link AjaxLazyLoadPanel} extension which allows it to
* {...@link #restart(AjaxRequestTarget)} the process of showing the
loading
* indicator, then load it's contents using a separate Ajax request.
*
* @author Antony Stubbs
*/
abstract public class ReloadingAjaxLazyPanel extends
AjaxLazyLoadPanel {
private static final long serialVersionUID = 1L;
public ReloadingAjaxLazyPanel(String id) {
super( id );
}
/**
* Causes the {...@link AjaxLazyLoadPanel} to re-display the loading
indicator,
* then in a seperate ajax request, get it's contents.
*
* @param target
*/
public void restart(AjaxRequestTarget target) {
target.addComponent( this );
// replace panel contents with loading icon
Component loadingComponent = getLoadingComponent( content );
this.replace( loadingComponent );
// add ajax behaviour to install call back
loadingComponent.add( new AbstractDefaultAjaxBehavior() {
private static final long serialVersionUID = 1L;
@Override
protected void respond(AjaxRequestTarget target) {
Component component =
ReloadingAjaxLazyPanel.this.getLazyLoadComponent( content );
ReloadingAjaxLazyPanel.this.replace(
component.setRenderBodyOnly( true ) );
target.addComponent( ReloadingAjaxLazyPanel.this );
// setState((byte)2);
}
@Override
public void renderHead(IHeaderResponse response) {
super.renderHead( response );
response.renderOnDomReadyJavascript(
getCallbackScript().toString() );
}
} );
}
}
As you can see, there is duplication from AjaxLazyLoadingPanel -
which would
need re-factoring in order to remove. - no problem there.
But also, because the setState method is private, I can't use that
state
system.
Regards,
Antony Stubbs,
NZ
http://friendfeed.com/astubbs
-
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: Error filterStart -- how to know what caused tomcat start failure?
Also, check out catalina.out On Sat, May 30, 2009 at 4:26 PM, David Chang david_q_zh...@yahoo.com wrote: Vitek, you are right. Under tomcat\logs directory, one type of logs called localhost contains more info than what tomcat start screen reveals. Thanks for the pointer. --- On Sat, 5/30/09, Vit Rozkovec rozkovec...@email.cz wrote: From: Vit Rozkovec rozkovec...@email.cz Subject: Re: Error filterStart -- how to know what caused tomcat start failure? To: users@wicket.apache.org Date: Saturday, May 30, 2009, 12:24 PM There are also other tomcat logs, have you looked into them? I found an cause of this error in other log, but I do not remember which one was that. Vitek David Chang wrote: I googled a lot but failed to find satisfactory answers. I just find a way to make tomcat to produce more error info than simply May 30, 2009 12:06:57 PM org.apache.catalina.core.StandardContext start SEVERE: Error filterStart May 30, 2009 12:06:57 PM org.apache.catalina.core.StandardContext start SEVERE: Context [/wic] startup failed due to previous errors I am learning from the book Wicket in Action. The funny thing is that the new stuff is no problem, but the tomcat error is. --- On Sat, 5/30/09, Mathias Nilsson wicket.program...@gmail.com wrote: From: Mathias Nilsson wicket.program...@gmail.com Subject: Re: Error filterStart -- how to know what caused tomcat start failure? To: users@wicket.apache.org Date: Saturday, May 30, 2009, 12:07 PM I guess this isn't wicket specific. goggle on your error and you may get information on how to solve this. -- View this message in context: http://www.nabble.com/Error-filterStarthow-to-know-what-caused-tomcat-start-failure--tp23794740p23794783.html Sent from the Wicket - User 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 - 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 - 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: Wicket Quickstart vs WIA eclipse projects: why so different?
Hello Igor, thanks - that did the trick. Regards, David. - Original Message - From: Igor Vaynberg igor.vaynb...@gmail.com To: users@wicket.apache.org Sent: Saturday, May 30, 2009 4:13:37 PM GMT -06:00 US/Canada Central Subject: Re: Wicket Quickstart vs WIA eclipse projects: why so different? window/preferences/compiler/building - remove *.html from output folder/filtered resources -igor On Sat, May 30, 2009 at 2:09 PM, David Brown dbr...@sexingtechnologies.com wrote: Hello Luther, thanks for the informative and speedy reply. I'm going to take things one-step-at-a-time. So far, Igor is right about running the Start.class (as found in the test-classes directory). The only issue now is the Eclipse bug-a-boo about not copying the .HTML files along with the .CLASS files. See RuntimeException included below. As soon as I learn how to turn off the filter I will try your way if this fails. Yes, I am basically looking for anyway of speeding up the: edit, build, deploy cycle. Directly deploying .WAR files is OK once but since I'm trying to develop something for work I'm running out of time quickly. Thanks and regards, David. - Original Message - From: Luther Baker lutherba...@gmail.com To: users@wicket.apache.org Sent: Saturday, May 30, 2009 9:36:55 AM GMT -06:00 US/Canada Central Subject: Re: Wicket Quickstart vs WIA eclipse projects: why so different? For what its worth, I run a few Wicket 1.4x projects as within Eclipse/m2plugin and pages, etc refresh just fine. I use the Run/Debug Configurations and create a Maven application and then select the jetty plugin, correct workspace and jetty:run command. There are also Jetty options you can include directly in the POM file that define how and when Jetty should regularly will scan the deployed files ... restarting Jetty if changes detected. What I've described is too different mechanisms for picking up changes ... is that what you're asking for? -Luther On Sat, May 30, 2009 at 7:53 AM, Ben Tilford bentilf...@gmail.com wrote: Something that may be worth trying is mvn jetty:run-exploded On Fri, May 29, 2009 at 6:10 PM, Igor Vaynberg igor.vaynb...@gmail.com wrote: like i said, the best way is to right click the Start class and do run as java application. you can, of course, do it any other way you like - including installing jetty eclipse launcher plugin. -igor On Fri, May 29, 2009 at 3:17 PM, David Brown dbr...@sexingtechnologies.com wrote: Hello Igor, thanks for the reply. Can I just ignore the QuickStart embedded jetty and install jetty on Eclipse then do a run-as without any issues? Please advise, David. - Original Message - From: Igor Vaynberg igor.vaynb...@gmail.com To: users@wicket.apache.org Cc: david da...@davidwbrown.name Sent: Friday, May 29, 2009 4:51:02 PM GMT -06:00 US/Canada Central Subject: Re: Wicket Quickstart vs WIA eclipse projects: why so different? why dont you just start the project from eclipse directly using the Start class, that way you get debug and hotswap - which should be the real student's dream :) -igor On Fri, May 29, 2009 at 2:53 PM, David Brown dbr...@sexingtechnologies.com wrote: Hello Martin, Jeremy, dev, gurus, users and mortals. I have just finished ch. 13 of the WIA.pdf. I have followed closely the reading using the wicket-in-action eclipse project. I have the wicket-in-action running under the: mvn jetty:run. The wicket-in-action project is redeployed every 60 seconds (a student's dream). After finishing the 13th chapter I decided to leave the nest for the 1.4rc QuickStart. The new QuickStart project expanded and imported into the Eclipse workspace no-problemo. The mystery is what am I doing wrong to get the automatic 60 second re-deploy. As it stands now I have to kill jetty, mvn package and then restart jetty (mvn jetty:run). I have pasted in the: ** context-param param-nameconfiguration/param-name param-valuedevelopment/param-value /context-param ** from the wicket-in-action web.xml but no change. The Windows cmd console shows the usual Wicket WARNING: running in development mode. I plan to use the wicket-in-action almost verbatim including the Hibernate DAO for my current gig. It is probably only a few weeks before they start holding my feet to the fire. Please advise, David. - 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: OutOfMemory on certain combinations of controls
Thanks Igor. I didn't think about the callback keeping a reference to the calling page. I appreciate your help. igor.vaynberg wrote: the problem is the page inside the modal window has a reference to the outer page - you pass the modal window which has an anonymous close callback which keeps a reference to the page. so you keep serializing the entire page with every ajax request as part of the current page. you dont need the reference to the modalwindow, you can use ModalWindow.closeCurrent() to close it. -igor On Fri, May 29, 2009 at 1:45 PM, Flavius flav...@silverlion.com wrote: I put a quickstart build up at http://silverlion.com/tmp2/OutOfMemory.zip. Just unzip it, change to that dir and run mvn jetty:run and go to http://localhost:8080/OutOfMemory It has just one page, one modal window, one border, and one panel. The steps to repro this are there on the home page. Thanks for your help, Igor. igor.vaynberg wrote: there is too much going on in the sample you posted. if you want you can create a quickstart with the minimal amount of code necessary to reproduce this and i will take a look. -igor On Thu, May 28, 2009 at 2:12 PM, Flavius flav...@silverlion.com wrote: The sample I posted only has the single page with a link to the ModalWindow. The modal window keeps a reference to the ModalWindow param passed in to the constructor. That's only used to close the window when the AjaxRequestTarget is passed from the AjaxLink. When the OnChangeAjaxBehavior#onUpdate fires, it's rebuilding the repeating view and adding the WebMarkupContainer wrapper to the AjaxRequestTarget. So it's not keeping any references that I see. igor.vaynberg wrote: make sure you dont keep page references across pages. that may be it. -igor -- View this message in context: http://www.nabble.com/OutOfMemory-on-certain-combinations-of-controls-tp23750424p23770219.html Sent from the Wicket - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/OutOfMemory-on-certain-combinations-of-controls-tp23750424p23786803.html Sent from the Wicket - User 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- View this message in context: http://www.nabble.com/OutOfMemory-on-certain-combinations-of-controls-tp23750424p23799634.html Sent from the Wicket - User 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
how to reset a form
My application is using hibernate and wicket , I am trying to reset my form , My form model is hibernate entity and its LoadableDetachableModel . In order to reset my form I added ajax button , hoping to call form.clearInput () in the onSubmit , but realized that before the onSubmit , form updates model and becasue I am using hibernate open view session filter, my entity is persisted automatically , so instead of resetting I am persisting the form model , please help me how can I rest my form ?
