Re: Problems accessing dot net web service from java client
From: David Laub (dlaub_at_wheels.com)
Date: 01/10/05
- Next message: ashoksrini: "Bypassing Serialization/Deserialization in WebService/AP.NET"
- Previous message: David Laub: "Re: Problems accessing dot net web service from java client"
- In reply to: David Laub: "Re: Problems accessing dot net web service from java client"
- Next in thread: David Laub: "Re: Problems accessing dot net web service from java client"
- Reply: David Laub: "Re: Problems accessing dot net web service from java client"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 10 Jan 2005 13:25:41 -0600
I see many subtle differences in the wdsl files between a Sun site and a dot
net site
http://sunwireless.quimbik.com/serverscript2/serverscript?WSDL
http://www.dmlsoftware.com/CalculatorWS/Service1.asmx?WSDL
Maybe this differences are irrelevant, but I have a feeling some of them are
the key to solving the problem - if any kind soul who has cross java/dot net
web Service experience feels like taking this on, I'd be VERY grateful.
to repeat, the SOAP coming out of the java client has NO body - when
accessing the dmlsoftware site - but it WORKS, when accessing the identical
web service run on localhost
As an aside, if I point the java client to a NON web service, it gives the
same error (missing SOAP body), so it appears as if the java cleint does not
recognize a dot net web service as a Web Service
David Laub
"David Laub" <dlaub@wheels.com> wrote in message
news:OE3kNf09EHA.2572@tk2msftngp13.phx.gbl...
> I've see the java proxy/stub generator takes its encoding style from the
> wsdl file thet dot net generates - so, the java code IS generated with doc
> (versus rpc) style method calls
>
> I can change the dot net service to generate rpc style methods, and then
the
> java stub generator takes that into account, and then complains that it
> can't even generate code for rpc!! (versus doc)
>
> So, I'm still stuck, but thanks for your help anyhow
>
> Any other good ideas?
>
> Is the world of mixed vendor Web Services really that new?
>
> David Laub
> "David Laub" <dlaub@wheels.com> wrote in message
> news:e9Cnu4z9EHA.2568@TK2MSFTNGP10.phx.gbl...
> > Thru SOAPScope, I can see is that the java client sends a message with
no
> > body! So I'm not sure I can answer your question on "rpc encoded soap"
> > What, if anything can I do to find this out?
> >
> > Thanks
> >
> > David Laub
> > "Dilip Krishnan" <dkrishnan@NOSPAM.geniant.com> wrote in message
> > news:112790632407150836270048@msnews.microsoft.com...
> > > Hello David,
> > > Have you seen what the soap encoding style is? There could be some
> > interop
> > > problems if the j2me sends rpc encoded soap
> > >
> > > HTH
> > > Regards,
> > > Dilip Krishnan
> > > MCAD, MCSD.net
> > > dkrishnan at geniant dot com
> > > http://www.geniant.com
> > >
> > > > I've also posted this issue to a Sun/java formum, but since it
appears
> > > > to be an integration issue, this may be the better place to posr:
> > > >
> > > > I have written a dot net/c# Web Services doesn't fully work with
J2ME
> > > > client
> > > >
> > > > a) c# web service works with c# WIndows Client (local & remote web
> > > > service)
> > > > b) c# web service works with J2ME client - when the Web Service is
> > > > local
> > > > c) c# web service fails with J2ME client - when the Web Service is
> > > > remote
> > > > error/exception:
> > > >
> > > > "Missing SOAP Body or Envelope" -- This occurs at the point of
> > > > invoking the remote Web Service
> > > >
> > > > Similar/Identical problem documented in Sun Forum: (but no
resolution
> > > > for over two months!)
> > > >
> > > > http://forums.java.sun.com/thread.jspa?threadID=520204&tstart=240
> > > >
> > > > Speculation:
> > > >
> > > > a) dot net Web Services are "different" from Java Web services - yet
> > > > it
> > > > works fine in local mode
> > > > b) error is a misnomer & there is some other problem, perhaps
fixable
> > > > thru
> > > > Web.config changes remotely??
> > > > - changed Web.Config authentication (from Windows to none), but
> > > > this made
> > > > no difference
> > > > - changed back to default web service namespace of tempuri.org, but
> > > > this
> > > > made no difference
> > >
> > >
> >
> >
>
>
- Next message: ashoksrini: "Bypassing Serialization/Deserialization in WebService/AP.NET"
- Previous message: David Laub: "Re: Problems accessing dot net web service from java client"
- In reply to: David Laub: "Re: Problems accessing dot net web service from java client"
- Next in thread: David Laub: "Re: Problems accessing dot net web service from java client"
- Reply: David Laub: "Re: Problems accessing dot net web service from java client"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|