I think this is a interoperability problem with the Sun ORB being used by the client. Try using OpenORB on the client. You need to put an orb.properties file in $JAVA_HOME/lib. The file should contain.

org.omg.CORBA.ORBClass=org.openorb.CORBA.ORB
org.omg.CORBA.ORBSingletonClass=org.openorb.CORBA.ORBSingleton

I'm curious to know if it works with string or if a change to wstring is necessary. Hopefully not as using the Sun ORB and wstring results in a BAD_OPERATION exception from the ORB.

On Monday, January 7, 2002, at 05:38 AM, Franosch, Heike wrote:

Hi Kimbro,

yes it is part of the ISO Latin 1. On server side it just shows a ? .
Does it say something to you?

Thanks, Heike

-----Urspr�ngliche Nachricht-----
Von:    Kimbro Staken [SMTP:[EMAIL PROTECTED]
Gesendet am:    Montag, 7. Januar 2002 13:09
An:     [EMAIL PROTECTED]
Betreff:        Re: AW: xpath query problem

The CORBA string type supports the ISO Latin 1 character set. Is the
umlaut part of that set? What character do you get on the server?

On Monday, January 7, 2002, at 03:39 AM, Franosch, Heike wrote:

Hi Tom, hi all,

I debugged a while and it seems to be a corba issue. On client side my
umlaut in the xpath is well and on server
side it is scrambled. To be concrete: on client side,
XPathQueryServiceImple.query -> _CollectionStub.queryCollection
which is using the ValueHelper.write() all is well. And on server side
the
ValueHelper.read() does not catch
the umlaut correct.

Can someone please verify that it is not only my machine having this
problem?
<?xml version "1.0"?>
<direction><name>N�rnberg</name></direction>

with the following xpath
xindice xpath -c directionTest -q "/direction[name='N�rnberg']"

When inserting this document, the german umlauts are stored correct. I
could
verify this on server
side. This method is not using the ValueHelper.

I am running out of ideas ... can someone please help?

Thanks, Heike


Kimbro Staken
XML Database Software, Consulting and Writing
http://www.xmldatabases.org/




Reply via email to