Scott Marlow

@lukasj should we accept this challenge and exclude the test from Persistence 3.1?

Failing tests are: ``` Persistence 3.1 TCK: com/sun/ts/tests/jpa/core/inheritance/abstractentity/Client.java#abstractEntityTest1_from_standalone Failed. Test case throws exception: com.sun.ts.lib.harness.EETest$Fault: Setup failed: com/sun/ts/tests/jpa/core/inheritance/abstractentity/Client.java#abstractEntityTest2_from_standalone Failed. Test case throws exception: com.sun.ts.lib.harness.EETest$Fault: Setup failed: com/sun/ts/tests/jpa/core/inheritance/abstractentity/Client.java#abstractEntityTest3_from_standalone Failed. Test case throws...

I wonder if another JPA/Persistence Specification team committer could accept this challenge? @gavinking it looks to me like it would be ambiguous to specify @Table on both classes as which...

https://jakarta.ee/committees/specification/tckprocess/ speaks to this case I think which is why I thought it is valid: > The following scenarios are considered in scope for test challenges: > > - Claims...

The 3 challenged tests info from https://github.com/jakartaee/platform-tck/blob/10.0.x/src/com/sun/ts/tests/jpa/core/inheritance/abstractentity/Client.java: /* * @testName: abstractEntityTest1 * * @assertion_ids: PERSISTENCE:SPEC:589; PERSISTENCE:SPEC:590; * PERSISTENCE:SPEC:591; PERSISTENCE:SPEC:588; PERSISTENCE:SPEC:1126; * PERSISTENCE:SPEC:1126.1; PERSISTENCE:SPEC:1126.3; PERSISTENCE:SPEC:1126.4; * PERSISTENCE:JAVADOC:25; PERSISTENCE:JAVADOC:26; PERSISTENCE:JAVADOC:28; * PERSISTENCE:SPEC:1112;...

> [@arjantijms](https://github.com/arjantijms) I see that EE 11 platform is released here: https://repo1.maven.org/maven2/jakarta/platform/jakarta.jakartaee-api/11.0.0/ > > I'm a bit confused -- What exactly needs to be changed here? > > Do we...

> I can accept the challenge, however we would have to exclude the tests formally, or we'd have to ask for another exception with the specification committee again. Please do...

Note this line below: > Suppressed: javax.naming.NamingException: Exception resolving Ejb for 'Remote ejb-ref name=ejb/Stateless3VehicleBean,Remote 3.x interface =com.sun.ts.tests.common.vehicle.stateless3.Stateless3VehicleIF,ejb-link=Stateless3VehicleBean,lookup=,mappedName=,jndi-name=,refType=Session' . Actual (possibly internal) Remote JNDI name used for lookup is '#com.sun.ts.tests.common.vehicle.stateless3.Stateless3VehicleIF' [Root...

server.log contents are below: ``` [2024-10-22T11:34:54.579224-04:00] [] [INFO] [NCLS-GFLAUNCHER-00005] [jakarta.enterprise.launcher] [tid: _ThreadID=1 _ThreadName=main] [levelValue: 800] [[ JVM invocation command line: /usr/lib/jvm/java-17-openjdk/bin/java -cp /home/smarlow/tck/platformtck/glassfish-runner/jpa-platform-tck/target/glassfish8/glassfish/modules/glassfish.jar -DWALL_CLOCK_START=2024-10-22T15:34:54.159351825Z -XX:+UnlockDiagnosticVMOptions -XX:NewRatio=2 -Xmx512m --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED...

Paste of conversation from Jakarta EE TCK Slack channel https://eclipsefoundationhq.slack.com/archives/C0131MLD538/p1729612177243759: > Scott Marlow > Oct 22nd at 11:49 AM > Persistence TCK test (appclient) failure that is unclear to me...