Re: [GUMP] Build Failure - Axis

I will do what I can. - Original Message - From: "Davanum Srinivas" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, January 07, 2003 18:07 Subject: RE: [GUMP] Build Failure - Axis > Steve, > > Can do you something about our gump failure? > (http://ma

NPE in client junit tests

I've just been getting an NPE in autogenerated junit tests; tracked this down to extractAttachments() being called when there are no attachments. The fix I did was to guard the code with a test for attachments. Should I commit this or does anyone think there should be a better way. diff -r1.20 S

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

stevel 2003/01/07 22:44:27 Modified:java/src/org/apache/axis MessageContext.java Log: javadoc improvements and bracing all the if() statements. Revision ChangesPath 1.127 +105 -27 xml-axis/java/src/org/apache/axis/MessageContext.java Index: MessageContext.java

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

stevel 2003/01/07 22:43:00 Modified:java/docs reference.html index.html Added: java/docs security.html Log: new security document; more to the configuration reference. Revision ChangesPath 1.18 +15 -3 xml-axis/java/docs/reference.html Index: referen

DO NOT REPLY [Bug 13732] - WSDL2Java generates "" as namespace part of QNames in Stubs - causing 'xmlns=""' on the wire

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: [GUMP] Build Failure - Axis

Steve, Can do you something about our gump failure? (http://marc.theaimsgroup.com/?l=axis-dev&m=104194511415640&w=2) Thanks, dims = Davanum Srinivas - http://xml.apache.org/~dims/ __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Si

cvs commit: xml-axis/java/src/org/apache/axis/i18n resource.properties

dims2003/01/07 18:03:35 Modified:java/src/org/apache/axis/client AdminClient.java java/src/org/apache/axis/i18n resource.properties Log: previous checkin failed in test harness that checks if messages are correctly defined in resources.properties. Revision C

Re: MessageContext and final static strings

- Original Message - From: "James M Snell" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, January 07, 2003 17:06 Subject: Re: MessageContext and final static strings > Oy ve. I highly doubt changing them to final will break anything, but it > is a risk. I'd say don't change

Re: JMS transport not in 1.1 binary distribution

- Original Message - From: "Davanum Srinivas" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, January 07, 2003 05:11 Subject: RE: JMS transport not in 1.1 binary distribution > My idea of Jar-Hell :( Just like DLL's/SharedObject's Hell. The problem with DLL-hell is (a) the

Re: JMS transport not in 1.1 binary distribution

- Original Message - From: "James M Snell" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, January 06, 2003 21:11 Subject: RE: JMS transport not in 1.1 binary distribution > Btw, I personally think that individual Axis transports should be put into > their own jar files (e.g. a

Re: JMS transport not in 1.1 binary distribution

- Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, January 06, 2003 17:54 Subject: RE: JMS transport not in 1.1 binary distribution > > > > > The ideal solution would be for me as a user to simply specify the > transport/adapter

Re: JMS transport not in 1.1 binary distribution

- Original Message - From: "Glen Daniels" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, January 06, 2003 11:13 Subject: RE: JMS transport not in 1.1 binary distribution > > Actually, I did (JRun's), and have no idea why it wasn't in there. maybe happyaxis should probe for op

Re: cvs commit: xml-axis/java/tools/org/apache/axis/tools/ant/wsd l Wsdl2javaAntTask.java

Ant catches system.out calls and feeds them through the log, but we also need to get success/failure codes when things go wrong. Throwing ant BuildExceptions (which are a subclass of RTE) would be cool, but we cannot of course do that outside of the tasks. Instead callers (including the tasks) will

DO NOT REPLY [Bug 15848] - AdminClient (and admin-client Ant-task) host setting broken

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/i18n resource.properties

dims2003/01/07 17:15:11 Modified:java/src/org/apache/axis/client AdminClient.java java/src/org/apache/axis/i18n resource.properties Log: Fix for Bug 15848 - AdminClient (and admin-client Ant-task) host setting broken Notes: - Moved the strings to resources.p

Re: MessageContext and final static strings

Oy ve. I highly doubt changing them to final will break anything, but it is a risk. I'd say don't change them but I'd add the statement that these really should have been final from the beginning. But I'll vote +0 on it unless we find that it really does break existing code. As for the secon

MessageContext and final static strings

MessageContext has a lot of public static strings, but it seems to me that they should be public final static strings, since their target use is the various names of properties. Can we change these to final static strings? Or does everything out there break? If we cannot change the existing strin

cvs commit: xml-axis/java/test/soap12 TestVersionMismatch.java PackageTests.java

dims2003/01/07 13:29:07 Modified:java/test/soap12 PackageTests.java Added: java/test/soap12 TestVersionMismatch.java Log: Oops...missed the test case in the last check-in Revision ChangesPath 1.3 +1 -1 xml-axis/java/test/soap12/PackageTests.java

Re: Another API breaking change

Regardless of when the change was made, there is a problem. Looking at the axis 1.0 source distribution available from the website, ParameterDesc includes the constructor: ParameterDesc(QName name, byte mode, QName typeQName, Class javaType) Looking at the axis 1.1 beta source, this constru

Re: Another API breaking change

Where's the fun in that!? ;-) - James Snell IBM Emerging Technologies [EMAIL PROTECTED] (559) 587-1233 (office) (700) 544-9035 (t/l) Programming Web Services With SOAP O'Reilly & Associates, ISBN 0596000952 Have I not commanded you? Be strong and courageous.

Re: Another API breaking change

Agreed... from the dictionary's point of view, I can't say that it matters one way or another. >From javadoc's, AFAIK, it still needs to be "deprecate". Thanks, Jess On Tue, 2003-01-07 at 15:59, Scott Nichol wrote: > Maybe instead of writing "make sure that you deprecate the method", we > shoul

RE: Another API breaking change

There was a fix sometime back which made it possible for users to change paramaterdesc's for an operationdesc http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15284) Doesn't this mean it is a public API ??? thanks Vidyanand. -Original Message- From: Russell Butek [mailto:[EMAIL PROT

Re: Another API breaking change

Maybe instead of writing "make sure that you deprecate the method", we should write "make sure that you @deprecate the method", and avoid thesaurus.com altogether ;-) Scott Nichol - Original Message - From: "James M Snell" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, January

DO NOT REPLY [Bug 15764] - API changes break backwards compatibility with Axis 1.0

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: Another API breaking change

1.22.6.2 was done BEFORE 1.0 went out the door, so I didn't break any 1.0 code. (Besides, the ParameterDesc constructor shouldn't be considered a public API.) Russell Butek [EMAIL PROTECTED]

Re: Another API breaking change

Source: dictionary.com dep-re-cate 1. To express disapproval of, deplore 2. To belittle, depreciate dep-pre-ci-ate 1. To lessen the price or value of 2. To think or speak of as being of little worth; belittle Usage Note: The first and fully accepted meaning of deprecate is "to e

Re: Another API breaking change

> way to make this change would have been to depreciate the existing Deprecate... deprecate... deprecate... deprecate... deprecate... ;-) Ok, no offense, but this one is a pet-peeve of mine. Make sure that you deprecate the method. Don't depreciate it. Thanks, Jess 'Cuz-it-ain't-accounting

RE: Another API breaking change

James: It would be great if you could open up a new Bugzilla issue for each one of these things, so we can track them and mark them fixed when they're resolved. Thanks! --G > -Original Message- > From: James M Snell [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 07, 2003 3:13 PM

Another API breaking change

Found another API breaking change that needs to be fixed. This one made by Russell Butek and involves org.apache.axis.description.ParameterDesc . An Axis 1.0 constructor was changed in version 1.22.6.2. The appropriate way to make this change would have been to depreciate the existing constru

DO NOT REPLY [Bug 15764] - API changes break backwards compatibility with Axis 1.0

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/soap SOAP11Constants.java SOAP12Constants.java SOAPConstants.java

dims2003/01/07 11:41:58 Modified:java/src/org/apache/axis Constants.java java/src/org/apache/axis/message EnvelopeBuilder.java java/src/org/apache/axis/i18n resource.properties java/src/org/apache/axis/soap SOAP11Constants.java

DO NOT REPLY [Bug 15850] - VersionMismacth patch to reach soap 1.2 compliance

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 15850] - VersionMismacth patch to reach soap 1.2 compliance

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: [Bug 15741] - TCP Monitor does not handle WebDAV methods in proxy mode

I've never really felt very comfortable with tcpmon having an "http mode" because I never really wanted it to know what the data was, I just wanted it to be a dumb pass-thru. But, having the "xml filter" and having "resend" do the recalc'ing of the content length header has sort of moved us w

DO NOT REPLY [Bug 15850] New: - VersionMismacth patch to reach soap 1.2 compliance

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: [Bug 15741] - TCP Monitor does not handle WebDAV methods in proxymode

Doug Davis wrote: Huge +1 - that's what I do too. -Dug Tom Jordahl <[EMAIL PROTECTED]> on 01/06/2003 05:32:48 PM Please respond to [EMAIL PROTECTED] To:"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> cc: Subject:RE: DO NOT REPLY [Bug 15741] - TCP Monitor does not handle WebD AV met

DO NOT REPLY [Bug 13732] - WSDL2Java generates "" as namespace part of QNames in Stubs - causing 'xmlns=""' on the wire

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-wsif/java/samples/multibinding/client/stub README.html

nmukhi 2003/01/07 09:52:44 Modified:java/samples/customfactory/client/dynamic README.html java/samples/ejb/client/dynamic README.html java/samples/localjava/client/stub README.html java/samples/multibinding/client/dynamic README.html

cvs commit: xml-axis-wsif/java/test/mime MimeImpl.java Mime.wsdl MimeTest.java Mime.java

antelder2003/01/07 09:49:03 Modified:java/test/mime MimeImpl.java Mime.wsdl MimeTest.java Mime.java Log: Fix the bounceImage4 test by swapping the order of the arguments, so I could use it in the messaging attachments testcase. Raised bugzilla bug 15837 for t

cvs commit: xml-axis-wsif/java/test/docStyle/wsifservice Mime.wsdl

antelder2003/01/07 09:39:45 Modified:java/test/util WSIFTestRunner.java java/test/docStyle/wsifservice Mime.wsdl Added: java/test/docStyle MessagingAttachmentsTest.java Removed: java/test/docStyle MessagingRcvAttTest.java Log: New testcases for sending/re

cvs commit: xml-axis-wsif/java/src/org/apache/wsif/providers/soap/apacheaxis WSIFOperation_ApacheAxis.java

antelder2003/01/07 09:37:38 Modified:java/src/org/apache/wsif/providers/soap/apacheaxis WSIFOperation_ApacheAxis.java Log: Enable sending attachments when using messaging with the AXIS provider Revision ChangesPath 1.55 +54 -41 xml-axis-ws

RE: JMS transport not in 1.1 binary distribution

As I said, it's just an opinion. Take it or leave it :-) - James Snell IBM Emerging Technologies [EMAIL PROTECTED] (559) 587-1233 (office) (700) 544-9035 (t/l) Programming Web Services With SOAP O'Reilly & Associates, ISBN 0596000952 Have I not commanded you

RE: Initial Axis 1.1b Install Failure & Build Error

Tom, Till there's a official release Commons, We should not make it our default. For example, Commons HTTP has good support for HTTP1.1, which we don't. Another example is the bugs we have in our impl (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11296). Current check-in of CommonsHTTPSend

DO NOT REPLY [Bug 15848] New: - AdminClient (and admin-client Ant-task) host setting broken

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: Initial Axis 1.1b Install Failure & Build Error

Maybe it would be good to fish or cut bait on the CommonsHTTPSender class. Should we switch this to be the default implementation or remove the Commons based code all together. I believe the only (undocumented) way to use this class is to set a property. It *is* very confusing. Does the Commo

cvs commit: xml-axis-wsif/java/doc RELEASE_TASKS.txt

owenb 2003/01/07 07:23:02 Modified:java/doc RELEASE_TASKS.txt Log: Move task of investigating using Forrest from high priority to medium. Look to carry out conversion of web pages and documentation to use Forrest post 2.0 Revision ChangesPath 1.16 +3 -1

DO NOT REPLY [Bug 14540] - Inherited attributes are lost during serialization

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 14540] - Inherited attributes are lost during serialization

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 14540] - Inherited attributes are lost during serialization

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/wsdl/names build.xml

dims2003/01/07 05:44:50 Modified:java/test/wsdl/names build.xml Log: Make sure that test.wsdl.names.javanames.MyAddress gets built. Revision ChangesPath 1.8 +1 -1 xml-axis/java/test/wsdl/names/build.xml Index: build.xml ==

DO NOT REPLY [Bug 15837] New: - Attachments fail if in the wrong order

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

[GUMP] Build Failure - Axis

s\java\external\build\xml-apis.jar;\home\rubys\jakarta\xml-xerces2\java\build\xmlParserAPIs.jar;\home\rubys\jakarta\xml-xerces2\java\build\xercesImpl.jar;\home\rubys\jakarta\xml-axis\java;\usr\java\j2sdk1.4.1_01\jre\lib\rt.jar;\home\rubys\jakarta\jakarta-oro\jakarta-oro-20030107.jar;\home\rubys\jakarta\j

RE: JMS transport not in 1.1 binary distribution

My idea of Jar-Hell :( Just like DLL's/SharedObject's Hell. --- James M Snell <[EMAIL PROTECTED]> wrote: > Btw, I personally think that individual Axis transports should be put into > their own jar files (e.g. axis-jms.jar, axis-local.jar, axis-http.jar, > etc) so if a particular application d

cvs commit: xml-axis-wsif/java/test/docStyle/wsifservice Mime.wsdl

antelder2003/01/07 04:18:37 Modified:java/test/util WSIFTestRunner.java Added: java/test/docStyle MessagingRcvAttTest.java java/test/docStyle/wsifservice Mime.wsdl Log: New testcase for message style receiving an attachment Revision ChangesPath 1.1

cvs commit: xml-axis-wsif/java/src/org/apache/wsif/providers/soap/apacheaxis MIMEHelper.java WSIFOperation_ApacheAxis.java

antelder2003/01/07 04:03:02 Modified:java/src/org/apache/wsif/providers/soap/apacheaxis MIMEHelper.java WSIFOperation_ApacheAxis.java Log: More changes to get attachments with docstyle messaging to work Revision ChangesPath 1.2 +12 -0 xm