jsr343-experts@jms-spec.java.net

[jsr343-experts] Re: (JMS_SPEC-39) Make clientId optional when creating a durable subscription

From: Clebert Suconic <clebert.suconic_at_gmail.com>
Date: Thu, 15 Sep 2011 09:38:56 -0500

I understand the API would be compatible. On this case the semantic
will change a little bit.

To pass the TCK 1.1, we would need to make exceptional conditions on
our implementations to also support the old behaviour and to throw the
proper exceptions for the TCK 1.1. And I'm a bit concerned about the
cleaning state of my implementation. (what will be the same for
everybody probably).

As long as we agree that these tests on TCK 1.1 can go away, that's
ok. I just wanted to raise this issue. And I was talking in more
general terms, not just applying to this issue.