Detailed error messages for ?WSDL

Does anyone know how to view detailed error messages (i.e. - stack traces) for ?WSDL ? I am trying to use ?WSDL and I get a message that there was a java.lang.reflect.InvocationTargetException, but I don't get a stack trace so I can't figure out what's going wrong. Thanks, Matt

Re: Possible bug: empty namespaces for attributes using doc-literal

Thank you for your help Junaid, but I still think that we have found a bug. You're right, specifying elementFormDefault="qualified" gives me the output I want. However, I think the SOAP generated when elementFormDefault="unqualified" (or is unspecified) is wrong. I think that specifying xmlns=""

Re: Where is Axis in BugZilla?

PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, March 12, 2004 3:54 PM Subject: Re: Where is Axis in BugZilla? > Matthew Sgarlata wrote: > > I want to enter a bug for Axis > > [...] > > http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10460 > > Regards, > Tomek > > > Matt > >

Where is Axis in BugZilla?

I want to enter a bug for Axis (for WSDL2Java... this is a separate issue from my previous email), but when I go to BugZilla I don't see Axis in the list of projects. Am I doing something wrong? The URL below is correct for Axis' BugZilla, right? http://issues.apache.org/bugzilla/enter_bug.cgi

Possible bug: empty namespaces for attributes using doc-literal

I may have found a bug with Axis' treatment of doc-literal encoding in Axis 1.2 alpha. My basic steps were: 1) Create a WSDL file with complexTypes defined using XML Schema 2) Run wsdl2java to generate my WSDD, skeletons, etc. The classes generated by WSDL2Java that correspond to my complexTypes

SOAPMonitor cannot connect to server

I finally got the SOAPMonitor up-and-running today, but the applet complains, "The SOAP Monitor is unable to communicate with the server." I am guessing this means I specified the wrong SOAPMonitorPort in web.xml. What port should I use? I tried the default 5001 and the port on which my web serve

Re: wsdl2java mapping primitives to objects

Thanks Matt, Unfortunately, the WSDL does specify that the element is nillable, but it is still being mapped to an int.  In the wsdl the element looks like:  Bill Bill Heitzeg 1-734-995-9131  -Original Message----- From:   Matthew Sgarlata [mailto:[EMAIL PROT

Re: wsdl2java mapping primitives to objects

I believe that if the WSDL specifies that the field is nillable, then xsd:int is mapped to Integer instead of int. Can you change your WSDL? Matt - Original Message - From: "Heitzeg, Bill" <[EMAIL PROTECTED]> To: "Axis-User (E-mail)" <[EMAIL PROTECTED]> Sent: Tuesday, February 17, 2004 1

Re: [repost] Java2WSDL serialization problem

Thanks Tony!   I tried adding the noOp method, and using the -e option, but the WSDL still doesn't look right.  Here is the command I used:  java org.apache.axis.wsdl.Java2WSDL    -o document.wsdl    -lhttp://localhost/jrocservice/services/DocumentService    -ecom.bah.jroc.vo.DocumentVo   

[repost] Java2WSDL serialization problem

eNamespace com.bah.jroc.document.IDocumentService Thanks! Matt Matthew Sgarlata Senior Consultant Booz Allen Hamilton Inc. Work: 703-377-0871

Java2WSDL difficulty with BeanSerializer

Hello, I am having some trouble using the Java2WSDL emitter with Axis 1.2 alpha, and I am hoping someone could offer me some help. I am new to web services, and to Apache Axis as well. I deployed my web service using the AdminClient, and looked at its WSDL using ?WSDL. I can see that the BeanSe