| Re: [rest-dev] Is support for Java SE Bootstrap in Jakarta Rest 3.1 required for all spec implementors? |
The Java SE Bootstrap API is mandatory for those compliant products that already provide an way to natively bootstrap on Java SE. AFAIK it should be possible to run the TCK without the Java SE tests. If not, please let me know. There is no need to explicitly add a way to natively bootstrap on Java SE. At least this is what I had in mind when designing and proposing this API, and I cannot remember that agreed that Java SE must be added to all compliant products. -Markus Von: rest-dev [mailto:rest-dev-bounces@xxxxxxxxxxx] Im Auftrag von Jim Krueger Hi, Looking at the JAVA SE Bootstrap Issue (https://github.com/jakartaee/rest/issues/509) I see the following response from Markus on Apr 9, 2018: "@andymc12 The proposal is not that an implementation MUST support Java SE, but only that IF it supports Java SE it MUST support this particular API to boot it.” This would imply to me that the Java SE bootstrap support is optional for Jakarta Rest implementations. However, section 2.3 of the Jakarta RESTful Web Services specification contains the following: "Applications are published in different ways depending on whether the application is run in a Java SE environment or within a container. This section describes the alternate means of publication. A compliant implementation MUST support both alternatives on Java SE.” Also, looking at the TCK testcase (ee.jakarta.tck.ws.rs.sebootstrap.SeBootstrapIT) or the TCK user guide, I see nothing that gates this test to only those implementations that support Java SE. So is support for the Java SE Bootstrap formally a requirement for all Jakarta Rest 3.1 implementations? Thanks, Jim Krueger |