> Okay, you don't need worry about the encoding once > it's in the db. Ok.
> Also, check this XMLdbGUI tool to be sure it can > handle your encoding. Not all tools provide proper > support of encodings. ( I personally use Attrezzo > plugin for the Eclipse IDE to browse and edit > documents in Xindice) I'll do and I'll try to insert some documents programatically tomorrow, too. > When the document is retrive try calling : > Resource res = results.nextResource(); > System.out.println((String) res.getContent()); > > You should see a print out of each item in the result > with the <?xml?> line. Check the encoding of on this > line. If it is set to something other than UTF or > ISO-8859, you may have to do some work to keep you > encoding it sync. Nope. The line is there but without the encoding parameter...sighhh... > Also the class I referred to was called > XindiceQueryResultWrapper. If pass the ResourceSet to > the constructor and then call setResultTag then > buildResultSet methods you can use one of the getter > method to get a complete DOM Document of your query > results or a string contain the xml. I see. I'll try it again. > if this all fails, you could alwas use windows > character mapper to determine what the hex vale of > those characters are a write a regular expression to > remove them from your document. Currently I tried making just a simple String.replace(old, new), and it worked. But this is not the solution I wanted. I'm afraid this is working today and maybe not in the future... > I will give the issue more thought tonight, and see if > any other solutions come to mind. Thank you very much. I'll post tomorrow about my new problems or solutions if any. Best.
