my +1.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On February 15, 2014 at 10:02:19 AM, Daniel Kulp (
Hi Dennis,
This would be a great improvement. From the field there are concerns about
the fact that they want to have hard prove that the message was delivered
and they want to have their own administration of acknowledgement states.
Of course they should rely on the protocol but in most cases the
I guess the question is whether we want to duplicate the JMX
functionality. My thought was to keep this callback really simple, but
still supply the essential information (basically, that the message has
made it through to the far end) to the client. I suppose it would be
easy enough to add ano
+1.
Colm.
On Mon, Feb 17, 2014 at 4:13 AM, Freeman Fang wrote:
> +1
> －
> Freeman(Yue) Fang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
>
>
>
> On 2014-2-15, at 上午10:01, Daniel Kulp wrote:
>
> >
> > This is a vote to release 3.0.0-milestone2
> >
> > This has a bunch of mor
Hi Dennis,
right. It would be useful to make some information conveniently
available to the calling client.
But we might want to provide a callback not just for getting the ack
status but for getting various other WS-RM information such as the
sequence ID, message number and even some control ove
