yep a custom log4j appender is probably enough to follow logs. but with version 1 we should add event/logs to be complete.
- Romain 2011/11/9 Mohammad Nour El-Din <[email protected]> > I believe having a log handler would one solution and also it would be > configurable, this log handler can send these events to whatever > destination which developers can use as a more easier a nicer way than > parsing log messages. > > Thoughts ? > > On Wed, Nov 9, 2011 at 8:48 PM, Romain Manni-Bucau <[email protected] > >wrote: > > > i understand we can to add event but for this problem i wonder if they > will > > be relevant > > > > but we can generalize the question for sure! > > > > - Romain > > > > > > 2011/11/9 David Blevins <[email protected]> > > > > > > > > On Nov 9, 2011, at 9:06 AM, Romain Manni-Bucau wrote: > > > > > > > yep i understand, > > > > > > > > however it is hard to know before starting how many beans are "to > > > deploy". > > > > > > > > we could do something like: send an event when we know everything, > > send a > > > > event by bean...but i think it will have performance issues and i'm > not > > > > sure it is exactly what you want since the first phase will probably > be > > > as > > > > longer as the second. > > > > > > CDI events come to mind. There are a few places in our code I was > > > thinking CDI events might be nice. The multicast/multipoint "node > added" > > > and "node removed" events were rolling around my brain last week. > > > > > > How to pull that off isn't exactly clear, but it's certainly an > > > interesting itch to scratch. > > > > > > -David > > > > > > > > > > > > -- > Thanks > - Mohammad Nour > ---- > "Life is like riding a bicycle. To keep your balance you must keep moving" > - Albert Einstein >
