RE: AXIS Test Restructuring

Hi Richard! Yup, this change has already been discussed, and got some support (and no -1s) the last time I brought it up. I've been planning to do it (by moving test and samples under src/) but haven't had a chance yet. Tom and I are both IDEA-addicts and although the older version dealt fin

RE: [axis] : Code change across the board

Nice timing on that commit, Richard. :) Refactoring this stuff is easy (though it makes for big commit logs), so I'd like to just start from where you ended up and make the changes I suggest below. --G > -Original Message- > From: Glen Daniels [mailto:[EMAIL PROTECTED]] > Sent: Wednes

RE: [axis] : Code change across the board

Hi Richard! Thank you for posting this stuff before committing. In general, this is a fine direction, but I think these need another round of edits before they're ready for primetime. Some comments in no particular order: NS_URI is used to mean "namespace URI". Some of the constants are not

Re: AXIS Test Restructuring

While we are restructing the tests, could we move the directories named 'samples' and 'test' down into some subdirectory? These are 'root' package names (i.e. samples.echo.TestClient.java and test.soap.PackageTest.java). The java source is all down a level, under 'src'. The reason is that so

DO NOT REPLY [Bug 9510] New: - bug in the file creation process of the server-config.wsdd

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: Proposal to contribute WSIL4J to Apache Axis

Aside from wether this code should be apache/axis managed and maintained code and its long term viability.. I'd like to just say 'WoW!' - very neat piece of code - giving me exactly the right level of discoverability I needed for experimenting some dynamic management interfaces. Nice stuff ! Dw

RE: too many "inactive" committers

On Wed, 29 May 2002 [EMAIL PROTECTED] wrote: > On Wed, 29 May 2002, Glyn Normington wrote: ... > > thoroughly understood any change I commit or is it reasonable to put some > > trust in the submitter of the change? .. > Most of the time I trust the submitter - based on the assumption that > he s

Re: PATCH: Allow connection to unsigned SSL servers

On Wed, 29 May 2002, Steve Loughran wrote: > Speaking of crufty, unmaintained code, Costin, what is up with the jasper > command line stuff right now? :-) I assume you want to precompile JSPs ? I would recommend using the ant tasks ( recently updated and fixed ). I hope the CLI will be removed

RE: [axis] : Code change across the board

encoding.XMLType -- Note that it 'extends Constants', so it picks up the newly defined constants under the new name... turns out there is only a single reference to an XMLType.attribute, and that is the only field unique to XMLType: AXIS_VOID. For AXIS users, Rich has indicated that we should c

Re: PATCH: Allow connection to unsigned SSL servers

- Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 29, 2002 2:48 PM Subject: PATCH: Allow connection to unsigned SSL servers > I already sent this few months ago, maybe now there's a chance someone > will at least -1 it. > > This creates a hook

RE: too many "inactive" committers

On Wed, 29 May 2002, Tom Jordahl wrote: > > One of the problems is that we don't *have* the experts in many areas > any more because they are (per the subject line) inactive in the > project. That's one more reason to identify the code that is hard to understand and either refactor it or find

RE: too many "inactive" committers

At 05:42 PM 5/29/2002 -0400, you wrote: >One of the problems is that we don't *have* the experts in many areas any >more because they are (per the subject line) inactive in the project. > >We do have Glen, but he is only one man. :-) I swear he's at least three

RE: [axis] : Code change across the board

+1 Changes look OK to me. This may break users, especially the encoding.XMLType changes. That makes me nervous, but I am -0 to it. Can we deprecate the constants? -- Tom Jordahl Macromedia -Original Message- From: Richard Sitze [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 29, 200

PATCH: Allow connection to unsigned SSL servers

I already sent this few months ago, maybe now there's a chance someone will at least -1 it. This creates a hook to allow a SSLSocketFactory that will connect with SSL servers ( tomcat, apache, etc ) without requiring a signed cert on the server. The current solution is either buy a signature,

RE: too many "inactive" committers

One of the problems is that we don't *have* the experts in many areas any more because they are (per the subject line) inactive in the project. We do have Glen, but he is only one man. :-) -- Tom Jordahl Macromedia -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]

RE: Please Help-me - Basic install of Axis Beta2 on Resin 2.1.1 Web Server

Hi Jose If you take a look at the server-config.wsdd then you will see that in the element there is an invalid attribute "xmlns:" ( for wsdd namespace, and it appears twice) change it to xmlns and it should work fine. Vidyanand. -Original Message- From: Jose Airton F. da Silva [mailt

cvs commit: xml-axis/java/src/org/apache/axis/wsdl/fromJava Emitter.java

scheu 02/05/29 14:25:30 Modified:java/src/org/apache/axis/wsdl/fromJava Emitter.java Log: The binding input/output elements namespace attribute is being set incorrectly. It should be set to a valid namespace uri. Revision ChangesPath 1.36 +6 -4 xml-axis/jav

Re: Please Help-me - Basic install of Axis Beta2 on Resin 2.1.1 Web Server

Hi Scott Nichol, I'm still having problem with Axis and Resin. My environment is now with Windows 2000 server, Sun JDK 1.3.1, Resin 2.1.1 e Axis Beta2. I did this: 1. Unzip xml-axis-beta2.zip to e:\ (so Axis root is e:\xml-axis-beta2). 2. Unzip resin-2.1.1.zip to e:\ (so Resin root is e:

Re: [axis] : Code change across the board

It's been suggested that I submit for review the "new" Constants, WSDDConstants, and XMLType files before I commit them (and corresponding changes to many other files): (See attached file: Constants.java) (See attached file: WSDDConstants.java) (See attached file: XMLType.java) *

[axis] : Code change across the board

I'm in the process of replacing string literals with constants and removing redundant constants. I'll be checking that in shortly. Be aware that the names of various constants will be changing. The changes were made to consolidate towards a common scheme for such constant names (there were 3/2

RE: too many "inactive" committers

On Wed, 29 May 2002, Glyn Normington wrote: > change? I guess the problem is I'm hesitant to change code that I don't > personally understand well, so I tend to leave this to the experts in a > particular area, even though they may be too busy. Do I need to have > thoroughly understood any change

writing serializers/deserializers

Axis-dev –     i’d like to learn more about writing serializers/deserializers in Axis, and potentially contribute some missing XML Schema support.  There was a note awhile back about support for xsd:token, xsd:normalizedString, and xsd:positiveInteger.   Have these been tacked?   Would

RE: too many "inactive" committers

Perhaps I can help you understand the WSDL2Java refactoring. And if you have ideas on making it better, I'm all ears. I'm still not done with it (in fact, I'm working on my second round as I type this, which I'm hoping to present to axis-dev this week if my other tasks don't intrude too much).

Re: Proposal to contribute WSIL4J to Apache Axis

+1 to this, but as with the WSIF stuff, I'd like to see it in it's own project and it's own package. CVS Project: xml-axis-wsil Java Package: org.apache.wsil If this is accepted, I would like to be one of the committers for this project. - James M Snell/Fresno/IBM Web services archit

Proposal to contribute WSIL4J to Apache Axis

Last November, IBM and Microsoft jointly released the Web Services Inspection Language (WS-Inspection) specification [1]. The WS-Inspection specification defines a distributed Web service discovery method, which was complementary to the centralized service discovery method defined by UDDI. WS-Ins

RE: too many "inactive" committers

Sure. It will need some work though, I haven't had a look yet at the WSDL2Java refactoring. It is one of the area that I have modified. Sylvain. -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 29, 2002 1:42 PM To: [EMAIL PROTECTED] Subject:

RE: too many "inactive" committers

Glen, I feel a little bad that I had to use the force... (ref: "...about to give up") to get attention. Nonetheless, I feel this debate over the responsiveness of the Axis openSource core group is healthy to have. I am proud to be part of this group of people who believe in openSource softw

RE: too many "inactive" committers

Sylvain, Can you please submit a "cvs diff -u" against the latest CVS to jumpstart discussion again? Thanks, dims --- "St-Germain, Sylvain" <[EMAIL PROTECTED]> wrote: > See Inline. > > > -Original Message- > From: Tom Jordahl [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, May 28, 2002

Re: When adding new function

- Original Message - From: "Tom Jordahl" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 29, 2002 8:36 AM Subject: RE: When adding new function > > Glyn wrote: > > Also, I wonder if we should be consistently using the cvs contents such as > > the docs to describe facts

RE: too many "inactive" committers

See Inline. -Original Message- From: Tom Jordahl [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 28, 2002 6:18 PM To: '[EMAIL PROTECTED]' Subject: RE: too many "inactive" committers Sylvain, What are you waiting for feedback on at this point? Did you hash out an acceptable design with

RE: too many "inactive" committers

Glyn, Can you ping them again? The place-holders i checked in just now should be of some help for people who want to help in this effort. Thanks, dims > > > On a slightly different tack, I was approached on two separate occasions > > with offers of help to implement the JAXM SOAP interfaces,

PlaceHolders for javax.xml.soap.* support

Glyn, I checked in some changes for javax.xml.soap.* support. Here are the mappings in a table format. Please feel free to add/delete/update the code anyway you see fit. Folks, We need to support this package fully because JAX-RPC's SOAPMessageContext class (http://java.sun.com/xml/downloads/ja

cvs commit: xml-axis/java/src/org/apache/axis/soap MessageFactoryImpl.java SOAPConnectionFactoryImpl.java SOAPConnectionImpl.java SOAPElementFactoryImpl.java

dims02/05/29 10:00:01 Modified:java/src/javax/xml/soap MessageFactory.java SOAPConnectionFactory.java SOAPElementFactory.java java/src/org/apache/axis/message SOAPFaultElement.java Added: java/src/org/apache/axis/message Detail.java

RE: too many "inactive" committers

Glyn Normington wrote: > > People giving up *really* gets to me, especially as I must take partial > responsibility. Not only is Axis the worse, but the people involved > presumably go away feeling their contributions were unwanted, which is a > great shame. > > I'd like to play my part in fixing

Re: too many "inactive" committers

- Original Message - From: "Glyn Normington" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 29, 2002 8:21 AM Subject: RE: too many "inactive" committers > > >Perhaps reviewing the submissions and -1'ing them would be better than > >to keep silent. Otherwise, contributi

RE: [axis] finding NLS (National Language Support) properties

I think I am -0 on this name change. There are Java APIs which deal with resource.properties and will automatically find the correct localized version of the property file. The property file is qualified with a package name, so it is unique and 'standard'. Could we have a bit more of the jus

Re: When adding new function

So I have the following work items for the specified commit: a) code,    done. b) user documentation,    n/a c) design/architecture documentation,    We don't really have a section for mapping stuff.  I can work with Glyn on this and submit text per Tom's request. d) new or updated samples,  

RE: [VOTE] Chat

+1 for Wednesday 8:00am-9:00am +0 for weekly -- Tom Jordahl Macromedia -Original Message- From: James M Snell [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 22, 2002 12:44 PM To: [EMAIL PROTECTED] Subject: [VOTE] Chat Thursdays at 8:00am are out for me. I can go at any of the times

RE: When adding new function

Glyn wrote: > Also, I wonder if we should be consistently using the cvs contents such as > the docs to describe facts and the cvs commit logs to summarise *changes* > to the facts? I don't like seeing useful design notes get 'hidden' in cvs > logs. Glyn and I must be on the same wavelength today

RE: too many "inactive" committers

+1! I was also crafting a note about the fact that I would "ignore" patches that would make changes to code I don't fully understand. But Glyn said it better. We are only doing our best. Sometimes this means that people, patches and issues get dropped on the floor. -- Tom Jordahl Macromedia

RE: too many "inactive" committers

>Perhaps reviewing the submissions and -1'ing them would be better than >to keep silent. Otherwise, contributing has no sense, and people give up. >This is the fourth case that I'm aware of in axis-dev. People giving up *really* gets to me, especially as I must take partial responsibility. Not o

Re: When adding new function

>Not only do I agree, I would VOTE on getting **significant** >changes/function documented (rough would be find) and APPROVED >before implementing. I agree in principle, but I wouldn't like to commit speculative design changes into cvs and then seek approval as this would render the cvs document

Re: [axis] Transport Name

+1 to keeping/clarifying the distinction, but providing usable defaults. Glyn "Glen Daniels"

DO NOT REPLY [Bug 9492] - Public attribute serialization does not work

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: too many "inactive" committers

>> What are you waiting for feedback on at this point? >> Did you hash out an acceptable design with Glen? If so, check it in. > What do you mean by 'hash out an acceptable design with Glen'? > Must a would-be contributor agree on the design before submitting anything? No, there is history he

RE: Deploying Axis on j2ee deploytool - is this a bug?

Adel, It looks from the error message that you have file permission problems. Can Axis write to the directory D:\j2sdkee1.3.1\public_html\axis\WEB-INF? -- Tom Jordahl Macromedia -Original Message- From: Adel Habib [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 28, 2002 8:00 PM To: [EMAI

RE: example 2 submit

Richard, This file is used as Calculator.jws. See the users guide. I don't believe it is appropriate to add the package directive unless you update the users guide and test that it works. This might not be a bad idea, as jws files and packages are a bit tricky if I remember correctly. -- T

Re: AXIS BUG ?

These are not bugs. See my comments inline between ... Russell Butek [EMAIL PROTECTED] "Jean-Marc Taillant" <[EMAIL PROTECTED]> on 05/29/2002 08:41:06 PM Please respond to [EMAIL PROTECTED] To:<[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> cc: Subject:AXIS BUG ? Hi all, I found several

cvs commit: xml-axis/java/test/wsdl/qualify Qualify_BindingImpl.java Qualify_ServiceTestCase.java

dims02/05/29 07:30:02 Modified:java/samples/security LogHandler.java java/samples/transport FileReader.java FileSender.java java/samples/transport/tcp TCPListener.java TCPSender.java java/src/org/apache/axis Message.java ja

[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

DO NOT REPLY [Bug 9492] New: - Public attribute serialization does not work

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: When adding new function

Not only do I agree, I would VOTE on getting **significant** changes/function documented (rough would be find) and APPROVED before implementing. That would alleviate some of the tension between (at times) conflicting goals within the development community, and set out a road-map for other volunte

AXIS BUG ?

Hi all, I found several bugs in server sid generated WSDL ( invoked with the ?wsdl option in the URL...). I made tests with several tools ( XML spy ( soap debugger plug-in & SOAP:Net from www.soaptoolset.com) and i find this:   AXIS generate WSDL with "     This syntax is not understanded by

Re: too many "inactive" committers

Hi Sylvain! I'll take the heat for your problem, because I feel like I'm the one who's slowing things down for you. So let me say a) I apologize for being slow to respond, b) I'm still in Montreal today but am back tomorrow - can we plan to hash the details of the change out then? Meet on IRC a

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

dims02/05/29 06:05:54 Modified:java/src/org/apache/axis/attachments AttachmentPart.java AttachmentsImpl.java AttachmentUtils.java MimeUtils.java java/src/org/apache/axis/encoding/ser JAFDataHandle

Re: [axis] Transport Name

A transport (whether on the client or the server side) represents a given chunk of transport-specific functionality implemented in Handlers. This includes stuff like the HTTPSender (on the client side), but also potentially things like cookie-setting handlers, URL dispatchers, etc. It is very po

Re: [axis] Transport Name

Go for it. I thought about combining these once, but after 5 minutes of poking about I realized it was more than a 5 minute job, so I decided not to tackle it just then (ie., I gave up). org.apache.axis.client.AdminClient makes use of Call.TRANSPORT_NAME, so SOMEONE is hoping the name is meaningf

WSDL binding -> SOAP message spec? (was: RE: cvs commit: xml-axis/java/test/wsdl/faultsFaultService.wsdl FaultServiceSoapBindingImpl.java FaultServiceTestCase.java)

Tom, Rich, this lack of a spec for a mapping from WSDL faults to a SOAP message is just part of a bigger problem. As far as I can tell, there is NO spec that defines the mapping from ANY WSDL binding to a SOAP message. WSDL 1.1 doesn't do it. And that's where I think it belongs. We may have to

RE: too many "inactive" committers

Title: RE: too many "inactive" committers Hi Tom, > -Mensaje original- > De: Tom Jordahl [mailto:[EMAIL PROTECTED]] > Enviado el: miércoles 29 de mayo de 2002 0:18 > Para: '[EMAIL PROTECTED]' > Asunto: RE: too many "inactive" committers > > > > Sylvain, > > What are you waiting f

When adding new function

In "RE: cvs commit: xml-axis/java/test/wsdl/faults FaultService.wsdl FaultServiceSoapBindingImpl.java FaultServiceTestCase.java", Tom wrote: >The text of the submit should be captured in the architecture docs that Glyn has been working on. I'd be very happy for Rich to incorporate his text into

Re: WSIF package names

>I'd appreciate votes from anyone concerned with WSIF. I assume you mean Axis-WSIF committers? The rest of us shouldn't have binding votes. Glyn