So bundle X apparently has knowledge of bundle Y. Have you considered having bundle X register a LogListener with the LogReaderService then filtering the LogEntry objects received based on LogEntry.getBundle()? This would necessitate bundle Y logging to the LogService, of course.
Thank you. ____________________________ John W Ross Software Engineer IBM Software Group Office: 919.254.7348 Notes: John W Ross/Atlanta Internet: [email protected] "It is my belief these sheep are laboring under the misapprehension that they're birds.... Witness their attempts to fly from tree to tree. Notice how they not so much fly as plummet." Laurens van Uijthoven <laurensvanuijtho To [email protected]> [email protected] Sent by: cc osgi-dev-bounces@ mail.osgi.org Subject [osgi-dev] Logging problems with osgi 10/13/2010 10:59 PM Please respond to OSGi Developer Mail List <[email protected] gi.org> Hello, We have the following problem: Multiple bundles run on osgi, each of them has a log file. If bundle X calls bundle Y and a warning occurs in bundle Y, we want to log the warning in the log file of bundle X. But the problem we have at the moment is that bundle Y doesn’t know bundle X and how bundle Y knows who have called him. We have thought of 3 possible ways to solve the problem: 1. StackTrace, but we think it is slow and it’s not nice to use stackt race. 2. Set the context in another bundle, so bundle Y can use the function getlogger to our own created bundle 3. Security Manager, but we don’t know whether it works well with osgi. We want to know which way is the best or maybe someone has the experience with this problem or knows another solution that we haven’t thought of yet. kind regards, Laurens_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
<<inline: graycol.gif>>
<<inline: pic04952.gif>>
<<inline: ecblank.gif>>
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
