axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Walker, Jeff" <>
Subject RE: Axis 1.4 and .NET interop
Date Tue, 16 Oct 2007 13:58:00 GMT
My client is a .NET application. We use Doc/Literal-wrapped. My web
service is hosted on WebSphere 6.1. (It uses IBM's home-grown
implementation of the JAX-RPC standard. We are not using Axis on this
project, but previous projects I was on used Axis 1.3 and had .NET
clients. There were no issues once both parties agreed to the interface
layout and schema). No java objects of any kind are transferred. We
wrote a lot of XML Schema to represent the data going back and forth.
As long as you keep to using doc/literal-wrapped, and use schema to
represent all data passed, you should have no issues with .NET.
Read the IBM web page I put in the link below, It's a very good article
and spells it out nicely.

From: M N [] 
Sent: Tuesday, October 16, 2007 9:38 AM
Subject: RE: Axis 1.4 and .NET interop

	I am using WRAPPED/LITERAL style in WSDL. My question was about
java specific objects. Have you been successful in integrating .NET
client with axis 1.4 WS using the wrapped/literal approach ?

	"Walker, Jeff" <> wrote:

		Anne means Document Literal Wrapped style.
		Go here to see a good definition of the 4 major styles:
		The style we are advocating means you need to write XML
Schema and place it into your wsdl file. Then you run your wsdl file
through WSDL2Java to generate a bunch of serializer and deserializer
classes. The command is something like:
		%>java org.apache.axis.wsdl.WSDL2Java --server-side
--skeletonDeploy true <web_service_name>.wsdl


			From: M N [] 
			Sent: Tuesday, October 16, 2007 8:56 AM
			Subject: Re: Axis 1.4 and .NET interop
			Thanks Anne.
			when you say Java specific types I assume you
talking about something like Collections,arraylists etc. So far I dont
have anything like that.

			Anne Thomas Manes <> wrote:

				Wrapped style is the way to go. But you
still might encounter problems
				if your service is exposing
Java-specific types.
				On 10/16/07, M N wrote:
				> We have been using AXIS 1.1 ( yeah I
know its old) for past few years with
				> Jboss and everythings looks fine.We
have removed the jbossws.sar directory
				> completely.
				> Anyway so we have this new requirement
where we have to provide webservices
				> to a .NET client. No matter what we
provide .NET client keeps getting
				> exceptions. We found yesterday that
.NET does not support RPC transport from
				> java webservices. So we decided to use
				> created using ANT JAVA2WSDL tool) .
But then even when I test the WS from
				> Java side it keeps giving me NOT A
ARGUMENT(or something like that) error. I
				> read later on that AXIS 1.1 doesnt
support the DOCUMENT/LITERAL style well.
				> So we decided to upgrade to 1.4.
				> I still kept getting the NOT A ERROR
except when I
				> mention in ANT JAVA2WSDL utility that
I need WRAPPED/LITERAL style. Any
				> other style doesnt seem to work. So
now with WRAPPED/LITERAL style my Java
				> client stubs can successfully work
with Java WSs. We will be testing it with
				> .NET tomorrow. I am wondering if it
will work and there wont be any
				> exceptions.
				> Thanks
				> ________________________________
				> Moody friends. Drama queens. Your
life? Nope! - their life, your story.
				> Play Sims Stories at Yahoo! Games.
				To unsubscribe, e-mail:
				For additional commands, e-mail:


			Pinpoint customers
are looking for what you sell. 


	Looking for a deal? Find great prices on flights and hotels
>  with Yahoo! FareChase.

View raw message