Great stuff Philip! More feedback as I start digesting this fully and reading this whole thread but my first reaction is could we try to stick to standard annotations where possible - such as those defined in JSR 250? e.g.
http://geronimo.apache.org/xbean/annotation-based-dependency-injection.html so @ServiceStartup -> @PostConstruct @ServiceShutdown -> @PreDestroy am also wondering how many of the other annotations are really required on injected fields - could we just use @Resource to indicate stuff that is mandatory to be dependency injected (like EJB3s). I'm sure some of the annotations are required though; am just wondering how many of them are On 8/18/06, Philip Dodds <[EMAIL PROTECTED]> wrote:
I have knocked up some thoughts on a JBI POJO engine that could be used to provide a mechanism for annotating POJO specifically for more messaging level operations that the JSR181 service engine is aimed for. The idea is to provide a simple framework to replace the Spring Client Toolkit that is now defunt. Have a look at the idea - http://goopen.org/confluence/display/SM/JBI+Pojo+Service+Engine And all comments/thoughts are welcome!! P
-- James ------- http://radio.weblogs.com/0112098/
