that you are writing a SOAP interface to
> mathematica :) Right?
>
> -- dims
>
> --- Chris Williamson <[EMAIL PROTECTED]> wrote:
> > Hmmm. I don't mind getting rid of setType all that much, as
> long as I can
> > still set the type using attributes. Which mea
Hmmm. I don't mind getting rid of setType all that much, as long as I can
still set the type using attributes. Which means fixing that last bug I
submitted :) I have a fix btw, if you would like to see it. It is pretty
simple, but I am not sure it is as efficient as you would like. It is
howev
That is precisely why I was using it. I was using it only because I had to
keep track of the namespace mappings myself since the MessageElement was
having problems with it. Once everything is fixed, I will not keep track of
the mappings myself. So I will probably no longer use the function.
> -
out.println(element.toString());
Please take a look at these problems with MessageElement and let me know if
I am way off base. I would like to report these as bugs if they truly are.
They are important bugs to me. It makes my application completely unusable
at the moment.
Chris Williamson
