You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Patrick Calahan <pc...@bea.com> on 2004/03/27 04:23:52 UTC
JAM: Java API for Metadata
Hello everyone. I am a committer on Xml-Beans, another project currently
in the Apache Incubator. As part of my work there, I have developed an API
for representing Java types and their associated metadata which I believe
would be of general use to the community.
The API is called 'JAM' - the Java API for Metadata. On the surface, it
looks quite a bit like Reflection or the Doclet API, but it affords a
greater level of flexibility and convenience, and in particular provides
solutions for a number of thorny problems posed by JSR175.
I have had a few discussions with some folks on
general@incubator.apache.org about possibly spinning JAM up as an
independent project from xbeans. It was suggested that it would be useful
to test the waters in some other projects such as Geronimo to see if JAM
would indeed be generally useful. So, here I am testing. :)
Anyway, if you want more gory details, I have temporarily posted some white
papers and the API docs here:
http://www.pcal.net/jam
Any feedback is more than welcome.
Thanks,
-Patrick
Re: JAM: Java API for Metadata
Posted by ja...@mac.com.
On 27 Mar 2004, at 08:09, Patrick Calahan wrote:
> At 05:05 AM 3/27/2004 +0000, jastrachan@mac.com wrote:
>> I'd personally love to see JAM available as a separate package
>> somewhere with support for both a JDK 1.4 and JDK
>
> The good news here is that there is no need for separate 1.4 and 1.5
> versions. JAM's internals are factored in such a way that the same
> binary will run under both 1.4 and 1.5. When you are running under
> 1.5, JAM becomes 175-aware; when you're running under 1.4, JAM simply
> doesn't understand 175 annotations.
Cool
> (Actually, this last restriction may be removed if I ever get around
> to finishing my own java source parser - when that's done, you
> actually will be able to deal with 175 annotations under 1.4 if you
> have the original source files available. For that matter, it's not
> too hard to imagine writing something that parses the 175 annotations
> out of a classfile while running 1.4 - it's just not clear to me that
> anyone will have a need to do this).
BTW QDox can already parse Java source codes quickly for this kind of
job...
http://qdox.codehaus.org/
>> 1.5 version. It sounds great! I'd also love to see some experiment
>> done on a JDK 1.4 runtime metadata support so
>> that, say, as part of the build process we can turn doclet tags into
>> some generated classes so JAM could introspect the annotations at
>> runtime in a JDK 1.5-style way.
>
> There is support in there now for exactly this kind of thing, and I'm
> starting to use it in xml-beans. The basic idea is you write your own
> 'annotation proxy' class which can be populated from javadoc tags. By
> default, it is populated by lining up tag values with method names on
> your class, but you can easily customize this mapping by overriding a
> method or two. The proxy class most likely will look just like a 175
> annotation, but that's completely up to you.
>
> This gives you strong typing for javadoc tag info, but it has another
> benefit in that it can also be populated from 175 annotations. This
> means your code doesn't have to care whether it is dealing with tags
> or annotations.
Excellent.
>> Then the next step would be for us to be able to use AOP-style
>> introductions to generate the annotations using pointcuts (e.g. rules
>> to define where the annotations should go) so we don't have to litter
>> our code with doclet tags that we could infer using some simple rules
>> in our build systems (e.g. design patterns, naming conventions and so
>> forth - allowing the use of doclet tags to overload any such rules).
>
> Ah, that is interesting - I hadn't yet really thought about how
> aspects might fit in here. I'll definitely give that some more
> thought, and I'd love to hear more about what you guys are thinking
> about along these lines.
Basically it just allows us to do this (on 1.4)
parse Java source code -> pointcuts -> binary annotations class files.
on 1.5 this would probably be done with bytecode swizzling like most
AOP engines.
> As it is, JAM does provide some of its own machinery that might give
> you what you want. JAM allows you to plug in to it's 'classloading'
> process such that you can modify the view that is constructed for each
> java type. To sketch a trivial example: you could easily add a 'foo'
> annotation to every method which returns a boolean and whose name
> contains the word 'foo.'
Excellent :)
So I guess we could do all this at runtime. I guess it depends on which
end of the pipe you are (a developer of a package or a deployer of the
package).
For the annotation-introductions side of things I'd thought that a
developer should decide his naming conventions & rules, then use those
in the build process so that the jar of the code already has binary
annotations inside - so anyone can just use the binary and see the
correct annotations. Doing it the other way is interesting too - at
runtime modifying annotations - though I'm less interested in that side
of things just yet. I'm really keen on the former :)
> For a more concrete idea of how this works, take a look at the
> '...jam.mutable' subpackage; you basically get an opportunity to
> inspect objects of those types and modify them in any way you see fit.
>
> It may be worth noting that JAM's annotation processing features are
> really just specific uses of this mechanism. For example, I have a
> plugin which parses a class' comments as it is loaded and creates
> appropriate annotations for any javadoc tags found there.
Cool.
James
-------
http://radio.weblogs.com/0112098/
Re: JAM: Java API for Metadata
Posted by Thomas Hawtin <th...@tackline.demon.co.uk>.
Patrick Calahan wrote:
>
> (Actually, this last restriction may be removed if I ever get around to
> finishing my own java source parser - when that's done, you actually
> will be able to deal with 175 annotations under 1.4 if you have the
> original source files available. For that matter, it's not too hard to
> imagine writing something that parses the 175 annotations out of a
> classfile while running 1.4 - it's just not clear to me that anyone will
> have a need to do this).
Perhaps shomething could be done in conjunction with retroweaver
(.sourceforge.net)? That will generate 1.4 classes from 1.5, without the
need for source parsing. Keeping the annotations in standard 1.5 form
would appear to be convenient for most people.
Tom Hawtin
Re: JAM: Java API for Metadata
Posted by Patrick Calahan <pc...@bea.com>.
At 05:05 AM 3/27/2004 +0000, jastrachan@mac.com wrote:
>Hey Patrick
Hi James. Thanks for the feedback.
>I'd personally love to see JAM available as a separate package somewhere
>with support for both a JDK 1.4 and JDK
The good news here is that there is no need for separate 1.4 and 1.5
versions. JAM's internals are factored in such a way that the same binary
will run under both 1.4 and 1.5. When you are running under 1.5, JAM
becomes 175-aware; when you're running under 1.4, JAM simply doesn't
understand 175 annotations.
(Actually, this last restriction may be removed if I ever get around to
finishing my own java source parser - when that's done, you actually will
be able to deal with 175 annotations under 1.4 if you have the original
source files available. For that matter, it's not too hard to imagine
writing something that parses the 175 annotations out of a classfile while
running 1.4 - it's just not clear to me that anyone will have a need to do
this).
>1.5 version. It sounds great! I'd also love to see some experiment done on
>a JDK 1.4 runtime metadata support so
>that, say, as part of the build process we can turn doclet tags into some
>generated classes so JAM could introspect the annotations at runtime in a
>JDK 1.5-style way.
There is support in there now for exactly this kind of thing, and I'm
starting to use it in xml-beans. The basic idea is you write your own
'annotation proxy' class which can be populated from javadoc tags. By
default, it is populated by lining up tag values with method names on your
class, but you can easily customize this mapping by overriding a method or
two. The proxy class most likely will look just like a 175 annotation, but
that's completely up to you.
This gives you strong typing for javadoc tag info, but it has another
benefit in that it can also be populated from 175 annotations. This means
your code doesn't have to care whether it is dealing with tags or annotations.
>Then the next step would be for us to be able to use AOP-style
>introductions to generate the annotations using pointcuts (e.g. rules to
>define where the annotations should go) so we don't have to litter our
>code with doclet tags that we could infer using some simple rules in our
>build systems (e.g. design patterns, naming conventions and so forth -
>allowing the use of doclet tags to overload any such rules).
Ah, that is interesting - I hadn't yet really thought about how aspects
might fit in here. I'll definitely give that some more thought, and I'd
love to hear more about what you guys are thinking about along these lines.
As it is, JAM does provide some of its own machinery that might give you
what you want. JAM allows you to plug in to it's 'classloading' process
such that you can modify the view that is constructed for each java
type. To sketch a trivial example: you could easily add a 'foo' annotation
to every method which returns a boolean and whose name contains the word
'foo.'
For a more concrete idea of how this works, take a look at the
'...jam.mutable' subpackage; you basically get an opportunity to inspect
objects of those types and modify them in any way you see fit.
It may be worth noting that JAM's annotation processing features are really
just specific uses of this mechanism. For example, I have a plugin which
parses a class' comments as it is loaded and creates appropriate
annotations for any javadoc tags found there.
Thanks again,
-p
>Once we get there I'd be a very happy chap :)
>
>
>On 27 Mar 2004, at 03:23, Patrick Calahan wrote:
>>Hello everyone. I am a committer on Xml-Beans, another project currently
>>in the Apache Incubator. As part of my work there, I have developed an
>>API for representing Java types and their associated metadata which I
>>believe would be of general use to the community.
>>
>>The API is called 'JAM' - the Java API for Metadata. On the surface, it
>>looks quite a bit like Reflection or the Doclet API, but it affords a
>>greater level of flexibility and convenience, and in particular provides
>>solutions for a number of thorny problems posed by JSR175.
>>
>>I have had a few discussions with some folks on
>>general@incubator.apache.org about possibly spinning JAM up as an
>>independent project from xbeans. It was suggested that it would be
>>useful to test the waters in some other projects such as Geronimo to see
>>if JAM would indeed be generally useful. So, here I am testing. :)
>>
>>Anyway, if you want more gory details, I have temporarily posted some
>>white papers and the API docs here:
>>
>>http://www.pcal.net/jam
>>
>>Any feedback is more than welcome.
>>
>>
>>Thanks,
>>
>>-Patrick
>
>James
>-------
>http://radio.weblogs.com/0112098/
Re: JAM: Java API for Metadata
Posted by Patrick Calahan <pc...@bea.com>.
Yup, there does seem to be some overlap there. Earlier today, I sent email
to that project's developer, Leo Sutic, to see how we might combine our
efforts.
-p
At 12:31 AM 3/27/2004 -0800, Davanum Srinivas wrote:
>+1 from me. sounds like a good candidate for jakarta commons. please
>investigate working with
>commons' attributes projects
>http://jakarta.apache.org/commons/sandbox/attributes/ as well.
>
>-- dims
>
>--- jastrachan@mac.com wrote:
> > Hey Patrick
> >
> > I'd personally love to see JAM available as a separate package
> > somewhere with support for both a JDK 1.4 and JDK 1.5 version. It
> > sounds great! I'd also love to see some experiment done on a JDK 1.4
> > runtime metadata support so that, say, as part of the build process we
> > can turn doclet tags into some generated classes so JAM could
> > introspect the annotations at runtime in a JDK 1.5-style way.
> >
> > Then the next step would be for us to be able to use AOP-style
> > introductions to generate the annotations using pointcuts (e.g. rules
> > to define where the annotations should go) so we don't have to litter
> > our code with doclet tags that we could infer using some simple rules
> > in our build systems (e.g. design patterns, naming conventions and so
> > forth - allowing the use of doclet tags to overload any such rules).
> >
> > Once we get there I'd be a very happy chap :)
> >
> >
> > On 27 Mar 2004, at 03:23, Patrick Calahan wrote:
> > > Hello everyone. I am a committer on Xml-Beans, another project
> > > currently in the Apache Incubator. As part of my work there, I have
> > > developed an API for representing Java types and their associated
> > > metadata which I believe would be of general use to the community.
> > >
> > > The API is called 'JAM' - the Java API for Metadata. On the surface,
> > > it looks quite a bit like Reflection or the Doclet API, but it affords
> > > a greater level of flexibility and convenience, and in particular
> > > provides solutions for a number of thorny problems posed by JSR175.
> > >
> > > I have had a few discussions with some folks on
> > > general@incubator.apache.org about possibly spinning JAM up as an
> > > independent project from xbeans. It was suggested that it would be
> > > useful to test the waters in some other projects such as Geronimo to
> > > see if JAM would indeed be generally useful. So, here I am testing.
> > > :)
> > >
> > > Anyway, if you want more gory details, I have temporarily posted some
> > > white papers and the API docs here:
> > >
> > > http://www.pcal.net/jam
> > >
> > > Any feedback is more than welcome.
> > >
> > >
> > > Thanks,
> > >
> > > -Patrick
> > >
> > >
> >
> > James
> > -------
> > http://radio.weblogs.com/0112098/
> >
>
>
>=====
>Davanum Srinivas - http://webservices.apache.org/~dims/
Re: JAM: Java API for Metadata
Posted by Chris Perrin <cp...@hifiit.com>.
I am in the same boat as James. I think I'd like to help out on the project
if I could.
----- Original Message -----
From: <ja...@mac.com>
To: <ge...@incubator.apache.org>
Sent: Friday, March 26, 2004 11:05 PM
Subject: Re: JAM: Java API for Metadata
> Hey Patrick
>
> I'd personally love to see JAM available as a separate package
> somewhere with support for both a JDK 1.4 and JDK 1.5 version. It
> sounds great! I'd also love to see some experiment done on a JDK 1.4
> runtime metadata support so that, say, as part of the build process we
> can turn doclet tags into some generated classes so JAM could
> introspect the annotations at runtime in a JDK 1.5-style way.
>
> Then the next step would be for us to be able to use AOP-style
> introductions to generate the annotations using pointcuts (e.g. rules
> to define where the annotations should go) so we don't have to litter
> our code with doclet tags that we could infer using some simple rules
> in our build systems (e.g. design patterns, naming conventions and so
> forth - allowing the use of doclet tags to overload any such rules).
>
> Once we get there I'd be a very happy chap :)
>
>
> On 27 Mar 2004, at 03:23, Patrick Calahan wrote:
> > Hello everyone. I am a committer on Xml-Beans, another project
> > currently in the Apache Incubator. As part of my work there, I have
> > developed an API for representing Java types and their associated
> > metadata which I believe would be of general use to the community.
> >
> > The API is called 'JAM' - the Java API for Metadata. On the surface,
> > it looks quite a bit like Reflection or the Doclet API, but it affords
> > a greater level of flexibility and convenience, and in particular
> > provides solutions for a number of thorny problems posed by JSR175.
> >
> > I have had a few discussions with some folks on
> > general@incubator.apache.org about possibly spinning JAM up as an
> > independent project from xbeans. It was suggested that it would be
> > useful to test the waters in some other projects such as Geronimo to
> > see if JAM would indeed be generally useful. So, here I am testing.
> > :)
> >
> > Anyway, if you want more gory details, I have temporarily posted some
> > white papers and the API docs here:
> >
> > http://www.pcal.net/jam
> >
> > Any feedback is more than welcome.
> >
> >
> > Thanks,
> >
> > -Patrick
> >
> >
>
> James
> -------
> http://radio.weblogs.com/0112098/
>
Re: JAM: Java API for Metadata
Posted by Davanum Srinivas <di...@yahoo.com>.
+1 from me. sounds like a good candidate for jakarta commons. please investigate working with
commons' attributes projects http://jakarta.apache.org/commons/sandbox/attributes/ as well.
-- dims
--- jastrachan@mac.com wrote:
> Hey Patrick
>
> I'd personally love to see JAM available as a separate package
> somewhere with support for both a JDK 1.4 and JDK 1.5 version. It
> sounds great! I'd also love to see some experiment done on a JDK 1.4
> runtime metadata support so that, say, as part of the build process we
> can turn doclet tags into some generated classes so JAM could
> introspect the annotations at runtime in a JDK 1.5-style way.
>
> Then the next step would be for us to be able to use AOP-style
> introductions to generate the annotations using pointcuts (e.g. rules
> to define where the annotations should go) so we don't have to litter
> our code with doclet tags that we could infer using some simple rules
> in our build systems (e.g. design patterns, naming conventions and so
> forth - allowing the use of doclet tags to overload any such rules).
>
> Once we get there I'd be a very happy chap :)
>
>
> On 27 Mar 2004, at 03:23, Patrick Calahan wrote:
> > Hello everyone. I am a committer on Xml-Beans, another project
> > currently in the Apache Incubator. As part of my work there, I have
> > developed an API for representing Java types and their associated
> > metadata which I believe would be of general use to the community.
> >
> > The API is called 'JAM' - the Java API for Metadata. On the surface,
> > it looks quite a bit like Reflection or the Doclet API, but it affords
> > a greater level of flexibility and convenience, and in particular
> > provides solutions for a number of thorny problems posed by JSR175.
> >
> > I have had a few discussions with some folks on
> > general@incubator.apache.org about possibly spinning JAM up as an
> > independent project from xbeans. It was suggested that it would be
> > useful to test the waters in some other projects such as Geronimo to
> > see if JAM would indeed be generally useful. So, here I am testing.
> > :)
> >
> > Anyway, if you want more gory details, I have temporarily posted some
> > white papers and the API docs here:
> >
> > http://www.pcal.net/jam
> >
> > Any feedback is more than welcome.
> >
> >
> > Thanks,
> >
> > -Patrick
> >
> >
>
> James
> -------
> http://radio.weblogs.com/0112098/
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: JAM: Java API for Metadata
Posted by ja...@mac.com.
Hey Patrick
I'd personally love to see JAM available as a separate package
somewhere with support for both a JDK 1.4 and JDK 1.5 version. It
sounds great! I'd also love to see some experiment done on a JDK 1.4
runtime metadata support so that, say, as part of the build process we
can turn doclet tags into some generated classes so JAM could
introspect the annotations at runtime in a JDK 1.5-style way.
Then the next step would be for us to be able to use AOP-style
introductions to generate the annotations using pointcuts (e.g. rules
to define where the annotations should go) so we don't have to litter
our code with doclet tags that we could infer using some simple rules
in our build systems (e.g. design patterns, naming conventions and so
forth - allowing the use of doclet tags to overload any such rules).
Once we get there I'd be a very happy chap :)
On 27 Mar 2004, at 03:23, Patrick Calahan wrote:
> Hello everyone. I am a committer on Xml-Beans, another project
> currently in the Apache Incubator. As part of my work there, I have
> developed an API for representing Java types and their associated
> metadata which I believe would be of general use to the community.
>
> The API is called 'JAM' - the Java API for Metadata. On the surface,
> it looks quite a bit like Reflection or the Doclet API, but it affords
> a greater level of flexibility and convenience, and in particular
> provides solutions for a number of thorny problems posed by JSR175.
>
> I have had a few discussions with some folks on
> general@incubator.apache.org about possibly spinning JAM up as an
> independent project from xbeans. It was suggested that it would be
> useful to test the waters in some other projects such as Geronimo to
> see if JAM would indeed be generally useful. So, here I am testing.
> :)
>
> Anyway, if you want more gory details, I have temporarily posted some
> white papers and the API docs here:
>
> http://www.pcal.net/jam
>
> Any feedback is more than welcome.
>
>
> Thanks,
>
> -Patrick
>
>
James
-------
http://radio.weblogs.com/0112098/
RE: Java API for Metadata
Posted by Patrick Calahan <pc...@bea.com>.
Right, I think that's the only part of the build that hasn't been teased
out yet. Will fix that, thanks.
-p
At 04:42 PM 3/31/2004 +0900, Ias wrote:
>Thanks for your great work. I just feel like introducing it to my article in
>May issue of Microsoftware, a Korean journal for software developers.
>
>By the way, I actually failed to build JAM first. I figured it out by adding
>
> <ant dir='..' target='jsr173_api.jar' inheritAll='false' />
>
>to jsr173 target in build.xml for JAM. (I guess it was also because I hadn't
>built xmlbeans before building JAM.)
>
>Regards,
>
>Ias
>
>=========================================================
>Lee, Changshin (Korean name)
>Ias (International name)
> Company Web Site: http://www.tmax.co.kr
> Personal Web Site: http://www.iasandcb.pe.kr
>---------------------------------------------------------
>JSR 201, 204, 222 and 224 Expert Group Member
>Apache Web Services Project Member
>R&D Center
>Tmax Soft, Inc.
>=========================================================
>
> > -----Original Message-----
> > From: Patrick Calahan [mailto:pcal@bea.com]
> > Sent: Saturday, March 27, 2004 12:24 PM
> > To: geronimo-dev@incubator.apache.org
> > Subject: JAM: Java API for Metadata
> >
> > Hello everyone. I am a committer on Xml-Beans, another
> > project currently in the Apache Incubator. As part of my
> > work there, I have developed an API for representing Java
> > types and their associated metadata which I believe would be
> > of general use to the community.
> >
> > The API is called 'JAM' - the Java API for Metadata. On the
> > surface, it looks quite a bit like Reflection or the Doclet
> > API, but it affords a greater level of flexibility and
> > convenience, and in particular provides solutions for a
> > number of thorny problems posed by JSR175.
> >
> > I have had a few discussions with some folks on
> > general@incubator.apache.org about possibly spinning JAM up
> > as an independent project from xbeans. It was suggested that
> > it would be useful to test the waters in some other projects
> > such as Geronimo to see if JAM would indeed be generally
> > useful. So, here I am testing. :)
> >
> > Anyway, if you want more gory details, I have temporarily
> > posted some white papers and the API docs here:
> >
> > http://www.pcal.net/jam
> >
> > Any feedback is more than welcome.
> >
> >
> > Thanks,
> >
> > -Patrick
> >
Re: Feedback on Java API for Metadata
Posted by Patrick Calahan <pc...@bea.com>.
I don't think they've made b2 generally available yet, but I believe there
will be another drop soon.
-p
At 07:17 PM 4/4/2004 -0700, Ganga Sah wrote:
>Where from can JDK 1.5.0-beta2 be downloaded as I see
>only 1.5.0-beta1 at java.sun.com?
>
>--- Patrick Calahan <pc...@bea.com> wrote:
> > Hi Ias, thanks for the feedback. Sorry for the
> > confusion - you need the
> > latest 1.5 drop:
> >
> > > java -version
> > java version "1.5.0-beta2"
> > Java(TM) 2 Runtime Environment, Standard Edition
> > (build 1.5.0-beta2-b40)
> > Java HotSpot(TM) Client VM (build 1.5.0-beta2-b40,
> > mixed mode)
> >
> > I'll add a note somewhere about this (although it
> > shouldn't be an issue for
> > too much longer...)
> >
> > -p
> >
> >
> > build 1.5.0-beta2-b40
> >
> > At 02:07 PM 4/3/2004 +0900, Ias wrote:
> > >Hi all,
> > >
> > >I built JAM from the latest CVS Head and here's
> > what I've got with J2SE
> > >1.5.0 b32c(a.k.a. Tiger beta1)
> > >
> > >compile:
> > > [mkdir] Created dir:
> > D:\apache\xml\xmlbeans-v2\build\jam\classes
> > > [javac] Compiling 101 source files to
> > >D:\apache\xml\xmlbeans-v2\build\jam\classes
> > > [javac]
> >
> >D:\apache\xml\xmlbeans-v2\jam\src\org\apache\xmlbeans\impl\jam\internal\java
> > >15\Reflect15DelegateImpl.java:114: cannot find
> > symbol
> > > [javac] symbol : method annotationType()
> > > [javac] location: interface
> > java.lang.annotation.Annotation
> > > [javac]
> > (anns[i].annotationType().getName());
> > > [javac] ^
> > > [javac]
> >
> >D:\apache\xml\xmlbeans-v2\jam\src\org\apache\xmlbeans\impl\jam\internal\java
> > >15\Reflect15DelegateImpl.java:123: cannot find
> > symbol
> > > [javac] symbol : method annotationType()
> > > [javac] location: interface
> > java.lang.annotation.Annotation
> > > [javac] Class annType =
> > src.annotationType();
> > > [javac] ^
> > > [javac] Note: * uses or overrides a deprecated
> > API.
> > > [javac] Note: Recompile with
> > -Xlint:deprecation for details.
> > > [javac] 2 errors
> > >
> > >BUILD FAILED
> > >
> > >I also tried to build JAM with J2SE 1.5.0 b45 and
> > learned that "ant test"
> > >failed with the attached report.
> > >
> > >Thanks for your response in advance,
> > >
> > >Ias
> > >
> > >-
> >
>---------------------------------------------------------------------
> > >To unsubscribe, e-mail:
> > xmlbeans-dev-unsubscribe@xml.apache.org
> > >For additional commands, e-mail:
> > xmlbeans-dev-help@xml.apache.org
> > >Apache XMLBeans Project -- URL:
> > http://xml.apache.org/xmlbeans/
> >
> >
> > -
> >
>---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > xmlbeans-dev-unsubscribe@xml.apache.org
> > For additional commands, e-mail:
> > xmlbeans-dev-help@xml.apache.org
> > Apache XMLBeans Project -- URL:
> > http://xml.apache.org/xmlbeans/
> >
>
>
>__________________________________
>Do you Yahoo!?
>Yahoo! Small Business $15K Web Design Giveaway
>http://promotions.yahoo.com/design_giveaway/
>
>- ---------------------------------------------------------------------
>To unsubscribe, e-mail: xmlbeans-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
>Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
- ---------------------------------------------------------------------
To unsubscribe, e-mail: xmlbeans-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
Re: Feedback on Java API for Metadata
Posted by Patrick Calahan <pc...@bea.com>.
I don't think they've made b2 generally available yet, but I believe there
will be another drop soon.
-p
At 07:17 PM 4/4/2004 -0700, Ganga Sah wrote:
>Where from can JDK 1.5.0-beta2 be downloaded as I see
>only 1.5.0-beta1 at java.sun.com?
>
>--- Patrick Calahan <pc...@bea.com> wrote:
> > Hi Ias, thanks for the feedback. Sorry for the
> > confusion - you need the
> > latest 1.5 drop:
> >
> > > java -version
> > java version "1.5.0-beta2"
> > Java(TM) 2 Runtime Environment, Standard Edition
> > (build 1.5.0-beta2-b40)
> > Java HotSpot(TM) Client VM (build 1.5.0-beta2-b40,
> > mixed mode)
> >
> > I'll add a note somewhere about this (although it
> > shouldn't be an issue for
> > too much longer...)
> >
> > -p
> >
> >
> > build 1.5.0-beta2-b40
> >
> > At 02:07 PM 4/3/2004 +0900, Ias wrote:
> > >Hi all,
> > >
> > >I built JAM from the latest CVS Head and here's
> > what I've got with J2SE
> > >1.5.0 b32c(a.k.a. Tiger beta1)
> > >
> > >compile:
> > > [mkdir] Created dir:
> > D:\apache\xml\xmlbeans-v2\build\jam\classes
> > > [javac] Compiling 101 source files to
> > >D:\apache\xml\xmlbeans-v2\build\jam\classes
> > > [javac]
> >
> >D:\apache\xml\xmlbeans-v2\jam\src\org\apache\xmlbeans\impl\jam\internal\java
> > >15\Reflect15DelegateImpl.java:114: cannot find
> > symbol
> > > [javac] symbol : method annotationType()
> > > [javac] location: interface
> > java.lang.annotation.Annotation
> > > [javac]
> > (anns[i].annotationType().getName());
> > > [javac] ^
> > > [javac]
> >
> >D:\apache\xml\xmlbeans-v2\jam\src\org\apache\xmlbeans\impl\jam\internal\java
> > >15\Reflect15DelegateImpl.java:123: cannot find
> > symbol
> > > [javac] symbol : method annotationType()
> > > [javac] location: interface
> > java.lang.annotation.Annotation
> > > [javac] Class annType =
> > src.annotationType();
> > > [javac] ^
> > > [javac] Note: * uses or overrides a deprecated
> > API.
> > > [javac] Note: Recompile with
> > -Xlint:deprecation for details.
> > > [javac] 2 errors
> > >
> > >BUILD FAILED
> > >
> > >I also tried to build JAM with J2SE 1.5.0 b45 and
> > learned that "ant test"
> > >failed with the attached report.
> > >
> > >Thanks for your response in advance,
> > >
> > >Ias
> > >
> > >-
> >
>---------------------------------------------------------------------
> > >To unsubscribe, e-mail:
> > xmlbeans-dev-unsubscribe@xml.apache.org
> > >For additional commands, e-mail:
> > xmlbeans-dev-help@xml.apache.org
> > >Apache XMLBeans Project -- URL:
> > http://xml.apache.org/xmlbeans/
> >
> >
> > -
> >
>---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > xmlbeans-dev-unsubscribe@xml.apache.org
> > For additional commands, e-mail:
> > xmlbeans-dev-help@xml.apache.org
> > Apache XMLBeans Project -- URL:
> > http://xml.apache.org/xmlbeans/
> >
>
>
>__________________________________
>Do you Yahoo!?
>Yahoo! Small Business $15K Web Design Giveaway
>http://promotions.yahoo.com/design_giveaway/
>
>- ---------------------------------------------------------------------
>To unsubscribe, e-mail: xmlbeans-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
>Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
- ---------------------------------------------------------------------
To unsubscribe, e-mail: xmlbeans-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
Re: Feedback on Java API for Metadata
Posted by Ganga Sah <ga...@yahoo.com>.
Where from can JDK 1.5.0-beta2 be downloaded as I see
only 1.5.0-beta1 at java.sun.com?
--- Patrick Calahan <pc...@bea.com> wrote:
> Hi Ias, thanks for the feedback. Sorry for the
> confusion - you need the
> latest 1.5 drop:
>
> > java -version
> java version "1.5.0-beta2"
> Java(TM) 2 Runtime Environment, Standard Edition
> (build 1.5.0-beta2-b40)
> Java HotSpot(TM) Client VM (build 1.5.0-beta2-b40,
> mixed mode)
>
> I'll add a note somewhere about this (although it
> shouldn't be an issue for
> too much longer...)
>
> -p
>
>
> build 1.5.0-beta2-b40
>
> At 02:07 PM 4/3/2004 +0900, Ias wrote:
> >Hi all,
> >
> >I built JAM from the latest CVS Head and here's
> what I've got with J2SE
> >1.5.0 b32c(a.k.a. Tiger beta1)
> >
> >compile:
> > [mkdir] Created dir:
> D:\apache\xml\xmlbeans-v2\build\jam\classes
> > [javac] Compiling 101 source files to
> >D:\apache\xml\xmlbeans-v2\build\jam\classes
> > [javac]
>
>D:\apache\xml\xmlbeans-v2\jam\src\org\apache\xmlbeans\impl\jam\internal\java
> >15\Reflect15DelegateImpl.java:114: cannot find
> symbol
> > [javac] symbol : method annotationType()
> > [javac] location: interface
> java.lang.annotation.Annotation
> > [javac]
> (anns[i].annotationType().getName());
> > [javac] ^
> > [javac]
>
>D:\apache\xml\xmlbeans-v2\jam\src\org\apache\xmlbeans\impl\jam\internal\java
> >15\Reflect15DelegateImpl.java:123: cannot find
> symbol
> > [javac] symbol : method annotationType()
> > [javac] location: interface
> java.lang.annotation.Annotation
> > [javac] Class annType =
> src.annotationType();
> > [javac] ^
> > [javac] Note: * uses or overrides a deprecated
> API.
> > [javac] Note: Recompile with
> -Xlint:deprecation for details.
> > [javac] 2 errors
> >
> >BUILD FAILED
> >
> >I also tried to build JAM with J2SE 1.5.0 b45 and
> learned that "ant test"
> >failed with the attached report.
> >
> >Thanks for your response in advance,
> >
> >Ias
> >
> >-
>
---------------------------------------------------------------------
> >To unsubscribe, e-mail:
> xmlbeans-dev-unsubscribe@xml.apache.org
> >For additional commands, e-mail:
> xmlbeans-dev-help@xml.apache.org
> >Apache XMLBeans Project -- URL:
> http://xml.apache.org/xmlbeans/
>
>
> -
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> xmlbeans-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail:
> xmlbeans-dev-help@xml.apache.org
> Apache XMLBeans Project -- URL:
> http://xml.apache.org/xmlbeans/
>
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
http://promotions.yahoo.com/design_giveaway/
- ---------------------------------------------------------------------
To unsubscribe, e-mail: xmlbeans-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
Re: Feedback on Java API for Metadata
Posted by Ganga Sah <ga...@yahoo.com>.
Where from can JDK 1.5.0-beta2 be downloaded as I see
only 1.5.0-beta1 at java.sun.com?
--- Patrick Calahan <pc...@bea.com> wrote:
> Hi Ias, thanks for the feedback. Sorry for the
> confusion - you need the
> latest 1.5 drop:
>
> > java -version
> java version "1.5.0-beta2"
> Java(TM) 2 Runtime Environment, Standard Edition
> (build 1.5.0-beta2-b40)
> Java HotSpot(TM) Client VM (build 1.5.0-beta2-b40,
> mixed mode)
>
> I'll add a note somewhere about this (although it
> shouldn't be an issue for
> too much longer...)
>
> -p
>
>
> build 1.5.0-beta2-b40
>
> At 02:07 PM 4/3/2004 +0900, Ias wrote:
> >Hi all,
> >
> >I built JAM from the latest CVS Head and here's
> what I've got with J2SE
> >1.5.0 b32c(a.k.a. Tiger beta1)
> >
> >compile:
> > [mkdir] Created dir:
> D:\apache\xml\xmlbeans-v2\build\jam\classes
> > [javac] Compiling 101 source files to
> >D:\apache\xml\xmlbeans-v2\build\jam\classes
> > [javac]
>
>D:\apache\xml\xmlbeans-v2\jam\src\org\apache\xmlbeans\impl\jam\internal\java
> >15\Reflect15DelegateImpl.java:114: cannot find
> symbol
> > [javac] symbol : method annotationType()
> > [javac] location: interface
> java.lang.annotation.Annotation
> > [javac]
> (anns[i].annotationType().getName());
> > [javac] ^
> > [javac]
>
>D:\apache\xml\xmlbeans-v2\jam\src\org\apache\xmlbeans\impl\jam\internal\java
> >15\Reflect15DelegateImpl.java:123: cannot find
> symbol
> > [javac] symbol : method annotationType()
> > [javac] location: interface
> java.lang.annotation.Annotation
> > [javac] Class annType =
> src.annotationType();
> > [javac] ^
> > [javac] Note: * uses or overrides a deprecated
> API.
> > [javac] Note: Recompile with
> -Xlint:deprecation for details.
> > [javac] 2 errors
> >
> >BUILD FAILED
> >
> >I also tried to build JAM with J2SE 1.5.0 b45 and
> learned that "ant test"
> >failed with the attached report.
> >
> >Thanks for your response in advance,
> >
> >Ias
> >
> >-
>
---------------------------------------------------------------------
> >To unsubscribe, e-mail:
> xmlbeans-dev-unsubscribe@xml.apache.org
> >For additional commands, e-mail:
> xmlbeans-dev-help@xml.apache.org
> >Apache XMLBeans Project -- URL:
> http://xml.apache.org/xmlbeans/
>
>
> -
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> xmlbeans-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail:
> xmlbeans-dev-help@xml.apache.org
> Apache XMLBeans Project -- URL:
> http://xml.apache.org/xmlbeans/
>
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
http://promotions.yahoo.com/design_giveaway/
- ---------------------------------------------------------------------
To unsubscribe, e-mail: xmlbeans-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
Re: Feedback on Java API for Metadata
Posted by Patrick Calahan <pc...@bea.com>.
Hi Ias, thanks for the feedback. Sorry for the confusion - you need the
latest 1.5 drop:
> java -version
java version "1.5.0-beta2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-beta2-b40)
Java HotSpot(TM) Client VM (build 1.5.0-beta2-b40, mixed mode)
I'll add a note somewhere about this (although it shouldn't be an issue for
too much longer...)
-p
build 1.5.0-beta2-b40
At 02:07 PM 4/3/2004 +0900, Ias wrote:
>Hi all,
>
>I built JAM from the latest CVS Head and here's what I've got with J2SE
>1.5.0 b32c(a.k.a. Tiger beta1)
>
>compile:
> [mkdir] Created dir: D:\apache\xml\xmlbeans-v2\build\jam\classes
> [javac] Compiling 101 source files to
>D:\apache\xml\xmlbeans-v2\build\jam\classes
> [javac]
>D:\apache\xml\xmlbeans-v2\jam\src\org\apache\xmlbeans\impl\jam\internal\java
>15\Reflect15DelegateImpl.java:114: cannot find symbol
> [javac] symbol : method annotationType()
> [javac] location: interface java.lang.annotation.Annotation
> [javac] (anns[i].annotationType().getName());
> [javac] ^
> [javac]
>D:\apache\xml\xmlbeans-v2\jam\src\org\apache\xmlbeans\impl\jam\internal\java
>15\Reflect15DelegateImpl.java:123: cannot find symbol
> [javac] symbol : method annotationType()
> [javac] location: interface java.lang.annotation.Annotation
> [javac] Class annType = src.annotationType();
> [javac] ^
> [javac] Note: * uses or overrides a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] 2 errors
>
>BUILD FAILED
>
>I also tried to build JAM with J2SE 1.5.0 b45 and learned that "ant test"
>failed with the attached report.
>
>Thanks for your response in advance,
>
>Ias
>
>- ---------------------------------------------------------------------
>To unsubscribe, e-mail: xmlbeans-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
>Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
- ---------------------------------------------------------------------
To unsubscribe, e-mail: xmlbeans-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
Re: Feedback on Java API for Metadata
Posted by Patrick Calahan <pc...@bea.com>.
At 02:07 PM 4/3/2004 +0900, Ias wrote:
>Hi all,
>
>
>I also tried to build JAM with J2SE 1.5.0 b45 and learned that "ant test"
>failed with the attached report.
Oops, missed this part - looks like you have an even more recent drop than
I do. :) I'll take a look into this - the test that is failing is
extremely sensitive to even minor changes in the behavior of javadoc or
reflection.
Thanks again,
-p
- ---------------------------------------------------------------------
To unsubscribe, e-mail: xmlbeans-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
Re: Feedback on Java API for Metadata
Posted by Patrick Calahan <pc...@bea.com>.
At 02:07 PM 4/3/2004 +0900, Ias wrote:
>Hi all,
>
>
>I also tried to build JAM with J2SE 1.5.0 b45 and learned that "ant test"
>failed with the attached report.
Oops, missed this part - looks like you have an even more recent drop than
I do. :) I'll take a look into this - the test that is failing is
extremely sensitive to even minor changes in the behavior of javadoc or
reflection.
Thanks again,
-p
- ---------------------------------------------------------------------
To unsubscribe, e-mail: xmlbeans-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
Re: Feedback on Java API for Metadata
Posted by Patrick Calahan <pc...@bea.com>.
Hi Ias, thanks for the feedback. Sorry for the confusion - you need the
latest 1.5 drop:
> java -version
java version "1.5.0-beta2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-beta2-b40)
Java HotSpot(TM) Client VM (build 1.5.0-beta2-b40, mixed mode)
I'll add a note somewhere about this (although it shouldn't be an issue for
too much longer...)
-p
build 1.5.0-beta2-b40
At 02:07 PM 4/3/2004 +0900, Ias wrote:
>Hi all,
>
>I built JAM from the latest CVS Head and here's what I've got with J2SE
>1.5.0 b32c(a.k.a. Tiger beta1)
>
>compile:
> [mkdir] Created dir: D:\apache\xml\xmlbeans-v2\build\jam\classes
> [javac] Compiling 101 source files to
>D:\apache\xml\xmlbeans-v2\build\jam\classes
> [javac]
>D:\apache\xml\xmlbeans-v2\jam\src\org\apache\xmlbeans\impl\jam\internal\java
>15\Reflect15DelegateImpl.java:114: cannot find symbol
> [javac] symbol : method annotationType()
> [javac] location: interface java.lang.annotation.Annotation
> [javac] (anns[i].annotationType().getName());
> [javac] ^
> [javac]
>D:\apache\xml\xmlbeans-v2\jam\src\org\apache\xmlbeans\impl\jam\internal\java
>15\Reflect15DelegateImpl.java:123: cannot find symbol
> [javac] symbol : method annotationType()
> [javac] location: interface java.lang.annotation.Annotation
> [javac] Class annType = src.annotationType();
> [javac] ^
> [javac] Note: * uses or overrides a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] 2 errors
>
>BUILD FAILED
>
>I also tried to build JAM with J2SE 1.5.0 b45 and learned that "ant test"
>failed with the attached report.
>
>Thanks for your response in advance,
>
>Ias
>
>- ---------------------------------------------------------------------
>To unsubscribe, e-mail: xmlbeans-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
>Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
- ---------------------------------------------------------------------
To unsubscribe, e-mail: xmlbeans-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
Feedback on Java API for Metadata
Posted by Ias <ia...@hotmail.com>.
Hi all,
I built JAM from the latest CVS Head and here's what I've got with J2SE
1.5.0 b32c(a.k.a. Tiger beta1)
compile:
[mkdir] Created dir: D:\apache\xml\xmlbeans-v2\build\jam\classes
[javac] Compiling 101 source files to
D:\apache\xml\xmlbeans-v2\build\jam\classes
[javac]
D:\apache\xml\xmlbeans-v2\jam\src\org\apache\xmlbeans\impl\jam\internal\java
15\Reflect15DelegateImpl.java:114: cannot find symbol
[javac] symbol : method annotationType()
[javac] location: interface java.lang.annotation.Annotation
[javac] (anns[i].annotationType().getName());
[javac] ^
[javac]
D:\apache\xml\xmlbeans-v2\jam\src\org\apache\xmlbeans\impl\jam\internal\java
15\Reflect15DelegateImpl.java:123: cannot find symbol
[javac] symbol : method annotationType()
[javac] location: interface java.lang.annotation.Annotation
[javac] Class annType = src.annotationType();
[javac] ^
[javac] Note: * uses or overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] 2 errors
BUILD FAILED
I also tried to build JAM with J2SE 1.5.0 b45 and learned that "ant test"
failed with the attached report.
Thanks for your response in advance,
Ias
Feedback on Java API for Metadata
Posted by Ias <ia...@hotmail.com>.
Hi all,
I built JAM from the latest CVS Head and here's what I've got with J2SE
1.5.0 b32c(a.k.a. Tiger beta1)
compile:
[mkdir] Created dir: D:\apache\xml\xmlbeans-v2\build\jam\classes
[javac] Compiling 101 source files to
D:\apache\xml\xmlbeans-v2\build\jam\classes
[javac]
D:\apache\xml\xmlbeans-v2\jam\src\org\apache\xmlbeans\impl\jam\internal\java
15\Reflect15DelegateImpl.java:114: cannot find symbol
[javac] symbol : method annotationType()
[javac] location: interface java.lang.annotation.Annotation
[javac] (anns[i].annotationType().getName());
[javac] ^
[javac]
D:\apache\xml\xmlbeans-v2\jam\src\org\apache\xmlbeans\impl\jam\internal\java
15\Reflect15DelegateImpl.java:123: cannot find symbol
[javac] symbol : method annotationType()
[javac] location: interface java.lang.annotation.Annotation
[javac] Class annType = src.annotationType();
[javac] ^
[javac] Note: * uses or overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] 2 errors
BUILD FAILED
I also tried to build JAM with J2SE 1.5.0 b45 and learned that "ant test"
failed with the attached report.
Thanks for your response in advance,
Ias
RE: Java API for Metadata
Posted by Ias <ia...@tmax.co.kr>.
Thanks for your great work. I just feel like introducing it to my article in
May issue of Microsoftware, a Korean journal for software developers.
By the way, I actually failed to build JAM first. I figured it out by adding
<ant dir='..' target='jsr173_api.jar' inheritAll='false' />
to jsr173 target in build.xml for JAM. (I guess it was also because I hadn't
built xmlbeans before building JAM.)
Regards,
Ias
=========================================================
Lee, Changshin (Korean name)
Ias (International name)
Company Web Site: http://www.tmax.co.kr
Personal Web Site: http://www.iasandcb.pe.kr
---------------------------------------------------------
JSR 201, 204, 222 and 224 Expert Group Member
Apache Web Services Project Member
R&D Center
Tmax Soft, Inc.
=========================================================
> -----Original Message-----
> From: Patrick Calahan [mailto:pcal@bea.com]
> Sent: Saturday, March 27, 2004 12:24 PM
> To: geronimo-dev@incubator.apache.org
> Subject: JAM: Java API for Metadata
>
> Hello everyone. I am a committer on Xml-Beans, another
> project currently in the Apache Incubator. As part of my
> work there, I have developed an API for representing Java
> types and their associated metadata which I believe would be
> of general use to the community.
>
> The API is called 'JAM' - the Java API for Metadata. On the
> surface, it looks quite a bit like Reflection or the Doclet
> API, but it affords a greater level of flexibility and
> convenience, and in particular provides solutions for a
> number of thorny problems posed by JSR175.
>
> I have had a few discussions with some folks on
> general@incubator.apache.org about possibly spinning JAM up
> as an independent project from xbeans. It was suggested that
> it would be useful to test the waters in some other projects
> such as Geronimo to see if JAM would indeed be generally
> useful. So, here I am testing. :)
>
> Anyway, if you want more gory details, I have temporarily
> posted some white papers and the API docs here:
>
> http://www.pcal.net/jam
>
> Any feedback is more than welcome.
>
>
> Thanks,
>
> -Patrick
>