Thanks Tim. I think I've got the problem: the InjectedDsoInstance is applied to an instrumented class marked with Terracotta annotations; for the annotations I dropped the old tim-annotations because I saw they've been moved into the toolkit, but now I'm wondering: how does Terracotta notice the use of annotations if I don't configure them through the tim? To recap: I use Terracotta instrumentation but I use the toolkit for the annotations (such as Root and InstrumentedClass), how does Terracotta recognize which classes to instrument without the old tim-annotations?
On Tue, Jul 20, 2010 at 7:23 PM, Tim Eck <t...@terracottatech.com> wrote: > The InjectedDsoInstance is part of the tim-api library now, but I don't > know why it would be functioning any differently between 3.2 and 3.3. > > Are you trying to use it in an express usage context? > >> -----Original Message----- >> From: tc-dev-boun...@lists.terracotta.org [mailto:tc-dev- >> boun...@lists.terracotta.org] On Behalf Of Sergio Bossa >> Sent: Tuesday, July 20, 2010 9:18 AM >> To: tc-dev >> Subject: [tc-dev] Problems with InjectedDsoInstance annotation >> >> Hi guys, >> >> The InjectedDsoInstance annotation doesn't seem to work on 3.3: I get >> a null DsoCluster. >> In order to use it with terracotta 3.3, I had to switch to tim-api >> 1.3.0 ... is that right? Am I missing something? >> >> -- >> Sergio Bossa >> http://www.linkedin.com/in/sergiob >> _______________________________________________ >> tc-dev mailing list >> tc-dev@lists.terracotta.org >> http://lists.terracotta.org/mailman/listinfo/tc-dev > _______________________________________________ > tc-dev mailing list > tc-dev@lists.terracotta.org > http://lists.terracotta.org/mailman/listinfo/tc-dev > -- Sergio Bossa http://www.linkedin.com/in/sergiob _______________________________________________ tc-dev mailing list tc-dev@lists.terracotta.org http://lists.terracotta.org/mailman/listinfo/tc-dev
