Axis is NOT useless! Send us a stacktrace...
On Wed, Jun 17, 2009 at 4:42 PM, NathanDM <[email protected]> wrote: > > I am consistently getting this message when trying to call a .Net server > endpoint from various generated clients. I've generated both jaxws bound > clients and adb clients. I've gotten them to find the right url and port. > But I keep getting: > > "The input stream for an incoming message is null." > > It is so consistent that I must have something subtle wrong in my setup - > or > otherwise axis2 must be pretty useless. All the jars from Axis2 lib > directory are on the classpath. > > The same error happens if I have a JAXWS server generated from a WSDL and a > client, generated from that same wsdl, trying to call that server. > > Any ideas? > > I'm really stuck, and need ideas for something to use besides axis2 if > there > are no ideas. > > > > > -- > View this message in context: > http://www.nabble.com/The-input-stream-for-an-incoming-message-is-null-tp24067861p24067861.html > Sent from the Axis - User mailing list archive at Nabble.com. > >
