On Wed, Jan 4, 2012 at 7:57 PM, Andreas Veithen
wrote:
> I think it is useful to summarize a bit the discussion at this point.
>
> We have identified two approaches to address the SOAP infoset vs. JSON
> question:
>
> 1. As Amila suggests in his last post, put a dummy SOAP envelope in
> the messag
[
https://issues.apache.org/jira/browse/AXIS-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180680#comment-13180680
]
Jimmy Shah commented on AXIS-2624:
--
I am facing the same issue. I am getting a response ba
[
https://issues.apache.org/jira/browse/AXIS-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS-2538:
--
Fix Version/s: 1.4.1
Assignee: Andreas Veithen
The JAX-RPC spec is indeed very clear ab
OK, the client code that generates *two different signatures* but
transports the equivalent thing over the network is:
*DOOM enabled*
public class BinaryClient {
public static void main(String[] args) throws Exception {
ConfigurationContext ctx =
ConfigurationContextFactory.createCo
Hi devs,
I have been looking at deploying multiple spring services as AAR's within a
single axis2 container. Current issue with adding multiple service is that
when we add a second service, the first one does not work or rather the
deployment of the second service breaks the first. This is because
