Hi Again, I'm still looking into this issue. I've tried a couple things and indeed NCLOB contents seem to come out wrong of the SeRow. The unit test you guys created only test for CLOB and it doesn't check the returned value is the expected one. I'm not sure what is it though. Are the test strings inserted already UTF-16 encoded?
Are you certain CLOBS are being correctly decoded for you? and in that case, could you verify NCLOBs? I've tried inserting two strings, "Hello", and "World", instead of the two ones you've set up that are already byte[]. Neither of them come right from SdeRow.getObject, both for CLOB and NCLOB they come with garbage. Did you experience something similar at all? Cheers, Gabriel On 4/9/10 5:54 PM, Gabriel Roldan wrote: > Hi Mark/Jody. > > Running over outstanding issues for me I got to > <http://jira.codehaus.org/browse/GEOS-3692> which lead me to look at the > NCLOB support you added to the ArcSDE plugin a while back, and wonder > what's the rationale for assuming the NCLOB is always UTF-16 encoded? is > that always the case, may be by definition? sorry for the ignorance. > > Cheers, > Gabriel > -- Gabriel Roldan OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
