Activity

Up until now this was not needed the loading strategy was working on a simple algorithm because there was no dynamic change in the structures, myfaces was fully restructured upon artefact changes on faces-config level.
This works according to the source for managed beans nad nav handlers nothing more.

Now we introduce annotations this has to become more dynamic and has to react to annotations (which myfaces up until does not do)

Now we have to dynamically readjust our loading strategy from depending on what is changed (bean removed, class changed, manged property has changed etc...)
but we have to make a backpath from our 2.0 extensions into the core.

An intra module event system should be established which basically gives feedback to the core on what has happend internally so that the loading strategies can adjust to the current state the reloading system is in.

Werner Punz
added a comment - 25/Sep/09 16:37 Up until now this was not needed the loading strategy was working on a simple algorithm because there was no dynamic change in the structures, myfaces was fully restructured upon artefact changes on faces-config level.
This works according to the source for managed beans nad nav handlers nothing more.
Now we introduce annotations this has to become more dynamic and has to react to annotations (which myfaces up until does not do)
Now we have to dynamically readjust our loading strategy from depending on what is changed (bean removed, class changed, manged property has changed etc...)
but we have to make a backpath from our 2.0 extensions into the core.
An intra module event system should be established which basically gives feedback to the core on what has happend internally so that the loading strategies can adjust to the current state the reloading system is in.