Issue Details (XML | Word | Printable)

Key: GRAILS-820
Type: Sub-task Sub-task
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Marc Palmer
Reporter: Marc Palmer
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Grails
GRAILS-814

Make plugins register their arefact handlers as part of bootstrapping lifecycle

Created: 22/Feb/07 03:56 AM   Updated: 30/Mar/07 06:17 AM   Resolved: 30/Mar/07 06:17 AM
Component/s: None
Affects Version/s: None
Fix Version/s: 0.5-RC1

Time Tracking:
Not Specified

File Attachments: 1. Text File src_commons_new.patch (10 kB)
2. Text File test_commons.patch (0.6 kB)

Issue Links:
Duplicate
 
dependent
 


Marc Palmer added a comment - 01/Mar/07 02:36 AM

Requires changes to application and pluginManager wiring and reading of convention properties from plugin classes:

class MyPlugin {
      def artefacts = [artefactHandlerInstance1, ArtefactHandlerClass2]
}

Auto-sense instances vs. classes in same list, then call registerArtefact manually

We still need a two-phase Application init however, to give other code a chance to register artefacts, surely? Otherwise we might as well remove registerArtefact from the GrailsApplication interface. Can we do this with a spring event?


Chanwit Kaewkasi added a comment - 01/Mar/07 04:46 AM

Here's my working patch.