From: | "Markus KARG" <markus(at)headcrashing(dot)eu> |
---|---|
To: | "'List'" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Pre-processing during build |
Date: | 2015-06-18 19:44:28 |
Message-ID: | 00d701d0a9ff$30d5d8a0$928189e0$@eu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
> If that won't work, nobody could write a Java EE program and compile
> and test it agains the official javaee.jar, as that one not even
> contains
ANY
> byte code but SOLELY declarations. And that one's an official JAR from
the
> makers of Java!
>Sorry, but that doesn't make any sense at all. The "official" JavaEE jar does contain bytecode: interfaces and some supporting classes like exceptions.
Wrong. There are lots of classes in that JAR that actually are "broken" from the view of the JLS. When you try to instantiate them you'll simply get a weird exception telling you that for some of them the byte code is missing. This is done with several APIs of Java EE as due to the way it is specified in the particular specifications, it is up to the vendor to provide them. So you can compile against that explicitly bytecode-dropped classes without any problem, but you can neither test nor otherwise instantiate them.
Regards
-Markus
From | Date | Subject | |
---|---|---|---|
Next Message | Markus KARG | 2015-06-18 19:50:02 | Re: Pre-processing during build |
Previous Message | Vladimir Sitnikov | 2015-06-18 19:33:07 | Re: Pre-processing during build |