[Wonder-disc] ERXFileNotificationCenter is now tightly coupled with ERXApplication -- does it have to be?

[<aro...@cl...>]

Hello WOnder team,

I noticed that ERXFileNotificationCenter is now tightly coupled with 
ERXApplication and I'm wondering if this can be changed. This wasn't 
always the case and occurred in revision 1.15, Thu Jan 11.

It's in the constructor where it tries to determine if the App is run in 
development mode by getting the Application instance and casting it to 
ERXApplication. For us, this change causes a class cast exception because 
we don't extend our Application.java from ERXApplication. We like WOnder 
but aren't yet ready to convert everything over. 

Would it be too much to ask that the constructor first tries to create an 
instance of ERXApplication but if that fails fall back to checking if 
caching is enabled from an instance of WOApplication?

Perhaps something like the following:

    public ERXFileNotificationCenter() {
        try {
                developmentMode = 
ERXApplication.erxApplication().isDevelopmentMode();
        }
        catch ( ClassCastException e ) {
                developmentMode = ! 
WOApplication.application().isCachingEnabled();
        }

        ...

Do you think you could commit this change?

Thanks so much,
-- Aaron