Hi David
First of all, thank you for your clear and well written response (as
always).
I have been working (nearly 20 hours) to convert all openejb-jee and
openejb-jee-sxc to formal standard EE 8 descriptors but it is a painful
process for me. The generated schemas are not fit in to our current
Hello
If it helps there are twi things to consider:
1. When we supported ee7 we made most of these descriptors at lowest cost
which means we mainly let them pass and sometimes ignore some model part
not used at runtime and let the actual runtime lib read it (typically jsf)
2. All the current
It’s been a very long time since I worked with these, but I do remember that
switching to the openejb customized classes was a very big improvement. I think
it’s definitely worth having an object tree representing the deployment
descriptor where the objects make sense.
David Jencks
Sent from
> On Dec 2, 2018, at 2:59 AM, Gurkan Erdogdu wrote:
>
> Hi folks,
> I am working on the Java EE schema update to support Java EE 7 and Java EE8
> schemas which are specified in
> https://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/index.html
>
> Seems that two modules openejb-jee and
Hi folks,
I am working on the Java EE schema update to support Java EE 7 and Java EE8
schemas which are specified in
https://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/index.html
Seems that two modules openejb-jee and openejb-jee-accessor modules are
mostly updated by manually after
