A different angle: must I register my (dot net) Web Service with UDDI for it
to be callable form a java app? - the java doc I'm now reading implying this
UDDI registration is a MANDATORY step!
"David Laub" <dlaub@wheels.com> wrote in message
news:eaO81o09EHA.2572@tk2msftngp13.phx.gbl...[color=blue]
> I see many subtle differences in the wdsl files between a Sun site and a[/color]
dot[color=blue]
> net site
>
>
http://sunwireless.quimbik.com/serve...verscript?WSDL
>
>
http://www.dmlsoftware.com/Calculato...ice1.asmx?WSDL
>
> Maybe this differences are irrelevant, but I have a feeling some of them[/color]
are[color=blue]
> the key to solving the problem - if any kind soul who has cross java/dot[/color]
net[color=blue]
> 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[/color]
identical[color=blue]
> 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[/color]
not[color=blue]
> 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...[color=green]
> > 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[/color][/color]
doc[color=blue][color=green]
> > (versus rpc) style method calls
> >
> > I can change the dot net service to generate rpc style methods, and then[/color]
> the[color=green]
> > 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...[color=darkred]
> > > Thru SOAPScope, I can see is that the java client sends a message with[/color][/color]
> no[color=green][color=darkred]
> > > body! So I'm not sure I can answer your question on "rpc encoded[/color][/color][/color]
soap"[color=blue][color=green][color=darkred]
> > > 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[/color][/color][/color]
some[color=blue][color=green][color=darkred]
> > > 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[/color][/color]
> appears[color=green][color=darkred]
> > > > > 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[/color][/color]
> J2ME[color=green][color=darkred]
> > > > > 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[/color][/color]
> resolution[color=green][color=darkred]
> > > > > for over two months!)
> > > > >
> > > > >
http://forums.java.sun.com/thread.js...204&tstart=240
> > > > >
> > > > > Speculation:
> > > > >
> > > > > a) dot net Web Services are "different" from Java Web services -[/color][/color][/color]
yet[color=blue][color=green][color=darkred]
> > > > > it
> > > > > works fine in local mode
> > > > > b) error is a misnomer & there is some other problem, perhaps[/color][/color]
> fixable[color=green][color=darkred]
> > > > > 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,[/color][/color][/color]
but[color=blue][color=green][color=darkred]
> > > > > this
> > > > > made no difference
> > > >
> > > >
> > >
> > >[/color]
> >
> >[/color]
>
>[/color]
