[jira] Created: (AXIS2-54) Client not able to read the response sent by Axis on Tomcat (platform: Solaris SPARC)

Client not able to read the response sent by Axis on Tomcat (platform: Solaris SPARC) - Key: AXIS2-54 URL: http://issues.apache.org/jira/browse/AXIS2-54 Project: Apache Axis 2.0 (Axis2)

[jira] Resolved: (AXIS2-27) web.xml contained in M2-bin-zip's axis2.war caused tomcat parse error

[ http://issues.apache.org/jira/browse/AXIS2-27?page=all ] Srinath Perera resolved AXIS2-27: - Resolution: Fixed Fixed. Thanks Ajith > web.xml contained in M2-bin-zip's axis2.war caused tomcat parse error > --

[jira] Resolved: (AXIS2-44) Axis2 fault Handling need to be improved

[ http://issues.apache.org/jira/browse/AXIS2-44?page=all ] Srinath Perera resolved AXIS2-44: - Resolution: Fixed Fixed, thanks Eran > Axis2 fault Handling need to be improved > > > Key: AXIS2-44 >

[jira] Closed: (AXIS2-22) Need for Child API in OMDocument

[ http://issues.apache.org/jira/browse/AXIS2-22?page=all ] Jayachandra Sekhara Rao Sunkara closed AXIS2-22: Resolution: Fixed child API added into OMDocument. Done > Need for Child API in OMDocument > ---

[jira] Resolved: (AXIS2-14) No-namespace element not serialized

[ http://issues.apache.org/jira/browse/AXIS2-14?page=all ] Srinath Perera resolved AXIS2-14: - Resolution: Fixed verified that it is fixed, closing the isue > No-namespace element not serialized > --- > > Key

[jira] Commented: (AXIS2-22) Need for Child API in OMDocument

[ http://issues.apache.org/jira/browse/AXIS2-22?page=comments#action_12314733 ] Eran Chinthaka commented on AXIS2-22: - Jaya, Ashu, I think you have fixed this. Please close this bug, if its done. Chinthaka > Need for Child API in OMDocument >

[jira] Commented: (AXIS2-44) Axis2 fault Handling need to be improved

[ http://issues.apache.org/jira/browse/AXIS2-44?page=comments#action_12314732 ] Eran Chinthaka commented on AXIS2-44: - These are things that has to be done by the Fault initiator within Axis2 engine; 1. create SOAPFaultCode (mandatory), SOAPFaultReaso

[jira] Assigned: (AXIS2-41) XMLBeans data Binding support for Stubs and Skeltons

[ http://issues.apache.org/jira/browse/AXIS2-41?page=all ] Srinath Perera reassigned AXIS2-41: --- Assign To: Ajith Harshana Ranabahu (was: Dasarath Weeratunge) Assign the issue to the Ajith who is working on the issue > XMLBeans data Binding support fo

Re: [Axis2]formalities of 0.9 relase

Thanks dims .. will set up the wiki and send a note --Srinath On 6/30/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Please gather the information from the following sources. > > http://jakarta.apache.org/commons/releases/prepare.html > http://jakarta.apache.org/commons/releases/release.html >

Re: [Axis2]formalities of 0.9 relase

Please gather the information from the following sources. http://jakarta.apache.org/commons/releases/prepare.html http://jakarta.apache.org/commons/releases/release.html http://wiki.apache.org/incubator/ReleaseManager http://wiki.apache.org/jakarta/ReleaseManager http://ws.apache.org/juddi/committ

[Axis2]formalities of 0.9 relase

Hi Dims; Does the relase steps of 0.9 should be differed from the M2. For an example we did not sign the M2 relase. Should we need to do it for 0.9? Is there a place where I can find the steps I need to follow before relase 0.9? Thanks Srinath

[jira] Updated: (AXIS-2054) Axis sends xsi:nil for non-nillable, minOccurs=0 parameters

[ http://issues.apache.org/jira/browse/AXIS-2054?page=all ] Dave Marquard updated AXIS-2054: Attachment: omit-parameter-patch-v2.txt Attaching v2 of the patch. This fixes the all-tests failures that Dims noted last week. The new version of the patch do

[jira] Updated: (AXIS-2054) Axis sends xsi:nil for non-nillable, minOccurs=0 parameters

[ http://issues.apache.org/jira/browse/AXIS-2054?page=all ] Dave Marquard updated AXIS-2054: Attachment: omit-parameter-test.zip New test case for omit vs nillable parameter behavior. Adds a new test/wsdl/omitParameter/ test case. > Axis sends xsi:nil

Re: Patch for non-nillable, optional parameters (AXIS-2054)

I've fixed the test case failure below and uploaded a new version of the patch to the issue. I've also added a new test case to verify the desired "omit vs. add xsi:nil=true" behavior. ant all-tests now passes for me. Patch and test case available at http://issues.apache.org/jira/browse/AXIS-2054

Re: Client insists on sending xsi type

It depends what the WSDL says... If the WSDL defines the type as http://www.something.com/schema/20050101}QueueName and the application instead sends xsd:string, then Axis is *required* to send the xsi:type information. If the WSDL defines the type as xsd:string, then it might be a bug. Anne On

Re: [Axis2] JavaOne Presentation

Very nice presentation .. but we really have to get you to stop talking about handlers and to talk about modules .. and *then* handlers ;-). Other way around, dude. :) This was a room full of people who all understood Axis 1, and were in general already grokking the handler chain idea. So yo

RE: Client insists on sending xsi type

Title: RE: Client insists on sending xsi type Workaround found: The generated proxy code contained this line (word "something" was substituted for the real name):     elemField.setXmlType(new javax.xml.namespace.QName("http://www.something.com/schema/20050101", "QueueName")); When

[jira] Created: (AXIS-2094) Message.getMessageType() returns null

Message.getMessageType() returns null - Key: AXIS-2094 URL: http://issues.apache.org/jira/browse/AXIS-2094 Project: Apache Axis Type: Bug Versions: 1.2 Environment: eclipse/windows/tomcat Reporter: Jeff Saremi Prio

[jira] Created: (AXIS-2093) XPathAPI cannot find namespace nodes in Axis dom

XPathAPI cannot find namespace nodes in Axis dom Key: AXIS-2093 URL: http://issues.apache.org/jira/browse/AXIS-2093 Project: Apache Axis Type: Bug Versions: 1.2.1 Environment: Xerces 2.6.2, Xalan 2.6.0, Websph

[jira] Commented: (AXIS2-53) Binding service operations to wsa:Action

[ http://issues.apache.org/jira/browse/AXIS2-53?page=comments#action_12314678 ] Srinath Perera commented on AXIS2-53: - Yes this is a shortcomming of the corrent impl. +1 for fix this. But shall we make this post 0.9.? > Binding service operations to ws

[jira] Created: (AXIS-2092) developers-guide.html and reference.html are still refering axis.jar for log4j.properties

developers-guide.html and reference.html are still refering axis.jar for log4j.properties - Key: AXIS-2092 URL: http://issues.apache.org/jira/browse/AXIS-2092 Project: Apache Axis

[jira] Commented: (AXIS2-42) Message Context Serialization Support

[ http://issues.apache.org/jira/browse/AXIS2-42?page=comments#action_12314677 ] Saminda Wishwajith Abeyruwan commented on AXIS2-42: --- Serialization and Deserialization of Message Context work perfectly with standard Serialization of java. T

[jira] Created: (AXIS2-53) Binding service operations to wsa:Action

Binding service operations to wsa:Action Key: AXIS2-53 URL: http://issues.apache.org/jira/browse/AXIS2-53 Project: Apache Axis 2.0 (Axis2) Type: Improvement Components: core Reporter: Ruchith Fernando An operations s

Axis client endpoint resolving.

Title: Axis client endpoint resolving. Hi, I have generated a client using WSDL2JAVA. I want to implement a retry mechanism for using the webservice. My endpoint url contains a hostname. Does any one know if the hostname resolving is cached ? How can I achieve the hostname to be resolved

[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 85 p

[jira] Updated: (AXIS2-48) SOAP Encoding support

[ http://issues.apache.org/jira/browse/AXIS2-48?page=all ] Srinath Perera updated AXIS2-48: Component: databinding (was: core) > SOAP Encoding support > - > > Key: AXIS2-48 > URL: http://issues.apa

[jira] Updated: (AXIS2-41) XMLBeans data Binding support for Stubs and Skeltons

[ http://issues.apache.org/jira/browse/AXIS2-41?page=all ] Srinath Perera updated AXIS2-41: Component: databinding > XMLBeans data Binding support for Stubs and Skeltons > > > Key: AXIS2-41 >

[jira] Updated: (AXIS2-12) AXIS2: pluggable XML transformations (JavaBeans2XML, XSD with JaxMe/JAXB, Castor, XmlBeans, RelaxNG, ...)

[ http://issues.apache.org/jira/browse/AXIS2-12?page=all ] Srinath Perera updated AXIS2-12: Component: databinding > AXIS2: pluggable XML transformations (JavaBeans2XML, XSD with JaxMe/JAXB, > Castor, XmlBeans, RelaxNG, ...) > --

[jira] Updated: (AXIS2-52) Simple mail server for Axis2 and simple mailet implementation

[ http://issues.apache.org/jira/browse/AXIS2-52?page=all ] Srinath Perera updated AXIS2-52: Component: transports (was: core) > Simple mail server for Axis2 and simple mailet implementation > ---

[jira] Updated: (AXIS2-32) writing a maillet for Mail transport

[ http://issues.apache.org/jira/browse/AXIS2-32?page=all ] Srinath Perera updated AXIS2-32: Component: transports (was: core) > writing a maillet for Mail transport > > > Key: AXIS2-32 >

[jira] Updated: (AXIS2-47) JMS transport for Axis2

[ http://issues.apache.org/jira/browse/AXIS2-47?page=all ] Srinath Perera updated AXIS2-47: Component: transports (was: core) > JMS transport for Axis2 > --- > > Key: AXIS2-47 > URL: http://issues.

[jira] Resolved: (AXIS2-34) Commons transport sender for Axis2

[ http://issues.apache.org/jira/browse/AXIS2-34?page=all ] Srinath Perera resolved AXIS2-34: - Resolution: Fixed Checked in the code submitted by sumnda and add a test cases > Commons transport sender for Axis2 > -- >

[jira] Commented: (AXIS-2091) Namespaces dissappear when they appeared before

[ http://issues.apache.org/jira/browse/AXIS-2091?page=comments#action_12314673 ] Venkat Reddy commented on AXIS-2091: I think the namespace declaration gets stripped off because its not used. -venkat > Namespaces dissappear when they appeared before >

[jira] Commented: (AXIS-2081) use SOAPEnvelope.getChildElements() get multi SOAPBody objects

[ http://issues.apache.org/jira/browse/AXIS-2081?page=comments#action_12314672 ] Venkat Reddy commented on AXIS-2081: Couldn't reproduce the issue. I've deployed samples\userguide\example2\Calulator.java and ran your test case. I got the following outp

Re: Debugging Axis tests

You should take a look at targets.xml I add some jvmargs to launch the tests for remote debugging target : component-junit-functional (client side JVM) inside the junit task : target : start-functional-test-http-server (server side JVM) inside the java task : Sometimes, axis tests are runn