Re: .NET XML Web Service interop
- From: Kevin Burton <KevinBurton@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 6 Nov 2006 06:35:01 -0800
This was helpful. Thank you for your interest.
In building one of the samples (security) the message is "SUCCESSFUL" but I
get a stack trace. Was it really successful?
Thanks again.
Kevin
C:\axis2\samples\security>ant
Buildfile: build.xml
securitySample:
[java] log4j:WARN No appenders could be found for logger
(org.apache.axiom.
om.impl.builder.StAXOMBuilder).
[java] log4j:WARN Please initialize the log4j system properly.
[java] org.apache.axis2.AxisFault: Trying to engage a module which is
not a
vailable : addressing
[java] at
org.apache.axis2.engine.AxisConfiguration.engageModule(AxisCo
nfiguration.java:291)
[java] at
org.apache.axis2.deployment.DeploymentEngine.engageModules(De
ploymentEngine.java:743)
[java] at
org.apache.axis2.deployment.FileSystemConfigurator.engageGlob
alModules(FileSystemConfigurator.java:128)
[java] at
org.apache.axis2.context.ConfigurationContextFactory.createCo
nfigurationContext(ConfigurationContextFactory.java:41)
[java] at
org.apache.axis2.context.ConfigurationContextFactory.createCo
nfigurationContextFromFileSystem(ConfigurationContextFactory.java:90)
[java] at sample.security.Client.main(Client.java:48)
BUILD SUCCESSFUL
Total time: 1 second
"Scott Seely" wrote:
For WS-Security, you may find a lot of good resources at.
http://ws.apache.org/axis2/ as well.
"RYoung" wrote:
Hey Kevin,
I recently demo'ed a Java client to .NET web service scenario, where
messages in the IODEF format
(http://xml.coverpages.org/draft-ietf-inch-iodef-10.txt) were exchanged.
C# ASP.NET Web service, Java desktop client built using Borland JBuilder.
I'm not a Java programmer by far, but consuming the service was relatively
an easy matter.
I didn't do any security but plan to in the coming week. I'm gonna refer to
msdn.microsoft.com -> Web Services Developer Center -> Interopability
section. There are articles there on using WSE3 to provide security in an
disparate platform scenario.
Hopefully that helps you with tasks 1, 2, and 3.
There is also a tool named WSDL2Java which I've seen in google searches but
haven't tried out. As I mentioned, Borland JBuilder worked straight from the
installation for me. The Web service WSDL was defined completely in XML Spy
and I used wsdl.exe to generate the service interface code (thanks to Nick
Locke for posting his WSDL for me to learn that technique from).
Ron
Ron
"Kevin Burton" <KevinBurton@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:63A0C0EA-DA84-43D2-86A8-46A4813B66AB@xxxxxxxxxxxxxxxx
I found an article on calling a .NET web service from Java but it seemed to
rely on GLUE and I was unable to find out how to download that software.
There seems to be alot written on the Sun site, and I have downloaded the
SDK
and the web services SDK but I am not sure where to proceed from there.
Basically I want to show how to do these simple tasks:
1) Call a .NET web service from a Java client
2) Build Java proxies based on a WSDL.
3) Assign a Username token to a Java proxy and call the web service using
WS-Security
4) Use MTOM to send a potentially large file to a web service again using
a
Java client.
As a bonus I would like to get and associate a Kerberos ticket with a web
service call but it doesn't look like Sun supports Kerberos tokens.
Any help or pointers in getting these to work would be greatly
appreciated.
It is fairly straightforward to implement all of the above when I have
control over both ends (in other words .NET to .NET) but my experience
with
Java limits me at this point.
Thank you.
Kevin
- References:
- Re: .NET XML Web Service interop
- From: RYoung
- Re: .NET XML Web Service interop
- From: Scott Seely
- Re: .NET XML Web Service interop
- Prev by Date: Re: .NET XML Web Service interop
- Next by Date: Best Practices
- Previous by thread: Re: .NET XML Web Service interop
- Next by thread: Re: .NET XML Web Service interop
- Index(es):
Relevant Pages
|
