We do not want to change our Java classes ... but would appreciate any
suggestions for that too.
use typed arrays because:
1) it works
2) you get type checking on the client
cheers
timj
Jonathan,
> I'm getting this exception when passing a JavaBean that a couple of the
properties are java.sql.Date objects. i noticed from the archives that Axis
my have trouble with Dates and sql.Date. Is this true or is there a better
workaround?
I am using beta2, and can happily pass a ja
Chad, chester,
FWIW, this mirrors my experience _exactly_
timj
> I started with Apache SOAP 2.2 initailly and got basic simple web
service samples working.
> Considered it's maturity, I was about to recommended my company to use
it.
Then I start to build MS client against. And
Patricia,
> Does axis support deserializing bean which inherits other bean???
yes. i do this.
> If yes, do I have to write custom serializer, deserializer??
no
> Please
> explain
sorry, i can only say that it works for me. i would look somewhere else for
your problem.
cheers
timj
Jaba,
Thanks, but for now, we are going to develop our client as an application
instead of an applet. I am sick and tired of interoperability issues, and
can't cope with another SOAP service / client to integrate. I am hoping
that by the time we ship, axis will be applet compatible.
cheers
I am having terrible trouble getting axis to work from within an applet.
The problem is that the commons-logging won't initialise a logging class
(due to a security exception). So I have fixed this, but am still hitting
security problems with any logging interface i try.
has anyone solved this?
