Andrew, I was able to run your code past the issue you are reporting, therefore you either have a configuration or a dependency issue. Have you modified or removed axis2.xml? How are you invoking the tests (see documentation on how Axis2 finds axis2.xml)?
There was another report of this error that suggested a missing dependency that gets somehow obscured, pls see here: http://www.mail-archive.com/[email protected]/msg23511.html Incidentally, the code eventually does throw a fault, but that seems to be SOAPAction related, issue for another time. BTW, do you really need the "?WSDL" in your endpoint? Thanks' On 2/19/07, maskkkk <[EMAIL PROTECTED]> wrote:
I tried removing the setUseSeparateListener(false); That didn't really make a difference...*shrugs* I get the same error. Thank you, Andrew J. Leer Michele Mazzucco-2 wrote: > > > Andrew, > > there's no need to set the transport out. What you did should be enough. > Just in case, try to remove the options.setUseSeparateListener(false) > call - it's set to false by default. > > Michele > > > On 19 Feb 2007, at 19:55, maskkkk wrote: > >> >> Now I understand that I've already set the "in" transport >> protocol. But I >> really do not know how to set the "out" transport protocol or why I >> have to >> do it. The client example in the Axis2 documentation >> ( http://ws.apache.org/axis2/1_1_1/quickstartguide.html) does not >> require >> this: > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Transport-out-has-not-been-set.-tf3254864.html#a9053257 Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
