Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-tck-dev] Platform TCK run started


On Wed, Jun 10, 2020 at 9:33 PM Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:

I don't know. Since we are trying to get all the name-space issues ironed out --

I created https://github.com/eclipse-ee4j/jakartaee-tck/issues/317 that includes validating that any remaining javax.* classes referenced are correct.

I am not sure it will be very worthwhile to try and diagnose problems that crop up after we find there are still name-space issues in the packages. I'd try to get those issues corrected first since they suggest that the Jakartification work isn't quite finished yet.

https://github.com/eclipse-ee4j/jakartaee-tck/pull/316 is for updating to the EE 9 XSDs in the tests.

https://github.com/eclipse-ee4j/jakartaee-tck/issues/313 is open for updating the application archives that contain javax.ejb.SessionBean class references, to use jakarta.ejb.SessionBean.  Please also refer to comment https://github.com/eclipse-ee4j/jakartaee-tck/issues/313#issuecomment-642359469 that explains how these archives are testing backward compatibility with older EE versions.  

In theory, we could run these archives through a bytecode transformer (statically or during the test run), but IMO that isn't really required to be done.  For discussion, should we:

a.  Transform or rebuild the legacy application archives to reference jakarta.ejb.SessionBean?

b.  Remove the testing of these legacy application archives?

c.  Something else?

Imo, I think that we have to look deeper to see what we would be losing if we did (b).  Is there a viable (c) option?

Scott

-- Ed

On 6/10/2020 2:22 PM, Scott Marlow wrote:


On Wed, Jun 10, 2020 at 4:54 PM Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:

Scott,

In the domain log, of [1], the very first exception trace at line 335 includes javax.security which is probably not correct.

If this isn't expected, I would posit that it could be difficult to interpret results while there are still name-space errors.

Ed,

In that first exception trace, I do see javax.security.auth.Subject, which has almost the same package as https://github.com/eclipse-ee4j/authentication/tree/master/api/src/main/java/jakarta/security/auth but Subject is not there.  Subject is still in SE 11+, so any issue here?

Scott

Back to the top