I totally agreewith your last paragraph. Actually, we designed the schema years ago with OSGI in mind, but we weren't ready. It's probably time to take this road now that the api is OSGI complient...
Le samedi 15 août 2015, Stefan Seelmann <[email protected]> a écrit : > On 08/13/2015 11:53 PM, Emmanuel Lécharny wrote: > > So, here is what I think : we should have a diect access to those AT > > through the SchemaManager without having to do a lookup in the > > registries. Some ways to do it is to have a static class that is > > initialized after the SM, and which provides a direct access to the AT, > > like : > > Thanks Emmanuel for detailed explanation, I agree it makes sense to save > CPU (and memory). > > I agree to have a provider for direct access to often used AT and OC. > However I think we should avoid static class, instead initialize the > provider object once and inject it where needed. Avoiding static code > normally increases maintainability and makes testing easier. > > Kind Regards, > Stefan > > > -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
