i created a module xbean-xml in maven plugins to be able to commit but it should be in xbean i think (the mvn plugin too by the way).
the example needs openjpa (not jpa ;)) because before using the plugin i enhance the entities with the openjpa plugin so then the classes are enhanced and reference some openjpa classes so it is needed in this case. Concerning the verbosity of xml it is simply a ratio between useful characters and useless ones (yes i use vim :p). The scan.xml location is configurable. For the moment there is 2 properties but it can be (should be) merged in one (today we have base + relative path, i liked it because relative is the convention and base is whatever you want). The snippet David sent in his first mail is till available, i just added the notion of "profile" which are in my mind a set of predefined [implementations, subclasses, annotations] easier to configure (the one i provided is jee6, simply look what it looks like to understand why it is not so useless ;)). Maybe it should be done through files at the classpath instead of hardcoding it...was a first step ;) - Romain 2012/2/21 Alan D. Cabrera <l...@toolazydogs.com> > > On Feb 21, 2012, at 6:49 AM, Romain Manni-Bucau wrote: > > > the only reason i don't like it is because of its verbosity otherwise it > is > > a cool format. > > I never understood the "verbosity argument" but then I don't use vi as an > editor. My editor automatically adds end tags, quotes for attributes, and > even automatically does auto-completion if it has the schema. What's not > to like? :) > > > Well i pushed a version using the xml file. Here the several parts: > > * > > > https://svn.apache.org/repos/asf/openejb/trunk/maven-plugins/spi-helper-maven-plugin/ > > : > > the maven plugin to scan an app > > * rest-example pom ( > > > http://svn.apache.org/repos/asf/openejb/trunk/openejb/examples/webapps/rest-example/pom.xml > ) > > : one usage of the plugin (even if here it is probably useless) > > Awesome! > > The power of this scanner is that it puts the scan report in a known fixed > location. I think making it configurable weakens that feature. > > Why is JPA required? > > Do you intend to add the ability to look for certain annotations, classes, > interfaces? > > > * > https://svn.apache.org/repos/asf/openejb/trunk/maven-plugins/xbean-xml/ : > > the module containing jaxb classes and a helper class to create the > > annotation finder > > I can take a look at your plugin later tonight. Very excited! :) > > > * openejb-core/.../FinderFactory: updated to try to get the scan.xml file > > before creating a standard finder > > I think this code belongs in xbean. Xbean can look for the file and use > it. More specifically it needs to happen behind the scenes and not push > the complexity on xbean users. > > > Note: the descriptor is in META-INF/org/apache/xbean/scan.xml excepted > for > > webapp where META-INF is replaced by WEB-INF to be consistent with other > > descriptors. > > Makes sense. > > > Regards, > Alan > >
