DO NOT REPLY [Bug 16522] - Allow Axis HTTP 1.1 clients to use Keep-Alive

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: DO NOT REPLY [Bug 16587] New: - WSDL java:operation methodNameattribute is mandatory

Nirmal Mukhi wrote: Yes, I think so too. Back when we were defining this I believe we planned to make it optional, this might just have been a typo. Anybody have issues with making it optional? All this would require would be a change to the doc that described the java binding extensions and a

test/wsdl/echo testcase

Hi,   I am trying to build a more complicate test case for document/literal style. So I built one based on test/wsdl/echo testcase with small modification. But I can not make it to work.     The modification is to add one more parameter to the operation (see the attched WSDL):  

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

stevel 2003/01/30 17:30:58 Modified:java/src/org/apache/axis/wsdl/toJava Utils.java Log: added proper spelling of octet-stream; retained old one as a google search showed that it does get used sporadically Revision ChangesPath 1.68 +2 -1 xml-axis/java/src/org/

Re: Axis attachment naming enhancement (code attached)

- Original Message - From: "Rick Rineholt" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 30, 2003 15:17 Subject: Re: Axis attachment naming enhancement (code attached) > If the name or extensions are vital to the service then it should be part > of the specification

DO NOT REPLY [Bug 16623] New: - when Axis faults are generated from HTTP faults, can we have the error code in a separate detail

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

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 16110] - Fault Code empty on the client if AxisFault is subclassed

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 15103] - java2wsdl ant task seems not to 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

DO NOT REPLY [Bug 13312] - GET on .jws returns a misleading message

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: Axis attachment naming enhancement (code attached)

If the name or extensions are vital to the service then it should be part of the specification that defines that service's interface  and thus either implied as part of that specification or contained in the SOAP envelope.   Doing something like this automatically as part of Axis implementation  w

Re: Axis attachment naming enhancement (code attached)

- Original Message - From: "James M Snell" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 30, 2003 14:21 Subject: Re: Axis attachment naming enhancement (code attached) > +1. some kind of metadata is needed. >> Perhaps the real solution is to make Axis store the

Re: Axis attachment naming enhancement (code attached)

- Original Message - From: "Jim Lerner" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 30, 2003 14:24 Subject: Re: Axis attachment naming enhancement (code attached) > Since Axis is already willing to hand me the file (on the server or the > client) with a name like

Re: Axis attachment naming enhancement (code attached)

Since Axis is already willing to hand me the file (on the server or the client) with a name like "/tmp/Axis56789axis", I am able to do with it what I will. That means that if I wanted to rename it and possibly execute it, I could. What difference does it make to Axis or system security if the

Re: Axis attachment naming enhancement (code attached)

+1. some kind of metadata is needed. - 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 cou

DO NOT REPLY [Bug 16614] - Typo in deploy.wsdd of userguide/example5

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: Axis attachment naming enhancement (code attached)

I have been researching the integration of jakarta-slide on my server with axis to deal with this issue of what to do with the attachments after they get to the server. Would it be better to include hooks to an API for content management and then go to the local file system if that is not configur

cvs commit: xml-axis/java/samples/userguide/example5 deploy.wsdd

vidyanand2003/01/30 14:14:04 Modified:java/samples/userguide/example5 deploy.wsdd Log: Fix for http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16614 Changed qName to qname in beanMapping. The new WSDD.xsd specifies qname as the attribute. Revision ChangesPath 1.5

Re: Axis attachment naming enhancement (code attached)

Perhaps the real solution is to make Axis store the filename somewhere (perhaps in a file like Axis98765axis.properties)? I agree that letting the client control the server filename is a security risks, but carrying meta-data, such as whether or not the file is a .exe file) is useful. On Thu, 20

Re: Axis attachment naming enhancement (code attached)

- Original Message - From: "Jim Lerner" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 30, 2003 12:10 Subject: Axis attachment naming enhancement (code attached) > > The premise is simple: add a MIME header to each attachment with the > original filename. When the

Re: Axis attachment naming enhancement (code attached)

I have not looked at this issue in depth; however, my first reaction is that Axis should limit itself to implementing specs. AFAIK this is not a requirement of JAX-RPC, MIME, SOAPw/attachmetns etc.  If the particular names of your attachments are important that information should flow as part of y

RE: Axis attachment naming enhancement (code attached)

Jim Could you please folow the guidelines set out here http://nagoya.apache.org/wiki/apachewiki.cgi?SubmitPatches . Once it is done someone who is familiar with mime attachments will take a loot at it and do the needful. Thanks Vidyanand -Original Message- From: Jim Lerner [mailto:[EMA

DO NOT REPLY [Bug 16252] - axis.ServerConfigFile not working

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/configuration EngineConfigurationFactoryServlet.java

gdaniels2003/01/30 10:37:40 Modified:java/src/org/apache/axis/configuration EngineConfigurationFactoryServlet.java Log: Respect the axis.ServerConfigFile system property when in a servlet context. As it stands, if we don't find a specified config file, we

DO NOT REPLY [Bug 16614] - Typo in deploy.wsdd of userguide/example5

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 16614] New: - Typo in deploy.wsdd of userguide/example5

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 16610] - Similar problem to bug #16586 exists in the EJB provider

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 16610] - Similar problem to bug #16586 exists in the WSIF EJB provider

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 16610] New: - Similar problem to bug #16586 exists in the EJB provider

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 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

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

DO NOT REPLY [Bug 16418] - No deserialization context after changing SOAPBody in handler

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

[wsif] IRC chat log

Hi, We had a chat at 10am EST today as planned. Here's a summary: 0. Release wrap-up         We patted each other on the back as planned 1. Forrest source and building web site         Forrest src will be moved to WSIF CVS and we will add an ant task to build it 2. GUMP failure         Piotr pla

DO NOT REPLY [Bug 16418] - No deserialization context after changing SOAPBody in handler

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: Dalnet Demise(?) / IRC for Axis

I've forwarded a note about this to the apache members list - will post back here with the results of the discussion there. --Glen > -Original Message- > From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 27, 2003 11:23 PM > To: [EMAIL PROTECTED]; [EMAIL PROTEC

Re: DO NOT REPLY [Bug 16587] New: - WSDL java:operation methodNameattribute is mandatory

Hi, Yes, I think so too. Back when we were defining this I believe we planned to make it optional, this might just have been a typo. Anybody have issues with making it optional? All this would require would be a change to the doc that described the java binding extensions and a (probably minor) c

DO NOT REPLY [Bug 16591] - LDAP Authentication Handler

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 16591] New: - LDAP Authentication Handler

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 16587] New: - WSDL java:operation methodName attribute is mandatory

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 16586] New: - WSIF Java provider target object must have no agrs constructor

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