You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Controller actions do not get created when instantiation event is disabled.
config {
events {
instantiation = false
}
}
DefaultApplicationConfigurer has at least 2 dependencies on this event.
Can the Griffon guide please be updated to indicate this, as well disabling events can break plugins - e.g. Preferences plugin is dependent on the event (refer AbstractPreferencesManager constuctor). Specific dependencies on application lifecycle events could be listed in plugin guides.
The text was updated successfully, but these errors were encountered:
actually the Injector listens to NewInstance to invoke methods annotated with @PostConstruct. I'm thinking that adding the feature to skip instantiation and destruction events was not a good idea. Out of curiosity, why do you have to skip these events?
I was simply trying out the feature and ran into the issue - I was considering disabling events for some performance gain. I agree that disabling a feature which skips events required by the core framework makes sense.
Controller actions do not get created when instantiation event is disabled.
DefaultApplicationConfigurer has at least 2 dependencies on this event.
Can the Griffon guide please be updated to indicate this, as well disabling events can break plugins - e.g. Preferences plugin is dependent on the event (refer AbstractPreferencesManager constuctor). Specific dependencies on application lifecycle events could be listed in plugin guides.
The text was updated successfully, but these errors were encountered: