Tim Ward

> As a workaround (not as a final solution) does using Aries SPI Fly [Dynamic Weaving by auto properties](https://aries.apache.org/documentation/modules/spi-fly.html#_dynamic_weaving_by_auto_properties) work? Unfortunately my current codebase is way too big and interconnected...

Having left this to settle for a while, and looking at what is happening in similar specifications (HTTP whiteboard), I think that we have the following changes: 1. Rename the...

> I assume this change will depend upon the changes to http whiteboard? I'm not certain that this change does have a strict dependency on the HTTP whiteboard changes. The...

The Gecko REST implementation is now passing the whole TCK. I think that PR #417 is now ready to merge into the main branch, and the specification ready to begin...

> What is the general plan? Will new specs only support api from the jakarta namespace? Or both? Or do we decide per spec? If we can simplify the migration/coexistence...

> Well the obvious choice is to bump the spec major version and the spec API package major version and replace javax API references with jakarta API references. Renaming the...

> The runtime service is agnostic of the package space Except for the `ServletContextHelper`, which references `HttpServletRequest` and `HttpServletResponse` The JAX-RS whiteboard may be safe, but I'm not yet certain....

> Eclipse Link (and probably others) In my experience this isn't the case. The persistence unit name is used as a key by many providers, and therefore having multiple EMFs...

The general consensus is that there isn't anything to standardise here. The various implementations of the JPA Service are already able to provide this support, and the clients can be...

> can you reference some more? Aries JPA is the reference implementation >I think having more than one OSGi-JPA service won't work well anyways, All OSGi specifications have to deal...