DO NOT REPLY [Bug 8598] - Axis is generating wrong WSDL file

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: TestElement.java?

Contact the cvs admin - its a lower-vs-upper case naming problem. The file should just be removed from the cvs tree. -Dug Sam Ruby/Raleigh/IBM@IBMUS on 05/02/2002 06:23:43 PM Please respond to [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:TestElement.java? Is anybody else seeing

TestElement.java?

Is anybody else seeing this? What should be done? cvs server: Updating xml-axis/java/samples/encoding cvs server: nothing known about xml-axis/java/s

RE: soap:header new implementation

Thanks Glen for your feedback. Read my comments inline, any one interested in having higher level support for soap header should do so too! ;-) Sylvain. -Original Message- From: Glen Daniels [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 02, 2002 4:28 PM To: '[EMAIL PROTECTED]' Subject

Flash SOAP support for JBoss/JBoss.net

Good news! We have the beginnings of support for Flash clients directly invoking SOAP services on a JBoss server. The code has been checked into the CVS repository on Sourceforge. All that is needed is to uncomment/comment a section in two different files: install-axis.xml and axis-config.x

beta2, WEB-INF/jwsClasses/

After the fix for that little 'jws' .class files are visible bug I reported, the classes were meant to go into the dir jwsClasses =under WEB-INF. But I see from myserver index page a listing of a directory WEB-INFjwsClasses/ ...I wonder if this is intentional or a missing / in the appropriate sett

cvs commit: xml-axis/java/test/functional FunctionalTests.java

rineholt02/05/02 14:03:13 Modified:java build.xml java/test/functional FunctionalTests.java Log: Make mail.jar and activiation.jar once again optional. ;-) Revision ChangesPath 1.132 +2 -1 xml-axis/java/build.xml Index: build.xml ==

Interop with MS .NET

Hi, I am currently evaluating Axis. It is a great app and a huge improvement over Apache SOAP. I tried to publish a web service with two input parameters. Both of them are user defined data type. Invoking this web service failed from .NET with message "No deserializer for null". I tried to call a

RE: Flash Remoting was: Flash SOAP

Hi Frederick! Flash Remoting does XML/SOAP by utilizing the server as a proxy for Web Services requests (we're working on making this more clear on the web pages). It's super cool, you should check it out. :) --Glen > -Original Message- > From: Frederick N. Brier [mailto:[EMAIL PROT

RE: SOAPHeader - determining QName issue.

Hi Sylvain! > I am running into a situation where my server returns me a > SOAPHeader node > like: > http://developer.cognos.com/schemas/bibus/2/";> > which seems valid to me but the MessageElement constructor ends with > typeQName=null which prevents me from retreiving the object. That seems

RE: soap:header new implementation

Hi Sylvain! First off, I'm psyched that you're moving in this direction, because we clearly need to support headers in some way.The following is my take on things, both in terms of where I'd like to be able to go wrt extensions in general and also how to deal with the particular "fine-gra

cvs commit: xml-axis/java/src/org/apache/axis/deployment/wsdd WSDDService.java

gdaniels02/05/02 13:23:45 Modified:java/src/org/apache/axis/deployment/wsdd WSDDService.java Log: Add accessors for typemappings Vector (mostly for tool support). Revision ChangesPath 1.62 +8 -0 xml-axis/java/src/org/apache/axis/deployment/wsdd/WSDDService.jav

RE: [PATCH] WSDL2Java - BindingStub not registering all types.

We have to make sure that types defined for the purpose of header will allways be mapped with or without the --all (which is probably not the case now) Sylvain. -Original Message- From: Russell Butek [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 01, 2002 4:32 PM To: [EMAIL PROTECTED]

soap:header new implementation

Read on - design issue at the end. I have modified the original soap:header support implementation to allow full flexibility around the header management. The way I have achieve this is by allowing the user to specify the header object lifecycle. The current three lifecycles are: HeaderLifeCy

couple of questions on Axis

Hi all, I have few questions regarding Axis flexibility to use it with JAXP & JAXB. 1. How can I specify the list of features/properties to be considered when parsing the incoming SOAP message? Currently SAXParser is created by Util class org.apache.axis.utils.XMLUtils and the features/

Re: Flash Remoting was: Flash SOAP

One excerpt from the first link is "Access SOAP-based web services directly from Macromedia Flash using built-in SOAP Proxy Adaptor." So, it seems like Flash can be a SOAP client. Scott - Original Message - From: "Frederick N. Brier" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[E

[GUMP] Build timed out - Axis

This email is autogenerated from the output from: Build results exceed maximum length. Please see URL above for details. Last

RE: AxisFault

Hi Richard! Here's my take. 1) Faults across the wire should use the element to indicate what went wrong, and the element to contain specific data about the fault. In other words, faultcode should map to a particular exception. 2) Any fault inside Axis which may need to be sent across the

Re: Flash Remoting was: Flash SOAP

Please correct me if I am wrong. This Flash Remoting extension does not appear use XML or SOAP. Is this a Coldfusion MX specific solution? Frederick N. Brier Sr. Software Engineer Multideck Corporation At 01:13 AM 4/30/2002, Peter Farland wrote: >For dynamic/rpc flash development, take a look