isn't it close to our dump descriptor feature?
let imagine we can add the dumped descriptor during the build, if the
descriptor is metadata complete it is the same no?
- Romain
2012/2/21 Mohammad Nour El-Din nour.moham...@gmail.com
I have one concern, still by having an XML generated and we
On Tue, Feb 21, 2012 at 11:15 AM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:
isn't it close to our dump descriptor feature?
let imagine we can add the dumped descriptor during the build, if the
descriptor is metadata complete it is the same no?
AFAIU from what David said yes, but I was
Sorry Mohammad but i'm not sure i get your point on executable part?
a kind of serializable thing?
- Romain
2012/2/21 Mohammad Nour El-Din nour.moham...@gmail.com
On Tue, Feb 21, 2012 at 11:15 AM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:
isn't it close to our dump descriptor
I think that it would be nicer to have a simple file that all manner of tooling
can read, e.g. python.
With that said, the XML file format seems simple enough and I doubt that any
large jar would pose a problem memory or CPU wise. JMHO.
Regards,
Alan
On Feb 20, 2012, at 4:49 PM, Mohammad
I think the same.
I think we don't really have any choice regarding the format since we don't
want to bring another lib to do anything more than we need in tomee
webprofile.
It is either properties, plain txt or xml file.
- Romain
2012/2/21 Alan D. Cabrera l...@toolazydogs.com
I think that
I like XML because we can have enforcement via schema.
Regards,
Alan
On Feb 21, 2012, at 6:39 AM, Romain Manni-Bucau wrote:
I think the same.
I think we don't really have any choice regarding the format since we don't
want to bring another lib to do anything more than we need in tomee
the only reason i don't like it is because of its verbosity otherwise it is
a cool format.
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
There's JSON schema [1] for instance but I guess that pulls in another
dependency...
[1] http://tools.ietf.org/html/draft-zyp-json-schema-03
Cheers
Daniel
On Tue, Feb 21, 2012 at 3:41 PM, Alan D. Cabrera l...@toolazydogs.com wrote:
I like XML because we can have enforcement via schema.
yep i think so.
when we'll get JAXRS in webprofile we'll be able use it ;) (moreover it
will still be jaxb :p)
- Romain
2012/2/21 dsh daniel.hais...@googlemail.com
There's JSON schema [1] for instance but I guess that pulls in another
dependency...
[1]
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
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
On Feb 21, 2012, at 7:40 AM, Romain Manni-Bucau wrote:
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
- Romain
2012/2/21 Alan D. Cabrera l...@toolazydogs.com
On Feb 21, 2012, at 7:40 AM, Romain Manni-Bucau wrote:
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 ;))
updated to manage only one file path property and to use external profiles.
I like the i don't need to write what i scan feature provided by profiles.
plugin
groupIdorg.apache.openejb/groupId
version0.0.1-SNAPSHOT/version
artifactIdspi-helper-maven-plugin/artifactId
Was wondering if we could use tomee instead of xbean in the groupid. Also
the artifact id could be something like classpath-scan-optimizer. The
resulting scan.xml could be stored in a package named org.apache.tomee
instead of org.apache.xbean. The more usage of tomee would be better. As
a user, I
15 matches
Mail list logo
