Turning off ModificationWatcher

[Matt Welch]

I'm experimenting with Wicket inside Google's new Java support for its App
Engine. My simple apps run fine if the configuration is set to DEPLOYMENT,
however in development mode, I get an exception related to
ModificationWatcher. Looking at the exception I think this
ModificationWatcher is being used as part of a new thread which is a no-no
inside the App Engine sandbox. Is there way way to just disbable this
modification watcher without putting the entire app in deployment mode?
There are a number of items I like about development mode but this one
glitch is preventing me from using it.

Matt

[Ryan Crumley]

Matt,

Add this to your WebApplication.init() method:

getResourceSettings().setResourcePollFrequency(null);

Ryan

On Wed, Apr 8, 2009 at 9:33 PM, Matthew Welch <matthew@...> wrote:

> I'm experimenting with Wicket inside Google's new Java support for its App
> Engine. My simple apps run fine if the configuration is set to DEPLOYMENT,
> however in development mode, I get an exception related to
> ModificationWatcher. Looking at the exception I think this
> ModificationWatcher is being used as part of a new thread which is a no-no
> inside the App Engine sandbox. Is there way way to just disbable this
> modification watcher without putting the entire app in deployment mode?
> There are a number of items I like about development mode but this one
> glitch is preventing me from using it.
>
> Matt
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jonathan Locke]

not sure, but try getResourceSettings().setResourcePollFrequency(null) in your app init

Matt Welch wrote:

I'm experimenting with Wicket inside Google's new Java support for its App
Engine. My simple apps run fine if the configuration is set to DEPLOYMENT,
however in development mode, I get an exception related to
ModificationWatcher. Looking at the exception I think this
ModificationWatcher is being used as part of a new thread which is a no-no
inside the App Engine sandbox. Is there way way to just disbable this
modification watcher without putting the entire app in deployment mode?
There are a number of items I like about development mode but this one
glitch is preventing me from using it.

Matt

[Martijn Dashorst]

Never *EVER* deploy your application in development mode. Use
deployment mode and turn those features you want on.

Martijn

On Thu, Apr 9, 2009 at 4:33 AM, Matthew Welch <matthew@...> wrote:

> I'm experimenting with Wicket inside Google's new Java support for its App
> Engine. My simple apps run fine if the configuration is set to DEPLOYMENT,
> however in development mode, I get an exception related to
> ModificationWatcher. Looking at the exception I think this
> ModificationWatcher is being used as part of a new thread which is a no-no
> inside the App Engine sandbox. Is there way way to just disbable this
> modification watcher without putting the entire app in deployment mode?
> There are a number of items I like about development mode but this one
> glitch is preventing me from using it.
>
> Matt
>

--
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-unsubscribe@...
For additional commands, e-mail: users-help@...

[Matt Welch]

I have no intention of actually deploying it in development mode.

I'm talking about the development sandbox provided by the Google App Engine Java SDK.

Matt

Martijn Dashorst wrote:

Never *EVER* deploy your application in development mode. Use
deployment mode and turn those features you want on.

Martijn

On Thu, Apr 9, 2009 at 4:33 AM, Matthew Welch <[e-mail]> wrote:
> I'm experimenting with Wicket inside Google's new Java support for its App
> Engine. My simple apps run fine if the configuration is set to DEPLOYMENT,
> however in development mode, I get an exception related to
> ModificationWatcher. Looking at the exception I think this
> ModificationWatcher is being used as part of a new thread which is a no-no
> inside the App Engine sandbox. Is there way way to just disbable this
> modification watcher without putting the entire app in deployment mode?
> There are a number of items I like about development mode but this one
> glitch is preventing me from using it.
>
> Matt
>



--
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: [e-mail]
For additional commands, e-mail: [e-mail]

[Matt Welch]

Thanks.

Matt

Ryan Crumley wrote:

Matt,

Add this to your WebApplication.init() method:

getResourceSettings().setResourcePollFrequency(null);

Ryan

On Wed, Apr 8, 2009 at 9:33 PM, Matthew Welch <[e-mail]> wrote:
> I'm experimenting with Wicket inside Google's new Java support for its App
> Engine. My simple apps run fine if the configuration is set to DEPLOYMENT,
> however in development mode, I get an exception related to
> ModificationWatcher. Looking at the exception I think this
> ModificationWatcher is being used as part of a new thread which is a no-no
> inside the App Engine sandbox. Is there way way to just disbable this
> modification watcher without putting the entire app in deployment mode?
> There are a number of items I like about development mode but this one
> glitch is preventing me from using it.
>
> Matt
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [e-mail]
For additional commands, e-mail: [e-mail]

[igor.vaynberg]

it is much simpler and more efficient to set proper caching headers.
concatenating resources often does not work because different
components on different pages contribute different resources, so there
are a lot of variations of these huge files you may end up with and
would have to stream to the user over and over. yes, it would only be
one request per page, but it would be a huge one over and over as
opposed to being able to cache a lot of small resources and never
request them again.

-igor

On Thu, Apr 9, 2009 at 9:00 AM, Matt Welch <matthew@...> wrote:

>
> Thanks.
>
> Matt
>
>
> Ryan Crumley wrote:
>>
>> Matt,
>>
>> Add this to your WebApplication.init() method:
>>
>> getResourceSettings().setResourcePollFrequency(null);
>>
>> Ryan
>>
>> On Wed, Apr 8, 2009 at 9:33 PM, Matthew Welch <matthew@...>
>> wrote:
>>> I'm experimenting with Wicket inside Google's new Java support for its
>>> App
>>> Engine. My simple apps run fine if the configuration is set to
>>> DEPLOYMENT,
>>> however in development mode, I get an exception related to
>>> ModificationWatcher. Looking at the exception I think this
>>> ModificationWatcher is being used as part of a new thread which is a
>>> no-no
>>> inside the App Engine sandbox. Is there way way to just disbable this
>>> modification watcher without putting the entire app in deployment mode?
>>> There are a number of items I like about development mode but this one
>>> glitch is preventing me from using it.
>>>
>>> Matt
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Turning-off-ModificationWatcher-tp22963478p22973975.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Sam Stainsby-2]

On Thu, 09 Apr 2009 08:41:20 +0200, Martijn Dashorst wrote:

> Never *EVER* deploy your application in development mode. Use deployment
> mode and turn those features you want on.

Just curious - does something catastrophic happen? I'm running a testing
demo for a client and haven't bothered turning off development mode (I
assume it is on by default?). It runs fine.

Cheers,
Sam.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[nick-224]

Thank you for your mail. I am presently on vacation and will return April 14th.  

If you need urgent assistance, please email support@.... You can also reach our Support via Skype callto://premiersupport

Thank you

Best regards,

Nick Wheeler

Booking Booster.com
t: [phone]
e: integration@...

a: The Brighton Forum
95 Ditchling Road
Brighton BN1 4ST
East Sussex
United Kingdom
Booking Booster is the smarter, easier and more elegant way to update agent websites. Save time, Boost Bookings with: http://www.bookingbooster.com





---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Martin Voigt-2]

Na, nothing "catastrophic" will happen, or else you won't be able to
development your app using development configuration...HOWEVER...the
performance of your app is likely to double when running in deployment
mode, some exceptions won't be visible to the user (i think
component-in-use-check and others), serialization checks won't slow
you down, that kind of stuff.

If you look at the WebApplication class, you will find lots of getters
like getRequestSettings(), getApplicationSettings() and so forth, from
what I know, development configuration is a defined set of these
configs which sorely focus on helping you while developing, but they
won't help you at all while running in production mode, cos they're
not optimized for that. On the other hand, deployment configuration is
a defined set of these configs which sorely help you getting
performance and "be in production".

It's like running your app with logging on trace level when in
development...If your app is any good, it may be it won't harm you at
all (we had an app out in production running in development mode for
weeks), but your performance will suffer for sure.

bw,
Martin

2009/4/10 Sam Stainsby <sam@...>:

> On Thu, 09 Apr 2009 08:41:20 +0200, Martijn Dashorst wrote:
>
>> Never *EVER* deploy your application in development mode. Use deployment
>> mode and turn those features you want on.
>
> Just curious - does something catastrophic happen? I'm running a testing
> demo for a client and haven't bothered turning off development mode (I
> assume it is on by default?). It runs fine.
>
> Cheers,
> Sam.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jonathan Locke]

Oh, it's MUCH worse than even that. Every single component constructed by your application will get a complete Java stack trace attached to it at the point of construction. Not only does that seriously damage your performance, but this stack trace also takes up space! This is why we warn you about not deploying in development mode on startup.

Martin Voigt-2 wrote:

Na, nothing "catastrophic" will happen, or else you won't be able to
development your app using development configuration...HOWEVER...the
performance of your app is likely to double when running in deployment
mode, some exceptions won't be visible to the user (i think
component-in-use-check and others), serialization checks won't slow
you down, that kind of stuff.

If you look at the WebApplication class, you will find lots of getters
like getRequestSettings(), getApplicationSettings() and so forth, from
what I know, development configuration is a defined set of these
configs which sorely focus on helping you while developing, but they
won't help you at all while running in production mode, cos they're
not optimized for that. On the other hand, deployment configuration is
a defined set of these configs which sorely help you getting
performance and "be in production".

It's like running your app with logging on trace level when in
development...If your app is any good, it may be it won't harm you at
all (we had an app out in production running in development mode for
weeks), but your performance will suffer for sure.

bw,
Martin

2009/4/10 Sam Stainsby <[e-mail]>:
> On Thu, 09 Apr 2009 08:41:20 +0200, Martijn Dashorst wrote:
>
>> Never *EVER* deploy your application in development mode. Use deployment
>> mode and turn those features you want on.
>
> Just curious - does something catastrophic happen? I'm running a testing
> demo for a client and haven't bothered turning off development mode (I
> assume it is on by default?). It runs fine.
>
> Cheers,
> Sam.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [e-mail]
> For additional commands, e-mail: [e-mail]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [e-mail]
For additional commands, e-mail: [e-mail]

[Jonathan Locke]

Oh, it's MUCH worse than even that. Every single component constructed by
your application will get a complete Java stack trace attached to it at the
point of construction. Not only does that seriously damage your performance,
but this stack trace also takes up space! This is why we warn you about not
deploying in development mode on startup.


Martin Voigt-2 wrote:

>
> Na, nothing "catastrophic" will happen, or else you won't be able to
> development your app using development configuration...HOWEVER...the
> performance of your app is likely to double when running in deployment
> mode, some exceptions won't be visible to the user (i think
> component-in-use-check and others), serialization checks won't slow
> you down, that kind of stuff.
>
> If you look at the WebApplication class, you will find lots of getters
> like getRequestSettings(), getApplicationSettings() and so forth, from
> what I know, development configuration is a defined set of these
> configs which sorely focus on helping you while developing, but they
> won't help you at all while running in production mode, cos they're
> not optimized for that. On the other hand, deployment configuration is
> a defined set of these configs which sorely help you getting
> performance and "be in production".
>
> It's like running your app with logging on trace level when in
> development...If your app is any good, it may be it won't harm you at
> all (we had an app out in production running in development mode for
> weeks), but your performance will suffer for sure.
>
> bw,
> Martin
>
> 2009/4/10 Sam Stainsby <sam@...>:
>> On Thu, 09 Apr 2009 08:41:20 +0200, Martijn Dashorst wrote:
>>
>>> Never *EVER* deploy your application in development mode. Use deployment
>>> mode and turn those features you want on.
>>
>> Just curious - does something catastrophic happen? I'm running a testing
>> demo for a client and haven't bothered turning off development mode (I
>> assume it is on by default?). It runs fine.
>>
>> Cheers,
>> Sam.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>
>

--
View this message in context: http://www.nabble.com/Turning-off-ModificationWatcher-tp22963478p22981612.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[igor.vaynberg]

i dont think that is on by default anymore. it made the app too slow
even for dev mode :)

-igor

On Thu, Apr 9, 2009 at 6:07 PM, Jonathan Locke <jonathan.locke@...> wrote:

>
>
> Oh, it's MUCH worse than even that. Every single component constructed by
> your application will get a complete Java stack trace attached to it at the
> point of construction. Not only does that seriously damage your performance,
> but this stack trace also takes up space! This is why we warn you about not
> deploying in development mode on startup.
>
>
> Martin Voigt-2 wrote:
>>
>> Na, nothing "catastrophic" will happen, or else you won't be able to
>> development your app using development configuration...HOWEVER...the
>> performance of your app is likely to double when running in deployment
>> mode, some exceptions won't be visible to the user (i think
>> component-in-use-check and others), serialization checks won't slow
>> you down, that kind of stuff.
>>
>> If you look at the WebApplication class, you will find lots of getters
>> like getRequestSettings(), getApplicationSettings() and so forth, from
>> what I know, development configuration is a defined set of these
>> configs which sorely focus on helping you while developing, but they
>> won't help you at all while running in production mode, cos they're
>> not optimized for that. On the other hand, deployment configuration is
>> a defined set of these configs which sorely help you getting
>> performance and "be in production".
>>
>> It's like running your app with logging on trace level when in
>> development...If your app is any good, it may be it won't harm you at
>> all (we had an app out in production running in development mode for
>> weeks), but your performance will suffer for sure.
>>
>> bw,
>> Martin
>>
>> 2009/4/10 Sam Stainsby <sam@...>:
>>> On Thu, 09 Apr 2009 08:41:20 +0200, Martijn Dashorst wrote:
>>>
>>>> Never *EVER* deploy your application in development mode. Use deployment
>>>> mode and turn those features you want on.
>>>
>>> Just curious - does something catastrophic happen? I'm running a testing
>>> demo for a client and haven't bothered turning off development mode (I
>>> assume it is on by default?). It runs fine.
>>>
>>> Cheers,
>>> Sam.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@...
>>> For additional commands, e-mail: users-help@...
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Turning-off-ModificationWatcher-tp22963478p22981611.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[cretzel]

This way you won't get no exceptions any more, but it's also terrible to develop without ModificationWatching. GAE does not allow spawning threads even in the local development environment.

I tried to use my own implementation of a modification watcher, that does not spawn any threads but instead it does the modification watching before every request. Unfortunately it's not possible to replace the default ModificationWatcher in Wicket, because it's got dependencies to the concrete default ModificationWatcher and that is final, so you can't replace it with another implementation.

You can work around this by doing some classpath messing and put your own ModificationWatcher implementation in your project into same package org.apache.wicket.util.watch of the Wicket ModificationWatcher see here.

Would be nice if Wicket relied on an interface IModificationWatcher in future versions, so that it can be replaced by a customized version. Or don't make it final.

- cretzel




not sure, but try getResourceSettings().setResourcePollFrequency(null) in your app init

Matt Welch wrote:

I'm experimenting with Wicket inside Google's new Java support for its App
Engine. My simple apps run fine if the configuration is set to DEPLOYMENT,
however in development mode, I get an exception related to
ModificationWatcher. Looking at the exception I think this
ModificationWatcher is being used as part of a new thread which is a no-no
inside the App Engine sandbox. Is there way way to just disbable this
modification watcher without putting the entire app in deployment mode?
There are a number of items I like about development mode but this one
glitch is preventing me from using it.

Matt

[igor.vaynberg]

or you can add an rfe into jira to make it more open...

-igor

On Thu, Jun 18, 2009 at 3:11 PM, cretzel<mailinglists.nw@...> wrote:

>
> This way you won't get no exceptions any more, but it's also terrible to
> develop without ModificationWatching. GAE does not allow spawning threads
> even in the local development environment.
>
> I tried to use my own implementation of a modification watcher, that does
> not spawn any threads but instead it does the modification watching before
> every request. Unfortunately it's not possible to replace the default
> ModificationWatcher in Wicket, because it's got dependencies to the concrete
> default ModificationWatcher and that is final, so you can't replace it with
> another implementation.
>
> You can work around this by doing some classpath messing and put your own
> ModificationWatcher implementation in your project into same package
> org.apache.wicket.util.watch of the Wicket ModificationWatcher see
> http://kimenye.blogspot.com/2009/06/google-app-engine-wicket.html here .
>
> Would be nice if Wicket relied on an interface IModificationWatcher in
> future versions, so that it can be replaced by a customized version. Or
> don't make it final.
>
> - cretzel
>
>
>
> Jonathan Locke wrote:
>>
>>
>> not sure, but try getResourceSettings().setResourcePollFrequency(null) in
>> your app init
>>
>>
>> Matt Welch wrote:
>>>
>>> I'm experimenting with Wicket inside Google's new Java support for its
>>> App
>>> Engine. My simple apps run fine if the configuration is set to
>>> DEPLOYMENT,
>>> however in development mode, I get an exception related to
>>> ModificationWatcher. Looking at the exception I think this
>>> ModificationWatcher is being used as part of a new thread which is a
>>> no-no
>>> inside the App Engine sandbox. Is there way way to just disbable this
>>> modification watcher without putting the entire app in deployment mode?
>>> There are a number of items I like about development mode but this one
>>> glitch is preventing me from using it.
>>>
>>> Matt
>>>
>>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Turning-off-ModificationWatcher-tp22963478p24099680.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[cretzel]

Posted https://issues.apache.org/jira/browse/WICKET-2340

igor.vaynberg wrote:

or you can add an rfe into jira to make it more open...

-igor

[cretzel]

Fixed as of Wicket 1.4.0-RC6.

"now uses an interface. you may use IResourceSettings.setResourceWatcher() to set whatever IModificationWatcher you want "


Posted https://issues.apache.org/jira/browse/WICKET-2340

igor.vaynberg wrote:

or you can add an rfe into jira to make it more open...

-igor