Hi everyone,
I was wondering what the status is of issue GEOS-4773. There has been no Jira activity in the past 2 years. This issue is important for one of our clients and we are considering to solve it via a pull request.
Before starting work on this I'd like to know if someone else is already taking care of this issue. If not, then it would be nice if we could have a small discussion on how this could be solved.
Looking forward to your responses!
Cheers,
Jan
--
----------------------------------------
Geodan
Buitenhaven 27-A
5211 TP 's-Hertogenbosch (NL)
T +31 (0)73 - 692 5151
M +31 (0)6 - 2395 1191
E jan.boonen@anonymised.com
www.geodan.nl | www.geodan.nl/disclaimer
----------------------------------------
On Fri, Sep 27, 2013 at 1:55 PM, Jan Boonen <jan.boonen@anonymised.com> wrote:
Hi everyone,
I was wondering what the status is of issue GEOS-4773. There has been no
Jira activity in the past 2 years. This issue is important for one of
our clients and we are considering to solve it via a pull request.
Before starting work on this I'd like to know if someone else is already
taking care of this issue. If not, then it would be nice if we could
have a small discussion on how this could be solved.
As far as I know nobody looked at it, mostly because it's believed that
it's hard to fix,
and that possibly only Justin could make a patch in a relatively short
amount of time (being
Justin the one that wrote the code in question and knows the issues with
XSD schema
managing inside out.. it's a nasty beast unfortunately)
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
-------------------------------------------------------