Bogdan Stefanescu a écrit : > > For example we may name the XML file that declare a service through the > Manifest (with optional extension points) > Name_Of_The_Service.xml
Actually most files currently registered in MANIFEST.MF files are of the form: NameOfTheComponentService.xml or NameOfTheComponentServiceExtensions.xml so that we can stick to that. > The standalone XML files should be suffixed., We may choose let say > -component.xml (because -service.xml is already reserved by JBoss) > So a standalone XML component will be named: > Name_Of_The_Service-component.xml > > And a component that declares only extensions (contributions) we may > name it > Name_Of_The_Contributions-extension.xml > or > Name_Of_The_Contributions-contribution.xml If the recommended way is to avoid the *-bundle.xml files and embed them in OSGI-INF folders from MANIFEST.MF as metioned earlier, then we don't really need a naming convention at that level. We should better move the existing standalone *-bundle.xml files (actions, treemanager, ...) to OSGI-INF folders and use the NameOfTheComponentService.xml / NameOfTheComponentServiceExtensions.xml convention instead. -- Olivier _______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm
