[jira] [Assigned] (ISIS-1710) AppManifestAbstract#withAdditionalServices replaces rather than appends.

2017-11-13 Thread Dan Haywood (JIRA)

 [ 
https://issues.apache.org/jira/browse/ISIS-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dan Haywood reassigned ISIS-1710:
-

Assignee: Dan Haywood

> AppManifestAbstract#withAdditionalServices replaces rather than appends.
> 
>
> Key: ISIS-1710
> URL: https://issues.apache.org/jira/browse/ISIS-1710
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Minor
> Fix For: 1.16.0
>
>
> Unlike withAdditionalModules, that appends.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (ISIS-1714) AppManifestAbstract#withConfigurationProperty overwrites value set by -D system property.

2017-11-13 Thread Dan Haywood (JIRA)

 [ 
https://issues.apache.org/jira/browse/ISIS-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dan Haywood resolved ISIS-1714.
---
Resolution: Fixed

> AppManifestAbstract#withConfigurationProperty overwrites value set by -D 
> system property.
> -
>
> Key: ISIS-1714
> URL: https://issues.apache.org/jira/browse/ISIS-1714
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Minor
> Fix For: 1.16.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (ISIS-1714) AppManifestAbstract#withConfigurationProperty overwrites value set by -D system property.

2017-11-13 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/ISIS-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251026#comment-16251026
 ] 

ASF subversion and git services commented on ISIS-1714:
---

Commit 3605c0c20c164fbd48b9d3666b376a4281379d41 in isis's branch 
refs/heads/master from [~danhaywood]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=3605c0c ]

ISIS-1714: uses add rather than put for the config properties provided by the 
app manifest


> AppManifestAbstract#withConfigurationProperty overwrites value set by -D 
> system property.
> -
>
> Key: ISIS-1714
> URL: https://issues.apache.org/jira/browse/ISIS-1714
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Minor
> Fix For: 1.16.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (ISIS-1714) AppManifestAbstract#withConfigurationProperty overwrites value set by -D system property.

2017-11-13 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/ISIS-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16250476#comment-16250476
 ] 

ASF subversion and git services commented on ISIS-1714:
---

Commit 4b32677ee691a303b940ee67869a30e86a0b5c84 in isis's branch 
refs/heads/ISIS-1714 from [~danhaywood]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=4b32677 ]

ISIS-1714: uses add rather than put for the config properties


> AppManifestAbstract#withConfigurationProperty overwrites value set by -D 
> system property.
> -
>
> Key: ISIS-1714
> URL: https://issues.apache.org/jira/browse/ISIS-1714
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Minor
> Fix For: 1.16.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (ISIS-1714) AppManifestAbstract#withConfigurationProperty overwrites value set by -D system property.

2017-11-13 Thread Dan Haywood (JIRA)

 [ 
https://issues.apache.org/jira/browse/ISIS-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dan Haywood reassigned ISIS-1714:
-

Assignee: Dan Haywood

> AppManifestAbstract#withConfigurationProperty overwrites value set by -D 
> system property.
> -
>
> Key: ISIS-1714
> URL: https://issues.apache.org/jira/browse/ISIS-1714
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Minor
> Fix For: 1.16.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (ISIS-1739) DisableXxx() method is always called while hideXxx() returns true

2017-11-13 Thread Dan Haywood (JIRA)

 [ 
https://issues.apache.org/jira/browse/ISIS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dan Haywood resolved ISIS-1739.
---
Resolution: Fixed

> DisableXxx() method is always called while hideXxx() returns true
> -
>
> Key: ISIS-1739
> URL: https://issues.apache.org/jira/browse/ISIS-1739
> Project: Isis
>  Issue Type: Bug
>  Components: Core: Viewer: Wicket
>Affects Versions: 1.15.0
>Reporter: Erik de Hair
>Assignee: Dan Haywood
> Fix For: 1.16.0
>
>
> I have a contributed action that must be rendered on the first parameter's 
> page (OrderAbstract) on top of the page but shouldn't be rendered on the 
> other parameter's page.
> public Blob downloadDealerQuotationAsPdf(final OrderAbstract order, final 
> Contact recipient){
>  Blob quotation = ...
>  return quotation;
> }
> public String disableDownloadDealerQuotationAsPdf(final OrderAbstract order, 
> final Contact recipient){
>  if(order.getOrderLines().isEmpty()){
>  return "No orderline added yet");
>  }
>  return null;
> }
> public boolean hideDownloadDealerQuotationAsPdf(final OrderAbstract order, 
> final Contact recipient) {
>  return order == null || !order.getCompany().hasDealer();
> }
> As far as I can see the disableXXX method wouldn't be called in Apache Isis 
> 1.14.x when the Contact page was rendered, because this was suppressed by the 
> fact that the action was already hidden by the hiddenXXX method. But now 
> they're both called but when rendering the
> Contact page it will fail due to a NPE on the first line of the disableXXX 
> method so I have to change this method to
> public String disableDownloadDealerQuotationAsPdf(final OrderAbstract order, 
> final Contact recipient){
>  if(order == null){
>  return "Some dummy reason";
>  }
>  // actual disable conditions
>  ...
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (ISIS-1739) DisableXxx() method is always called while hideXxx() returns true

2017-11-13 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/ISIS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16250459#comment-16250459
 ] 

ASF subversion and git services commented on ISIS-1739:
---

Commit 558b04f45bed00e8fd6ed0ee43829593157e8895 in isis's branch 
refs/heads/master from [~danhaywood]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=558b04f ]

ISIS-1739: don't call disableXxx if hideXxx returns true for actions.


> DisableXxx() method is always called while hideXxx() returns true
> -
>
> Key: ISIS-1739
> URL: https://issues.apache.org/jira/browse/ISIS-1739
> Project: Isis
>  Issue Type: Bug
>  Components: Core: Viewer: Wicket
>Affects Versions: 1.15.0
>Reporter: Erik de Hair
>Assignee: Dan Haywood
> Fix For: 1.16.0
>
>
> I have a contributed action that must be rendered on the first parameter's 
> page (OrderAbstract) on top of the page but shouldn't be rendered on the 
> other parameter's page.
> public Blob downloadDealerQuotationAsPdf(final OrderAbstract order, final 
> Contact recipient){
>  Blob quotation = ...
>  return quotation;
> }
> public String disableDownloadDealerQuotationAsPdf(final OrderAbstract order, 
> final Contact recipient){
>  if(order.getOrderLines().isEmpty()){
>  return "No orderline added yet");
>  }
>  return null;
> }
> public boolean hideDownloadDealerQuotationAsPdf(final OrderAbstract order, 
> final Contact recipient) {
>  return order == null || !order.getCompany().hasDealer();
> }
> As far as I can see the disableXXX method wouldn't be called in Apache Isis 
> 1.14.x when the Contact page was rendered, because this was suppressed by the 
> fact that the action was already hidden by the hiddenXXX method. But now 
> they're both called but when rendering the
> Contact page it will fail due to a NPE on the first line of the disableXXX 
> method so I have to change this method to
> public String disableDownloadDealerQuotationAsPdf(final OrderAbstract order, 
> final Contact recipient){
>  if(order == null){
>  return "Some dummy reason";
>  }
>  // actual disable conditions
>  ...
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (ISIS-1766) Allow Xxx.layout.xml and menu.layout.xml to be served up as JSON via REST API

2017-11-13 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/ISIS-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16250458#comment-16250458
 ] 

ASF subversion and git services commented on ISIS-1766:
---

Commit 1e78cad339ba2de2e11f437a6b43a4fefa95519f in isis's branch 
refs/heads/master from [~danhaywood]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=1e78cad ]

ISIS-1766: adds an null guard for applications that don't yet have any 
menu.layout.xml - just use the fallback in these cases.


> Allow Xxx.layout.xml and menu.layout.xml to be served up as JSON via REST API
> -
>
> Key: ISIS-1766
> URL: https://issues.apache.org/jira/browse/ISIS-1766
> Project: Isis
>  Issue Type: New Feature
>Reporter: Dan Haywood
>Assignee: Dan Haywood
> Fix For: 1.16.0
>
>
> (dependent upon Accept Content header).
> Both Jackson and Moxy recognise JAXB annotations to serialize as JSON.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (ISIS-977) Allow the application menus to be specified using a appmenu.layout.xml file.

2017-11-13 Thread Dan Haywood (JIRA)

 [ 
https://issues.apache.org/jira/browse/ISIS-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dan Haywood resolved ISIS-977.
--
Resolution: Fixed

done as part of ISIS-1766 and related

> Allow the application menus to be specified using a appmenu.layout.xml file.
> 
>
> Key: ISIS-977
> URL: https://issues.apache.org/jira/browse/ISIS-977
> Project: Isis
>  Issue Type: New Feature
>  Components: Core, Core: Viewer: Wicket
>Affects Versions: viewer-wicket-1.7.0, core-1.7.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Minor
> Fix For: 1.16.0
>
>
> encapsulating the information in @DomainServiceLayout and @MemberOrder, eg:
> {
>   "PRIMARY": [
>   "FixedAssets": {
> "org.estatio.dom.assets.Properties": {
>   "actions": {
> "newProperty": {
>   "cssClassFa": "..."
> },
> "findProperties": {
>   ...
> }
>   }
> },
> "org.estatio.dom.assets.Units": {
>   ...
> },
> "org.estatio.dom.assets.FixedAssetRegistrations": {
>   ...
> }
>   },
>   "Parties": {
> ...
>   },
>   ...
>],
>"SECONDARY": [
>  "Prototyping": {
> ...
>  },
>  "Changes": {
> ...
>  },
>  "Security": {
> ...
>  }
>],
>"TERTIARY": {
>  "org.estatio.webapp.services.admin.EstatioAdministrationService": {
>"updateEpochDate": {},
>"listAllSettings": {}
>  }
>  "org.estatio.webapp.services.other.OtherServices": {
>"execute": {
>   "cssClassFa": "fa-bolt"
>},
>...   
>  }
>}
>  }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (ISIS-977) Allow the application menus to be specified using a appmenu.layout.xml file.

2017-11-13 Thread Dan Haywood (JIRA)

 [ 
https://issues.apache.org/jira/browse/ISIS-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dan Haywood reassigned ISIS-977:


Assignee: Dan Haywood

> Allow the application menus to be specified using a appmenu.layout.xml file.
> 
>
> Key: ISIS-977
> URL: https://issues.apache.org/jira/browse/ISIS-977
> Project: Isis
>  Issue Type: New Feature
>  Components: Core, Core: Viewer: Wicket
>Affects Versions: viewer-wicket-1.7.0, core-1.7.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Minor
> Fix For: 1.16.0
>
>
> encapsulating the information in @DomainServiceLayout and @MemberOrder, eg:
> {
>   "PRIMARY": [
>   "FixedAssets": {
> "org.estatio.dom.assets.Properties": {
>   "actions": {
> "newProperty": {
>   "cssClassFa": "..."
> },
> "findProperties": {
>   ...
> }
>   }
> },
> "org.estatio.dom.assets.Units": {
>   ...
> },
> "org.estatio.dom.assets.FixedAssetRegistrations": {
>   ...
> }
>   },
>   "Parties": {
> ...
>   },
>   ...
>],
>"SECONDARY": [
>  "Prototyping": {
> ...
>  },
>  "Changes": {
> ...
>  },
>  "Security": {
> ...
>  }
>],
>"TERTIARY": {
>  "org.estatio.webapp.services.admin.EstatioAdministrationService": {
>"updateEpochDate": {},
>"listAllSettings": {}
>  }
>  "org.estatio.webapp.services.other.OtherServices": {
>"execute": {
>   "cssClassFa": "fa-bolt"
>},
>...   
>  }
>}
>  }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ISIS-977) Allow the application menus to be specified using a appmenu.layout.xml file.

2017-11-13 Thread Dan Haywood (JIRA)

 [ 
https://issues.apache.org/jira/browse/ISIS-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dan Haywood updated ISIS-977:
-
Fix Version/s: (was: 2.3.0)
   1.16.0

> Allow the application menus to be specified using a appmenu.layout.xml file.
> 
>
> Key: ISIS-977
> URL: https://issues.apache.org/jira/browse/ISIS-977
> Project: Isis
>  Issue Type: New Feature
>  Components: Core, Core: Viewer: Wicket
>Affects Versions: viewer-wicket-1.7.0, core-1.7.0
>Reporter: Dan Haywood
>Priority: Minor
> Fix For: 1.16.0
>
>
> encapsulating the information in @DomainServiceLayout and @MemberOrder, eg:
> {
>   "PRIMARY": [
>   "FixedAssets": {
> "org.estatio.dom.assets.Properties": {
>   "actions": {
> "newProperty": {
>   "cssClassFa": "..."
> },
> "findProperties": {
>   ...
> }
>   }
> },
> "org.estatio.dom.assets.Units": {
>   ...
> },
> "org.estatio.dom.assets.FixedAssetRegistrations": {
>   ...
> }
>   },
>   "Parties": {
> ...
>   },
>   ...
>],
>"SECONDARY": [
>  "Prototyping": {
> ...
>  },
>  "Changes": {
> ...
>  },
>  "Security": {
> ...
>  }
>],
>"TERTIARY": {
>  "org.estatio.webapp.services.admin.EstatioAdministrationService": {
>"updateEpochDate": {},
>"listAllSettings": {}
>  }
>  "org.estatio.webapp.services.other.OtherServices": {
>"execute": {
>   "cssClassFa": "fa-bolt"
>},
>...   
>  }
>}
>  }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (ISIS-1739) DisableXxx() method is always called while hideXxx() returns true

2017-11-13 Thread Dan Haywood (JIRA)

 [ 
https://issues.apache.org/jira/browse/ISIS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dan Haywood reassigned ISIS-1739:
-

Assignee: Dan Haywood

> DisableXxx() method is always called while hideXxx() returns true
> -
>
> Key: ISIS-1739
> URL: https://issues.apache.org/jira/browse/ISIS-1739
> Project: Isis
>  Issue Type: Bug
>  Components: Core: Viewer: Wicket
>Affects Versions: 1.15.0
>Reporter: Erik de Hair
>Assignee: Dan Haywood
> Fix For: 1.16.0
>
>
> I have a contributed action that must be rendered on the first parameter's 
> page (OrderAbstract) on top of the page but shouldn't be rendered on the 
> other parameter's page.
> public Blob downloadDealerQuotationAsPdf(final OrderAbstract order, final 
> Contact recipient){
>  Blob quotation = ...
>  return quotation;
> }
> public String disableDownloadDealerQuotationAsPdf(final OrderAbstract order, 
> final Contact recipient){
>  if(order.getOrderLines().isEmpty()){
>  return "No orderline added yet");
>  }
>  return null;
> }
> public boolean hideDownloadDealerQuotationAsPdf(final OrderAbstract order, 
> final Contact recipient) {
>  return order == null || !order.getCompany().hasDealer();
> }
> As far as I can see the disableXXX method wouldn't be called in Apache Isis 
> 1.14.x when the Contact page was rendered, because this was suppressed by the 
> fact that the action was already hidden by the hiddenXXX method. But now 
> they're both called but when rendering the
> Contact page it will fail due to a NPE on the first line of the disableXXX 
> method so I have to change this method to
> public String disableDownloadDealerQuotationAsPdf(final OrderAbstract order, 
> final Contact recipient){
>  if(order == null){
>  return "Some dummy reason";
>  }
>  // actual disable conditions
>  ...
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (ISIS-1632) Support meta annotations for @Property/@Collection/@Action + @XxxLayout

2017-11-13 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/ISIS-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16250224#comment-16250224
 ] 

ASF subversion and git services commented on ISIS-1632:
---

Commit 0114eec2290c6cf8d965c18938fd7295fc0ab78b in isis's branch 
refs/heads/dev/2.0.0/ISIS-1632-meta-annotations from [~danhaywood]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=0114eec ]

ISIS-1632: adds migration notes for meta annotations, and changes defaults to 
NOT_SPECIFIED in all cases


> Support meta annotations for @Property/@Collection/@Action + @XxxLayout
> ---
>
> Key: ISIS-1632
> URL: https://issues.apache.org/jira/browse/ISIS-1632
> Project: Isis
>  Issue Type: New Feature
>Reporter: Dan Haywood
>Assignee: Dan Haywood
> Fix For: 2.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ISIS-1767) JEE 7+ Support

2017-11-13 Thread Andi Huber (JIRA)

 [ 
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'

||Server  ||fat-war ||skinny-war
 ||restEasy   ||con.pool   ||dom.events 
||swagger-ui||
|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}|
|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}|
|Glassfish (full 4.1.2)   |*OK*(1)  |*OK*(1)
 |{color:green}*OK*{color}|todo
|{color:green}*OK*{color}|{color:green}*OK*{color}|
|Glassfish (web 5.0.1 beta) |{color:green}*OK*{color} 
|{color:green}*OK*{color}|{color:red}*FAILED*(5){color}|todo   
|{color:green}*OK*{color}|{color:red}*FAILED*(5){color}|
|Glassfish (full 5.0) |{color:red}*FAILED*(2){color}|todo   
 |todo|todo|todo
|todo|
|Wildfly (full 11.0.0)|{color:red}*FAILED*(3){color}|todo   
 |todo|todo|todo
|todo|
|TomEE (plume 7.0.4)  |*OK*(4)  |todo   
 |{color:green}*OK*{color}|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)
org.jboss.resteasy.spi.UnhandledException: java.lang.AbstractMethodError: 
javax.ws.rs.core.Response$ResponseBuilder.status(ILjava/lang/String;)Ljavax/ws/rs/core/Response$ResponseBuilder;
at 
org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:77)
...
Caused by: java.lang.AbstractMethodError: 
javax.ws.rs.core.Response$ResponseBuilder.status(ILjava/lang/String;)Ljavax/ws/rs/core/Response$ResponseBuilder;
at javax.ws.rs.core.Response$ResponseBuilder.status(Response.java:921)
...



  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 

[jira] [Updated] (ISIS-1767) JEE 7+ Support

2017-11-13 Thread Andi Huber (JIRA)

 [ 
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

||Server  ||fat-war ||skinny-war
 ||restEasy   ||con.pool   ||dom.events 
||swagger-ui||
|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}|
|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}|
|Glassfish (full 4.1.2)   |*OK*(1)  |*OK*(1)
 |{color:green}*OK*{color}|todo
|{color:green}*OK*{color}|{color:green}*OK*{color}|
|Glassfish (web 5.0.1 beta) |{color:green}*OK*{color} 
|{color:green}*OK*{color}|{color:red}*FAILED*(5){color}|todo   
|{color:green}*OK*{color}|{color:red}*FAILED*(5){color}|
|Glassfish (full 5.0) |{color:red}*FAILED*(2){color}|todo   
 |todo|todo|todo
|todo|
|Wildfly (full 11.0.0)|{color:red}*FAILED*(3){color}|todo   
 |todo|todo|todo
|todo|
|TomEE (plume 7.0.4)  |*OK*(4)  |todo   
 |{color:green}*OK*{color}|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)
org.jboss.resteasy.spi.UnhandledException: java.lang.AbstractMethodError: 
javax.ws.rs.core.Response$ResponseBuilder.status(ILjava/lang/String;)Ljavax/ws/rs/core/Response$ResponseBuilder;
at 
org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:77)
...
Caused by: java.lang.AbstractMethodError: 
javax.ws.rs.core.Response$ResponseBuilder.status(ILjava/lang/String;)Ljavax/ws/rs/core/Response$ResponseBuilder;
at javax.ws.rs.core.Response$ResponseBuilder.status(Response.java:921)
...



  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)
* 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 Guava's EventBus

||Server  ||fat-war ||skinny-war
 ||restEasy   ||con.pool   ||dom.events||
|Payara (full 4.1.2.173)  |{color:green}*OK*{color} 

[jira] [Commented] (ISIS-1773) default view of a collection seems to be broken

2017-11-13 Thread Andi Huber (JIRA)

[ 
https://issues.apache.org/jira/browse/ISIS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16249480#comment-16249480
 ] 

Andi Huber commented on ISIS-1773:
--

Possibly fixed with https://issues.apache.org/jira/browse/ISIS-1698 
(coming with version 1.16.0)

> default view of a collection seems to be broken
> ---
>
> Key: ISIS-1773
> URL: https://issues.apache.org/jira/browse/ISIS-1773
> Project: Isis
>  Issue Type: Bug
>Affects Versions: 1.16.0
>Reporter: Johan Doornenbal
>
> Setting the default view as implemented and described in ISIS-1151 seems to 
> be broken. 
> Also I encountered a similar issue with default view map.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (ISIS-1698) CollectionLayout.defaultView not honored

2017-11-13 Thread Andi Huber (JIRA)

 [ 
https://issues.apache.org/jira/browse/ISIS-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andi Huber resolved ISIS-1698.
--
   Resolution: Fixed
 Assignee: Andi Huber  (was: Dan Haywood)
Fix Version/s: (was: 2.3.0)
   1.16.0

fix is already merged into master

> CollectionLayout.defaultView not honored
> 
>
> Key: ISIS-1698
> URL: https://issues.apache.org/jira/browse/ISIS-1698
> Project: Isis
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.15.0
>Reporter: Andi Huber
>Assignee: Andi Huber
> Fix For: 1.16.0
>
> Attachments: ISIS-1698.png
>
>
> It seems setting the defaultView for Collections does no longer work. (Since 
> release 1.15.0)
> The collection's view instead always defaults to "table", no matter if set 
> via Annotation or layout.xml.
> However the 'hinting mechanism' does work. The framework remembers the last 
> view as selected via user-interface . ('table, 'excel, ...')
> Steps to reproduce ...
> Take the SimpleObject demo app and test the following snipped:
> {code:java}
> @javax.inject.Inject
> SimpleObjectRepository simpleObjectRepository;
> @CollectionLayout(defaultView="hidden")
> public List getAll(){
>   return simpleObjectRepository.listAll();
> }
> {code}
> The collection should default to view type 'hidden' but renders as 'table'. 
> (Same applies if we try to default to 'excel', in case the excel-addon is 
> available.)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)