On Wednesday 29 September 2010 11:51:04 am Andrew Dinn wrote:
> Hi Dan,
>
> Thanks for the explanation. I have a few comments inline.
>
> On 09/29/2010 02:54 PM, Daniel Kulp wrote:
> > 1) JAX-WS async client callbacks. We need to correlate the incoming
> > message with the outgoing request so w
Hi Dan,
Thanks for the explanation. I have a few comments inline.
On 09/29/2010 02:54 PM, Daniel Kulp wrote:
1) JAX-WS async client callbacks. We need to correlate the incoming message
with the outgoing request so we can figure out which call back object to call.
This correlation could potent
On Wednesday 29 September 2010 4:53:25 am Andrew Dinn wrote:
> Hi Dan,
>
> I am afraid I have much shallower knowledge of the CXF code than
> Alessio so I hope you will forgive me asking a rather simple-minded
> question. Could you explain why CXF needs to perform correlation of
> outgoing reques
Hi Dan,
I am afraid I have much shallower knowledge of the CXF code than
Alessio so I hope you will forgive me asking a rather simple-minded
question. Could you explain why CXF needs to perform correlation of
outgoing requests and incoming responses?
regards,
Andrew Dinn
---
On 0
Hi Alessio,
On 09/29/2010 10:24 AM, Alessio Soldano wrote:
I actually had a brief chat about this with Dan yesterday. The main
reason seems to be in WS-RM needs, but I still need to look at the
details (to understand what actually needs to be copied from one
exchange to the other). Besides that,
Hi Andrew,
I actually had a brief chat about this with Dan yesterday. The main
reason seems to be in WS-RM needs, but I still need to look at the
details (to understand what actually needs to be copied from one
exchange to the other). Besides that, there're probably other
requirements related
On Tuesday 28 September 2010 7:26:24 am Alessio Soldano wrote:
> Hi Dan,
>
> On 09/27/2010 08:25 PM, Daniel Kulp wrote:
> > Hmm. I wonder if we can tackle some of these things kind of piece
> > meal, in steps:
> >
> > 1) Scenario one is a single Bus, but multiple MAPCodec's. This should
On Tuesday 28 September 2010 9:09:56 am Alessio Soldano wrote:
> Hi,
>
> On 09/28/2010 01:26 PM, Alessio Soldano wrote:
> >> similar to (1), but the storage could be pre-configured and shareable.
> >
> > 2) Scenario two is a single JVM/classlaoder with multiple bus's. This is
> > Yes. Btw this
Hi,
On 09/28/2010 01:26 PM, Alessio Soldano wrote:
similar to (1), but the storage could be pre-configured and shareable.
2) Scenario two is a single JVM/classlaoder with multiple bus's. This is
Yes. Btw this is more or less the scenario we're on right now, as we
could have this storage as a
Hi Dan,
On 09/27/2010 08:25 PM, Daniel Kulp wrote:
Hmm. I wonder if we can tackle some of these things kind of piece meal,
in steps:
1) Scenario one is a single Bus, but multiple MAPCodec's. This should be
fairly easy. If the MAPCodec stores it's storage map as a property on the
Bus,
On Monday 27 September 2010 4:42:55 am Andrew Dinn wrote:
> On 09/24/2010 07:58 PM, Daniel Kulp wrote:
> > I'm not sure I understand. Does the RelatesTo on the response properly
> > match the message id of the request? If so, why is the MAPCodec not
> > able to correlate the message?
>
> The pr
On 09/24/2010 07:58 PM, Daniel Kulp wrote:
I'm not sure I understand. Does the RelatesTo on the response properly match
the message id of the request? If so, why is the MAPCodec not able to
correlate the message?
The problem is that when using ReplyTo/FaultTo the response may be sent
from o
Hi Dan,
On 09/24/2010 08:58 PM, Daniel Kulp wrote:
I'm not sure I understand. Does the RelatesTo on the response properly match
the message id of the request?
Yes, it does; here is an example of request and response:
POST /wstf/sc003/Sc003Service HTTP/1.1
xmlns:soap="http://schemas.xmlsoap
I'm not sure I understand. Does the RelatesTo on the response properly match
the message id of the request? If so, why is the MAPCodec not able to
correlate the message?
I guess my concern is around a potential memory leak if the MAPCodec is
holding onto messages waiting for a response. B
Hi,
I'm currently dealing with an application meant for testing the
scenarios defined by WSTF (http://www.wstf.org/). The application uses
JBossWS-CXF, currently leveraging Apache CXF trunk.
The third scenario of those WSTF tests is about WS-Addressing
interoperability, see http://www.wstf.org
15 matches
Mail list logo
