Adding jaxb's users list.
On 10/27/14 12:58 AM, Pollock, Wayne wrote:
> I have seen this behavior for some time now, under Windows 7,
> warning messages coming from javaee.jar, as this output shows:
>
> C:\Temp>javac -version
> javac 1.8.0_25
>
> C:\Temp>asadmin version
> Version = GlassFish Server Open Source Edition 4.1 (build 13)
> Command version executed successfully.
>
> C:\Temp>type Foo.java
> class Foo {}
>
> C:\Temp>set CLASSPATH=.
>
> C:\Temp>javac -Xlint:all Foo.java
>
> C:\Temp>set CLASSPATH=.;\Java\glassfish4\glassfish\lib\javaee.jar
>
> C:\Temp>javac -Xlint:all Foo.java
> warning: [path] bad path element
> "\Java\glassfish4\glassfish\lib\..\modules\jaxb-core-2.2.10-b140802
> .1033.jar": no such file or directory
> warning: [path] bad path element
> "\Java\glassfish4\glassfish\lib\..\modules\jaxb-xjc-2.2.10-b140802.
> 1033.jar": no such file or directory
> warning: [path] bad path element
> "\Java\glassfish4\glassfish\lib\..\modules\jaxb-impl-2.2.10-b140802
> .1033.jar": no such file or directory
> warning: [path] bad path element
> "\Java\glassfish4\glassfish\lib\..\modules\jaxb-jxc-2.2.10-b140802.
> 1033.jar": no such file or directory
> warning: [path] bad path element
> "\Java\glassfish4\glassfish\lib\..\modules\jaxb1-impl-2.2.10-b14080
> 2.1033.jar": no such file or directory
> warning: [path] bad path element
> "\Java\glassfish4\glassfish\lib\..\modules\jaxb-runtime-2.2.10-b140
> 802.1033.jar": no such file or directory
> warning: [path] bad path element
> "\Java\glassfish4\glassfish\lib\..\modules\jaxb-api-2.2.12-b140109.
> 1041.jar": no such file or directory
> warning: [path] bad path element
> "\Java\glassfish4\glassfish\lib\..\modules\txw2-2.2.10-b140802.1033
> .jar": no such file or directory
> warning: [path] bad path element
> "\Java\glassfish4\glassfish\lib\..\modules\istack-commons-runtime-2
> .19.jar": no such file or directory
> warning: [path] bad path element
> "\Java\glassfish4\glassfish\lib\..\modules\stax-ex-1.7.7.jar": no s
> uch file or directory
> warning: [path] bad path element
> "\Java\glassfish4\glassfish\lib\..\modules\FastInfoset-1.2.13.jar":
> no such file or directory
> warning: [path] bad path element
> "\Java\glassfish4\glassfish\lib\..\modules\msv-core-2013.6.1.jar":
> no such file or directory
> warning: [path] bad path element
> "\Java\glassfish4\glassfish\lib\..\modules\xsdlib-2013.6.1.jar": no
> such file or directory
> warning: [path] bad path element
> "\Java\glassfish4\glassfish\lib\..\modules\relaxngDatatype-20020414
> .jar": no such file or directory
> warning: [path] bad path element
> "\Java\glassfish4\glassfish\lib\..\modules\isorelax-20090621.jar":
> no such file or directory
> 15 warnings
>
> C:\Temp>
>
> I have traced the bad class path elements to jaxb-osgi.jar.
> The manifest seems to be an old template manifest, not the
> correct one, but I don't know that for certain.
>
> By editing that manifest file, I can eliminate the warning
> messages. However I think some of the elements do need to be
> there, just without the "-<versionNumber>" part; for example,
> "jaxb-api.jar".
>
> More troubling is the reference to "jaxb1-impl-2.2.10-b14080.jar",
> which I replaced with "jaxb-impl.jar". (It's also strange to me
> I was able to get away with this; the gf jars aren't signed!?)
> with such drastic changes, I have little confidence that my
> modified gf is correct.
>
> But it seems strange to me that nobody else posted about this, so
> I'm thinking I must had done something dumb? Can someone more
> knowledgeable than I look into this?
>
> If this is indeed a bug, I would like to suggest the correct manifest
> be used, the code recompiled under a supported version of Java (the
> current manifest suggests Java 6 was used), and then regression and
> compliance testing be redone.
>