Since there is a consensus that NonBlockingLocalTransportSender
doesn't work with a pure Axis2 setup, is not unit testable and is only
relevant for Synapse, the logical conclusion would be that it should
not be included in Axis2 but in Synapse.
Andreas
On Thu, Jun 16, 2011 at 08:43, Heshan Suriya
[
https://issues.apache.org/jira/browse/AXIS2-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050364#comment-13050364
]
Sagara Gunathunga commented on AXIS2-5063:
---
This is required few improvements a
[
https://issues.apache.org/jira/browse/AXIS2-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sagara Gunathunga reassigned AXIS2-5066:
-
Assignee: Sagara Gunathunga
> Provide support for complex type arrays.
> ---
[
https://issues.apache.org/jira/browse/AXIS2-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sagara Gunathunga resolved AXIS2-5063.
---
Resolution: Fixed
Fixed in r1136443.
> Provide support for complex object types.
> -
[
https://issues.apache.org/jira/browse/AXIS2-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sagara Gunathunga resolved AXIS2-5066.
---
Resolution: Fixed
This also fixed with AXIS2-5063.
> Provide support for complex typ
[
https://issues.apache.org/jira/browse/AXIS2-5065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sagara Gunathunga reassigned AXIS2-5065:
-
Assignee: Sagara Gunathunga
> Provide support for org.w3c.dom.Document in web se
Hello,
It often happens that a call to a REST service returns only an HTTP
status code. For example a POST to "http://foo/resources/create"; might
return 201 - resource created. The Axis client can't cope with this.
Respectively if I have an Axis2 REST service it seems there is no way
for my POJO
Forgot to add that in my particular use case I use JSON. It was pretty
easy to patch the JSON OMBuilder to return nothing but the rest of
Axis can't cope with that since the only thing to signify nothing is
to return null. There apparently is no such thing as an empty
OMElement to return out of OMB
We are currently using version 1.4 of axis2 and are looking to upgrade
1.6. Is this upgrade path supported, or would we first have to upgrade
to 1.5?
In version 1.6.0, were there any API changes that effect existing 1.4
APIs? Meaning we will have to modify existing code based on axis2 1.4
On Thu, Jun 16, 2011 at 9:32 PM, Heather Doone Nightingale
wrote:
>
> We are currently using version 1.4 of axis2 and are looking to upgrade 1.6.
> Is this upgrade path supported, or would we first have to upgrade to 1.5?
Better to upgrade to version 1.6.0 instead of 1.5.x.
>
> In version 1.6.
[
https://issues.apache.org/jira/browse/AXIS2-5072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050692#comment-13050692
]
Sagara Gunathunga commented on AXIS2-5072:
---
Can you attach a small sample to re
[
https://issues.apache.org/jira/browse/AXIS2-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050732#comment-13050732
]
Hudson commented on AXIS2-5067:
---
Integrated in Axis2 #809 (See [https://builds.apache.org/jo
[
https://issues.apache.org/jira/browse/AXIS2-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050733#comment-13050733
]
Hudson commented on AXIS2-5063:
---
Integrated in Axis2 #809 (See [https://builds.apache.org/jo
[
https://issues.apache.org/jira/browse/AXIS2-5072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050778#comment-13050778
]
Jason Tholstrup commented on AXIS2-5072:
Sure. Take the pojo example in the sampl
[
https://issues.apache.org/jira/browse/AXIS2-5072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050780#comment-13050780
]
Jason Tholstrup commented on AXIS2-5072:
Just realized that the title should be "m
15 matches
Mail list logo
