[Axis2] Moving all the transports into a common modules

Hi all, Few months back we all agreed to move all commons transports (from Axis2 and Synapse) to a common module. As the first step of that I have moved all the Axis2 to transport into a common module in ws-commons [1]. In addition to that we have setup nightly builds from that modules. So now it

[jira] Commented: (AXIS2-3191) Failure when WSDL imports schema that imports other schemas from relative URLs

[ https://issues.apache.org/jira/browse/AXIS2-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633017#action_12633017 ] Chyi Pin Lim commented on AXIS2-3191: - This is a possible fix. I ran into a similar pr

Re: [AXIS2] Should JSON messages be considered as REST?

Hi Keith and all, This argument is based on the following assumption ( You know about assumptions, if you've watched "Under Siege 2" ;) ) Axis2 REST implementation is based on WSDL 2.0 HTTP Binding. At least this was the case, when I was implementing and sorry if the implementation is now changed

Re: [AXIS2] Should JSON messages be considered as REST?

Hi Keith, This solution will solve the JSON problem (if we consider JSON messages as REST, which I'll comment in a different email), but will not solve the more general question IMO. We have enabled to plug custom content types, and do we wanna restrict these custom types to always be either REST

[jira] Created: (AXIS2-4040) Web Service with Java generic type

Web Service with Java generic type -- Key: AXIS2-4040 URL: https://issues.apache.org/jira/browse/AXIS2-4040 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: wsdl Affects Versions: 1.4.1