.NET webservice

Hi,
I am looking to create a .NET webservice that will have a parameterised and a non parameterised function which returns some XML.

I wanted to know how can I create a component that will consume my webservice and display the results.

I came across getSOAPXML function but I cannot see any documentation on it.

I would be greatful if anyone can help me with this.

Thank you.

Kind regards,
Murtaza

Installed Software:
Interwoven LiveSite 3.0.2.0.68986
Interwoven TeamSite 6.7.1 Service Pack 1

Find more posts tagged with

Comments

tec_iwov

the soap based component is very old. You should use the Axis library to communicate /w your webservice.

http://ws.apache.org/axis/java/user-guide.html

if your .net impl produces a wsdl file then you can generate the stubs for it with axis

murti

Hi tec_iwov,

Thank you for your reply.

I was looking at that but didn't have a clue if a .NET webservice could be transformed into Java service.

My .NET webservice does have a wsdl file.

I will look through the link you have sent me, thanks!

Any things I need to pay attention to? or is it just a matter of reading that link and going through it?

Thank you very much.

Kind regards,
Murti

cute_guy

Hi,
I am looking to create a .NET webservice that will have a parameterised and a non parameterised function which returns some XML.

I wanted to know how can I create a component that will consume my webservice and display the results.

I came across getSOAPXML function but I cannot see any documentation on it.

I would be greatful if anyone can help me with this.

Thank you.

Kind regards,
Murtaza

Installed Software:
Interwoven LiveSite 3.0.2.0.68986
Interwoven TeamSite 6.7.1 Service Pack 1

Check out this blog on [font=Arial Black]Consuming .NET Web Service from Java.

[/font]

With the help of NetBeans IDE create java proxy classes to access .NET webservice.

Once your java proxy classes are created try to call them in your external component

http://srikanthtechnologies.com/blog/dotnet/wsdaljava.aspx

AlexC

You can also consider making the .NET service REST/HTTP based then anything that can do HTTP requests can use it instead of being tied closely to the .NET specification.

murti

Thank you for all your suggestions!