Encoder can actually perfom a single encode, a second will fail
---------------------------------------------------------------
Key: GEOT-3047
URL: http://jira.codehaus.org/browse/GEOT-3047
Project: GeoTools
Issue Type: Bug
Components: ext xml-xsd
Affects Versions: 2.6.3
Reporter: Andrea Aime
Assignee: Justin Deoliveira
Fix For: 2.6.4
Calling encoder.encode(...) twice is a row will result in a null pointer
exception.
This is because the schema index is destroyed at the end of the first encode, a
second destroy call will result in an NPE (but I doubt the second encode is
working properly using an already disposed of schema index)
Ways out of this:
- don't destroy the schema index (will this cause memory leaks?)
- build the schema index at the beginning of encode and destroy it at the end
- explicitly state that the encoder cannot do more than a single encode
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
