[jira] [Updated] (ISIS-1767) JEE 7+ Support
[
https://issues.apache.org/jira/browse/ISIS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andi Huber updated ISIS-1767:
-
Description:
Collective tasks for Java EE 7+ support.
Designated branch ...
{code}dev/2.0.0/ISIS-1767-jee-7{code}
+Tests+
* *Server*: JEE 7+ implementation (or similar), launched with JDK8 (Version
1.8.0_152); for deployment we use the HelloWorld artifact 1.15.1 with minor
modifications
* *fat-war*: deploy all dependencies with single war (hsqldb in memory)
* *skinny-war*: prepare container with shared libraries and shared domain
objects, deploy only a subset of domain classes with single war (hsqldb in
memory)
* *restEasy*: check whether restEasy responds
* managed connection pool (*con.pool*): use mysql db connection pool managed by
the JEE container and provided via JNDI
* domain events (*dom.events*): test whether domain events are emitted and
handled using AxonFramework's SimpleEventBus
* *swagger-ui*: test whether the static index.html from swagger-ui is served
and verify that a request for '//restful/swagger/private' returns
a JSON, that has the 'basePath' set to '//restful'
* *redeploy*: test whether all previous tests succeed if we do a
deploy-undeploy-deploy process
||Server ||fat-war ||skinny-war
||restEasy ||con.pool ||dom.events
||swagger-ui||redeploy||
|Payara (full 4.1.2.173) |{color:green}*OK*{color}
|{color:green}*OK*{color}|{color:green}*OK*{color}|{color:green}*OK*{color}|{color:green}*OK*{color}|{color:green}*OK*{color}|*OK*(6)|
|Payara (web 4.1.2.173) |{color:green}*OK*{color}
|{color:green}*OK*{color}|{color:green}*OK*{color}|{color:green}*OK*{color}|{color:green}*OK*{color}|{color:green}*OK*{color}|*OK*(6)|
|Glassfish (full 4.1.2) |*OK*(1) |*OK*(1)
|{color:green}*OK*{color}|todo
|{color:green}*OK*{color}|{color:green}*OK*{color}|*OK*(6)|
|Glassfish (web 5.0.1 beta)|{color:green}*OK*{color}
|{color:green}*OK*{color}|*OK*(5)|todo
|{color:green}*OK*{color}|{color:green}*OK*{color}|*OK*(6)|
|Glassfish (full 5.0) |{color:red}*FAILED*(2){color}|todo
|todo|todo|todo
|todo|todo|
|Wildfly (full 11.0.0)|{color:red}*FAILED*(3){color}|todo
|todo|todo|todo
|todo|todo|
|TomEE (plume 7.0.4) |*OK*(4) |todo
|{color:green}*OK*{color}|todo|todo
|todo|todo|
Notes:
(1)
Guava version conflict: GF 4.2.1 has Guava-13, Isis has Guava-19;
WORKAROUND modify your glassfish installation ...
* in glassfish/modules/ replace guava.jar with that which comes packaged with
Payara-4.1.2.173 (Guava-19)
* you need to clear the OSGI cache: delete the folder
glassfish/domains/domainXXX/osgi-cache/felix
(2)
ON-HOLD waiting for GF 5.0.1 release!
class-loading issues with Hibernate Validator, though library is included in
war ... java.lang.ClassNotFoundException: org.joda.time.ReadableInstant;
using patch https://github.com/hibernate/hibernate-validator/pull/857/files
does not help: introduces new class-loading issues;
(3)
class-loading issues, though library is included in war ...
javax.persistence.PersistenceException: WFLYJPA0057: PersistenceProvider
'org.apache.isis.core.webapp.jee.PersistenceUnitNoopProvider' not found;
(4)
requires CXF to be disabled, see
https://stackoverflow.com/questions/41496204/tomee-7-0-2-how-to-disable-cxf-rs
throws exceptions on undeploy
(5)
JAX-RS API version clash
requires 4.0.0.Beta1
see https://issues.apache.org/jira/browse/ISIS-1779
(6)
dedicated issue https://issues.apache.org/jira/browse/ISIS-1754
might throw org.datanucleus.metadata.InvalidClassMetaDataException, but yet not
reproducable by tests
was:
Collective tasks for Java EE 7+ support.
Designated branch ...
{code}dev/2.0.0/ISIS-1767-jee-7{code}
+Tests+
* *Server*: JEE 7+ implementation (or similar), launched with JDK8 (Version
1.8.0_152); for deployment we use the HelloWorld artifact 1.15.1 with minor
modifications
* *fat-war*: deploy all dependencies with single war (hsqldb in memory)
* *skinny-war*: prepare container with shared libraries and shared domain
objects, deploy only a subset of domain classes with single war (hsqldb in
memory)
* *restEasy*: check whether restEasy responds
* managed connection pool (*con.pool*): use mysql db connection pool managed by
the JEE container and provided via JNDI
* domain events (*dom.events*): test whether domain events are emitted and
handled using AxonFramework's SimpleEventBus
* *swagger-ui*: test whether the static index.html from
[jira] [Updated] (ISIS-1779) Transition to JAX-RS 2.0 Client API
[ https://issues.apache.org/jira/browse/ISIS-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-1779: - Description: It seems JEE 8 servers (compliant with JAX-RS 2.1 API) conflict with deployment of resteasy-jaxrs.version 3.x (which is JAX-RS 2.0 API) and JEE 7 servers (compliant with JAX-RS 2.0 API) conflict with deployment of resteasy-jaxrs.version 4.x (which is JAX-RS 2.1 API). So by now there is no easy way to package a war file with resteasy included, that will run on both JEE 7 and 8. I've successfully tested 4.0.0.Beta1 on glassfish 5, 3.0.17.Final on glassfish 4, 3.1.4.Final on glassfish 4. Note: transitioning resteasy-jaxrs from 3.0.x to any higher version involves removal of deprecated classes in org.jboss.resteasy.client.*, which we are using it in core/viewer-resfulobjects-applib. was: It seems JEE 8 servers (compliant with JAX-RS 2.1 API) conflict with deployment of resteasy-jaxrs.version 3.x (which is JAX-RS 2.0 API) and JEE 7 servers (compliant with JAX-RS 2.0 API) conflict with deployment of resteasy-jaxrs.version 4.x (which is JAX-RS 2.1 API). So by now there is no easy way to package a war file with resteasy included, that will run on both JEE 7 and 8. I've successfully tested 4.0.0.Beta1 on glassfish 5, 3.0.17.Final on glassfish 4, 3.1.4.Final on glassfish 4. org.jboss.resteasy.client.* was deprecated. We are using it in core/viewer-resfulobjects. > Transition to JAX-RS 2.0 Client API > --- > > Key: ISIS-1779 > URL: https://issues.apache.org/jira/browse/ISIS-1779 > Project: Isis > Issue Type: Improvement > Components: Core: Viewer: RestfulObjects >Affects Versions: 1.15.1 >Reporter: Andi Huber >Assignee: Andi Huber > Fix For: 2.0.0 > > > It seems JEE 8 servers (compliant with JAX-RS 2.1 API) conflict with > deployment of resteasy-jaxrs.version 3.x (which is JAX-RS 2.0 API) > and JEE 7 servers (compliant with JAX-RS 2.0 API) conflict with deployment of > resteasy-jaxrs.version 4.x (which is JAX-RS 2.1 API). > So by now there is no easy way to package a war file with resteasy included, > that will run on both JEE 7 and 8. > I've successfully tested > 4.0.0.Beta1 on glassfish 5, > 3.0.17.Final on glassfish 4, > 3.1.4.Final on glassfish 4. > Note: transitioning resteasy-jaxrs from 3.0.x to any higher version involves > removal of deprecated classes in > org.jboss.resteasy.client.*, which we are using it in > core/viewer-resfulobjects-applib. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1779) Transition to JAX-RS 2.0 Client API
[ https://issues.apache.org/jira/browse/ISIS-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-1779: - Description: It seems JEE 8 servers (compliant with JAX-RS 2.1 API) conflict with deployment of resteasy-jaxrs.version 3.x (which is JAX-RS 2.0 API) and JEE 7 servers (compliant with JAX-RS 2.0 API) conflict with deployment of resteasy-jaxrs.version 4.x (which is JAX-RS 2.1 API). So by now there is no easy way to package a war file with resteasy included, that will run on both JEE 7 and 8. I've successfully tested 4.0.0.Beta1 on glassfish 5, 3.0.17.Final on glassfish 4, 3.1.4.Final on glassfish 4. org.jboss.resteasy.client.* was deprecated. We are using it in core/viewer-resfulobjects. was: RESTEasy's org.jboss.resteasy.client.* was deprecated. We are using it in core/viewer-resfulobjects. It seems, this deprecated client API prevents Isis deployment to glassfish 5. > Transition to JAX-RS 2.0 Client API > --- > > Key: ISIS-1779 > URL: https://issues.apache.org/jira/browse/ISIS-1779 > Project: Isis > Issue Type: Improvement > Components: Core: Viewer: RestfulObjects >Affects Versions: 1.15.1 >Reporter: Andi Huber >Assignee: Andi Huber > Fix For: 2.0.0 > > > It seems JEE 8 servers (compliant with JAX-RS 2.1 API) conflict with > deployment of resteasy-jaxrs.version 3.x (which is JAX-RS 2.0 API) > and JEE 7 servers (compliant with JAX-RS 2.0 API) conflict with deployment of > resteasy-jaxrs.version 4.x (which is JAX-RS 2.1 API). > So by now there is no easy way to package a war file with resteasy included, > that will run on both JEE 7 and 8. > I've successfully tested > 4.0.0.Beta1 on glassfish 5, > 3.0.17.Final on glassfish 4, > 3.1.4.Final on glassfish 4. > org.jboss.resteasy.client.* was deprecated. > We are using it in core/viewer-resfulobjects. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
