[Gvsig_english] Problems with printing and exporting a map containing data from a geodatabase

[Juan Lucas Dominguez Rubio]

Hello, Georg:
 
There might be a problem with the Oracle driver too. Please do this:
 
- close gvSIG if it's running
- delete all the files *log* in /home/<user>/gvSIG/
- start gvSIG and perform the actions that bring you to the error
- close gvSIG 
- create a zip file with all the files *log* in /home/<user>/gvSIG/ and send the zip file to the list (it's not a good idea to cut the log files in pieces, it's better to send the whole log file)
 
 
If you can create a dump file (.dmp) so that I can recreate that table here, it'll be great.
 
regards,
 
Juan Lucas Domínguez Rubio
---
Prodevelop SL, Valencia (España)
Tlf.: 96.351.06.12 -- Fax: 96.351.09.68
http://www.prodevelop.es <http://www.prodevelop.es/> 
---

________________________________

De: gvsig_internacional-bounces at listserv.gva.es en nombre de georgsedlmeir
Enviado el: mié 16/02/2011 12:20
Para: gvsig_internacional at listserv.gva.es
Asunto: [Gvsig_english] Problems with printing and exporting a map containing data from a geodatabase




Dear community members,
using gvSIG 1.10 I connected to a geoDB of our local land survey office in
Munich to retrieve a single polygon layer of data and created a map
consisting of only that one layer, making use of standard symbols for
visualization.
However, neither printing nor exporting the map was possible. Trying to
export the map brought up an error message console with the java stacktrace
contained in the attached file stacktrace_export.txt.
Trying to print the map gave a similar result, with the error message (shown
in stacktrace_print.txt) being slightly different.
Besides, a look into the logfile reveals a warning message repeating over
and over during the session, as shown in attached file gvSIG_kopie.log.

After converting the geoDB layer to a shapefile and using that one for
display both printing and exporting worked.

Maybe someone has experienced that issue too? Despite the existing
workaround a solution would be much appreciated, since it's much more
convenient to work with data from the geodatabase instead of being forced to
make a local copy via the export function.

Best,
Georg Sedlmeir


http://osgeo-org.1803224.n2.nabble.com/file/n6031316/stacktrace_export.txt
stacktrace_export.txt
http://osgeo-org.1803224.n2.nabble.com/file/n6031316/stacktrace_print.txt
stacktrace_print.txt
http://osgeo-org.1803224.n2.nabble.com/file/n6031316/gvSIG_kopie.log
gvSIG_kopie.log

--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Problems-with-printing-and-exporting-a-map-containing-data-from-a-geodatabase-tp6031316p6031316.html
Sent from the gvSIG users mailing list archive at Nabble.com.
_______________________________________________
Gvsig_internacional mailing list
Gvsig_internacional at listserv.gva.es
http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listserv.gva.es/pipermail/gvsig_internacional/attachments/20110216/843736e2/attachment.htm