Re: [jakartaee-tck-dev] Updating the TCK for javax -> jakarta transition

[Mark Thomas <markt@xxxxxxxxxx>]

On 20/01/2020 18:18, Jan Supol wrote:
> Hi Mark,
> 
> Looking at the EL, it uses Servlet web.xml descriptor, i.e. web-app
> version="2.5" xmlns="http://java.sun.com/xml/ns/javaee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
> http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd.
> 
> Does Servlet plans to update the schema? It's a bit tricky, JAX-RS used
> to specifically use Servlet 2.5 schema since Servlet 2.5 was the minimum
> Servlet implementation version demanded by the JAX-RS Spec. So either
> the new Servlet would require to understand the old Java EE schema, or
> the minimum version of Servlet for Jakarta REST would have to be Servlet
> 5.0, IMHO.
> 
> What schema do you plan to use in EL?

The EL API does not have any dependencies on any other specs (including
Servlet). Neither should any implementation.

The TCK may have a dependency - I haven't checked. I hope to get to
looking at the TCK for EL later today. I'd be surprised if the TCK
required a Servlet container since EL is meant to be stand-alone.

My instinct is that, if there is a dependency on Servlet in the EL TCK,
it will be simpler (possibly even necessary) to update that dependency
to Jakarta Servlet

It is a little off-topic but supporting older versions of the schemas
should not be an issue for a Jakarta EE implementation. Apache Tomcat,
for example, has an initial Jakarta Servlet/El/JSp/WebSocket
implementation and it supports all the Java EE schemas (without any
additional changes required to do so).

Mark


> 
> Thanks,
> 
> Jan
> 
> On 20.01.2020 15:07, Mark Thomas wrote:
>> Ping.
>>
>> Absent any guidance, the plan I intend to follow for each of the
>> specifications I am involved in (WebSocket, EL, JSP, Servlet) is to:
>>
>> 1. Follow the guide on the wiki to build the stand-alone TCK.
>>
>> 2. Using the milestone releases of the API project(s) and Apache Tomcat
>> as the implementation, figure out what I need to change to get the
>> stand-alone TCK to pass with a Jakarta EE 9 implementation.
>>
>> 3. Submit a PR with those changes.
>>
>> Confirmation this is the right thing to do or corrections if it isn't
>> would be much appreciated.
>>
>> I intend to start with the EL TCK.
>>
>> Mark
>>
>>
>>
>> On 08/01/2020 18:18, Bill Shannon wrote:
>>> Like Mark, I'd like to know where and how to contribute changes for the
>>> javax -> jakarta transition.
>>>
>>> Are we putting those changes in the master branch, or is that still
>>> reserved
>>> for exclude list updated for Jakarta EE 8?
>>>
>>> Are we putting those changes in some new "9.0.0" branch?
>>>
>>> Of course, this ties into GlassFish as well, so I'll need to ask the
>>> same
>>> question on the GlassFish list.  The update platform TCK will need an
>>> updated
>>> GlassFish to test against.
>>>
>>> It would probably ne nice if there was some coordination between how
>>> we handle
>>> branching, etc. for these two projects for Jakarta EE 9.
>>>
>>> Thanks.
>>>
>>>
>>> Mark Thomas wrote on 1/8/20 2:40 AM:
>>>> Hi,
>>>>
>>>> I'm working on migrating a number of projects from javax to jakarta for
>>>> Jakarta EE 9.
>>>>
>>>> What, if anything, is the TCK project expecting from the individual
>>>> projects to help the TCK project with the transition?
>>>>
>>>> Can we use Jakarta EL as an explicit example?
>>>>
>>>> I'd be happy to try and put together a PR if I knew what was required.
>>>>
>>>> Thanks,
>>>>
>>>> Mark
>>>> _______________________________________________
>>>> jakartaee-tck-dev mailing list
>>>> jakartaee-tck-dev@xxxxxxxxxxx
>>>> To change your delivery options, retrieve your password, or
>>>> unsubscribe from this list, visit
>>>> https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
>>>>
>> _______________________________________________
>> jakartaee-tck-dev mailing list
>> jakartaee-tck-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or
>> unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
> _______________________________________________
> jakartaee-tck-dev mailing list
> jakartaee-tck-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev