Hi,
the version of Xstream we are using (1.3.1) has known problems dealing with objects without a default
constructor when running on JDK 7. This is affecting a downstream project that is using GeoServer
along with custom plugins leveraging XStream over beans that do not have a default constructor.
The issue has been solved with XStream 1.4 (http://xstream.codehaus.org/changes.html#1.4),
of which the latest release is 1.4.3.
Any objection to upgrading GeoServer trunk to 1.4.3, and if no particular problem arises,
backport the upgrade to 2.2.x by 2.2.1?
Cheers
Andrea
–
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
No objection here. I agree though that this upgrade should be put through its paces on trunk since its a change to our core serialization stuff.
On Tue, Jul 31, 2012 at 6:45 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:
Hi,
the version of Xstream we are using (1.3.1) has known problems dealing with objects without a default
constructor when running on JDK 7. This is affecting a downstream project that is using GeoServer
along with custom plugins leveraging XStream over beans that do not have a default constructor.
The issue has been solved with XStream 1.4 (http://xstream.codehaus.org/changes.html#1.4),
of which the latest release is 1.4.3.
Any objection to upgrading GeoServer trunk to 1.4.3, and if no particular problem arises,
backport the upgrade to 2.2.x by 2.2.1?
Cheers
Andrea
–
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
Live Security Virtual Conference
Exclusive live event will cover all the ways today’s security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Sounds good to me. On a related note, at some point we'd need to
upgrade the jettison version, but comes with pitfalls for restconfig:
<http://osgeo-org.1560.n6.nabble.com/Upgrade-Jettison-dependency-version-td3819327.html>
On Tue, Jul 31, 2012 at 11:35 AM, Justin Deoliveira
<jdeolive@anonymised.com> wrote:
No objection here. I agree though that this upgrade should be put through
its paces on trunk since its a change to our core serialization stuff.
On Tue, Jul 31, 2012 at 6:45 AM, Andrea Aime <andrea.aime@anonymised.com>
wrote:
Hi,
the version of Xstream we are using (1.3.1) has known problems dealing
with objects without a default
constructor when running on JDK 7. This is affecting a downstream project
that is using GeoServer
along with custom plugins leveraging XStream over beans that do not have a
default constructor.
The issue has been solved with XStream 1.4
(http://xstream.codehaus.org/changes.html#1.4),
of which the latest release is 1.4.3.
Any objection to upgrading GeoServer trunk to 1.4.3, and if no particular
problem arises,
backport the upgrade to 2.2.x by 2.2.1?
Cheers
Andrea
--
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Yeah, my same stance stands… if the upgrade will have backward compatibility changes it should be done only on master. And ideally now while master is still in an “unstable” state.
On Tue, Jul 31, 2012 at 8:49 AM, Gabriel Roldan <groldan@anonymised.com> wrote:
Sounds good to me. On a related note, at some point we’d need to
upgrade the jettison version, but comes with pitfalls for restconfig:
<http://osgeo-org.1560.n6.nabble.com/Upgrade-Jettison-dependency-version-td3819327.html>
On Tue, Jul 31, 2012 at 11:35 AM, Justin Deoliveira
<jdeolive@anonymised.com> wrote:
No objection here. I agree though that this upgrade should be put through
its paces on trunk since its a change to our core serialization stuff.
On Tue, Jul 31, 2012 at 6:45 AM, Andrea Aime <andrea.aime@anonymised.com>
wrote:
Hi,
the version of Xstream we are using (1.3.1) has known problems dealing
with objects without a default
constructor when running on JDK 7. This is affecting a downstream project
that is using GeoServer
along with custom plugins leveraging XStream over beans that do not have a
default constructor.
The issue has been solved with XStream 1.4
(http://xstream.codehaus.org/changes.html#1.4),
of which the latest release is 1.4.3.
Any objection to upgrading GeoServer trunk to 1.4.3, and if no particular
problem arises,
backport the upgrade to 2.2.x by 2.2.1?
Cheers
Andrea
–
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
Live Security Virtual Conference
Exclusive live event will cover all the ways today’s security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Live Security Virtual Conference
Exclusive live event will cover all the ways today’s security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
On Wed, Aug 1, 2012 at 4:19 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:
Yeah, my same stance stands… if the upgrade will have backward compatibility changes it should be done only on master. And ideally now while master is still in an “unstable” state.
Oops, I’m afraid this as never done… and as a result we have issues in GS 2.2.0 ogr2ogr output
format (at the very least) when GS is used against JDK 7
Bummer… I’ll try to make the upgrade on trunk asap (which means in a few days) and
maybe we can backport to 2.2.x later
Cheers
Andrea
–
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it