Re: Mozilla and automatic ?wsdl generation with Axis 1.0

I have noticed that Mozilla displays the XML usefully if there is an HTTP header saying the media type is "text/plain". And IE does OK in that situation, as long as the content begins with an XML declaration (as is already the case for the WSDL returned by Axis). What do you think of making A

Re: Class loader madness and useless error reporting

Matthias, you asked how you can do the ClassLoader printing I suggested. It depends on who "you" are. Axis users can't do it; my suggestion is aimed at Axis implementors. I'm suggesting that Axis (and Tomcat) code should be alert for class-loading exceptions&errors and do us all the favor of

Re: Class loader madness and useless error reporting

For exceptions like these, wouldn't it help if the contents of the ClassLoader & ancestors were printed out? Try it: you'll find they're all URLClassLoaders, and you can query them for the URLs they contain. Mike

"wsdl2java --testCase" scope

(1) I don't see the --testCase option documented in the Axis User Manual (in Axis 1.0). Is it documented anywhere (and if so, where)? (2) Is --testCase supposed to work for all inputs? That is, cover complex types, schema import, document/literal/rpc, etc? (3) Currently --testCase produces co

Re: Stubs moving to single-threadedness

I'm not going to cast an official vote, since I'm not an official contributor (just lurking here), but I'l de-lurk to point out that I do not consider the proposal to be intuitive. In general, "object" != "thread". From a user's point of view, the constraint that "each stub should only be us

Re: Having more trouble with Axis RC1&2: "Problem with servlet engineconfig file" & JWS doesn't work

Steve, are you referring to bug 12372? You have marked that "RESOLVED FIXED"; perhaps I don't understand exactly what that means. Thanks for the clue. "GET Foo.jws?wsdl" is working for me, so yes I see the problem is confined to "GET Foo.jws". Is the error message about "Problem with servlet

Having more trouble with Axis RC1&2: "Problem with servlet engine configfile" & JWS doesn't work

Now that I've got RC2 passing validation, the next test fails. Here's my Tomcat 4.0.4 typescript: Starting service Tomcat-Standalone Apache Tomcat/4.0.4 Starting service Tomcat-Apache Apache Tomcat/4.0.4 - Problem with servlet engine config file: /WEB-INF/server-config.wsdd That last line come

Re: Validation fails due to NoClassDefFoundError: org/w3c/dom/DOMErrorHandler, eventhough xercesImpl.jar is in webapps/axis-rc1/WEB-INF/lib

1. As was shown in my typescript, I am using IBM's "JDK" 1.3.1. 2. When I removes Xerces --- specifically, xercesImpl.jar and xmlParserAPIs.jar --- from my Axis RC2 WEB-INF/lib/, the validation succeeds! Note that Tomcat 4.0.4 ships with a "xerces.jar" in its common/lib/. I recommend a fix

Problem with Axis RC1&2: Validation fails due to NoClassDefFoundError: org/w3c/dom/DOMErrorHandler, eventhough xercesImpl.jar is in webapps/axis-rc1/WEB-INF/lib

See and (why do those messages have no thread/list navigation links?).

Problem with Axis RC1&2: Validation fails due to NoClassDefFoundError: org/w3c/dom/DOMErrorHandler, eventhough xercesImpl.jar is in webapps/axis-rc1/WEB-INF/lib

See and (why do those messages have no thread/list navigation links?).