"matthew.hawthorne" <[EMAIL PROTECTED]> writes:
> I'm not sure if this is it -- but ThreadLocals don't work inside of
> app servers that use thread pooling.
that's news to me. care to clarify this?
perhaps you mean that for a series of requests coming as part of a
single session, the several re
"Zedler, Michel" <[EMAIL PROTECTED]> writes:
> Any hints what is going wrong here?
two things: have you tried building from a clean tree? also make
sure that your runtime environment has the same versions of the
relevant libraries as the compile env.
just a few days ago, I did a CVS update on a
"Liu, Scott" <[EMAIL PROTECTED]> writes:
> Will anyone in the Axis community care to respond? Or is this a fact of
> life?
I don't have an answer for you, but can perhaps add something that
might help in tracking this down.
"�" is probably coming from �, which is the NULL
character, which is
Anderson Jonathan <[EMAIL PROTECTED]> writes:
> Maybe we'll see an XML Schema "Lite" in the future?
we already have one of these:
http://www.relaxng.org/
or maybe you meant "maybe we'll see support for other schema languages
in our WS tools in the future", in which case I wonder the same thin
Greg Hess <[EMAIL PROTECTED]> writes:
> For fun I tested RMI too:
>
> Case: 100M zip, over 1000 calls with zip byte[] passed as method arg:
>
> Product Memory(ave per
> call) Time(ave round trip)
>
I wonder what, if anything, people are doing to manage client-side
configuration?
I would like to make it as simple as possible for people to write
Java code against services I've deployed. I had envisioned something
like this:
* clients require a jar file containing the service interface and
I have only recently started using Axis, so I'm not sure if I'm even
understanding your question correctly. but it sounds like you're
trying to do something I just did yesterday.
I had written a Java interface with a bunch of methods. The
arguments and return values of the methods were either s
[EMAIL PROTECTED] writes:
> However, there is one caveat for both DynamicInvoker and WSIF:
> they work, as they are, only with simple java types. If you want to
> use complex types, you have to have a corresponding Java class created
> on the client side - which makes dynamic invocation much
