[jboss-dev-forums] [JBoss OSGi Development] - Re: Extender Patter vs. LifecycleInterceptors

"thomas.diesler(a)jboss.com" wrote : | What code would actually be reused by adding these adaptors? | Any existing Deployer or LI. Vice-versa. "thomas.diesler(a)jboss.com" wrote : | Perhaps you think an interceptor *is* a deployer and the invocation and ordering should be done by the deployer framework. | No, I don't think that. I just wanna re-use the Deployer/LI logic I once wrote. e.g. I don't wanna copy/paste some huge/large Deployer I once wrote, which has zero custom logic and could easily be reused in LI. "thomas.diesler(a)jboss.com" wrote : | This is something I'm not so sure about. considering how the deployers are being invoked on the various bundle state changes. | What's so different? Our VDF has, imho, similar linear lifecycle/state system, so mapping existing DeploymentStages against OSGi lifecycle integers shouldn't be a problem. Or even if it is, you simply report that: "Cannot adapt Deployer to LI, illegal deployment stage". "thomas.diesler(a)jboss.com" wrote : | Also, how would that work in Felix and other frameworks when it becomes standard. | For any non-MC_OSGi_facade I don't care. This is impl detail of MC's VDF. I would go even further, and simply provide spi/api for this LI framework, where most of the work would again just delegate to our VDF via some facade/adaptors. "thomas.diesler(a)jboss.com" wrote : | I'd still like to see a use case or actual code that could be reused by the adaptors that yo have in mind. Take any existing Deployer that works just on top of plain resources and attachments. e.g. grab something out from attachments, add custom logic, and put it back in View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262751#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...