Re: [VOTE] merge terra service test case change into 1.0

+1 Glyn Russell

Re: [VOTE] bug 13149/client needs servlet.jar merged into 1.0

+0 Glyn Doug

Re: [VOTE] Bug 13167 merged into 1.0

-0 as we will run the danger of delaying delivery of 1.0 unless we are pretty ruthless in locking it down. If we didn't include this one, I'd vote for it being rolled into a bugfix release (1.0.1) say a month after shipment of 1.0. Doug: is that the last of the current defects you would like to

Re: [wsif] Bug 13038 - WSIF's dynamic port/operation creation confusionabout message names

I'm inclined to go with the lenient code I suggested below which allows the binding input/output names to not match if there's only one binding operation matching the portType operation name. The WSDL spec seems a bit ambiguous on whether the binding operation input/output names must match, but

Re: [VOTE] Bug 13167 merged into 1.0

Glyn wrote: > Doug: is that the last of the current defects you would like to include? Don't know - we're still in the process of upgrading (but it is winding down). -Dug "Glyn Normington" <[EMAIL PROTECTED]> on 10/02/2002 04:12:18 AM Please respond to [EMAIL PROTECTED] To:[EMAIL PROT

[GUMP] Build Failure - Axis

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

Re: Whatever happened to Castor support?

Doug, Anything not in bugzilla is likely to "slip through the cracks"Please add a enhancement request at http://nagoya.apache.org/bugzilla. You can also use "create an attachment" on the bugzilla page to upload zip files etc. Thanks, dims --- Douglas Bitting <[EMAIL PROTECTED]> wrote: > A

Re: TCPMon Audio Feedback Mod ("RPC-Synth") RFC

Wow - that was quick! Might not get a chance to look at it for a little bit - perhaps someone else on the team might be able to scan it and if it looks good then commit it. Sounds really really promising! Thanks Dan! -Dug "Dan Kamins" <[EMAIL PROTECTED]> on 10/01/2002 09:18:11 PM To:

Re: [wsif] Bug 13038 - WSIF's dynamic port/operation creation confusion about message names

Sounds good, particularly if the code gets comments suggesting the appropriate change when WSDL4J supports the 2.4.5 naming algorithm. Jeff - Original Message - From: "Anthony Elder" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 02, 2002 12:54 AM Subject: Re: [wsif]

cvs commit: xml-axis/java/src/org/apache/axis/message SOAPFaultDetailsBuilder.java

dims2002/10/02 05:09:58 Added: java/src/org/apache/axis/message Tag: interop4 SOAPFaultDetailsBuilder.java Log: This file was accidently checked into HEAD instead of interop4 Revision ChangesPath No revision No

Re: [wsif] Bug 13038 - WSIF's dynamic port/operation creation confusion about message names

I guess it would be good if WSDL4J had a utility function to implement the default name algorithm. However, I don't think it should set the name to the default value if a name wasn't there. Sanjiva. - Original Message - From: "Jeff Greif" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent:

cvs commit: xml-axis/java/src/org/apache/axis/message SOAPFaultDetailsBuilder.java

dims2002/10/02 05:13:44 Removed: java/src/org/apache/axis/message SOAPFaultDetailsBuilder.java Log: This file was accidently checked into HEAD instead of interop4

What fixes are now in R 1.0?

I've asked for some fixes voted into R 1.0 without any -1's and I've seen others do the same, but not sure except doing diffs and being familiar with all the changes to determine what has been accepted in R1.0. Is there another way and I just missed it? (except the diff solution :-) Rick Rineh

cvs commit: xml-axis/java/docs reference.html

butek 2002/10/02 06:06:35 Modified:java/docs reference.html Log: The WSDL2Java and Java2WSDL sections now match the tools. Revision ChangesPath 1.12 +77 -61xml-axis/java/docs/reference.html Index: reference.html =

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

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

Rich, Make sure you have o.a.a.client.Service.java version 1.76.2.1. This has the definition of the FaultInfo class (inside the Service class). -- Tom Jordahl Macromedia Server Development -Original Message- From: R J Scheuerle Jr [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 01

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

Huh. Any CVS type out there know how to put this file only on the interop4 branch? -- Tom Jordahl Macromedia Server Development -Original Message- From: R J Scheuerle Jr [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 01, 2002 7:06 PM To: [EMAIL PROTECTED] Subject: Re: cvs commit: xm

RE: cvs commit: xml-axis/java/src/org/apache/axis/message SOAPFaultDetailsBuilder.java

Thanks Dims! You da (CVS) man! -- Tom Jordahl Macromedia Server Development -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 8:14 AM To: [EMAIL PROTECTED] Subject: cvs commit: xml-axis/java/src/org/apache/axis/message SOAPFaultDet

RE: What fixes are now in R 1.0?

No fixes have been merged in to 1.0 since rc2 was built on Monday. Perhaps it would help if there was a summary of fixes that are in consideration? My take on it is that NO src/* fixes will be approved (automatic -1 from Sam) unless we have an overwhelming agreement on inclusion. My take on th

RE: TCPMon Audio Feedback Mod ("RPC-Synth") RFC

Dan, Nice stuff - I would be +1 for these changes to go in to CVS, AFTER 1.0 has shipped (figure a week or so). -- Tom Jordahl Macromedia Server Development -Original Message- From: Doug Davis [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 7:42 AM To: Dan Kamins Cc: [EM

cvs commit: xml-axis/java/test/wsdl/interop4 - New directory

gdaniels2002/10/02 07:15:43 xml-axis/java/test/wsdl/interop4 - New directory

RE: What fixes are now in R 1.0?

Tom, I don't remember us agreeing on " automatic -1, or the overwhelming agreement on inclusion". I would have -1 that plan. I think if someone has gone to the trouble of asking something to be put in and someone disagrees it deserves a REAL -1 reply AND a some reason why. The approach I wo

RE: What fixes are now in R 1.0?

Rick, See http://marc.theaimsgroup.com/?l=axis-dev&m=103339449319208&w=2 This plan was approved via Email and on the Conference call that followed it (which I believe you were a part of). We are in truckstopper mode: Would you run after the truck taking the CDs away to fix this bug? -- Tom

cvs commit: xml-axis/java/src/org/apache/axis/message SOAPFaultBuilder.java

tomj2002/10/02 07:53:56 Modified:java/src/org/apache/axis/message Tag: interop4 SOAPFaultBuilder.java Log: Lookup wrapper types and convert them to their base type when passing them in to the Exception constructor. Revision ChangesPath No

cvs commit: xml-axis/java/src/org/apache/axis/wsdl/toJava JavaStubWriter.java

tomj2002/10/02 08:14:56 Modified:java/src/org/apache/axis/message Tag: interop4 SOAPFaultDetailsBuilder.java java/src/org/apache/axis/wsdl/toJava Tag: interop4 JavaStubWriter.java Log: All tests in the simple-rpc-enc

DO NOT REPLY [Bug 13209] New: - SOAPBuilders "Round 4" Group I (WSDL/XSD testing) WSDL fails

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_b

RE: What fixes are now in R 1.0?

No Tom, that's not what that says nor does it say that we are going to just ignore what people have requested in. What I asked has also nothing todo with the "Truckstopper" mode criteria nor does that mean abandoning what we agreed on earlier namely committers requesting things put in and if som

cvs commit: xml-axis/java/src/org/apache/axis/handlers BasicHandler.java

rsitze 2002/10/02 08:27:12 Modified:java/src/org/apache/axis FaultableHandler.java java/src/org/apache/axis/handlers/soap SOAPService.java java/src/org/apache/axis/handlers BasicHandler.java Log: Issue being solved: WSDDService with 0 (zero) options:

Re: Whatever happened to Castor support?

- Original Message - From: "Douglas Bitting" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 01, 2002 11:49 PM Subject: Whatever happened to Castor support? > A while back, some files were posted to the list which enabled support Castor (de)serialization. Did the pow

RE: What fixes are now in R 1.0?

Rick, This was discussed in detail on the conference calls with Sam, the release manager, and a large number of committers. I believe you were on these calls. The time for raising objections to the plan is not after the plan has been agreed upon. :-( We are in closedown mode - very little to

cvs commit: xml-axis/java/test/wsdl/interop4/groupH - New directory

gdaniels2002/10/02 09:16:57 xml-axis/java/test/wsdl/interop4/groupH - New directory

cvs commit: xml-axis/java/test/wsdl/interop4/groupH/simpleRPCenc - New directory

gdaniels2002/10/02 09:17:02 xml-axis/java/test/wsdl/interop4/groupH/simpleRPCenc - New directory

cvs commit: xml-axis/java/test/wsdl/interop4/groupH/simpleRPCenc build.xml simple-rpc-encoded.wsdl

gdaniels2002/10/02 09:17:36 Added: java/test/wsdl/interop4/groupH/simpleRPCenc Tag: interop4 build.xml simple-rpc-encoded.wsdl Log: Getting ready to run this in an automated fashion... Revision ChangesPath No revision N

Re: Whatever happened to Castor support?

- Original Message - From: "Davanum Srinivas" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 02, 2002 9:01 AM Subject: Re: Whatever happened to Castor support? > Steve, > > Is it possible to hold off checking it in till friday...(for axis 1.0 release) > > Thanks, >

cvs commit: xml-axis/java/test/wsdl/interop4/groupH/simpleRPCenc SimpleRpcEncServiceTestCase.java build.xml

tomj2002/10/02 09:29:09 Modified:java/test/wsdl/interop4/groupH/simpleRPCenc Tag: interop4 build.xml Added: java/test/wsdl/interop4/groupH/simpleRPCenc Tag: interop4 SimpleRpcEncServiceTestCase.java Log: Add test case for t

Re: Whatever happened to Castor support?

Steve, Is it possible to hold off checking it in till friday...(for axis 1.0 release) Thanks, dims --- Steve Loughran <[EMAIL PROTECTED]> wrote: > > - Original Message - > From: "Douglas Bitting" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, October 01, 2002 11:49 PM >

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

- Original Message - From: "Mike Spreitzer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 02, 2002 6:11 AM Subject: Re: Having more trouble with Axis RC1&2: "Problem with servlet engine config file" & JWS doesn't work > Steve, are you referring to bug 12372? You

DO NOT REPLY [Bug 13214] New: - Nexted xs:import statements do not work 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_b

DO NOT REPLY [Bug 13215] New: - Axis does not seem to support xs:group

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_b

cvs commit: xml-axis/java/src/org/apache/axis/wsdl/gen Parser.java

gdaniels2002/10/02 10:18:54 Modified:java/src/org/apache/axis/wsdl/gen Tag: interop4 Parser.java Log: If a bindingEntry is undefined, don't use it! Revision ChangesPath No revision No revision 1.11.4.1 +1 -1 xml-a

Re: RE: What fixes are now in R 1.0?

>Rick, >This was discussed in detail on the conference calls with Sam, the release >manager, and a large number of committers. I believe you were on these calls. >The time for raising objections to the plan is not after the plan has been >agreed upon. :-( If you want to go in "truckstopper"

cvs commit: xml-axis/java/src/org/apache/axis/wsdl/gen Parser.java

gdaniels2002/10/02 10:24:03 Modified:java/src/org/apache/axis/wsdl/gen Parser.java Log: If a bindingEntry is undefined, don't use it! This prevents problems with SOAP1.2 (or any other unknown) bindings. Fixes bug http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13209

RE: RE: What fixes are now in R 1.0?

Rick wrote: >If you want to go in "truckstopper" mode and be more selective of fixes >and discuss that in a conference that's fine. If you decide we are going >to change the way things have worked and just ignore what other people >request accept for the select few, shouldn't have that been vote

VOTE : RE: cvs commit: xml-axis/java/src/org/apache/axis/wsdl/gen Parser.java

All - this is a serious bug, and I think it merits the "we'll look like dorks if it's not fixed" label. It changes nothing except that bindings which aren't explicitly referenced (i.e. SOAP 1.1) are ignored when generating code. This means that we won't mistakenly generate mismatched interfa

RE: Whatever happened to Castor support?

That's all I was looking for. I haven't yet decided if I'm going to use castor for our project, but it's one of the things I'm considering. It would be nice if these could make it into the CVS_HEAD (after 1.0 releases is fine w/ me) so that I could play around with it to explore the implicatio

cvs commit: xml-axis/java/test/wsdl/filegen AllOptionTestCase.java

gdaniels2002/10/02 10:48:03 Modified:java/test/wsdl/filegen AllOptionTestCase.java Log: If we don't understand it, we shouldn't generate it. Fix test to comply with new behavior. Revision ChangesPath 1.3 +0 -1 xml-axis/java/test/wsdl/filegen/AllOptionTestCa

Re: VOTE : RE: cvs commit: xml-axis/java/src/org/apache/axis/wsdl/gen Parser.java

-0. We only look like dorks NOW that we looked at some new WSDL. NOBODY complained to us about this in the past, so only folks who look at this new WSDL will think we're dorks (OK, so perhaps these are important people, that's why I didn't vote -1). This is not a regression. Russell Butek

RE: VOTE : RE: cvs commit: xml-axis/java/src/org/apache/axis/wsdl/gen Parser.java

It's not a "regression" in that we didn't test this before, true. However, it's a one-line change which means we won't generate uncompilable code in some circumstances with perfectly valid WSDLs out in the world. That's why I think it should go in. --Glen > -Original Message- > From

cvs commit: xml-axis/java/src/org/apache/axis/wsdl/symbolTable BindingEntry.java Parameter.java SymbolTable.java

butek 2002/10/02 11:21:30 Modified:java/src/org/apache/axis/wsdl/symbolTable BindingEntry.java Parameter.java SymbolTable.java Log: First cut at explicit header support. This just adds support to the symbol table. Revision ChangesPath 1.4

Re: cvs commit: xml-axis/java/src/org/apache/axis/wsdl/symbolTableBindingEntry.java Parameter.java SymbolTable.java

Dang! Sorry, folks. Looks like I don't know what I'm doing. I was trying to commit some header work into a branch, not the head. I COULD leave this stuff here in the head, it's only new symbol table stuff and until something uses the new symbol table info, our functionality won't change.

Re: What fixes are now in R 1.0?

All, Given that I introduced this notion of "truckstopper" mode, I think I should clarify what I meant by it a little better. - Its really much more effective if its part of a larger plan that includes things like "Feature freeze" and "code freeze". Its really intended for a period of time ~2 we

cvs commit: xml-axis/java/src/org/apache/axis/wsdl/symbolTable Parameter.java

butek 2002/10/02 12:28:06 Modified:java/src/org/apache/axis/wsdl/symbolTable Tag: explicitHeaderWork Parameter.java Log: Make sure I know what I'm doing. This SHOULD go into the explicitHeaderWork branch. Revision ChangesPath No

cvs commit: xml-axis/java/src/org/apache/axis/wsdl/toJava JavaStubWriter.java

butek 2002/10/02 12:32:49 Modified:java/src/org/apache/axis/client Tag: explicitHeaderWork Call.java java/src/org/apache/axis/description Tag: explicitHeaderWork OperationDesc.java ParameterDesc.java java/sr

cvs commit: xml-axis/java/src/org/apache/axis/wsdl/toJava JavaDeployWriter.java JavaSkelWriter.java

butek 2002/10/02 13:09:00 Modified:java/src/org/apache/axis/description Tag: explicitHeaderWork ParameterDesc.java java/src/org/apache/axis/wsdl/toJava Tag: explicitHeaderWork JavaDeployWriter.java JavaSkelWriter.java Lo

cvs commit: xml-axis/java/src/org/apache/axis/providers/java RPCProvider.java

scheu 2002/10/02 13:39:07 Modified:java/src/org/apache/axis/client Tag: explicitHeaderWork Call.java java/src/org/apache/axis/deployment/wsdd Tag: explicitHeaderWork WSDDConstants.java WSDDOperation

Re: What fixes are now in R 1.0?

- Original Message - From: "David Chappell" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 02, 2002 12:20 PM Subject: Re: What fixes are now in R 1.0? > - Its based on a premise that *any* change, no matter how small, has the > potential to break for more than what

cvs commit: xml-axis/java/src/org/apache/axis/wsdl/symbolTable SymbolTable.java

butek 2002/10/02 13:46:55 Modified:java/src/org/apache/axis/wsdl/symbolTable SymbolTable.java Log: Fix for http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13214. XML import processing was faulty. Thanks to Charles Savage ([EMAIL PROTECTED]) for the fix. Revision Ch

DO NOT REPLY [Bug 13214] - Nexted xs:import statements do not work 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_b

JMS Transport Patch

All, Attached is a minor patch to the JMS transport. It includes a first cut at a vendor-specific exception handling mechanism. This extension allows the JMS connector to fail-fast when it encounters vendor specific exceptions that cannot be recovered from. The old behavior was to retry for a

cvs commit: xml-axis/java/test/wsdl/interop4/groupi - New directory

dims2002/10/02 13:57:31 xml-axis/java/test/wsdl/interop4/groupi - New directory

cvs commit: xml-axis/java/test/wsdl/interop4/groupi build.xml client-config.wsdd round4XSD.wsdl Round4XSDTestTestCase.java

dims2002/10/02 14:05:20 Added: java/test/wsdl/interop4/groupi Tag: interop4 build.xml client-config.wsdd round4XSD.wsdl Round4XSDTestTestCase.java Log: SoapBuilders Round V GroupI testcase going against MSFT server (Has 2 failure

cvs commit: xml-axis/java/src/org/apache/axis/wsdl/symbolTable Utils.java

dims2002/10/02 14:43:42 Modified:java/test/wsdl/interop4/groupi Tag: interop4 Round4XSDTestTestCase.java java/src/org/apache/axis/wsdl/symbolTable Tag: interop4 Utils.java Log: Down to 1 failure for GroupIWe were

cvs commit: xml-axis/java/test/wsdl/interop4/groupi Round4XSDTestTestCase.java

dims2002/10/02 14:54:03 Modified:java/test/wsdl/interop4/groupi Tag: interop4 Round4XSDTestTestCase.java Log: Ok. We're kosher against the MSFT GroupI endpoint. Revision ChangesPath No revision No re

cvs commit: xml-axis/java/test/wsdl/interop4/groupi Round4XSDTestSoapImpl.java build.xml round4XSD.wsdl

dims2002/10/02 15:15:22 Modified:java/test/wsdl/interop4/groupi Tag: interop4 build.xml round4XSD.wsdl Added: java/test/wsdl/interop4/groupi Tag: interop4 Round4XSDTestSoapImpl.java Log: Trying to expose a GroupI endpoint (

cvs commit: xml-axis/java/src/org/apache/axis/message RPCElement.java

scheu 2002/10/02 16:37:37 Modified:java/src/org/apache/axis/description Tag: explicitHeaderWork ParameterDesc.java java/src/org/apache/axis/message Tag: explicitHeaderWork RPCElement.java Log: Revision Changes

WSDL generation broken?

Is WSLD generation broken in some way, or do I just not understand how it's supposed to work? (This is all with RC2 in Tomcat 4.0.5). I create a Java class that I want to expose as a service (BustedWSDL.java, below). I deploy it (as per the userguide) using a static deploy.wsdd file (also be

cvs commit: xml-axis/java/test/wsdl/interop4/groupi build.xml Round4XSDTestTestCase.java

dims2002/10/02 17:28:04 Modified:java/test/wsdl/interop4/groupi Tag: interop4 build.xml Round4XSDTestTestCase.java Log: - Force GMT before calling echoDate - Force a overwrite for the Impl.java Revision ChangesPath No revis

cvs commit: xml-axis/java/test/wsdl/interop4/groupi Round4XSDTestTestCase.java

dims2002/10/02 17:42:26 Modified:java/test/wsdl/interop4/groupi Tag: interop4 Round4XSDTestTestCase.java Log: Force GMT on return calendar before checking if input/output are equal. Now testcase work both with our endpoint and MSFT's endpoint. Revis

cvs commit: xml-axis/java/test/wsdl/interop4/groupi round4XSD.wsdl Round4XSDTestTestCase.java

dims2002/10/02 17:52:42 Modified:java/test/wsdl/interop4/groupi Tag: interop4 round4XSD.wsdl Round4XSDTestTestCase.java Log: Reduce errors with WhiteMesa Endpoint. Revision ChangesPath No revision No

Correctness of org.apache.axis.wsdl.toJava.Utils.getOperationQName

I have a situation where I a client is using an element instead of a type for a message parameter in my WSDL file (simplified example attached). When I generate the stubs, the operation name call looks like this: _call.setOperationName(new javax.xml.namespace.QName("http://www.xyz.com/schem

[Interop4] Group4 XSD testcase / impl checked in.

Glen, Sam, Tom, Please take a look at the test/wsdl/interop4/groupi in the interop4 branch. It has the testcase that works ok against our own impl as well as MSFT's endpoint. I have 3 failues with whitemesa's endpoint. They are as follows: (see details at the bottom) 1. EchoDate fails as they

DO NOT REPLY [Bug 13230] New: - Axis does not validate bad hrefs

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_b