it is currently deactiated by default. can be turn on by activating a syst prop which can be put in system.properties or ~/.openejb/system.properties. I think it is a good compromise since it can always be activated if a user wants but it doesn't modify the default behavior.
- Romain 2012/2/2 Alan D. Cabrera <[email protected]> > Reaching out to some external server would never go well in the production > environments of the organizations that I am and have worked at. They're > really kind of anal about that kind of stuff. > > With that said, nobody sits down with a bag of beer and chips and casually > scans the logs, not when there are thousands of logs to scan. :) The > engineers have to setup some kind of Splunk report. I'm sure they would > opt for a simple announcement list to be notified of updates and security > issues. > > imo, it should be in a jar that you can add if you want the feature so it > can't be accidentally turned on. > > > Regards, > Alan > > > On Feb 1, 2012, at 7:51 AM, Romain Manni-Bucau wrote: > > > i would like to see it activated by default. > > > > a little timeout (3s?) > > > > a thread ran in the configuration factory > > and the result get (through a future) in the assembler (to avoid to > wait)? > > > > - Romain > > > > > > 2012/2/1 David Blevins <[email protected]> > > > >> This sounds like a great feature. > >> > >> My gut instinct is that maybe it should be disabled by default and > >> something we encourage people to enable. > >> > >> What do others think? > >
