[Mulgara-general] execute command doesn't seem to work
Paul Gearon
gearon at ieee.org
Wed Aug 12 21:26:46 UTC 2009
On Wed, Aug 12, 2009 at 1:15 PM, Alex Hall<alexhall at revelytix.com> wrote:
> Hmm... I'm taking a closer look at this problem. It's not going to be
> trivial to fix. The ExecuteScript command is trying to use the
> connection passed in from the interpreter to execute each command in the
> script. The interpreter, in turn, uses the server URI that it gets from
> the ExecuteScript command to create the connection (or re-use an
> existing connection). The ExecuteScript command, being a local command,
> does not know any server URI so it gets a dummy connection with a null
> session, hence the NullPointerException.
OK, so what if the ExecuteScript command ignores the connection that
it's given and creates connections of its own?
>From memory, we're sending the entire command to the server... is that
right? If so, then we'd have to do the parsing at the client end
and..... err, it's looking messy already. Sigh.
Paul
More information about the Mulgara-general
mailing list