What need are you specifically referring to?
Regards, Alan On Feb 22, 2012, at 12:06 PM, Romain Manni-Bucau wrote: > So finally removing the package in the location answer to the need? > > - Romain > > Le 22 févr. 2012 20:49, "Mohammad Nour El-Din" <nour.moham...@gmail.com> a > écrit : > >> Hi Romain and Alan :) >> >> I didn't say ever to not use XML or a simple file, which what I meant by >> the declarative side, what I mean is additionally to that, at the time of >> deploy that out of that file Java code is generated which provides the >> information we need while scanning and thats what I meant by the >> execution/runtime perspective. >> >> On Wed, Feb 22, 2012 at 8:37 PM, David Blevins <david.blev...@gmail.com >>> wrote: >> >>> Additional note that the ultimate goal of the scan.xml file is to provide >>> something that could be standardized. There is interest for having a >> more >>> general solution. >>> >>> This probably affects the scan.xml file itself, the plugin could live >>> anywhere (I'd imagined we'd eventually put it in xbean). >>> >>> Ideally a standard file would be: >>> >>> - in META-INF/scan.xml >>> - list classes and packages >>> - something a user can create by hand >>> >>> Anything that adds xbean/openejb/tomee branding, is not xml, or contains >>> plugin-specific information would have to be removed from any proposals >> to >>> Java EE 7. >>> >>> Some things to keep in mind as we discuss. >>>
