[jira] Updated: (AXIS2-4838) Code-generation failure in wsdl documents for complex types with null sequence

[ https://issues.apache.org/jira/browse/AXIS2-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udayanga Wickramasinghe updated AXIS2-4838: --- Attachment: WSDL2javacodegen.patch i attached the following patch to resolve

Axis 1.4 add support for NTLMv2

Hi allI am trying to make Axis 1.4 communicate with NTLMv2 authentication web service,Because internal Axis Imple uses HttpClient that doesn't support NTLMv2 I am considering a commercial library (called Jespa) .As far as I understand I will have to replace the transport impl in client-config.

[jira] Created: (AXIS2-4839) Wrong wsa:Action on Fault messages

Wrong wsa:Action on Fault messages -- Key: AXIS2-4839 URL: https://issues.apache.org/jira/browse/AXIS2-4839 Project: Axis2 Issue Type: Bug Components: Addressing, jaxws Reporter: Brian De

[jira] Updated: (AXIS2-4839) Wrong wsa:Action on Fault messages

[ https://issues.apache.org/jira/browse/AXIS2-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian DePradine updated AXIS2-4839: --- Attachment: patch.txt Patch supplied. > Wrong wsa:Action on Fault messages > ---

Re: Axis 1.4 add support for NTLMv2

2010/10/7 Sharon H : > Hi all > I am trying to make Axis 1.4  communicate with NTLMv2 authentication web > service, > Because internal Axis Imple uses HttpClient that doesn't support NTLMv2 I am > considering a commercial library (called Jespa) . > As far as I understand I will have to replace the

[jira] Closed: (AXIS2-4823) Error "Address is invalid on local machine..." occurs when http.proxyHost is "" (blank) instead of null.

[ https://issues.apache.org/jira/browse/AXIS2-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dzung Tran closed AXIS2-4823. - Resolution: Not A Problem This was due to another software that was setting the proxy variables incorrec

RE: Axis 1.4 add support for NTLMv2

Hi Sharon, If you implemented the appropriate interface (BasicHandler), then this should do the trick. You should compare the difference between the two implementations of HTTPSender that we have in the tree, but implementing invoke() is about all Axis needs. Tom Jordahl From: Sharon H [mail

RE: Plan for updating axis(yes it is axis 1 not 2)

Hi dilly, If you are interested in taking on a caretaker role for Axis 1.x, I can give you a hand. If you have changes (and tests!) that you want to check in to the trunk, I could do that for you, then we can get you committer status so you could then do that on your own. Note that the tentat

Re: Plan for updating axis(yes it is axis 1 not 2)

Thank you for reply, Tom :) Yes axis 1 has a long history, and now there is axis2(also xfire, etc.) for web service. But axis 1 still has its value, as I insist. For one thing, the web server with jdk 1.4 or lower needs it, as I mentioned before, for another, Eclipse 3.5 J2EE formally support

Re: Axis 1.4 add support for NTLMv2

I just tried that mailing list, and was told to come here by an auto-generated reply like the followiing: : This mailing list has moved to java-user at axis.apache.org. So here is the only cabin for axiser to go -_-! dilly(Ma Yu) Shanghai, China 于 2010-10-8 1:28, robert lazarski 写道: 2010/1

[jira] Assigned: (AXIS2-4840) Need a way to specify weather we need to cache the HttpClient in CommonsHTTPTransportSender configuration

[ https://issues.apache.org/jira/browse/AXIS2-4840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Kamburugamuva reassigned AXIS2-4840: -- Assignee: Supun Kamburugamuva > Need a way to specify weather we need to cache

[jira] Created: (AXIS2-4840) Need a way to specify weather we need to cache the HttpClient in CommonsHTTPTransportSender configuration

Need a way to specify weather we need to cache the HttpClient in CommonsHTTPTransportSender configuration - Key: AXIS2-4840 URL: https://issues.apache.org/jira