Developer Forum

First problem seems to be driven by data in the FoodMart 2000 datasource. I
haven't narrowed it down yet, but it appears that selecting members in one
of the Product hierarchies causes an error during XMLSchema construction --
look for a dimension, hierarchy or member name that contains a '<'. Seems
you're trying to encode the < as < which is invalid for an element name.

Second problem is that you return an invalid XML response when the previous
error is encountered. If the request does not specify Data or None for the
Content property, the error above is encountered while the schema element is
being constructed. When you hit the error, you don't reset the pending
response... instead, you start streaming a new XML document for the SOAP
Fault right in the middle of the element name where the error occurred.

Clear "theair" to respond to me directly.

> First problem seems to be driven by data in the FoodMart 2000 datasource.
I
one
--
Seems
name.

I don't believe there are any Product members with < in their names. There
are some % but that's about it. Even if there were, I believe all the
element names are in the spec and not generated dynamically so an illegal
character shouldn't be an issue.

Perhaps you can dump the result XML doc but the situation you describe
doesn't seem likely.

previous
the
is

I suspect the same root cause is just killing your whole code. What kind of
front-end/client are you using to send and parse the SOAP?

-z

On 2004-01-28 09:47:12 -0800, "Brenda Bell"
< XXXX@XXXXX.COM > said:

I
one
--
Seems
name.
previous
the
is

Hi Brenda,

Have you managed to narrow down the repro for this? I have never seen this
problem before, but we've seen the SOAP Fault issue before with other
scenarios so if you can give me a specific repro I can investigate and try
and fix it.

Thanks,
Akshai


I
construction --
name.
previous
the
is