[jira] Closed: (AXISCPP-662) In NillableArrays test sever side Auto generated code have some error.

[ http://issues.apache.org/jira/browse/AXISCPP-662?page=all ] Chinthana Danapala closed AXISCPP-662: -- (Visible to axiscpp-developers) In NillableArrays test sever side Auto generated code have some error.

[jira] Commented: (AXISCPP-573) problem in setURI() API in IAttribute class

[ http://issues.apache.org/jira/browse/AXISCPP-573?page=comments#action_12312843 ] Dushshantha Chandradasa commented on AXISCPP-573: - Here the problem is that the method setURI (const AxisChar* uri) just set a string variable. The engine

[jira] Resolved: (AXISCPP-622) Support for the WSDL construct any

[ http://issues.apache.org/jira/browse/AXISCPP-622?page=all ] Chinthana Danapala resolved AXISCPP-622: Resolution: Fixed I have tested and seems to me any is working fine. According to definition of any construct implementation have done.

[jira] Commented: (AXISCPP-622) Support for the WSDL construct any

[ http://issues.apache.org/jira/browse/AXISCPP-622?page=comments#action_12312847 ] Chinthana Danapala commented on AXISCPP-622: I have tested and seems to me 'any' is working fine. According to definition of 'any' construct implementation has

[jira] Assigned: (AXISCPP-617) an exception occurs in running WS client

[ http://issues.apache.org/jira/browse/AXISCPP-617?page=all ] Chinthana Danapala reassigned AXISCPP-617: -- Assign To: Chinthana Danapala an exception occurs in running WS client Key:

[jira] Closed: (AXISCPP-580) Ability to run a single server side test in the server side test Automation

[ http://issues.apache.org/jira/browse/AXISCPP-580?page=all ] Chinthana Danapala closed AXISCPP-580: -- Resolution: Fixed (Visible to axiscpp-developers) Ability to run a single server side test in the server side test Automation

Deserializing attachments

Hi Rangika, From looking through the code, deserialization of a mime message seems to be missing. The SoapDeSerializer passes the SOAPTransport through to the XMLParser, but a MIME message is not XML. I will go ahead and implement this function, unless this is something that you have

[jira] Closed: (AXISCPP-573) problem in setURI() API in IAttribute class

[ http://issues.apache.org/jira/browse/AXISCPP-573?page=all ] Dushshantha Chandradasa closed AXISCPP-573: --- Fixed problem in setURI() API in IAttribute class --- Key: AXISCPP-573

[jira] Commented: (AXIS-2041) wsdl2java WSDL processing error [missing xmlns=http://schemas.xmlsoap.org/wsdl/]

[ http://issues.apache.org/jira/browse/AXIS-2041?page=comments#action_12312844 ] Roman Hrivik commented on AXIS-2041: oc4j is Oracle IAS application container but anyway it does not matter. the main thing is that if there is no

[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_12312867 ] Vladimir Ilmov commented on AXIS-1903: -- I have same exception in webLogic81 in axis 1.2 final release. IncompatibleClassChangeError when deploying Axis 1.2-RC3 on

[jira] Commented: (AXIS-1818) MessageElement [] for any doesn't include all elements

[ http://issues.apache.org/jira/browse/AXIS-1818?page=comments#action_12312864 ] Davanum Srinivas commented on AXIS-1818: yes. (for now) MessageElement [] for any doesn't include all elements

[jira] Updated: (AXIS-2041) wsdl2java WSDL processing error [missing xmlns=http://schemas.xmlsoap.org/wsdl/]

[ http://issues.apache.org/jira/browse/AXIS-2041?page=all ] Roman Hrivik updated AXIS-2041: --- Attachment: OplusWS.wsdl AXIS generated file via URL http://localhost:/OPlus/services/OplusWS?wsdl wsdl2java WSDL processing error [missing

[jira] Updated: (AXIS-2041) wsdl2java WSDL processing error [missing xmlns=http://schemas.xmlsoap.org/wsdl/]

[ http://issues.apache.org/jira/browse/AXIS-2041?page=all ] Roman Hrivik updated AXIS-2041: --- Attachment: oplus-ws-root-error.log log file after ANT task axis-wsdl2java pre target name=OplusWS.wsdl2java depends=prepare description=Generate Java sources

[jira] Commented: (AXIS-2041) wsdl2java WSDL processing error [missing xmlns=http://schemas.xmlsoap.org/wsdl/]

[ http://issues.apache.org/jira/browse/AXIS-2041?page=comments#action_12312877 ] Roman Hrivik commented on AXIS-2041: console output c:\eclipseProjects\oplus-ws\test-clientant OplusWS.wsdl2java Buildfile: build.xml prepare: [echo] prepare

[Axis][Castor] Changes in CastorSerializer.java

Title: Message Hello! Wonder if someone could tell me why the code in CastorSerializer has changed from using StringWriter tousing AxisContentHandler !? Anything wrong with using StringWriter !? Performance issues !? I had some trouble migrating to Axis 1.2 Final because

[jira] Created: (AXIS-2042) Premature end of file

Premature end of file - Key: AXIS-2042 URL: http://issues.apache.org/jira/browse/AXIS-2042 Project: Axis Type: Bug Versions: current (nightly) Environment: Tomcat 5.0 JDK142_05 Reporter: Tan Cuong Nguyen I am using axis-1_2_1 at

[Axis2]Axis2-M2:org.apache.axis.receivers.RawXMLINOnlyMessageRecevier

Hi, This is probably a cosmetic issue. However I thought of bringing it to the attention of Axis2 developers. I think the class org.apache.axis.receivers.RawXMLINOnlyMessageRecevier should be re-named to org.apache.axis.receivers.RawXMLINOnlyMessageReceiver, so that it will be consistent with

Re: [Axis][Castor] Changes in CastorSerializer.java

Can u please check the cvs commit log: http://cvs.apache.org/viewcvs.cgi/ws-axis/java/src/org/apache/axis/encoding/ser/castor/CastorSerializer.java thanks, dims On 6/7/05, Tysnes Are Thobias [EMAIL PROTECTED] wrote: Hello! Wonder if someone could tell me why the code in

Re: [Axis2]Axis2-M2:org.apache.axis.receivers.RawXMLINOnlyMessageRecevier

+1 On 6/7/05, Harsha Perera [EMAIL PROTECTED] wrote: Hi, This is probably a cosmetic issue. However I thought of bringing it to the attention of Axis2 developers. I think the class org.apache.axis.receivers.RawXMLINOnlyMessageRecevier should be re-named to

[jira] Commented: (AXIS-2041) wsdl2java WSDL processing error [missing xmlns=http://schemas.xmlsoap.org/wsdl/]

[ http://issues.apache.org/jira/browse/AXIS-2041?page=comments#action_12312885 ] Guillaume Sauthier commented on AXIS-2041: -- wsdl2java has nothing to do with your problem. Yes, the WSDL is not correct : - we need to add default namespace pointing

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

[ http://issues.apache.org/jira/browse/AXIS-119?page=comments#action_12312892 ] Guus Gerrits commented on AXIS-119: --- I am facing the same problems. I defined following simple wsString to make sure that no empty--Strings are sent into the Webservice. Also

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

Unable to omit element if nillable=true or minoccurs=0/maxoccurs=1 -- Key: AXIS2-24 URL: http://issues.apache.org/jira/browse/AXIS2-24 Project: Axis2 Type: Bug Components: engine Environment:

[ANN]AXIS2-M2 released

The Apache Axis2 Team is pleased to announce the second milestone release of Apache Axis2. You can download the releases from: http://cvs.apache.org/dist/axis/v2.0-M2/axis2-M2-src.zip http://cvs.apache.org/dist/axis/v2.0-M2/axis2-M2-bin.zip This milestone release has the following

[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

[EMAIL PROTECTED]: Project ws-axis (in module ws-axis) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project ws-axis has an issue affecting its community integration. This issue affects 1

[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-2041) wsdl2java WSDL processing error [missing xmlns=http://schemas.xmlsoap.org/wsdl/]

[ http://issues.apache.org/jira/browse/AXIS-2041?page=comments#action_12312865 ] Davanum Srinivas commented on AXIS-2041: Am suspecting that you are not using Xerces. can you please post the whole stack trace? wsdl2java WSDL processing error

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

[ http://issues.apache.org/jira/browse/AXIS-2026?page=all ] Hans updated AXIS-2026: --- Attachment: patch.txt Attached new patch.txt. Test failed because wrappers were also generated for arrays with element having minOccurs=0 which is incorrect. wsdl2java does

[jira] Commented: (AXIS-2029) SOAPHeader.appendChild() throws unexpected ClassCastException

[ http://issues.apache.org/jira/browse/AXIS-2029?page=comments#action_12312975 ] Mark Tye commented on AXIS-2029: Venkat, to the best of my knowledge, the 1.1 version of the SOAP spec makes no mention of whitespace or how it should be processed. In the

[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_12312976 ] Davanum Srinivas commented on AXIS-2026: Hans, Can i persuade you to run ant clean all-tests from ws-axis/java directory? there are more failures with latest patch.