By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,262 Members | 1,161 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,262 IT Pros & Developers. It's quick & easy.

Problems accessing dot net web service from java client

P: n/a
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.js...204&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
Nov 23 '05 #1
Share this Question
Share on Google+
7 Replies


P: n/a
Assuming that you got the permission and authetication are correctly
configured including the IIS,

The best posible way to diagnose this is , try to use some kind of
diagnostic tool, like tcptrace, or SOAPScope to view the message on the
wire. then the asp.net web services will normally return and HTML pages
when there's and error.

regards
erymuzuan

David Laub wrote:
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.js...204&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


Nov 23 '05 #2

P: n/a
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.js...204&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

Nov 23 '05 #3

P: n/a
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" <dk*******@NOSPAM.geniant.com> wrote in message
news:11**********************@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.js...204&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


Nov 23 '05 #4

P: n/a
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" <dl***@wheels.com> wrote in message
news:e9**************@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" <dk*******@NOSPAM.geniant.com> wrote in message
news:11**********************@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.js...204&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



Nov 23 '05 #5

P: n/a
I see many subtle differences in the wdsl files between a Sun site and a dot
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 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" <dl***@wheels.com> wrote in message
news:OE**************@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" <dl***@wheels.com> wrote in message
news:e9**************@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" <dk*******@NOSPAM.geniant.com> wrote in message
news:11**********************@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.js...204&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



Nov 23 '05 #6

P: n/a
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" <dl***@wheels.com> wrote in message
news:ea**************@tk2msftngp13.phx.gbl...
I see many subtle differences in the wdsl files between a Sun site and a dot 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 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" <dl***@wheels.com> wrote in message
news:OE**************@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" <dl***@wheels.com> wrote in message
news:e9**************@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" <dk*******@NOSPAM.geniant.com> wrote in message
news:11**********************@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.js...204&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
>
>



Nov 23 '05 #7

P: n/a
Hello

It seems to me that you found your problem there. In SOAP specifications
the body is a MANDATORY tag. If your client isn't sending it then the
client has something bad.

UDDI is not mandatory.

As far as i tested, i have java clients working fine with .NET web services.

And yes, there are diferences between WSDL generated from JAVA and WSDL
generated from .NET, but they only seem to be namespace differences.
David Laub wrote:
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" <dk*******@NOSPAM.geniant.com> wrote in message
news:11**********************@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.js...204&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



Nov 23 '05 #8

This discussion thread is closed

Replies have been disabled for this discussion.