Hi Karl, On Wed, Oct 19, 2011 at 9:38 AM, Karl Pauls <karlpa...@gmail.com> wrote:
> iirc, all you need to do is to have iPOJO on the classpath. > That was the first thing i tried, but unfortunately it didn't save me . > > regards, > > Karl > > On Wed, Oct 19, 2011 at 5:21 AM, Göktürk Gezer <gokturk.ge...@gmail.com> > wrote: > > Hi Everyone, > > > > We're in the middle of moving our codebase to OSGI using IPojo. Problem > is, > > I can not instantiate the manipulated classes without IPojo. > > > > AFAIK, IPojo manipulates the constructors with no argument and > BundleContext > > argument. So we can use other constructors for instance creation without > > getting through IPojo, and all field and method delegations will be > disabled > > in that case. Am i wrong? > > > > IPojoized classes are subclasses of some generic type, and i just use > > @Component and @Provides on them. That's all, just for easy service > > publication. But after that i can not instantiate them using > _ctor(String) > > constructor. > > > > If you ask why you're using normal instantiation, these usages without > IPojo > > are just on unit tests. Eventually we'll move these tests to OSGI, but it > > would be cool to be able to still use them until we do. > > > > > > Regards, > > Gokturk > > > > > > -- > Karl Pauls > karlpa...@gmail.com > http://twitter.com/karlpauls > http://www.linkedin.com/in/karlpauls > https://profiles.google.com/karlpauls > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@felix.apache.org > For additional commands, e-mail: users-h...@felix.apache.org > >
