[jira] Closed: (AXIS-2700) axisproviderlib.sda for SAP XI

[ https://issues.apache.org/jira/browse/AXIS-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jordahl closed AXIS-2700. - Resolution: Invalid This sure sounds like you should contact SAP about this issue. If you can pinpoint

[jira] Commented: (AXIS-2682) wsdl2Java generates invalid empty string namespaces

[ https://issues.apache.org/jira/browse/AXIS-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515379 ] Tom Jordahl commented on AXIS-2682: --- The construct data xmlns=foo/data Is to make the data element unqualified.

[jira] Resolved: (AXIS-2442) java file genrated using WSDL2JAVA fail to compile with 'too many parameters' error

[ https://issues.apache.org/jira/browse/AXIS-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jordahl resolved AXIS-2442. --- Resolution: Fixed Fix Version/s: current (nightly) I believe I fixed this in the current

[jira] Commented: (AXIS-2668) Axis 1.3 - Garbage collection issue

[ https://issues.apache.org/jira/browse/AXIS-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507898 ] Tom Jordahl commented on AXIS-2668: --- Hi Prasanna, I am afraid you get what you pay for in Open Source Land and if

[jira] Commented: (AXIS2-2831) Codegen creating too many stubs most of the time

[ https://issues.apache.org/jira/browse/AXIS2-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506615 ] Tom Jordahl commented on AXIS2-2831: Axis 1.x had the right idea for this, why doesn't Axis2 follow suit? In

[jira] Resolved: (AXIS-2626) xsd:dateTime in wsdl produces GMT date time SOAP output in the form yyyy-mm-ddThh:MM:ss.msz and not in locale specific. The format of dateout cannot be controlled

[ https://issues.apache.org/jira/browse/AXIS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jordahl resolved AXIS-2626. --- Resolution: Won't Fix You can not get Axis to put dates on the wire in anything other than UTC. This

[jira] Commented: (AXIS-2635) File download fails without crimson

[ https://issues.apache.org/jira/browse/AXIS-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479356 ] Tom Jordahl commented on AXIS-2635: --- Axis has always used Xerces, never crimson, so I am not sure why you would see

[jira] Updated: (AXIS-2064) The format of multi-cookie in HTTP request head.

[ https://issues.apache.org/jira/browse/AXIS-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jordahl updated AXIS-2064: -- Priority: Blocker (was: Major) Affects Version/s: 1.4 1.3 Add 1.3

[jira] Resolved: (AXIS-2064) The format of multi-cookie in HTTP request head.

[ https://issues.apache.org/jira/browse/AXIS-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jordahl resolved AXIS-2064. --- Resolution: Fixed Fix Version/s: current (nightly) Fix in SVN head of Axis 1.x tree, revision

[jira] Commented: (AXIS2-1247) wsdl2java generated client throws NumberFormatException on nil integer

[ http://issues.apache.org/jira/browse/AXIS2-1247?page=comments#action_12441249 ] Tom Jordahl commented on AXIS2-1247: Note that an Axis 1.x, any integer type that is nillable has to become a Java Integer. Otherwise you can not tell if 0

[jira] Commented: (AXIS2-1272) Cannot differentiate between an int sent as 0 and an int sent as nil

[ http://issues.apache.org/jira/browse/AXIS2-1272?page=comments#action_12441253 ] Tom Jordahl commented on AXIS2-1272: (Commented on AXIS2-1247 also) Note that an Axis 1.x, any integer type that is nillable has to become a Java Integer.

[jira] Commented: (AXIS2-1274) WSDL2Java does not create Stub class for PortType

[ http://issues.apache.org/jira/browse/AXIS2-1274?page=comments#action_12441255 ] Tom Jordahl commented on AXIS2-1274: Dims, Does this mean that by default wsdl2java does not emit code for all the ports in a WSDL? That seems bad to me.

[jira] Closed: (AXIS-2481) Deserialization of SOAP Fault fails with 'org.xml.sax.SAXParseException: Comment must start with !--'

[ http://issues.apache.org/jira/browse/AXIS-2481?page=all ] Tom Jordahl closed AXIS-2481. - Resolution: Invalid Closing per request. Deserialization of SOAP Fault fails with 'org.xml.sax.SAXParseException: Comment must start with !--'

[jira] Commented: (AXIS-2510) Problem with consuming a WSDL for a Web Service

[ http://issues.apache.org/jira/browse/AXIS-2510?page=comments#action_12417363 ] Tom Jordahl commented on AXIS-2510: --- Could you try with the source in the tree or from a recent release (1.4)? Problem with consuming a WSDL for a Web Service

[jira] Commented: (AXIS2-763) Code generated by WSDL2 Java expects a return element that does not exist in the WSDL nor in the return message.

[ http://issues.apache.org/jira/browse/AXIS2-763?page=comments#action_12412961 ] Tom Jordahl commented on AXIS2-763: --- Two things: 1. If the WSDL is rpc/encoded then Axis2 should *definitely* print a clear and early warning that we don't support this

[jira] Commented: (AXIS2-665) WSDL2Java generated code does not run correctly

[ http://issues.apache.org/jira/browse/AXIS2-665?page=comments#action_12378025 ] Tom Jordahl commented on AXIS2-665: --- Does Axis2 not automatically support WSDL with multiple ports? That seems pretty important. Has anyone run WSDL2Java on the Mappoint

[jira] Commented: (AXIS2-656) Support for basic authentication

[ http://issues.apache.org/jira/browse/AXIS2-656?page=comments#action_12378027 ] Tom Jordahl commented on AXIS2-656: --- Lets not screw the users in the name of purity here. setUsername() and setPasword() are pretty obvious and important attrributes on the

[jira] Commented: (AXIS-2467) Inconsistent/garbled statements about WSDL2Java's -T --typeMappingVersion option in Axis Reference Guide

[ http://issues.apache.org/jira/browse/AXIS-2467?page=comments#action_12376495 ] Tom Jordahl commented on AXIS-2467: --- Please do not change the default for this switch in the WSDL2Java code. Summary: This switch is a mess. Details: It was implemented to

[jira] Closed: (AXIS-2462) Axis is not JDK1.5 compliant

[ http://issues.apache.org/jira/browse/AXIS-2462?page=all ] Tom Jordahl closed AXIS-2462: - Resolution: Invalid You don't use this package, you use org.apache.axis.constants.* instead. Everything in Axis 1.3 and above uses the new pacakge. The old

[jira] Closed: (AXIS-2450) The generated deserialization methods are producing the wrong code for nillable simple-type elements

[ http://issues.apache.org/jira/browse/AXIS-2450?page=all ] Tom Jordahl closed AXIS-2450: - Resolution: Invalid It doesn't sound like this is an Axis 1.x problem - are you ising Axis2? If so then please open a bug in their bug base. Thanks. The

[jira] Closed: (AXIS-2451) The generated deserialization methods are producing the wrong code for nillable simple-type elements

[ http://issues.apache.org/jira/browse/AXIS-2451?page=all ] Tom Jordahl closed AXIS-2451: - Resolution: Invalid closing per Olivier's comment The generated deserialization methods are producing the wrong code for nillable simple-type elements

[jira] Closed: (AXIS-2441) xmlns not reachable: http://xml.apache.org/axis/wsdd/

[ http://issues.apache.org/jira/browse/AXIS-2441?page=all ] Tom Jordahl closed AXIS-2441: - Resolution: Invalid Why should this URI be reachable? It is just a namespace, not a web page. xmlns not reachable: http://xml.apache.org/axis/wsdd/

[jira] Commented: (AXIS-2442) java file genrated using WSDL2JAVA fail to compile with 'too many parameters' error

[ http://issues.apache.org/jira/browse/AXIS-2442?page=comments#action_12371303 ] Tom Jordahl commented on AXIS-2442: --- If this is a wrapped document/literal service, you should use the --noWrapped switch to WSDL2Java to turn off the unwrapping of the

[jira] Commented: (AXIS-2399) Problem with unbounded elements and sequence in SimpleAxisServer

[ http://issues.apache.org/jira/browse/AXIS-2399?page=comments#action_12366804 ] Tom Jordahl commented on AXIS-2399: --- SimpleAxisServer should be fine for the use that Thomas is using it for. The error indicates that there are missing type mappings for

[jira] Updated: (AXIS-2391) WSDL2Java ignores attributes for complex types that have only element with maxOccurs=unbounded in sequence

[ http://issues.apache.org/jira/browse/AXIS-2391?page=all ] Tom Jordahl updated AXIS-2391: -- Priority: Blocker (was: Major) Upgrading to a blocker as requested. Note that you may have to provide the fix for this yourself, as this priority doesn't imply

[jira] Commented: (AXIS-2388) Invalid SOAP envelope sent when ws-security is enabled

[ http://issues.apache.org/jira/browse/AXIS-2388?page=comments#action_12365639 ] Tom Jordahl commented on AXIS-2388: --- Two comments - Have you tried the latest release of Axis (1.3) or the latest SVN source from the tree? - You probably will need to debug

[jira] Commented: (AXIS-2386) Java2WSDL changes type double array into a single double.

[ http://issues.apache.org/jira/browse/AXIS-2386?page=comments#action_12365642 ] Tom Jordahl commented on AXIS-2386: --- The code is the same for ?WSDL generation and Java2WSDL. So if one works and the other doesn't, it would be interesting to know why.

[jira] Commented: (AXIS-2146) Different class loading used in attachment type mapping causing NoClassDefFoundError

[ http://issues.apache.org/jira/browse/AXIS-2146?page=comments#action_12364088 ] Tom Jordahl commented on AXIS-2146: --- Wouldn't the change be for the attachement code to use the ClassUtils function instead? If I recall correctly, ClassUtils solves

[jira] Commented: (AXIS-2376) incomplete generation of 'Stub' due to missing wsdl:part .../ of (WSDL-)Message

[ http://issues.apache.org/jira/browse/AXIS-2376?page=comments#action_12363284 ] Tom Jordahl commented on AXIS-2376: --- You can't have a wrapped operation without the following conditions being met: - Single part (a problem here) - Part is an element with

[jira] Closed: (AXIS-2368) Axis failing with error Server did not recognize the value of HTTP Header SOAPAction:

[ http://issues.apache.org/jira/browse/AXIS-2368?page=all ] Tom Jordahl closed AXIS-2368: - Resolution: Invalid Please reopen if there is something that we can fix in Axis. Axis failing with error Server did not recognize the value of HTTP Header

[jira] Closed: (AXIS-2343) NoSuchMethodError:javax.xml.namespace.QName.getPrefix with WSDL2Java

[ http://issues.apache.org/jira/browse/AXIS-2343?page=all ] Tom Jordahl closed AXIS-2343: - Resolution: Invalid This indicates you have another version of the QName classes that were loaded instead of the ones in jaxrpc.jar. Older versions old wsdl4j

[jira] Commented: (AXIS-2272) Duplicated operation names

[ http://issues.apache.org/jira/browse/AXIS-2272?page=comments#action_12360599 ] Tom Jordahl commented on AXIS-2272: --- Fair enough. A simple test case and patches welcome. Duplicated operation names -- Key: AXIS-2272

[jira] Commented: (AXIS-1551) SOAPMonitor should display exceptions too

[ http://issues.apache.org/jira/browse/AXIS-1551?page=comments#action_12360419 ] Tom Jordahl commented on AXIS-1551: --- I would say it is fairly certain that no one is actively working on this bug. Patches are always welcome. SOAPMonitor should display

[jira] Commented: (AXIS-2235) Autogenerated WSDL does not qualify the wsdl:types at all

[ http://issues.apache.org/jira/browse/AXIS-2235?page=comments#action_12360306 ] Tom Jordahl commented on AXIS-2235: --- Why does the XML parser affect this? What does Resin use instead of Xerces, Crimson? I would say you need to file a bug against the

[jira] Closed: (AXIS-2235) Autogenerated WSDL does not qualify the wsdl:types at all

[ http://issues.apache.org/jira/browse/AXIS-2235?page=all ] Tom Jordahl closed AXIS-2235: - Resolution: Duplicate duplicate of Axis-2336. Autogenerated WSDL does not qualify the wsdl:types at all

[jira] Commented: (AXIS-1297) Axis's jaxrpc.jar includes some interfaces from JAXP, causing class cast exceptions in JBoss, possibly Tomcat

[ http://issues.apache.org/jira/browse/AXIS-1297?page=comments#action_12360360 ] Tom Jordahl commented on AXIS-1297: --- Just remove the classes from the Axis 1.1 jaxrpc.jar. Axis's jaxrpc.jar includes some interfaces from JAXP, causing class cast

[jira] Commented: (AXIS-2235) Autogenerated WSDL does not qualify the wsdl:types at all

[ http://issues.apache.org/jira/browse/AXIS-2235?page=comments#action_12359590 ] Tom Jordahl commented on AXIS-2235: --- I don't see this bug on Axis 1.2.1 or 1.3. I have WSDL that has both the default namespace and the wsdl prefix. Autogenerated WSDL

[jira] Commented: (AXIS-2329) Skeleton class don't compile

[ http://issues.apache.org/jira/browse/AXIS-2329?page=comments#action_12359591 ] Tom Jordahl commented on AXIS-2329: --- Java itself has a 64K (I think) limit on the size of a function. We take steps to avoid this limit. Could you be hitting a Java class

[jira] Commented: (AXIS-2319) Bad parsing of content type header for multipart messages

[ http://issues.apache.org/jira/browse/AXIS-2319?page=comments#action_12359125 ] Tom Jordahl commented on AXIS-2319: --- Since Axis is using a standard JavaMail jar file, the bug seems to be in that library. Since we do not control these jar files, fixing

[jira] Commented: (AXIS2-313) TypeSystemHolder does not exist compile errors from WSDL2Java

[ http://issues.apache.org/jira/browse/AXIS2-313?page=comments#action_12358667 ] Tom Jordahl commented on AXIS2-313: --- Should Axis2 actually *do* something useful with this XML Beans class file to make it easier for users to get this to work? Perhaps put

[jira] Commented: (AXIS-2285) Deserializing objects on client side with unknown data members from server side causes exception, makes server code harder to maintain

[ http://issues.apache.org/jira/browse/AXIS-2285?page=comments#action_12356810 ] Tom Jordahl commented on AXIS-2285: --- What you are talking about here is changing the contract (the Schema in the WSDL) and versioning the service. This is a very hard

[jira] Commented: (AXIS-2288) Bad document style request processing

[ http://issues.apache.org/jira/browse/AXIS-2288?page=comments#action_12356811 ] Tom Jordahl commented on AXIS-2288: --- You are correct, the dispatching of the operations is based on the child element of the SOAP body. How would you expect this to work?

[jira] Commented: (AXIS-2278) Memory leak cause by JavaUtils.enumMap

[ http://issues.apache.org/jira/browse/AXIS-2278?page=comments#action_12356510 ] Tom Jordahl commented on AXIS-2278: --- A patch would be appreciated. Thanks. Memory leak cause by JavaUtils.enumMap -- Key:

[jira] Commented: (AXIS-2256) NullPointerException in JavaBeanWriter.preprocess

[ http://issues.apache.org/jira/browse/AXIS-2256?page=comments#action_12331898 ] Tom Jordahl commented on AXIS-2256: --- At the minimum, you will need to attach the full WSDL to the bug. We would much rather see a very *small* WSDL with the data type or

[jira] Commented: (AXIS-2249) CLONE -Array deserialization

[ http://issues.apache.org/jira/browse/AXIS-2249?page=comments#action_12331606 ] Tom Jordahl commented on AXIS-2249: --- FYI Around Axis 1.1 the array code was changed to not allocate the size of the array as specified in the SOAP to protect against a DOS

[jira] Commented: (AXIS-1283) can't use mime:multipartRelated in wsdl:output element of a wsdl:operation

[ http://issues.apache.org/jira/browse/AXIS-1283?page=comments#action_12331389 ] Tom Jordahl commented on AXIS-1283: --- Clearly no one is working on this. Patches and tests are welcome. can't use mime:multipartRelated in wsdl:output element of a

[jira] Closed: (AXIS-2239) Sample transport/tcp

[ http://issues.apache.org/jira/browse/AXIS-2239?page=all ] Tom Jordahl closed AXIS-2239: - Resolution: Invalid closing per comments Sample transport/tcp Key: AXIS-2239 URL:

[jira] Commented: (AXIS-2227) Axis fails to emit WSDL when using beans classes ex WSDL2Java

[ http://issues.apache.org/jira/browse/AXIS-2227?page=comments#action_12330203 ] Tom Jordahl commented on AXIS-2227: --- Two things: - You need to inline the schema so we can see what that types are. - It sounds like you are defining an attribute as a URI

[jira] Resolved: (AXIS-2228) Missing documented methods on QName object in jaxrpc.jar

[ http://issues.apache.org/jira/browse/AXIS-2228?page=all ] Tom Jordahl resolved AXIS-2228: --- Resolution: Invalid Vincent, Just ran in to this myself where a classloader issue cause an old wsdl4j jar to be loaded. If you are using a wsdl4j.jar older

[jira] Reopened: (AXIS-2138) Regression with base64Binary and simpleType elements

[ http://issues.apache.org/jira/browse/AXIS-2138?page=all ] Tom Jordahl reopened AXIS-2138: --- Reopening per Steve Green's comments. Regression with base64Binary and simpleType elements

[jira] Commented: (AXIS2-230) I wish the codegen tool generated code was indented nicely

[ http://issues.apache.org/jira/browse/AXIS2-230?page=comments#action_12330022 ] Tom Jordahl commented on AXIS2-230: --- Just make sure that the XSLT template have good indentation, that will cover 90% of the problem, right? I wish the codegen tool

[jira] Commented: (AXIS2-215) Getting the operation implementation details from WSDL

[ http://issues.apache.org/jira/browse/AXIS2-215?page=comments#action_12324455 ] Tom Jordahl commented on AXIS2-215: --- I would think that Axis2 would examine the implementation class to get the operation, just like Axis1 does. Perhaps the title should be

[jira] Commented: (AXIS2-211) All printStackTrace() calls should be removed

[ http://issues.apache.org/jira/browse/AXIS2-211?page=comments#action_12323252 ] Tom Jordahl commented on AXIS2-211: --- If we are printing stack traces when tests *fail*, then this is a good thing. I don't think you can have too much info in that case.

[jira] Closed: (AXIS-2214) JWS deployment fails on OS X: libJ3D.jnilib causes error in opening zip file

[ http://issues.apache.org/jira/browse/AXIS-2214?page=all ] Tom Jordahl closed AXIS-2214: - Resolution: Invalid There isn't much that Axis can do. The compilation of JWS is done by the tools.jar javac compiler which comes with the JDK. See the

[jira] Commented: (AXIS-2215) Adding SSL support to SimpleAxisServer

[ http://issues.apache.org/jira/browse/AXIS-2215?page=comments#action_12323069 ] Tom Jordahl commented on AXIS-2215: --- Leonard, Could you please attach a diff against the latest SVN source? Adding SSL support to SimpleAxisServer

[jira] Closed: (AXIS-2213) ClassNotFoundException when using Xalan 2.7

[ http://issues.apache.org/jira/browse/AXIS-2213?page=all ] Tom Jordahl closed AXIS-2213: - Resolution: Invalid Closing per Andy's comments. ClassNotFoundException when using Xalan 2.7 --- Key:

[jira] Commented: (AXIS-2213) ClassNotFoundException when using Xalan 2.7

[ http://issues.apache.org/jira/browse/AXIS-2213?page=comments#action_12322972 ] Tom Jordahl commented on AXIS-2213: --- Axis doesn't use or depend on Xalan. ClassNotFoundException when using Xalan 2.7 ---

[jira] Reopened: (AXIS-1976) dotnet_soapenc_bugfix is blindly reset

[ http://issues.apache.org/jira/browse/AXIS-1976?page=all ] Tom Jordahl reopened AXIS-1976: --- Reopening the bug per Clint's comment. dotnet_soapenc_bugfix is blindly reset Key: AXIS-1976

[jira] Closed: (AXIS-2190) Configuration file location process different for client and server files

[ http://issues.apache.org/jira/browse/AXIS-2190?page=all ] Tom Jordahl closed AXIS-2190: - Resolution: Invalid Closing per Jasons comment. Configuration file location process different for client and server files

[jira] Commented: (AXIS-2200) Unable to throw CustomException without hostname and exceptionName being added to details

[ http://issues.apache.org/jira/browse/AXIS-2200?page=comments#action_12322893 ] Tom Jordahl commented on AXIS-2200: --- There is a switch that turns off the stack trace in the exception. It would be reasonable to enhance that switch to turn off the

[jira] Commented: (AXIS-2210) wsdl2java reverses urn namespace when creating package name.

[ http://issues.apache.org/jira/browse/AXIS-2210?page=comments#action_12322894 ] Tom Jordahl commented on AXIS-2210: --- No spec that I know of. But Axis has done this for a long time, changing it now may be a bad thing. wsdl2java reverses urn namespace

[jira] Commented: (AXIS-2210) wsdl2java reverses urn namespace when creating package name.

[ http://issues.apache.org/jira/browse/AXIS-2210?page=comments#action_12322768 ] Tom Jordahl commented on AXIS-2210: --- This is Axis behaving exactly as expected. It does reverse the urn name, just like we reverse the hostname in an HTTP URI. wsdl2java

[jira] Commented: (AXIS-2209) Axis org.apache.axis.client.Call setter methods do not set corresponding javax.xml.rpc.* properties

[ http://issues.apache.org/jira/browse/AXIS-2209?page=comments#action_12322769 ] Tom Jordahl commented on AXIS-2209: --- Still it would be good to make sure that the JAX-RPC standard properties are set when the Axis convenience methods are called. Adrian,

[jira] Commented: (AXIS2-129) Internationalisation support for OM

[ http://issues.apache.org/jira/browse/AXIS2-129?page=comments#action_12318112 ] Tom Jordahl commented on AXIS2-129: --- I would hope that you can just take the Axis 1.x i18n package and use it. Internationalisation support for OM

[jira] Commented: (AXIS-2155) Cannot distinguish element not present and element present and nil

[ http://issues.apache.org/jira/browse/AXIS-2155?page=comments#action_12317594 ] Tom Jordahl commented on AXIS-2155: --- We can't do this in Java, as xsd:int is represented as Integer, not a class. Emitting a JavaBean class for minoccurs=0 element wil

[jira] Commented: (AXIS2-109) Databinding completeness in the stubs that are generated

[ http://issues.apache.org/jira/browse/AXIS2-109?page=comments#action_12317618 ] Tom Jordahl commented on AXIS2-109: --- Since this is a wrapped doc/lit WSDL, it is expected that the request message will be treated as a sequence of parameters, and a Stub

[jira] Commented: (AXIS-1587) WSDL2Java doesn't identify nillable- attributes

[ http://issues.apache.org/jira/browse/AXIS-1587?page=comments#action_12317114 ] Tom Jordahl commented on AXIS-1587: --- Omittable is not the same thing as nillable. One implies leave out the element, the other says you can set it type to 'nil'. I do not

[jira] Commented: (AXIS-2114) GeoCoder failure

[ http://issues.apache.org/jira/browse/AXIS-2114?page=comments#action_12316097 ] Tom Jordahl commented on AXIS-2114: --- The Geocoder WSDL says this: - xsd:complexType name=ArrayOfGeocoderResult

[jira] Updated: (AXIS-2114) GeoCoder failure

[ http://issues.apache.org/jira/browse/AXIS-2114?page=all ] Tom Jordahl updated AXIS-2114: -- Description: Bug report from Tom. We have a report from one of our customers that a web services that used to work with 1.2 RC2, no longer does with Axis 1.2.1.

[jira] Commented: (AXIS-119) WSDL2Java doesn't honor restrictions in schema

[ http://issues.apache.org/jira/browse/AXIS-119?page=comments#action_12315771 ] Tom Jordahl commented on AXIS-119: -- There are no plans to support this in Axis 1.x. Axis2 is using XMLBeans, which I believe generates code to enforce restrictions.

[jira] Commented: (AXIS-2025) Illegal XML characters in String arguments and return values cause XML exceptions in Axis calls

[ http://issues.apache.org/jira/browse/AXIS-2025?page=comments#action_12315334 ] Tom Jordahl commented on AXIS-2025: --- So enhancing the scanning of strings does not seem like a viable option here? At this point, returning a reasonable fault may be the best

[jira] Commented: (AXIS-2025) Illegal XML characters in String arguments and return values cause XML exceptions in Axis calls

[ http://issues.apache.org/jira/browse/AXIS-2025?page=comments#action_12314606 ] Tom Jordahl commented on AXIS-2025: --- With less jumping up and down and more providing of a patch, I would think that this is a valid bug and be inclined to apply the patch.

[jira] Reopened: (AXIS-2025) Illegal XML characters in String arguments and return values cause XML exceptions in Axis calls

[ http://issues.apache.org/jira/browse/AXIS-2025?page=all ] Tom Jordahl reopened AXIS-2025: --- Illegal XML characters in String arguments and return values cause XML exceptions in Axis calls

[jira] Commented: (AXIS-1903) IncompatibleClassChangeError when deploying Axis 1.2-RC3 on WebSphere 5.1 with PARENT_FIRST classloading

[ http://issues.apache.org/jira/browse/AXIS-1903?page=comments#action_12313820 ] Tom Jordahl commented on AXIS-1903: --- This is in release 1.2.1, which was released yesterday. IncompatibleClassChangeError when deploying Axis 1.2-RC3 on WebSphere 5.1

[jira] Closed: (AXIS-2058) WSDL2java fails with an error code Type ... is referenced but not defined when run against valid schema.

[ http://issues.apache.org/jira/browse/AXIS-2058?page=all ] Tom Jordahl closed AXIS-2058: - Resolution: Duplicate Duplicate of Axis-2022 WSDL2java fails with an error code Type ... is referenced but not defined when run against valid schema.

[jira] Closed: (AXIS-2052) Slow Response time and CPU utilization shoots up.

[ http://issues.apache.org/jira/browse/AXIS-2052?page=all ] Tom Jordahl closed AXIS-2052: - Resolution: Duplicate duplicate of 2051 Slow Response time and CPU utilization shoots up. - Key:

[jira] Updated: (AXIS-2051) Slow response and CPU Utilization increases of the java process increases.

[ http://issues.apache.org/jira/browse/AXIS-2051?page=all ] Tom Jordahl updated AXIS-2051: -- Priority: Major (was: Blocker) Slow response and CPU Utilization increases of the java process increases.

[jira] Commented: (AXIS-2051) Slow response and CPU Utilization increases of the java process increases.

[ http://issues.apache.org/jira/browse/AXIS-2051?page=comments#action_12313591 ] Tom Jordahl commented on AXIS-2051: --- You will have to try with at least Axis 1.2, but we would prefer you try to reproduce with the latest CVS source which will soon become

[jira] Commented: (AXIS-895) Axis doesn't maintain more than one cookie with http

[ http://issues.apache.org/jira/browse/AXIS-895?page=comments#action_12313486 ] Tom Jordahl commented on AXIS-895: -- Thanks for the patch! Watch it - you are changing the function signature of a public function in HTTPSender. Someone may be overriding it

[jira] Commented: (AXIS-2050) .NET interop failure on arrays of complex types.

[ http://issues.apache.org/jira/browse/AXIS-2050?page=comments#action_12313499 ] Tom Jordahl commented on AXIS-2050: --- The only difference that the XML diff tool at http://apps.gotdotnet.com/xmltools/xmldiff/ reports is that the nightly repsonse has the

[jira] Commented: (AXIS-1976) dotnet_soapenc_bugfix is blindly reset

[ http://issues.apache.org/jira/browse/AXIS-1976?page=comments#action_12313294 ] Tom Jordahl commented on AXIS-1976: --- It certainly seems wrong to unconditionally set this switch (which I added a while back) to be true or false depending on the type

[jira] Resolved: (AXIS-2035) isOnlyLiteralReferenced flag improperly set

[ http://issues.apache.org/jira/browse/AXIS-2035?page=all ] Tom Jordahl resolved AXIS-2035: --- Fix Version: 1.2.1 Resolution: Fixed I believe I fixed this on June 03 2005 with the following check in:

[jira] Commented: (AXIS-1604) Generated depoy.wsdd

[ http://issues.apache.org/jira/browse/AXIS-1604?page=comments#action_12313295 ] Tom Jordahl commented on AXIS-1604: --- I would say no, we will not change this for 1.2.1. I would be much more inclined to accept a patch that provides a new option to output

[jira] Commented: (AXIS-2021) String Array Regression causes SAXException: Found character data ...

[ http://issues.apache.org/jira/browse/AXIS-2021?page=comments#action_12313202 ] Tom Jordahl commented on AXIS-2021: --- An maxOccurrs=unbounded string array should work from WSDL. That is doesn't is a pretty big bug. :-( The ArrayOf stuff is ugly and we

[jira] Commented: (AXIS-119) WSDL2Java doesn't honor restrictions in schema

[ http://issues.apache.org/jira/browse/AXIS-119?page=comments#action_12312923 ] Tom Jordahl commented on AXIS-119: -- At this point Axis 1.x just doesn't support these kinds of restrictions. WSDL2Java doesn't honor restrictions in schema

[jira] Commented: (AXIS2-24) Unable to omit element if nillable=true or minoccurs=0/maxoccurs=1

[ http://issues.apache.org/jira/browse/AXIS2-24?page=comments#action_12312924 ] Tom Jordahl commented on AXIS2-24: -- If the nilable attribute is TRUE, then Axis will always nil the element if the value passed in is null. If nilable is FALSE, then Axis

[jira] Commented: (AXIS-2043) WSDL prcoessing varies by toolset

[ http://issues.apache.org/jira/browse/AXIS-2043?page=comments#action_12312929 ] Tom Jordahl commented on AXIS-2043: --- I seem to remember fixing this missing 'name' attribute on faults quite a while ago. Are you using Axis 1.0 or 1.1? Can you try 1.2?

[jira] Commented: (AXIS-2037) attachment temp files are not deleted

[ http://issues.apache.org/jira/browse/AXIS-2037?page=comments#action_12312544 ] Tom Jordahl commented on AXIS-2037: --- How do you suggest that Axis clean up these files? It is the responsiblity of the service or the client to remove the attachements when

[jira] Closed: (AXIS-1958) IncompatibleClassChangeError when running 1.2rc3 in SAP EP 6.40

[ http://issues.apache.org/jira/browse/AXIS-1958?page=all ] Tom Jordahl closed AXIS-1958: - Resolution: Invalid This is a classpath issue as commented above. IncompatibleClassChangeError when running 1.2rc3 in SAP EP 6.40

[jira] Commented: (AXIS-2026) wsdl2java does not generate array of wrappers for soapenc array nillable elements

[ http://issues.apache.org/jira/browse/AXIS-2026?page=comments#action_1 ] Tom Jordahl commented on AXIS-2026: --- I checked in a test case for this bug in test/wsdl/arrays. Check the Structure TypeTestCase.java file and change the fld2 from int[]

[jira] Closed: (AXIS-1972) The options specified in a deploy file cannot be accessed with JavaProvider

[ http://issues.apache.org/jira/browse/AXIS-1972?page=all ] Tom Jordahl closed AXIS-1972: - Resolution: Invalid closed per Dmytro's comment. The options specified in a deploy file cannot be accessed with JavaProvider

[jira] Resolved: (AXIS-2016) Bug in method for accessing SOAP-message header attributes with namespace

[ http://issues.apache.org/jira/browse/AXIS-2016?page=all ] Tom Jordahl resolved AXIS-2016: --- Resolution: Fixed Fix Version: 1.2.1 Applied patch. Thanks. Bug in method for accessing SOAP-message header attributes with namespace

[jira] Commented: (AXIS-2020) wsdl2java does not generate array of wrappers for array of nillable primitives

[ http://issues.apache.org/jira/browse/AXIS-2020?page=comments#action_66461 ] Tom Jordahl commented on AXIS-2020: --- But the Schema explicitly sets the nilable=true option on the both the element (fld1) and the type (intarr) so we need to map these to

[jira] Resolved: (AXIS-1955) Axis 1.2rc3 does not write derived types from abstract classes to wsdl

[ http://issues.apache.org/jira/browse/AXIS-1955?page=all ] Tom Jordahl resolved AXIS-1955: --- Resolution: Fixed Fix Version: 1.2.1 Applies the patch. Thanks. Axis 1.2rc3 does not write derived types from abstract classes to wsdl

[jira] Resolved: (AXIS-2019) Bug in getElementsByTagNameNS() method of SOAPDocumentImpl class

[ http://issues.apache.org/jira/browse/AXIS-2019?page=all ] Tom Jordahl resolved AXIS-2019: --- Resolution: Fixed Applied patch. Thanks! Bug in getElementsByTagNameNS() method of SOAPDocumentImpl class

[jira] Resolved: (AXIS-1525) xsd:group behavior is wrong

[ http://issues.apache.org/jira/browse/AXIS-1525?page=all ] Tom Jordahl resolved AXIS-1525: --- Resolution: Fixed Fix Version: 1.2.1 Looks like Venkat applied this patch on 5/20/2005. Marking as fixed. xsd:group behavior is wrong

[jira] Updated: (AXIS-1762) xs:list attributes do not deserialize

[ http://issues.apache.org/jira/browse/AXIS-1762?page=all ] Tom Jordahl updated AXIS-1762: -- Attachment: 1752-and-1762-diff.txt I am attaching an updated version of the patch for both this bug and 1752. This patch causes the test/wsdl/gateway functional

[jira] Updated: (AXIS-1752) xs:list attributes do not serialize

[ http://issues.apache.org/jira/browse/AXIS-1752?page=all ] Tom Jordahl updated AXIS-1752: -- Attachment: 1752-and-1762-diff.txt I am attaching an updated version of the patch for both this bug and 1762. This patch causes the test/wsdl/gateway functional

[jira] Commented: (AXIS-2020) wsdl2java does not generate array of wrappers for array of nillable primitives

[ http://issues.apache.org/jira/browse/AXIS-2020?page=comments#action_66487 ] Tom Jordahl commented on AXIS-2020: --- I am only seeing the first field become Integer with your patch Andrei. The second is still int[]. wsdl2java does not generate

[jira] Commented: (AXIS-2020) wsdl2java does not generate array of wrappers for array of nillable primitives

[ http://issues.apache.org/jira/browse/AXIS-2020?page=comments#action_66490 ] Tom Jordahl commented on AXIS-2020: --- This patch also causes the test/wsdl/datatypes test case to fail because of the ArrayOfInt complexType in the WSDL:

  1   2   >