The signature test is a well known part
of the TCK that essentially tests whether all the classes
and methods are exactly there, without any method missing,
and without any class or method or annotation etc being
added, or any parameter being changed, even if it’s in a
seemingly binary compatible way.
On Saturday, September 14, 2019, Markus KARG <markus@xxxxxxxxxxxxxxx>
wrote:
What I do not understand in the following
part of your explanation:
"An API jar file in combination with an implementation can
pass the TCK."
This implies that there is something in the TCK that does
not check the implementation, but in fact does check the API
JAR. Can you give an example what part of Jakarta REST's TCK
actually does test the API jar instead of testing the
implementation? You mention "signature tests". What is the
intention of that? I am asking because next step at Jakarta
REST certainly will be the adoption of our TCK into our
repo, so we need to learn the not-so-obvious parts of that.
Thanks
-Markus
-----Ursprüngliche Nachricht-----
Von: Bill Shannon [mailto:bill.shannon@xxxxxxxxxx]
Gesendet: Montag, 9. September 2019 23:36
An: jaxrs developer discussions; Markus KARG
Betreff: Re: [jaxrs-dev] Jakarta RESTful Web Services API
2.1.6 is available in maven central
I thought it did. Maybe you'd like to restate your
question?
Perhaps there's some subtlety that I'm missing.
To be clear, an API jar file *alone* can not pass the TCK.
An API jar file in combination with an implementation can
pass the TCK.
Given the intended use of an API jar file, it should pass
the signature
tests in the TCK, which can be shown by running the full TCK
against
the API jar file plus an implementation.
Markus KARG wrote on 9/7/19 12:52 AM:
> I know that, but it does not answer my original
question to Jan.
> -Markus
>
> -----Ursprüngliche Nachricht-----
> Von: Bill Shannon [mailto:bill.shannon@xxxxxxxxxx]
> Gesendet: Freitag, 6. September 2019 20:20
> An: jaxrs developer discussions; Markus KARG
> Betreff: Re: [jaxrs-dev] Jakarta RESTful Web Services
API 2.1.6 is available in maven central
>
> Presumably the TCK was run with the new API jar file
and the existing
> implementation. That combination would be compatible
with the spec
> requirements.
>
> The API jar file alone meets the spec requirements in
the sense that it
> provides valid signatures for the APIs. API jar files
are only intended
> for use to compile against (although they may be useful
for other things)
> so only the API signatures matter.
>
>
> Markus KARG wrote on 9/6/19 9:30 AM:
>> How can an API pass its own TCK? Only an
implementation can pass a TCK.
>> -Markus
>>
>> -----Ursprüngliche Nachricht-----
>> Von: jaxrs-dev-bounces@xxxxxxxxxxx
[mailto:jaxrs-dev-bounces@xxxxxxxxxxx]
Im Auftrag von Jan Supol
>> Gesendet: Freitag, 6. September 2019 18:14
>> An: jaxrs-dev@xxxxxxxxxxx
>> Betreff: Re: [jaxrs-dev] Jakarta RESTful Web
Services API 2.1.6 is available in maven central
>>
>> Hi Markus,
>>
>> Well, it passed the Jakarta RESTful Web Services
TCK 2.1 :)
>>
>> -- Jan
>>
>> On 06.09.2019 10:26, Markus KARG wrote:
>>> Thanks, Jan!
>>>
>>> But actually I am wondering what "Jakarta EE 8
COMPLIANT" means? How is that
>>> COMPLIANCE defined?
>>>
>>> -Markus
>>>
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: jaxrs-dev-bounces@xxxxxxxxxxx
[mailto:jaxrs-dev-bounces@xxxxxxxxxxx]
Im
>>> Auftrag von Jan Supol
>>> Gesendet: Donnerstag, 5. September 2019 22:08
>>> An: jaxrs-dev@xxxxxxxxxxx
>>> Betreff: [jaxrs-dev] Jakarta RESTful Web
Services API 2.1.6 is available in
>>> maven central
>>>
>>> Dear Jakarta RESTful Web Services Community,
>>>
>>> The Jakarta EE 8 compliant Jakarta RESTful Web
Services API 2.1.6 is
>>> available in maven central [1].
>>>
>>> Thank you,
>>>
>>> Jan
>>>
>>> [1]
>>> https://search.maven.org/artifact/jakarta.ws.rs/jakarta.ws.rs-api/2.1.6/bund
>>> le
>>>
>>> _______________________________________________
>>> jaxrs-dev mailing list
>>> jaxrs-dev@xxxxxxxxxxx
>>> To change your delivery options, retrieve your
password, or unsubscribe from
>>> this list, visit
>>> https://www.eclipse.org/mailman/listinfo/jaxrs-dev
>>>
>>> _______________________________________________
>>> jaxrs-dev mailing list
>>> jaxrs-dev@xxxxxxxxxxx
>>> To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
>>> https://www.eclipse.org/mailman/listinfo/jaxrs-dev
>> _______________________________________________
>> jaxrs-dev mailing list
>> jaxrs-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/jaxrs-dev
>>
>> _______________________________________________
>> jaxrs-dev mailing list
>> jaxrs-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/jaxrs-dev
>>
>
> _______________________________________________
> jaxrs-dev mailing list
> jaxrs-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jaxrs-dev
>
_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jaxrs-dev
