DO NOT REPLY [Bug 7557] - when using simpleType, wsdd type mapping is not interpreted correctly

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

DO NOT REPLY [Bug 7560] New: - Sample: EchoAttachments File comparison aggressively suboptimal

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

DO NOT REPLY [Bug 7557] New: - when using simpleType, wsdd type mapping is not interpreted correctly

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

DO NOT REPLY [Bug 7311] - WSDL2Java generates wrong code

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

DO NOT REPLY [Bug 7311] - WSDL2Java generates wrong code

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

DO NOT REPLY [Bug 7536] - Incorrect session timeout logic

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

cvs commit: xml-axis/java/test/session TestSimpleSession.java

gdaniels02/03/27 19:15:18 Modified:java/src/org/apache/axis/handlers SimpleSessionHandler.java java/test/session TestSimpleSession.java Log: Fix serious bug in session timeouts. Reported by [EMAIL PROTECTED] (Ken Weiner) - thanks! Revision ChangesPath

RE: Compile error on generated client stubs

We could, I suppose, map char/Character to xsd:string, and then provide a conversion from String -> char/Character which verified that there was only a single character --Glen > -Original Message- > From: David L. Cole [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, March 26, 2002 6:04

RE: Discovered some problems with the meta data.

The metadata is definitely intended to support both. I think the right thing to do WRT the QNames is to always keep the schema QNames in the metadata, and then qualify the elements or not depending on the encodingStyle. That is, I believe, what we do now, but the edge cases are a little uncle

RE: .Net-Axis sessions?

Hi Oliver! Do you know how .NET does sessions? Axis has two approaches - one with HTTP cookies, and another with SOAP headers. .Net certainly wouldn't support the SOAP header version out of the box, and I doubt that the cookies we use would match the ones they use (if they do). I just sent

cvs commit: xml-axis/java/test/wsdl/multibinding VerifyFilesTestCase.java

gdaniels02/03/27 14:58:18 Modified:java/src/org/apache/axis/wsdl/toJava Emitter.java java/test/wsdl Wsdl2javaAntTask.java java/test/wsdl/clash VerifyFilesTestCase.java java/test/wsdl/multibinding VerifyFilesTestCase.java Log: Throw the bi

.Net-Axis sessions?

Hi all, Has anybody managed to get a .Net client talk to an Axis service, using a session context? I've got an Axis (beta1) web service talking successfully with both an Axis and a .Net (beta2, C#) client. I've also added session management on the server side: - MessageContext.getCurrentContex

DO NOT REPLY [Bug 7536] New: - Incorrect session timeout logic

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

DO NOT REPLY [Bug 7311] - WSDL2Java generates wrong code

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

cvs commit: xml-axis/java/src/org/apache/axis/encoding TypeMappingRegistryImpl.java

butek 02/03/27 12:24:06 Modified:java TODO.txt java/src/javax/xml/rpc JAXRPCException.java ParameterMode.java ServiceException.java java/src/javax/xml/rpc/encoding TypeMapping.java TypeMappingRegistry.ja

RE: prefix mapping resolution bug.

The problem here was that the DeserializationContextImpl was using the current element's mappings, and only checking its local NSStack if there was no current element. During the creation of a new element, there is an attempt to get the type qname, which needs to be able to turn strings like

cvs commit: xml-axis/java/src/org/apache/axis/encoding DeserializationContextImpl.java

gdaniels02/03/27 12:16:25 Modified:java/src/org/apache/axis/client Call.java java/src/org/apache/axis/encoding DeserializationContextImpl.java Log: Two small bugs. * Make sure to check the in-scope namespace mappings *before* asking t

Re: Best working (nightly) build?

Any nightly build that contains all of the following files is a successful build and passes all of our tests. If only some of these files exist (just the src files, for example), then the build did not complete and there's no runtime distribution that you can use. The last good nightly build is

Re: Changing JAX-RPC interfaces - philosophical question

I got 4 votes for #1 and none for #2. So I'll forgo any deprecations for now. It certainly makes MY life easier! (but be prepared to get a few user complaints) Russell Butek [EMAIL PROTECTED] Russell Butek/Austin/IBM@IBMUS on 03/27/2002 07:56:13 AM Please respond to [EMAIL PROTECTED] To:

Best working (nightly) build?

If I wanted to embed Axis into my program and make it available to the public, which nightly build would you recommend to use? Or should I just stick with Beta 1 (March 19th version) ? Thanks for your help. Cheers, Frederic

cvs commit: xml-axis/java/src/org/apache/axis/encoding SerializationContextImpl.java

gdaniels02/03/27 11:27:47 Modified:java/src/org/apache/axis/client Call.java java/src/org/apache/axis/deployment/wsdd WSDDService.java java/src/org/apache/axis/encoding SerializationContextImpl.java Log: Don't send xsi:types/mult

cvs commit: xml-axis/java/src/javax/xml/rpc FaultException.java

butek 02/03/27 10:57:22 Removed: java/src/javax/xml/rpc FaultException.java Log: FaultException is really old. No one should have been using it for months, so it's gone.

RE: Changing JAX-RPC interfaces - philosophical question

Title: RE: Changing JAX-RPC interfaces - philosophical question Ya, mon.  +1 to taking the hit now. -Original Message-From: Volkmann, Mark [mailto:[EMAIL PROTECTED]]Sent: Wednesday, March 27, 2002 9:31 AMTo: '[EMAIL PROTECTED]'Subject: RE: Changing JAX-RPC interfaces - philo

cvs commit: xml-axis/java/test/wsdl/getPort GetPortTestCase.java

butek 02/03/27 10:36:48 Modified:java TODO.txt java/src/javax/xml/rpc JAXRPCException.java ServiceException.java java/test/wsdl/getPort GetPortTestCase.java Log: ServiceException/JAXRPCException.getCause changed to getLin

Re: Changing JAX-RPC interfaces - philosophical question

+1 #1, If we weren't beta I'd go with #2. <:-) I guess insisting people who write and change specs support thousands of lines of code based on their spec is not an option :-)/> Rick Rineholt "The truth is out there... All you need is a better search engine!" [EMAIL PROTECTED] Russell Butek

cvs commit: xml-axis/java/test/utils TestJavaUtils.java

gdaniels02/03/27 10:29:08 Modified:java/src/org/apache/axis/utils JavaUtils.java java/test/utils TestJavaUtils.java Log: Fix xmlToJavaName() to correctly deal with cases where punctuation (i.e. "_") starts an identifier that has multiple capital letters. "_OID" sho

cvs commit: xml-axis/java/src/org/apache/axis/client ServiceFactory.java

butek 02/03/27 10:17:43 Modified:java TODO.txt java/src/javax/xml/rpc ServiceFactory.java java/src/org/apache/axis/client ServiceFactory.java Log: I've updated javax.xml.rpc.ServiceFactory to JAX-RPC 0.8 and changed org.apache.axis.client.Servic

Re: Changing JAX-RPC interfaces - philosophical question

#1 - Pull the band-aid off quickly! :-) Russell Butek/Austin/IBM@IBMUS on 03/27/2002 08:56:13 AM Please respond to [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Changing JAX-RPC interfaces - philosophical question There are some changes in the JAX-RPC spec that will affect users

cvs commit: xml-axis/java/test/outparams TestOutParams.java

butek 02/03/27 08:46:57 Modified:java TODO.txt java/docs user-guide.html java/samples/attachments EchoAttachment.java java/samples/bidbuy TestClient.java v3.java java/samples/echo EchoService.java

Axis server generates invalid WSDL

Hi.   I deployed and ran the attachment example included in the beta-1 release without problems.  When I tried to access the WSDL using the URL http://localhost:8080/axis/servlet/AxisServlet/urn:EchoAttachmentsService?wsdl , I get an invalid WSDL file (attached in this message).  It looks to

Re: Collection Ser/Des

How did you get a stub with a return of java.util.Collection. I don't see how WSDL2Java could produce this kind of stub. Rich Scheuerle XML & Web Services Development 512-838-5115 (IBM TL 678-5115)

[GUMP] Build timed out - Axis

This email is autogenerated from the output from: Buildfile: build.xml setenv: [mkdir] Created dir: /home/rubys/jakarta/x

RE: Changing JAX-RPC interfaces - philosophical question

Title: RE: Changing JAX-RPC interfaces - philosophical question I don't think there is too much suffering involved in correcting constant references. I'm not an Axis developer, I'm an Axis user. I'd prefer to get things right during the beta process and not leave incorrect remnants behind when

Changing JAX-RPC interfaces - philosophical question

There are some changes in the JAX-RPC spec that will affect users. For example, javax.xml.rpc.ParameterMode.PARAM_MODE_IN has changed to javax.xml.rpc.ParameterMode.IN. We can do one of two things here: 1. Make the change and let users suffer (we ARE in beta, after all) 2. Provide both and de

cvs commit: xml-axis/java/src/org/apache/axis/client Stub.java

butek 02/03/27 05:35:56 Modified:java TODO.txt java/src/javax/xml/rpc Stub.java java/src/org/apache/axis/client Stub.java Log: I brought the Stub interface/implementation up to JAX-RPC 0.8 snuff, which meant simply moving the standard property c

[PATCH] Undeploying services

Undeployment doesn't fully work - there's a lingering namespace mapping that's set up in WSDDService.deployToRegistry() that isn't being removed. See a proposed fix below (done against the beta, sorry). +Melissa WSDDDeployment.java (no change since beta) WSDDDeployment.patch Description: B