search

MiguelEspinozaMedina / javaapiforkml

Automatically exported from code.google.com/p/javaapiforkml
0 stars 0 forks source link

Please change dependency to jaxb-impl, jaxb-xjc from SNAPSHOT to released version #18

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Hello,

Currently the JavaAPIforKml-2.2.0.pom contains:
        <dependency>
            <groupId>com.sun.xml.bind</groupId>
            <artifactId>jaxb-impl</artifactId>
            <version>2.2-SNAPSHOT</version>
        </dependency>
        <dependency>
            <groupId>com.sun.xml.bind</groupId>
            <artifactId>jaxb-xjc</artifactId>
            <version>2.2-SNAPSHOT</version>
        </dependency>

Could you change it to ?
        <dependency>
            <groupId>com.sun.xml.bind</groupId>
            <artifactId>jaxb-impl</artifactId>
            <version>2.2</version>
        </dependency>
        <dependency>
            <groupId>com.sun.xml.bind</groupId>
            <artifactId>jaxb-xjc</artifactId>
            <version>2.2</version>
        </dependency>

Thanks in advance.

Original issue reported on code.google.com by marco.br...@googlemail.com on 13 Jan 2010 at 3:35

GoogleCodeExporter commented 9 years ago 
ok, done that (:

Original comment by bachmann...@gmail.com on 13 Jan 2010 at 5:09

GoogleCodeExporter commented 9 years ago 
In the POM
http://download.java.net/maven/2/de/micromata/jak/JavaAPIforKml/2.2.0/JavaAPIfor
Kml-2.2.0.pom
still dependencies to the SNAPSHOT versions of jaxb-imp,jaxb-xjc are used. 
Could you
update this POM, too?

Obviously I use Maven to reference javaapiforkml, so I get the POM from the 
repository.

Original comment by marco.br...@googlemail.com on 14 Jan 2010 at 8:09

GoogleCodeExporter commented 9 years ago 
If I try to unmarshal the example KML from
http://labs.micromata.de/display/jak/HelloKML+%28Quickstart%29 using the 2.2 
versions
of jaxb-impl, jaxb-xjc I get the following error:

com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 7 counts of
IllegalAnnotationExceptions
XmlElementRef points to a non-existent class.
    this problem is related to the following location:
        at protected de.micromata.opengis.kml.v_2_2_0.Feature
de.micromata.opengis.kml.v_2_2_0.Kml.feature
        at de.micromata.opengis.kml.v_2_2_0.Kml
XmlElementRef points to a non-existent class.
    this problem is related to the following location:
        at protected de.micromata.opengis.kml.v_2_2_0.AbstractView
de.micromata.opengis.kml.v_2_2_0.NetworkLinkControl.abstractView
        at de.micromata.opengis.kml.v_2_2_0.NetworkLinkControl
        at protected de.micromata.opengis.kml.v_2_2_0.NetworkLinkControl
de.micromata.opengis.kml.v_2_2_0.Kml.networkLinkControl
        at de.micromata.opengis.kml.v_2_2_0.Kml
XmlElementRef points to a non-existent class.
    this problem is related to the following location:
        at protected java.util.List de.micromata.opengis.kml.v_2_2_0.Delete.feature
        at de.micromata.opengis.kml.v_2_2_0.Delete
        at protected java.util.List
de.micromata.opengis.kml.v_2_2_0.Update.createOrDeleteOrChange
        at de.micromata.opengis.kml.v_2_2_0.Update
        at protected de.micromata.opengis.kml.v_2_2_0.Update
de.micromata.opengis.kml.v_2_2_0.NetworkLinkControl.update
        at de.micromata.opengis.kml.v_2_2_0.NetworkLinkControl
        at protected de.micromata.opengis.kml.v_2_2_0.NetworkLinkControl
de.micromata.opengis.kml.v_2_2_0.Kml.networkLinkControl
        at de.micromata.opengis.kml.v_2_2_0.Kml
XmlElementRef points to a non-existent class.
    this problem is related to the following location:
        at protected de.micromata.opengis.kml.v_2_2_0.AbstractView
de.micromata.opengis.kml.v_2_2_0.Feature.abstractView
        at de.micromata.opengis.kml.v_2_2_0.Feature
        at protected java.util.List de.micromata.opengis.kml.v_2_2_0.Delete.feature
        at de.micromata.opengis.kml.v_2_2_0.Delete
        at protected java.util.List
de.micromata.opengis.kml.v_2_2_0.Update.createOrDeleteOrChange
        at de.micromata.opengis.kml.v_2_2_0.Update
        at protected de.micromata.opengis.kml.v_2_2_0.Update
de.micromata.opengis.kml.v_2_2_0.NetworkLinkControl.update
        at de.micromata.opengis.kml.v_2_2_0.NetworkLinkControl
        at protected de.micromata.opengis.kml.v_2_2_0.NetworkLinkControl
de.micromata.opengis.kml.v_2_2_0.Kml.networkLinkControl
        at de.micromata.opengis.kml.v_2_2_0.Kml
XmlElementRef points to a non-existent class.
    this problem is related to the following location:
        at protected de.micromata.opengis.kml.v_2_2_0.TimePrimitive
de.micromata.opengis.kml.v_2_2_0.Feature.timePrimitive
        at de.micromata.opengis.kml.v_2_2_0.Feature
        at protected java.util.List de.micromata.opengis.kml.v_2_2_0.Delete.feature
        at de.micromata.opengis.kml.v_2_2_0.Delete
        at protected java.util.List
de.micromata.opengis.kml.v_2_2_0.Update.createOrDeleteOrChange
        at de.micromata.opengis.kml.v_2_2_0.Update
        at protected de.micromata.opengis.kml.v_2_2_0.Update
de.micromata.opengis.kml.v_2_2_0.NetworkLinkControl.update
        at de.micromata.opengis.kml.v_2_2_0.NetworkLinkControl
        at protected de.micromata.opengis.kml.v_2_2_0.NetworkLinkControl
de.micromata.opengis.kml.v_2_2_0.Kml.networkLinkControl
        at de.micromata.opengis.kml.v_2_2_0.Kml
XmlElementRef points to a non-existent class.
    this problem is related to the following location:
        at protected java.util.List de.micromata.opengis.kml.v_2_2_0.Feature.styleSelector
        at de.micromata.opengis.kml.v_2_2_0.Feature
        at protected java.util.List de.micromata.opengis.kml.v_2_2_0.Delete.feature
        at de.micromata.opengis.kml.v_2_2_0.Delete
        at protected java.util.List
de.micromata.opengis.kml.v_2_2_0.Update.createOrDeleteOrChange
        at de.micromata.opengis.kml.v_2_2_0.Update
        at protected de.micromata.opengis.kml.v_2_2_0.Update
de.micromata.opengis.kml.v_2_2_0.NetworkLinkControl.update
        at de.micromata.opengis.kml.v_2_2_0.NetworkLinkControl
        at protected de.micromata.opengis.kml.v_2_2_0.NetworkLinkControl
de.micromata.opengis.kml.v_2_2_0.Kml.networkLinkControl
        at de.micromata.opengis.kml.v_2_2_0.Kml
XmlElementRef points to a non-existent class.
    this problem is related to the following location:
        at protected java.util.List de.micromata.opengis.kml.v_2_2_0.Create.container
        at de.micromata.opengis.kml.v_2_2_0.Create
        at protected java.util.List
de.micromata.opengis.kml.v_2_2_0.Update.createOrDeleteOrChange
        at de.micromata.opengis.kml.v_2_2_0.Update
        at protected de.micromata.opengis.kml.v_2_2_0.Update
de.micromata.opengis.kml.v_2_2_0.NetworkLinkControl.update
        at de.micromata.opengis.kml.v_2_2_0.NetworkLinkControl
        at protected de.micromata.opengis.kml.v_2_2_0.NetworkLinkControl
de.micromata.opengis.kml.v_2_2_0.Kml.networkLinkControl
        at de.micromata.opengis.kml.v_2_2_0.Kml

    at
com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnn
otationsException.java:66)
    at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:389)
    at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:236)
    at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:76)
    at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:55)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:211)
    at javax.xml.bind.ContextFinder.find(ContextFinder.java:372)
    at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
    at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:522)
    at de.micromata.opengis.kml.v_2_2_0.Kml.unmarshal(Kml.java:801)
    at de.micromata.opengis.kml.v_2_2_0.Kml.unmarshal(Kml.java:830)
    at

Original comment by marco.br...@googlemail.com on 14 Jan 2010 at 8:23

GoogleCodeExporter commented 9 years ago 
Hi Marco,
I just tested the issue in Eclipse with a new Maven project 
and I can't reproduce your error message (but it says it can't find jaxb)

I uploaded to Screenshots, of how it should look:

Original comment by bachmann...@gmail.com on 15 Jan 2010 at 9:13

Attachments:

GoogleCodeExporter commented 9 years ago 
The two screenshots show the difference between JAK 2.2.0 (build on 30-Nov-2009 
03:32
and uses the SNAPSHOT-versions of JAXB) and JAK 2.2.0-SNAPSHOT (the newer one. 
build
on 13-Jan-2010 09:42 and doesn't use the JAXB's SNAPSHOT-version). The right 
side of
each image shows how Maven resolved the dependency path.

I hope I could help you a bit

Original comment by bachmann...@gmail.com on 15 Jan 2010 at 9:17

GoogleCodeExporter commented 9 years ago 
Thank you for your analysis!

I think I have a problem with the used JAXB version during runtime. I deploy my
application to Oracle Weblogic Application Server. Probably an old version of 
JAXB
(2.0) is used instead of my deployed Jars. I'll look if  I can change this 
behaviour.

Thanks.

Original comment by marco.br...@googlemail.com on 18 Jan 2010 at 7:39

GoogleCodeExporter commented 9 years ago 
Unfortunately I am not able to change the used JAXB version from 2.0 to 2.2 in 
Oracle
Weblogic 10.0 MP1. So I can not use your API.

Original comment by marco.br...@googlemail.com on 22 Jan 2010 at 10:36