Scott M Stark

So the ee10 dist has essentially the same application-client.xml: ``` jpa_core_EntityGraph_stateless3_vehicle_client ejb/Stateless3VehicleBean Session com.sun.ts.tests.common.vehicle.stateless3.Stateless3VehicleIF Stateless3VehicleBean ``` and a sun-ejb-jar.xml file of: ``` Stateless3VehicleBean jpa_core_EntityGraph_stateless3_vehicle_Stateless3VehicleBean ``` So the jndi-name is different,...

@arjantijms @dmatej I have created a simple reproducer that shows the problem. The appclient has an entry in the java:comp/env/ejb/StatelessVehicleBean location, but the EjbReferenceProxy value bound there ends up attempting...

The appclient-jndi branch is in the main platform-tck repo. I just tried a clean checkout and test run: ``` starksm@Scotts-Mac-Studio /tmp % rm -rf platform-tck starksm@Scotts-Mac-Studio /tmp % git clone...

The problem with that is that this is a common vehicle ejb and the test artifact changes across tests. If the lookup-name is required, every test needs to have a...

So I don't see that Glassfish and I assume other servers honor the lookup value as where to bind the EJB on the server side. It is used on the...

That is not working as I'm trying it in my issue1667 branch. The problem is that the call path is different in these tests as the Stateless3VehicleRunner is not the...

I'm not even seeing it try to inject. I'm using the ee.jakarta.tck.persistence.core.EntityGraph.ClientStateless3Test. Which test are you trying?

That is using the same structure as ClientStateless3Test. Where do you see that 'could not inject the' msg?

Ah, ok. So I have added the code to inject the runner for the Stateless3VehicleRunner, but CDI is not available: ``` 11-26-2024 10:51:44: TRACE: Vehicle to be used for this...

I can't say it is a known issue. Do you have an example project repo that illustrates this?