[jira] Updated: (AXIS2C-1411) thread_unix and thread_windows inconsistency as for axutil_thread_exit

[ https://issues.apache.org/jira/browse/AXIS2C-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Mireaux updated AXIS2C-1411: - Attachment: util.patch Here is a patch for thread_unix.c to make it work like Windows

Re: [Axis2] Update to JAX-WS 2.2

Hi Dims, I'm interested in joining this axis-tck mailing list and getting access to the TCK. Could you please tell me the fax number to send this NDA? it's not there in the jcp page. And also I think we need some improvements in the JAXWS user guide as well. Isn't it? For example, it still says

[jira] Created: (AXIS2-4548) WSDL11ToAxisServiceBuilder ( client side) doesn't correctly build the bindings

WSDL11ToAxisServiceBuilder ( client side) doesn't correctly build the bindings -- Key: AXIS2-4548 URL: https://issues.apache.org/jira/browse/AXIS2-4548 Project: Axis 2.0

[jira] Assigned: (AXIS2-3817) JAXWS error occurs when invoking java-first service in RESTful manner

[ https://issues.apache.org/jira/browse/AXIS2-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Eranga Suriarachchi reassigned AXIS2-3817: Assignee: Isuru Eranga Suriarachchi JAXWS error occurs when

[jira] Resolved: (AXIS2-3817) JAXWS error occurs when invoking java-first service in RESTful manner

[ https://issues.apache.org/jira/browse/AXIS2-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Eranga Suriarachchi resolved AXIS2-3817. -- Resolution: Invalid Hi Charitha, As Charith has already pointed out,

Re: [Axis2] Update to JAX-WS 2.2

Looks like email to secret...@apache.org / fax to +1-919-573-9199 http://markmail.org/message/bz6q5oyjrj3hb37v The mailing list itself is: jaxws-tck AT incubator.apache.org (sorry i wrote the wrong address before) You may also want to join: (where you can ask questions on existing resources,

Re: [VOTE] Web Services Reorg Part 1 : Axis2 TLP

+1 Ruwan On Sun, Nov 8, 2009 at 11:36 PM, Bill Nagy n...@watson.ibm.com wrote: +1 -Bill On Fri, 2009-11-06 at 09:20 -0800, Glen Daniels wrote: Greetings, everyone. A bunch of us here at ApacheCon were talking about the Axis2 TLP idea, and how to move this forward in the simplest

Re: How to set SOAP Action using JAXWS dispatch client API?

Hi Isuru, You need to add some code similar to the following to your client, import javax.xml.ws.BindingProvider; MapString, Object map = dispatch.getRequestContext(); map.put(BindingProvider.SOAPACTION_USE_PROPERTY, Boolean.TRUE);

Re: [VOTE] Web Services Reorg Part 1 : Axis2 TLP

+1 Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where will you find the time to do it again? From: Glen Daniels g...@thoughtcraft.com To: gene...@ws.apache.org

Re: [VOTE] Web Services Reorg Part 1 : Axis2 TLP

Sorry for the delay +1 indeed Aj On Mon, Nov 9, 2009 at 1:11 PM, Ruwan Linton ruwan.lin...@gmail.com wrote: +1 Ruwan On Sun, Nov 8, 2009 at 11:36 PM, Bill Nagy n...@watson.ibm.com wrote: +1 -Bill On Fri, 2009-11-06 at 09:20 -0800, Glen Daniels wrote: Greetings, everyone. A

Axis2/Java 1.5.1 and Rampart 1.4 (no SoapFault returned)

Hi, we use a service with a plain userid/password. We use RAMPART to deal with this. In case the clients passes a wrong userid or password (or none at all) we get an ugly NullPointerException (see below) . No SOAP Response is returned (we check with SOAPMonitor). This is of course very

Re: [VOTE] Web Services Reorg Part 1 : Axis2 TLP

+1 Thanks, Ruchith On Fri, Nov 6, 2009 at 12:20 PM, Glen Daniels g...@thoughtcraft.com wrote: Greetings, everyone. A bunch of us here at ApacheCon were talking about the Axis2 TLP idea, and how to move this forward in the simplest and most effective way.  We came up with *exactly* the same

Re: How to set SOAP Action using JAXWS dispatch client API?

Hi Brian, Thanks. It works.. Do we have any documents on this kind of stuff? Thanks, ~Isuru On Mon, Nov 9, 2009 at 11:43 PM, Brian De Pradine prad...@uk.ibm.comwrote: Hi Isuru, You need to add some code similar to the following to your client, import javax.xml.ws.BindingProvider;