Any (good) reason why wsdl2java error reporting continues to be so, er,
stone-age? For example:
Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: Element QName is null for
Dear Axis developers, please can you wake up and realize that the whole world
wants simpler access to get/set HTTP headers (and cookies in particular).
Please forget your low-level development mindset for a moment and appreciate
that the absence of this kind of thing is crippling a lot of your
= rsp.getMimeHeaders();
String [] cookies = mhd.getHeader(set-cookie);
if (cookies != null)
{
// parse value of JSESSIONID from cookies[0]
}
service.dosomethingelse();
service.logout();
jarmod wrote:
I've read about 14 million internet posts (OK, it was just 13 million) on
the topic of how an Axis (1.4
I've read about 14 million internet posts (OK, it was just 13 million) on the
topic of how an Axis (1.4 in this case) client might retrieve cookies and,
quite surprisingly, I have yet to find a solution that actually works.
My Axis client uses the highest-level abstraction so looks something
