Re: [Axis2] Nigtly builds

I have uploaded the nightly builds here: http://people.apache.org/dist/axis2/nightly/c/ Samisa... Samisa Abeysinghe wrote: Deepal jayasinghe wrote: Hi Samisa, Like we are doing in Axis2/Java let's do the daily nightly builds for Axis2/C as well. Java guys are using Gump I suppose. I

[jira] Updated: (AXIS2C-609) NullPointerException generating WSDL with anonymous simple types

[ https://issues.apache.org/jira/browse/AXIS2C-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Voelkle updated AXIS2C-609: -- Attachment: test.wsdl From AXIS2-1867 NullPointerException generating WSDL with anonymous

[jira] Commented: (AXIS2-2417) unimplemented code in kernel module saaj SOAPPartImpl

[ https://issues.apache.org/jira/browse/AXIS2-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503756 ] sumedha rubasinghe commented on AXIS2-2417: --- Hi Mike, I could not get the test to run. Following is what I

[jira] Updated: (AXIS2-2118) Wrong action name using WS-Addressing

[ https://issues.apache.org/jira/browse/AXIS2-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brecht Yperman updated AXIS2-2118: -- Attachment: extractdata.wsdl This is the wsdl, I didn't generate any code myself, I used the

[jira] Updated: (AXIS2-2795) Axis2 generated stubs does not support saaj

[ https://issues.apache.org/jira/browse/AXIS2-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Franck HUGOT updated AXIS2-2795: Attachment: WSImpressionStub.java And here is the axis2 generated client. The GetFullDocument

AXIS2 XSI:TYPE and qualified namespaces Different SOAP request Body for JMS and HTTP why ?

Hi, I have the following schema for a Books type that I am testing AXIS2 against. I'm trying to run the SOAP JMS webservice. While HTTP request runs perfectly the JMS does not. I debugged it and found that AXIS2 is generating different request strings for JMS and HTTP. The xsi type is not

[jira] Reopened: (AXIS2-2775) nullpointer by invoking web service and RPCMessageReceiver problem

[ https://issues.apache.org/jira/browse/AXIS2-2775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haha reopened AXIS2-2775: - Thanks for your helps very much. I have no more those failures, but i don't know why, i guess, that the

[jira] Issue Comment Edited: (AXIS2-2775) nullpointer by invoking web service and RPCMessageReceiver problem

[ https://issues.apache.org/jira/browse/AXIS2-2775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503789 ] haha edited comment on AXIS2-2775 at 6/12/07 2:23 AM: -- Thanks for your helps very much. I have

[jira] Issue Comment Edited: (AXIS2-2775) nullpointer by invoking web service and RPCMessageReceiver problem

[ https://issues.apache.org/jira/browse/AXIS2-2775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503789 ] haha edited comment on AXIS2-2775 at 6/12/07 2:26 AM: -- Thanks for your helps very much. I have

[jira] Commented: (AXIS2-2554) Webservice client code is not able to contact server with IP address.

[ https://issues.apache.org/jira/browse/AXIS2-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503819 ] haha commented on AXIS2-2554: - I got the same Errors. i had started the server, the EPR is right too, but i cann't

[jira] Commented: (AXIS2-2571) SOAPAction mismatch invoking service

[ https://issues.apache.org/jira/browse/AXIS2-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503821 ] Jose Antonio commented on AXIS2-2571: - I developed the service I was writing in Muse using plain Axis2 and it

[jira] Commented: (AXIS2-2624) ~WSDL gets IP Addresses in ports instead of hostnames in release 1.2

[ https://issues.apache.org/jira/browse/AXIS2-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503851 ] Kevin Jin commented on AXIS2-2624: -- Thanks very much. I will give it try and let you know. ~WSDL gets IP

[jira] Created: (AXIS2-2796) NullPointerException in ADB serialization of optional attribute

NullPointerException in ADB serialization of optional attribute --- Key: AXIS2-2796 URL: https://issues.apache.org/jira/browse/AXIS2-2796 Project: Axis 2.0 (Axis2) Issue Type: Bug

[jira] Updated: (AXIS2-1754) Exceptions thrown by service methods are not propogated to clients properly.

[ https://issues.apache.org/jira/browse/AXIS2-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Kucypera updated AXIS2-1754: -- Attachment: ReceiverUtils.java Davanum Srinivas asked me to upload my patch for serializing

[jira] Updated: (AXIS2-2796) NullPointerException in ADB serialization of optional attribute

[ https://issues.apache.org/jira/browse/AXIS2-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Ananiev updated AXIS2-2796: Attachment: jira.zip Attached files that demonstrate the problem: WSDL/XSD, generated files + code

Re: [axis2] WSDL2Java / Java2WSDL and Faults (PLEASE CHIME IN?)

In my case, I was using the HTTP binding of WSDL2 and one operation had several faults with the same type. The way to distinguish them was by looking at the HTTP status code, as specified in the binding section. In the patch I submitted there were different classes for each fault and those

Re: [axis2] WSDL2Java / Java2WSDL and Faults (PLEASE CHIME IN?)

On 6/12/07, Dennis Sosnoski [EMAIL PROTECTED] wrote: I think it would be much cleaner to fix the code generation handling, so that the same exception can be used by multiple methods. Why complicate the interface with multiple classes for the same data? So my response to Glen's questions would

[jira] Commented: (AXIS2-2796) NullPointerException in ADB serialization of optional attribute

[ https://issues.apache.org/jira/browse/AXIS2-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503866 ] Oleg Ananiev commented on AXIS2-2796: - I have tried to run the same code with Axiom 1.2.4 and Axis 1.1.1 and got

[jira] Created: (AXIS2-2797) Do we send 400 and 500 status codes correctly?

Do we send 400 and 500 status codes correctly? -- Key: AXIS2-2797 URL: https://issues.apache.org/jira/browse/AXIS2-2797 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: transports

[jira] Reopened: (AXIS2-2642) Inconsistencies in getting engaged modules

[ https://issues.apache.org/jira/browse/AXIS2-2642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaliya Ekanayake reopened AXIS2-2642: - Better to return module references at all these cases. Inconsistencies in getting engaged

[Axis2][continuum] BUILD FAILURE

Online report : http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2301 Build statistics: State: Failed Previous State: Failed Started at: Tue, 12 Jun 2007 14:03:58 + Finished at: Tue, 12 Jun 2007 14:29:57 + Total

Re: [Axis2] Fixing blockers in Axis2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All I can say is it will come soon. We are working hard in this hackathon to get it. Please report any problems that you encounter using the current release. Thanks, Chinthaka Mark Badorrek wrote: Is there a target date for 1.3? Mark B

Re: [Axis2] Fixing blockers in Axis2

I suspect we'll know a lot more in a few days. :) --G Mark Badorrek wrote: Is there a target date for 1.3? Mark B From: Eran Chinthaka [mailto:[EMAIL PROTECTED] Sent: Tue 6/12/2007 5:32 AM To: axis-dev@ws.apache.org Subject: [Axis2] Fixing blockers in

Re: Axis2 contexts use unsyncronized HashMap instead of Hashtables

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ajith Ranabahu wrote: IIRC the flip side of the same argument was brought as a reason. Hashtables are slower than hashmaps due to the synching. In how many places do we have to synch if we just use the map ? if there are many I suggest we use the

[Axis2][continuum] BUILD FAILURE

Online report : http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2303 Build statistics: State: Failed Previous State: Failed Started at: Tue, 12 Jun 2007 15:09:18 + Finished at: Tue, 12 Jun 2007 15:41:43 + Total

[jira] Commented: (AXIS2-2796) NullPointerException in ADB serialization of optional attribute

[ https://issues.apache.org/jira/browse/AXIS2-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503890 ] Amila Chinthaka Suriarachchi commented on AXIS2-2796: - tried a sample program with your wsdl and

[jira] Commented: (AXIS2-2774) Lack of support for XML Schema Inheiritance

[ https://issues.apache.org/jira/browse/AXIS2-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503895 ] Amila Chinthaka Suriarachchi commented on AXIS2-2774: - can you have a look at with a nightly

[jira] Commented: (AXIS2-2755) Incomplete code generation with wsdl2java, in adb mode

[ https://issues.apache.org/jira/browse/AXIS2-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503896 ] Amila Chinthaka Suriarachchi commented on AXIS2-2755: - can you attach your wsdl? Incomplete

Re: [axis2] WSDL2Java / Java2WSDL and Faults (PLEASE CHIME IN?)

Amila Suriarachchi wrote: On 6/12/07, *Dennis Sosnoski* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I think it would be much cleaner to fix the code generation handling, so that the same exception can be used by multiple methods. Why complicate the interface with

[Axis2][continuum] BUILD FAILURE

Online report : http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2305 Build statistics: State: Failed Previous State: Failed Started at: Tue, 12 Jun 2007 16:31:22 + Finished at: Tue, 12 Jun 2007 17:04:52 + Total

[jira] Created: (AXIS2-2798) Soap action string mismatch does not prevent web service method from running.

Soap action string mismatch does not prevent web service method from running. - Key: AXIS2-2798 URL: https://issues.apache.org/jira/browse/AXIS2-2798 Project: Axis 2.0

Re: Axis2 contexts use unsyncronized HashMap instead of Hashtables

On 6/12/07, Eran Chinthaka [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ajith Ranabahu wrote: IIRC the flip side of the same argument was brought as a reason. Hashtables are slower than hashmaps due to the synching. In how many places do we have to synch if we just

[Axis2][continuum] BUILD FAILURE

Online report : http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2308 Build statistics: State: Failed Previous State: Failed Started at: Tue, 12 Jun 2007 18:03:00 + Finished at: Tue, 12 Jun 2007 18:29:07 + Total

[jira] Resolved: (AXIS2-1812) Running ant in quickstart sample folder fails to deploy the sample

[ https://issues.apache.org/jira/browse/AXIS2-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eran Chinthaka resolved AXIS2-1812. --- Resolution: Fixed Fixed all the scripts that I saw. It is strange that this was a JIRA for a

Re: Axis2 contexts use unsyncronized HashMap instead of Hashtables

We talked about this at the beginning .. and concluded that this was the right solution because synchronizing *EVERY* access was way overkill and would add a HUGE performance overhead. PLEASE don't change this unless (1) we have a problem that we're trying to solve and (2) we have some idea

[jira] Commented: (AXIS2-2327) RPCMessageReceiver; response envelope dose not serialize properly

[ https://issues.apache.org/jira/browse/AXIS2-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503976 ] Deepal Jayasinghe commented on AXIS2-2327: -- What I mean was its totaly depend on underline parser's

[jira] Resolved: (AXIS2-1649) Invocation with useSeparateListener option set will never complete if an error occurs in the outbound transport

[ https://issues.apache.org/jira/browse/AXIS2-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-1649. -- fixed in the current SVN Invocation with useSeparateListener option set will never

[jira] Commented: (AXIS2-1363) RPCInOutAsyncMessageReceiver mis behaviour

[ https://issues.apache.org/jira/browse/AXIS2-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503988 ] Srinath Perera commented on AXIS2-1363: --- After F2F discussion this is what we did. If addressing not present

[jira] Commented: (AXIS2-1134) Want to Store the MessageContext together with the OutputStream for later use

[ https://issues.apache.org/jira/browse/AXIS2-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503990 ] Srinath Perera commented on AXIS2-1134: --- I purposed not to support this. It is not clear how Output stream is

[jira] Commented: (AXIS2-2327) RPCMessageReceiver; response envelope dose not serialize properly

[ https://issues.apache.org/jira/browse/AXIS2-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503991 ] Eran Chinthaka commented on AXIS2-2327: --- I just checked Axiom with the following code and I don't see any

[jira] Commented: (AXIS2-2327) RPCMessageReceiver; response envelope dose not serialize properly

[ https://issues.apache.org/jira/browse/AXIS2-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503993 ] Eran Chinthaka commented on AXIS2-2327: --- Saminda, Can you please confirm the observation and comment or

[jira] Created: (AXIS2-2799) Improvements to module documentation page (http://ws.apache.org/axis2/modules/index.html) and subpages

Improvements to module documentation page (http://ws.apache.org/axis2/modules/index.html) and subpages -- Key: AXIS2-2799 URL:

[jira] Updated: (AXIS2-2799) Improvements to module documentation page (http://ws.apache.org/axis2/modules/index.html) and subpages

[ https://issues.apache.org/jira/browse/AXIS2-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glen Mazza updated AXIS2-2799: -- Attachment: moduledocpatch.txt Improvements to module documentation page

[Axis2][continuum] BUILD SUCCESSFUL

Online report : http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2311 Build statistics: State: Ok Previous State: Failed Started at: Tue, 12 Jun 2007 20:24:26 + Finished at: Tue, 12 Jun 2007 20:57:15 + Total time:

[jira] Resolved: (AXIS2-1363) RPCInOutAsyncMessageReceiver mis behaviour

[ https://issues.apache.org/jira/browse/AXIS2-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinath Perera resolved AXIS2-1363. --- Resolution: Fixed last comment RPCInOutAsyncMessageReceiver mis behaviour

[jira] Commented: (AXIS2-2696) namespaceURI problems when moving form Axis2 1.1.1 to Axis2 1.2

[ https://issues.apache.org/jira/browse/AXIS2-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504006 ] Jaliya Ekanayake commented on AXIS2-2696: - The namespace uri which maps to the

[jira] Created: (AXIS2-2800) Remove async message receivers

Remove async message receivers -- Key: AXIS2-2800 URL: https://issues.apache.org/jira/browse/AXIS2-2800 Project: Axis 2.0 (Axis2) Issue Type: Improvement Reporter: Glen Daniels Srinath was working

[jira] Updated: (AXIS2-2800) Remove async message receivers

[ https://issues.apache.org/jira/browse/AXIS2-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glen Daniels updated AXIS2-2800: Fix Version/s: 1.3 Remove async message receivers --

[jira] Commented: (AXIS2-1889) WSDL with relative imports fails with FileNotFoundException.

[ https://issues.apache.org/jira/browse/AXIS2-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504010 ] Eran Chinthaka commented on AXIS2-1889: --- I just looked at this problem and it seems the resolver is able to

Re: [axis2] WSDL2Java / Java2WSDL and Faults (PLEASE CHIME IN?)

On 6/12/07, Dennis Sosnoski [EMAIL PROTECTED] wrote: Amila Suriarachchi wrote: On 6/12/07, *Dennis Sosnoski* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I think it would be much cleaner to fix the code generation handling, so that the same exception can be used by

[jira] Resolved: (AXIS2-2797) Do we send 400 and 500 status codes correctly?

[ https://issues.apache.org/jira/browse/AXIS2-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eran Chinthaka resolved AXIS2-2797. --- Resolution: Fixed Fixed in r546640. Do we send 400 and 500 status codes correctly?

[jira] Assigned: (AXIS2-2797) Do we send 400 and 500 status codes correctly?

[ https://issues.apache.org/jira/browse/AXIS2-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eran Chinthaka reassigned AXIS2-2797: - Assignee: Eran Chinthaka Do we send 400 and 500 status codes correctly?

Re: [axis2] WSDL2Java / Java2WSDL and Faults (PLEASE CHIME IN?)

Amila Suriarachchi wrote: On 6/12/07, *Dennis Sosnoski* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: ...This should be changed so that there doesn't need to be a message data object type for faults with no content (corresponding to an exception that only provides an

[jira] Resolved: (AXIS2-2195) Expose module's classes outside of the module

[ https://issues.apache.org/jira/browse/AXIS2-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-2195. -- Resolution: Fixed We can not implement this , since module get its own class loader so

[jira] Updated: (AXIS2-2780) Multiple MAR files written to temp dir - could cause hard disk to fill up

[ https://issues.apache.org/jira/browse/AXIS2-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe updated AXIS2-2780: - Priority: Blocker (was: Major) Multiple MAR files written to temp dir - could cause

[jira] Assigned: (AXIS2-2800) Remove async message receivers

[ https://issues.apache.org/jira/browse/AXIS2-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-2800: Assignee: Glen Daniels Remove async message receivers

[jira] Assigned: (AXIS2-2796) NullPointerException in ADB serialization of optional attribute

[ https://issues.apache.org/jira/browse/AXIS2-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-2796: Assignee: Amila Chinthaka Suriarachchi NullPointerException in ADB serialization

[jira] Assigned: (AXIS2-2795) Axis2 generated stubs does not support saaj

[ https://issues.apache.org/jira/browse/AXIS2-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-2795: Assignee: Amila Chinthaka Suriarachchi Axis2 generated stubs does not support

[jira] Assigned: (AXIS2-2799) Improvements to module documentation page (http://ws.apache.org/axis2/modules/index.html) and subpages

[ https://issues.apache.org/jira/browse/AXIS2-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-2799: Assignee: Chatra Nakkawita Improvements to module documentation page

[jira] Assigned: (AXIS2-2798) Soap action string mismatch does not prevent web service method from running.

[ https://issues.apache.org/jira/browse/AXIS2-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-2798: Assignee: Deepal Jayasinghe Soap action string mismatch does not prevent web

[jira] Resolved: (AXIS2-1598) minimize response from RPCMessageReceiver

[ https://issues.apache.org/jira/browse/AXIS2-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-1598. -- Resolution: Fixed fixid in current SVN minimize response from RPCMessageReceiver

[jira] Resolved: (AXIS2-2603) Java2WSDL does not generate hierarchy if father class is not present in any service operation

[ https://issues.apache.org/jira/browse/AXIS2-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-2603. -- Resolution: Fixed fixed in the current svn and I got the following WSDL ?xml

[Axis2][continuum] BUILD FAILURE

Online report : http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2316 Build statistics: State: Failed Previous State: Ok Started at: Wed, 13 Jun 2007 00:07:17 + Finished at: Wed, 13 Jun 2007 00:38:28 + Total time:

Re: [Axis2][continuum] BUILD FAILURE

The build is working fine in my machine. Thanks Deepal davidillsley (Continuum) wrote: Online report : http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2316 Build statistics: State: Failed Previous State: Ok Started

[Axis2][continuum] BUILD SUCCESSFUL

Online report : http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2318 Build statistics: State: Ok Previous State: Failed Started at: Wed, 13 Jun 2007 01:24:56 + Finished at: Wed, 13 Jun 2007 02:08:47 + Total time:

[Axis2] Feedback on Axis2

James, Just saw your feedback on Axis2 [1]. we (Axis2 team) are working hard to cleanup the api etc. We are working on a F2F/hackathon actually this week and any information on specific issues you saw would be extremely helpful. Can you please send a bit more specific information so that we can

java.lang.reflect.InvocationTargetException

Hi All: I am using Tomcat 5.5, Axis 1.4, and myEclipse 5.5. I am new to java web services and Axis. I am trying an example from the book Beginning Java Web Services by Henry Bequet. This is the Stock Quote example on Chapter 3 page 113. When I tried the following