Re: Markup Reloading
yeah well, that is a pretty extreme and unnecessary hack :)
not to mention it is not disabled in deployment mode...
-igor
On Sun, Mar 2, 2008 at 12:13 AM, carloc <[EMAIL PROTECTED]> wrote:
>
> This is what I did and it seems to work alreadyl.
>
> addComponentInstantiationListener(new
> IComponentInstantiationListener() {
>
> public void onInstantiation(Component component) {
> // TODO Auto-generated method stub
> System.out.println("HELLO");
>
> get().getMarkupSettings().getMarkupCache().clear();
> }
>
> });
>
>
>
> igor.vaynberg wrote:
> >
> > if wicket is in development mode it will reload resources on the fly.
> > if this is not working for you then something is not properly
> > configured, eg when you save your .css file your ide does not copy it
> > out of src folder into classes folder...
> >
> > -igor
> >
> >
> > On Sat, Mar 1, 2008 at 9:57 AM, carloc <[EMAIL PROTECTED]> wrote:
> >>
> >> Hi Guys,
> >>
> >> I've noticed that everytime I want to change something in my markup I
> >> would
> >> need to restart
> >> the server as the changes don't take effect immediately. Is there
> >> anything I
> >> can do to avoid this behavior?
> >> I'm trying to adjust my css and i'm spending more time restarting the
> >> server...
> >>
> >> Thanks
> >> Carlo
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Markup-Reloading-tp15779009p15779009.html
> >> Sent from the Wicket - User mailing list archive at Nabble.com.
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Markup-Reloading-tp15779009p15784708.html
>
>
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Markup Reloading
This is what I did and it seems to work alreadyl.
addComponentInstantiationListener(new IComponentInstantiationListener()
{
public void onInstantiation(Component component) {
// TODO Auto-generated method stub
System.out.println("HELLO");
get().getMarkupSettings().getMarkupCache().clear();
}
});
igor.vaynberg wrote:
>
> if wicket is in development mode it will reload resources on the fly.
> if this is not working for you then something is not properly
> configured, eg when you save your .css file your ide does not copy it
> out of src folder into classes folder...
>
> -igor
>
>
> On Sat, Mar 1, 2008 at 9:57 AM, carloc <[EMAIL PROTECTED]> wrote:
>>
>> Hi Guys,
>>
>> I've noticed that everytime I want to change something in my markup I
>> would
>> need to restart
>> the server as the changes don't take effect immediately. Is there
>> anything I
>> can do to avoid this behavior?
>> I'm trying to adjust my css and i'm spending more time restarting the
>> server...
>>
>> Thanks
>> Carlo
>> --
>> View this message in context:
>> http://www.nabble.com/Markup-Reloading-tp15779009p15779009.html
>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> -----
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Markup-Reloading-tp15779009p15784708.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Markup Reloading
my setup is pretty simple. i use eclipse with the Start class that is generated using wicket-quickstart archetype. the only change i had to make was in eclipse preferences: java/compiler/building/filtererd resources - i remove *.html from filtered resources. other then that everything is reloading as it should be in ffox/explorer/foo. i just right click Start class and do run/debug as java application, thats it. -igor On Sat, Mar 1, 2008 at 11:32 PM, carloc <[EMAIL PROTECTED]> wrote: > > It's being transferred properly. I've noticed that when I run it on Europa > tomcat server it works properly. However server is reloaded in the > background everytime it is run. > When I use the embedded jetty server witht eh wicket start application, I've > noticed that it has something to do with the cache. When I try to switch > from browser to browser, the changes effect properly. HOwever, clearing the > cache of firefox for example won't do a thing. I would need to change to > konqueror > or something to see my changes. > > What application server launcher do you recommend or something? > > > > > > igor.vaynberg wrote: > > > > if wicket is in development mode it will reload resources on the fly. > > if this is not working for you then something is not properly > > configured, eg when you save your .css file your ide does not copy it > > out of src folder into classes folder... > > > > -igor > > > > > > On Sat, Mar 1, 2008 at 9:57 AM, carloc <[EMAIL PROTECTED]> wrote: > >> > >> Hi Guys, > >> > >> I've noticed that everytime I want to change something in my markup I > >> would > >> need to restart > >> the server as the changes don't take effect immediately. Is there > >> anything I > >> can do to avoid this behavior? > >> I'm trying to adjust my css and i'm spending more time restarting the > >> server... > >> > >> Thanks > >> Carlo > >> -- > >> View this message in context: > >> http://www.nabble.com/Markup-Reloading-tp15779009p15779009.html > >> Sent from the Wicket - User mailing list archive at Nabble.com. > >> > >> > >> - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > View this message in context: > http://www.nabble.com/Markup-Reloading-tp15779009p15784702.html > > > Sent from the Wicket - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Markup Reloading
It's being transferred properly. I've noticed that when I run it on Europa tomcat server it works properly. However server is reloaded in the background everytime it is run. When I use the embedded jetty server witht eh wicket start application, I've noticed that it has something to do with the cache. When I try to switch from browser to browser, the changes effect properly. HOwever, clearing the cache of firefox for example won't do a thing. I would need to change to konqueror or something to see my changes. What application server launcher do you recommend or something? igor.vaynberg wrote: > > if wicket is in development mode it will reload resources on the fly. > if this is not working for you then something is not properly > configured, eg when you save your .css file your ide does not copy it > out of src folder into classes folder... > > -igor > > > On Sat, Mar 1, 2008 at 9:57 AM, carloc <[EMAIL PROTECTED]> wrote: >> >> Hi Guys, >> >> I've noticed that everytime I want to change something in my markup I >> would >> need to restart >> the server as the changes don't take effect immediately. Is there >> anything I >> can do to avoid this behavior? >> I'm trying to adjust my css and i'm spending more time restarting the >> server... >> >> Thanks >> Carlo >> -- >> View this message in context: >> http://www.nabble.com/Markup-Reloading-tp15779009p15779009.html >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Markup-Reloading-tp15779009p15784702.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Markup Reloading
Thanks, I'll give that a go. > i think it is: > > getapplication().getmarkupsettings().getmarkupcache().clear(); which > will clear the entire cache. > > there is also a jmx hook. > > -igor > > > On Sat, Mar 1, 2008 at 3:25 PM, Chris Colman > <[EMAIL PROTECTED]> wrote: > > > On Sat, Mar 1, 2008 at 3:10 PM, Chris Colman > > > <[EMAIL PROTECTED]> wrote: > > > > I have a similar problem but it's to do with creating new markup > > > > variations - each new one I add requires a server restart for it > to > > be > > > > detected. Apparently customers don't like that for some strange > > reason > > > > =) > > > > > > we cache the fact that variation does not exist, otherwise we would > > > have to perform the expensive search every time. your problem can be > > > solved by clearing the markup cache after you deploy new variations - > > > that should work even in production mode servers. > > > > > > -igor > > > > Arh, now I understand the mechanism. The cache doesn't only cache > > existing markup variations it also caches tokens that say, "this markup > > variation does not exist". So it's caching non existent entities ... > > which sounds very strange at first but I can understand why that makes > > sense for performance reasons. > > > > How would one go about clearing this cache? Is it possible to just > clear > > a specific page's cache of a non existent variant or it a "clear > entire" > > cache a better approach. Clearing the entire cache seems easier and is > a > > 100% improvement over rebouncing the entire web app. > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Markup Reloading
i think it is: getapplication().getmarkupsettings().getmarkupcache().clear(); which will clear the entire cache. there is also a jmx hook. -igor On Sat, Mar 1, 2008 at 3:25 PM, Chris Colman <[EMAIL PROTECTED]> wrote: > > On Sat, Mar 1, 2008 at 3:10 PM, Chris Colman > > <[EMAIL PROTECTED]> wrote: > > > I have a similar problem but it's to do with creating new markup > > > variations - each new one I add requires a server restart for it to > be > > > detected. Apparently customers don't like that for some strange > reason > > > =) > > > > we cache the fact that variation does not exist, otherwise we would > > have to perform the expensive search every time. your problem can be > > solved by clearing the markup cache after you deploy new variations - > > that should work even in production mode servers. > > > > -igor > > Arh, now I understand the mechanism. The cache doesn't only cache > existing markup variations it also caches tokens that say, "this markup > variation does not exist". So it's caching non existent entities ... > which sounds very strange at first but I can understand why that makes > sense for performance reasons. > > How would one go about clearing this cache? Is it possible to just clear > a specific page's cache of a non existent variant or it a "clear entire" > cache a better approach. Clearing the entire cache seems easier and is a > 100% improvement over rebouncing the entire web app. > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Markup Reloading
> On Sat, Mar 1, 2008 at 3:10 PM, Chris Colman > <[EMAIL PROTECTED]> wrote: > > I have a similar problem but it's to do with creating new markup > > variations - each new one I add requires a server restart for it to be > > detected. Apparently customers don't like that for some strange reason > > =) > > we cache the fact that variation does not exist, otherwise we would > have to perform the expensive search every time. your problem can be > solved by clearing the markup cache after you deploy new variations - > that should work even in production mode servers. > > -igor Arh, now I understand the mechanism. The cache doesn't only cache existing markup variations it also caches tokens that say, "this markup variation does not exist". So it's caching non existent entities ... which sounds very strange at first but I can understand why that makes sense for performance reasons. How would one go about clearing this cache? Is it possible to just clear a specific page's cache of a non existent variant or it a "clear entire" cache a better approach. Clearing the entire cache seems easier and is a 100% improvement over rebouncing the entire web app. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Markup Reloading
On Sat, Mar 1, 2008 at 3:10 PM, Chris Colman <[EMAIL PROTECTED]> wrote: > I have a similar problem but it's to do with creating new markup > variations - each new one I add requires a server restart for it to be > detected. Apparently customers don't like that for some strange reason > =) we cache the fact that variation does not exist, otherwise we would have to perform the expensive search every time. your problem can be solved by clearing the markup cache after you deploy new variations - that should work even in production mode servers. -igor > > I think your problem is easily solved - you just have to run you > production server in development mode but even in development mode my > problem is not solved. > > > > > Hi Guys, > > > > I've noticed that everytime I want to change something in my markup I > > would > > need to restart > > the server as the changes don't take effect immediately. Is there > anything > > I > > can do to avoid this behavior? > > I'm trying to adjust my css and i'm spending more time restarting the > > server... > > > > Thanks > > Carlo > > -- > > View this message in context: http://www.nabble.com/Markup-Reloading- > > tp15779009p15779009.html > > Sent from the Wicket - User mailing list archive at Nabble.com. > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Markup Reloading
I have a similar problem but it's to do with creating new markup variations - each new one I add requires a server restart for it to be detected. Apparently customers don't like that for some strange reason =) I think your problem is easily solved - you just have to run you production server in development mode but even in development mode my problem is not solved. > Hi Guys, > > I've noticed that everytime I want to change something in my markup I > would > need to restart > the server as the changes don't take effect immediately. Is there anything > I > can do to avoid this behavior? > I'm trying to adjust my css and i'm spending more time restarting the > server... > > Thanks > Carlo > -- > View this message in context: http://www.nabble.com/Markup-Reloading- > tp15779009p15779009.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Markup Reloading
if wicket is in development mode it will reload resources on the fly. if this is not working for you then something is not properly configured, eg when you save your .css file your ide does not copy it out of src folder into classes folder... -igor On Sat, Mar 1, 2008 at 9:57 AM, carloc <[EMAIL PROTECTED]> wrote: > > Hi Guys, > > I've noticed that everytime I want to change something in my markup I would > need to restart > the server as the changes don't take effect immediately. Is there anything I > can do to avoid this behavior? > I'm trying to adjust my css and i'm spending more time restarting the > server... > > Thanks > Carlo > -- > View this message in context: > http://www.nabble.com/Markup-Reloading-tp15779009p15779009.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Markup Reloading
Hi Guys, I've noticed that everytime I want to change something in my markup I would need to restart the server as the changes don't take effect immediately. Is there anything I can do to avoid this behavior? I'm trying to adjust my css and i'm spending more time restarting the server... Thanks Carlo -- View this message in context: http://www.nabble.com/Markup-Reloading-tp15779009p15779009.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
