Problem with Polymorphic data types with ADB stubs on client side and RPC*MessageReceiver on Server side.

Hi, I have an existing spring framework based Java application where-in the services were exposed as web services using Axis 1.3. Now we are migrating the same to Axis2 1.4.1. I have used the RPC*MessageReceiver classes for my MEPs and instead of service implementation class parameter

Which WSDL version

Hello, How to know which version of WSDL (1.1 or 2.0) is generated by Axis ? Thank You.

Re: Which WSDL version

Hi, ?wsdl generates WSDL 1.1 while ?wsdl2 generates WSDL 2.0. Thanks, Keith. On Thu, Apr 23, 2009 at 2:09 PM, Rudy rud...@gmail.com wrote: Hello, How to know which version of WSDL (1.1 or 2.0) is generated by Axis ? Thank You. -- Keith Chapman Senior Software Engineer WSO2 Inc.

Re: Which WSDL version

Ok thank you. 2009/4/23 keith chapman keithgchap...@gmail.com Hi, ?wsdl generates WSDL 1.1 while ?wsdl2 generates WSDL 2.0. Thanks, Keith. On Thu, Apr 23, 2009 at 2:09 PM, Rudy rud...@gmail.com wrote: Hello, How to know which version of WSDL (1.1 or 2.0) is generated by Axis ?

Re: Problem with Polymorphic data types with ADB stubs on client side and RPC*MessageReceiver on Server side.

Hi, it goes against the philosophy of web services to become dependent on java packages or .net assemblies or whatever. it is essential that a classname within a soap-message is NOT relied upon for communication purposes to have a special meaning within a certain framework. you would kill

[jira] Created: (AXIS2-4321) Generated axis2.war gives AxisAdminServlet not found when trying to administer through web interface

Generated axis2.war gives AxisAdminServlet not found when trying to administer through web interface Key: AXIS2-4321 URL:

[jira] Commented: (AXIS2-4320) Error when running an Axis2 client code

[ https://issues.apache.org/jira/browse/AXIS2-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12701865#action_12701865 ] Maria Claribelle Loto commented on AXIS2-4320: -- Hi Guys, Anyone who have an

Missing org.apache.axis2.transport.tcp.TCPTransportSender into Axis2 1.5 RC

Hi everybody, I found out that we are missing the org.apache.axis2.transport.tcp.TCPTransportSender class into the distribution. You can check that pretty easy. Just deploy the axis2-1.5-war in Tomcat. Before that you should go and modify the axis2\WEB-INF\conf\axis2.xml and uncomment the:

[jira] Updated: (AXIS2-4313) Some MTOMPolicy module improvements are not merged to Axis2 1.5 branch

[ https://issues.apache.org/jira/browse/AXIS2-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dobri Kitipov updated AXIS2-4313: - Attachment: MTOMOutHandler_setDoingMTOM.patch Attaching a fix for the optional scenario. Some

[jira] Created: (AXIS2-4322) Cannot connect via NTLM proxy on Mac machine.

Cannot connect via NTLM proxy on Mac machine. - Key: AXIS2-4322 URL: https://issues.apache.org/jira/browse/AXIS2-4322 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: transports

[jira] Updated: (AXIS2-4323) Performance Imporvement when using JAX-WS ProviderOM

[ https://issues.apache.org/jira/browse/AXIS2-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker updated AXIS2-4323: - Attachment: patch_apache.txt Attached is the patch for this change. Performance Imporvement

[jira] Created: (AXIS2-4323) Performance Imporvement when using JAX-WS ProviderOM

Performance Imporvement when using JAX-WS ProviderOM -- Key: AXIS2-4323 URL: https://issues.apache.org/jira/browse/AXIS2-4323 Project: Axis 2.0 (Axis2) Issue Type: Improvement

[jira] Resolved: (AXIS2-4323) Performance Imporvement when using JAX-WS ProviderOM

[ https://issues.apache.org/jira/browse/AXIS2-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker resolved AXIS2-4323. -- Resolution: Fixed Issue resolved with svn revision #767971 Performance Imporvement when

[jira] Work started: (AXIS2-4323) Performance Imporvement when using JAX-WS ProviderOM

[ https://issues.apache.org/jira/browse/AXIS2-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AXIS2-4323 started by Nikhil Thaker. Performance Imporvement when using JAX-WS ProviderOM --

[jira] Closed: (AXIS2-4323) Performance Imporvement when using JAX-WS ProviderOM

[ https://issues.apache.org/jira/browse/AXIS2-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker closed AXIS2-4323. Performance Imporvement when using JAX-WS ProviderOM

[jira] Created: (AXIS2-4324) setenv.sh - extended shell functionality used where /bin/sh specified

setenv.sh - extended shell functionality used where /bin/sh specified - Key: AXIS2-4324 URL: https://issues.apache.org/jira/browse/AXIS2-4324 Project: Axis 2.0 (Axis2)