[jira] [Commented] (ISIS-2034) [NOT A PROBLEM] REST operations return empty response
[ https://issues.apache.org/jira/browse/ISIS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692714#comment-16692714 ] Andi Huber commented on ISIS-2034: -- Also note, that for the 'simpleapp' basic-auth should work with curl as well. > [NOT A PROBLEM] REST operations return empty response > - > > Key: ISIS-2034 > URL: https://issues.apache.org/jira/browse/ISIS-2034 > Project: Isis > Issue Type: Bug > Components: Core: Viewer: RestfulObjects >Affects Versions: 2.0.0-M2 > Environment: Windows 7 >Reporter: Brian Kalbfus >Assignee: Andi Huber >Priority: Minor > Labels: not-an-issue > Fix For: 2.0.0-M2 > > Attachments: simpleappswaggerui.png > > > to reproduce: > # checkout HEAD of v2 branch > # mvn clean install > # cd to isis/example/application/simpleapp/webapp > # set PROTOTYPING=true > # mvn jetty:run > # open web browser to localhost:8080/wicket, sign in as sven/pass > # from prototyping menu, open swagger-ui > # reload private spec > # select simple - /service/simple.SimpleObjectMenu/actions/listAll/invoke > # click "Try it out" > expected: Response body should have some output - some json with metadata or > something > actual: Reponse body says "no content" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ISIS-2034) [NOT A PROBLEM] REST operations return empty response
[ https://issues.apache.org/jira/browse/ISIS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber closed ISIS-2034. Resolution: Not A Problem Thanks Brian! Thing is, in general, we have no idea about what actual authentication mechanism protects the restful viewer. This is up the deployment scenario. Hence our customized swagger-ui does simply ignore this aspect. I'm afraid, that's the best we can do on our side. Cheers Andi! > [NOT A PROBLEM] REST operations return empty response > - > > Key: ISIS-2034 > URL: https://issues.apache.org/jira/browse/ISIS-2034 > Project: Isis > Issue Type: Bug > Components: Core: Viewer: RestfulObjects >Affects Versions: 2.0.0-M2 > Environment: Windows 7 >Reporter: Brian Kalbfus >Assignee: Andi Huber >Priority: Minor > Labels: not-an-issue > Fix For: 2.0.0-M2 > > Attachments: simpleappswaggerui.png > > > to reproduce: > # checkout HEAD of v2 branch > # mvn clean install > # cd to isis/example/application/simpleapp/webapp > # set PROTOTYPING=true > # mvn jetty:run > # open web browser to localhost:8080/wicket, sign in as sven/pass > # from prototyping menu, open swagger-ui > # reload private spec > # select simple - /service/simple.SimpleObjectMenu/actions/listAll/invoke > # click "Try it out" > expected: Response body should have some output - some json with metadata or > something > actual: Reponse body says "no content" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ISIS-2041) LogonFixture is deprecated, replace by FixtureScript
Andi Huber created ISIS-2041: Summary: LogonFixture is deprecated, replace by FixtureScript Key: ISIS-2041 URL: https://issues.apache.org/jira/browse/ISIS-2041 Project: Isis Issue Type: Improvement Components: Core Reporter: Andi Huber Fix For: 2.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-2034) [NOT A PROBLEM] REST operations return empty response
[ https://issues.apache.org/jira/browse/ISIS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-2034: - Summary: [NOT A PROBLEM] REST operations return empty response (was: REST operations return empty response) > [NOT A PROBLEM] REST operations return empty response > - > > Key: ISIS-2034 > URL: https://issues.apache.org/jira/browse/ISIS-2034 > Project: Isis > Issue Type: Bug > Components: Core: Viewer: RestfulObjects >Affects Versions: 2.0.0-M2 > Environment: Windows 7 >Reporter: Brian Kalbfus >Assignee: Andi Huber >Priority: Minor > Labels: not-an-issue > Fix For: 2.0.0-M2 > > Attachments: simpleappswaggerui.png > > > to reproduce: > # checkout HEAD of v2 branch > # mvn clean install > # cd to isis/example/application/simpleapp/webapp > # set PROTOTYPING=true > # mvn jetty:run > # open web browser to localhost:8080/wicket, sign in as sven/pass > # from prototyping menu, open swagger-ui > # reload private spec > # select simple - /service/simple.SimpleObjectMenu/actions/listAll/invoke > # click "Try it out" > expected: Response body should have some output - some json with metadata or > something > actual: Reponse body says "no content" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ISIS-2034) REST operations return empty response
[ https://issues.apache.org/jira/browse/ISIS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692407#comment-16692407 ] Brian Kalbfus commented on ISIS-2034: - OK, that did it. I see you are using cookie authentication now. The curl command displayed isn't accurate if you have to include a cookie in the process. Maybe modifying the api specification document (/restful/swagger/private) will work better with Swagger-UI and generated clients. You can add a security scheme like is described in [https://swagger.io/docs/specification/authentication/cookie-authentication/] . Thanks! Brian > REST operations return empty response > - > > Key: ISIS-2034 > URL: https://issues.apache.org/jira/browse/ISIS-2034 > Project: Isis > Issue Type: Bug > Components: Core: Viewer: RestfulObjects >Affects Versions: 2.0.0-M2 > Environment: Windows 7 >Reporter: Brian Kalbfus >Assignee: Andi Huber >Priority: Minor > Labels: not-an-issue > Fix For: 2.0.0-M2 > > Attachments: simpleappswaggerui.png > > > to reproduce: > # checkout HEAD of v2 branch > # mvn clean install > # cd to isis/example/application/simpleapp/webapp > # set PROTOTYPING=true > # mvn jetty:run > # open web browser to localhost:8080/wicket, sign in as sven/pass > # from prototyping menu, open swagger-ui > # reload private spec > # select simple - /service/simple.SimpleObjectMenu/actions/listAll/invoke > # click "Try it out" > expected: Response body should have some output - some json with metadata or > something > actual: Reponse body says "no content" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ISIS-2034) REST operations return empty response
[ https://issues.apache.org/jira/browse/ISIS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692205#comment-16692205 ] Andi Huber commented on ISIS-2034: -- Response code 401 is 'unauthorized', so thats the problem here. You might notice that I've added a link on the swagger-ui top bar labeled 'Direct API Link (Login)' which points to the restful servlet's base URL '/restful/'. You need to authorize once with Basic Auth (sven:pass), to get access to the restful viewer. After that everything should work. > REST operations return empty response > - > > Key: ISIS-2034 > URL: https://issues.apache.org/jira/browse/ISIS-2034 > Project: Isis > Issue Type: Bug > Components: Core: Viewer: RestfulObjects >Affects Versions: 2.0.0-M2 > Environment: Windows 7 >Reporter: Brian Kalbfus >Assignee: Andi Huber >Priority: Minor > Labels: not-an-issue > Fix For: 2.0.0-M2 > > Attachments: simpleappswaggerui.png > > > to reproduce: > # checkout HEAD of v2 branch > # mvn clean install > # cd to isis/example/application/simpleapp/webapp > # set PROTOTYPING=true > # mvn jetty:run > # open web browser to localhost:8080/wicket, sign in as sven/pass > # from prototyping menu, open swagger-ui > # reload private spec > # select simple - /service/simple.SimpleObjectMenu/actions/listAll/invoke > # click "Try it out" > expected: Response body should have some output - some json with metadata or > something > actual: Reponse body says "no content" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ISIS-2034) REST operations return empty response
[ https://issues.apache.org/jira/browse/ISIS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692159#comment-16692159 ] Brian Kalbfus edited comment on ISIS-2034 at 11/19/18 7:42 PM: --- Hi Andi, It gives me the same result if I create SimpleObject instances. See attached screenshot. If there are no instances, I'd expect there would be returned an empty list. I just did 'git pull' and rebuilt the simpleapp; I have the same result. The HTTP status code (missing from screenshot) is 401. Thanks, Brian was (Author: bkalbfus): Hi Andi, It gives me the same result if I create SimpleObject instances. See attached screenshot. If there are no instances, I'd expect there would be returned an empty list. I just did 'git pull' and rebuilt the simpleapp; I have the same result. Thanks, Brian > REST operations return empty response > - > > Key: ISIS-2034 > URL: https://issues.apache.org/jira/browse/ISIS-2034 > Project: Isis > Issue Type: Bug > Components: Core: Viewer: RestfulObjects >Affects Versions: 2.0.0-M2 > Environment: Windows 7 >Reporter: Brian Kalbfus >Assignee: Andi Huber >Priority: Minor > Labels: not-an-issue > Fix For: 2.0.0-M2 > > Attachments: simpleappswaggerui.png > > > to reproduce: > # checkout HEAD of v2 branch > # mvn clean install > # cd to isis/example/application/simpleapp/webapp > # set PROTOTYPING=true > # mvn jetty:run > # open web browser to localhost:8080/wicket, sign in as sven/pass > # from prototyping menu, open swagger-ui > # reload private spec > # select simple - /service/simple.SimpleObjectMenu/actions/listAll/invoke > # click "Try it out" > expected: Response body should have some output - some json with metadata or > something > actual: Reponse body says "no content" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ISIS-2034) REST operations return empty response
[ https://issues.apache.org/jira/browse/ISIS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692159#comment-16692159 ] Brian Kalbfus commented on ISIS-2034: - Hi Andi, It gives me the same result if I create SimpleObject instances. See attached screenshot. If there are no instances, I'd expect there would be returned an empty list. I just did 'git pull' and rebuilt the simpleapp; I have the same result. Thanks, Brian > REST operations return empty response > - > > Key: ISIS-2034 > URL: https://issues.apache.org/jira/browse/ISIS-2034 > Project: Isis > Issue Type: Bug > Components: Core: Viewer: RestfulObjects >Affects Versions: 2.0.0-M2 > Environment: Windows 7 >Reporter: Brian Kalbfus >Assignee: Andi Huber >Priority: Minor > Labels: not-an-issue > Fix For: 2.0.0-M2 > > Attachments: simpleappswaggerui.png > > > to reproduce: > # checkout HEAD of v2 branch > # mvn clean install > # cd to isis/example/application/simpleapp/webapp > # set PROTOTYPING=true > # mvn jetty:run > # open web browser to localhost:8080/wicket, sign in as sven/pass > # from prototyping menu, open swagger-ui > # reload private spec > # select simple - /service/simple.SimpleObjectMenu/actions/listAll/invoke > # click "Try it out" > expected: Response body should have some output - some json with metadata or > something > actual: Reponse body says "no content" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-2034) REST operations return empty response
[ https://issues.apache.org/jira/browse/ISIS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Kalbfus updated ISIS-2034: Attachment: simpleappswaggerui.png > REST operations return empty response > - > > Key: ISIS-2034 > URL: https://issues.apache.org/jira/browse/ISIS-2034 > Project: Isis > Issue Type: Bug > Components: Core: Viewer: RestfulObjects >Affects Versions: 2.0.0-M2 > Environment: Windows 7 >Reporter: Brian Kalbfus >Assignee: Andi Huber >Priority: Minor > Labels: not-an-issue > Fix For: 2.0.0-M2 > > Attachments: simpleappswaggerui.png > > > to reproduce: > # checkout HEAD of v2 branch > # mvn clean install > # cd to isis/example/application/simpleapp/webapp > # set PROTOTYPING=true > # mvn jetty:run > # open web browser to localhost:8080/wicket, sign in as sven/pass > # from prototyping menu, open swagger-ui > # reload private spec > # select simple - /service/simple.SimpleObjectMenu/actions/listAll/invoke > # click "Try it out" > expected: Response body should have some output - some json with metadata or > something > actual: Reponse body says "no content" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ISIS-2040) Authentication/Shiro: Add OpenID support
Andi Huber created ISIS-2040: Summary: Authentication/Shiro: Add OpenID support Key: ISIS-2040 URL: https://issues.apache.org/jira/browse/ISIS-2040 Project: Isis Issue Type: New Feature Components: Core: Security: Shiro Reporter: Andi Huber Assignee: Andi Huber Fix For: 2.0.0 Extend the shiro core plugin with buji-pac4j [1] [1] https://github.com/bujiio/buji-pac4j -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ISIS-2039) Redesign of Configuration
Andi Huber created ISIS-2039: Summary: Redesign of Configuration Key: ISIS-2039 URL: https://issues.apache.org/jira/browse/ISIS-2039 Project: Isis Issue Type: Improvement Components: Core Reporter: Andi Huber Assignee: Andi Huber Fix For: 2.0.0 Goals (proposed): 1) decouple configuration from the rest of the framework infrastructure 2) remove the concept of framework internal configuration services 3) plan for supporting 'Spring Configuration' or 'MicroProfile Configuration 1.1' via plugins 4) lets have immutable java data classes (config beans) to represent configuration instead of key/value maps 5) when PROTOTYPING, allow for download of a text-file, which can be edited offline and reused as we do with layouts -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-2038) Darkly Theme: tooltips render white text on almost white background
[ https://issues.apache.org/jira/browse/ISIS-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-2038: - Fix Version/s: 2.0.0-M2 > Darkly Theme: tooltips render white text on almost white background > --- > > Key: ISIS-2038 > URL: https://issues.apache.org/jira/browse/ISIS-2038 > Project: Isis > Issue Type: Sub-task >Reporter: Andi Huber >Priority: Minor > Fix For: 2.0.0-M2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ISIS-2038) Darkly Theme: tooltips render white text on almost white background
Andi Huber created ISIS-2038: Summary: Darkly Theme: tooltips render white text on almost white background Key: ISIS-2038 URL: https://issues.apache.org/jira/browse/ISIS-2038 Project: Isis Issue Type: Sub-task Reporter: Andi Huber -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-1757) JEE Support - container-provided connection pools
[ https://issues.apache.org/jira/browse/ISIS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-1757: - Fix Version/s: (was: 2.0.0-M2) 2.0.0 > JEE Support - container-provided connection pools > - > > Key: ISIS-1757 > URL: https://issues.apache.org/jira/browse/ISIS-1757 > Project: Isis > Issue Type: Sub-task >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0 > > > as per > https://lists.apache.org/thread.html/a815c6d3e50c02111d0cd3df93b70b529c18193f321e613b116119b4@%3Cdev.isis.apache.org%3E > I use JEE container provided connection pools and bind them to Isis/JDO via > JNDI. I'm not an expert on this, but I believe this works totally sane. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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:
-
Fix Version/s: (was: 2.0.0-M2)
2.0.0
> JEE 7+ Support
> --
>
> Key: ISIS-1767
> URL: https://issues.apache.org/jira/browse/ISIS-1767
> Project: Isis
> Issue Type: Improvement
> Components: Core
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0
>
>
> 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}|{color:green}*OK*{color}(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}|{color:green}*OK*{color}(6)|
> |Glassfish (full 4.1.2) |*OK*(1) |*OK*(1)
>|{color:green}*OK*{color}|todo
> |{color:green}*OK*{color}|{color:green}*OK*{color}|{color:green}*OK*{color}(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}|todo|
> |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)
> successfully tested against DN-5.1.5-SNAPSHOT (dedicated issue
> https://issues.apache.org/jira/browse/ISIS-1754)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (ISIS-1894) [WONT-FIX] Resteasy: Reactivate PrettyPrinting
[ https://issues.apache.org/jira/browse/ISIS-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber closed ISIS-1894. Resolution: Won't Fix Assignee: Andi Huber pretty printing is gone; modern browsers do this anyway on the client-side > [WONT-FIX] Resteasy: Reactivate PrettyPrinting > --- > > Key: ISIS-1894 > URL: https://issues.apache.org/jira/browse/ISIS-1894 > Project: Isis > Issue Type: Sub-task > Components: Core Plugins >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Minor > Fix For: 2.0.0-M2 > > > When splitting resteasy specific classes into the new > isis/plugins/jaxrs-resteasy-3 plugin I deactivated the PrettyPrinting > integration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ISIS-1845) [WONT-FIX] Improve code coverage regarding applib's test-suite
[ https://issues.apache.org/jira/browse/ISIS-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber closed ISIS-1845. Resolution: Won't Fix Code coverage by tests is an ongoing endeavor. Apparently a task, never to be completed. So I'm closing this. > [WONT-FIX] Improve code coverage regarding applib's test-suite > -- > > Key: ISIS-1845 > URL: https://issues.apache.org/jira/browse/ISIS-1845 > Project: Isis > Issue Type: Sub-task >Reporter: Andi Huber >Priority: Major > Fix For: 2.0.0-M2 > > > Currently we have about 28% code covered by tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-1845) [WONT-FIX] Improve code coverage regarding applib's test-suite
[ https://issues.apache.org/jira/browse/ISIS-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-1845: - Summary: [WONT-FIX] Improve code coverage regarding applib's test-suite (was: Improve code coverage regarding applib's test-suite) > [WONT-FIX] Improve code coverage regarding applib's test-suite > -- > > Key: ISIS-1845 > URL: https://issues.apache.org/jira/browse/ISIS-1845 > Project: Isis > Issue Type: Sub-task >Reporter: Andi Huber >Priority: Major > Fix For: 2.0.0-M2 > > > Currently we have about 28% code covered by tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-1277) Prepare for JDK 11
[ https://issues.apache.org/jira/browse/ISIS-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-1277: - Fix Version/s: (was: 2.0.0) 2.0.0-M2 > Prepare for JDK 11 > -- > > Key: ISIS-1277 > URL: https://issues.apache.org/jira/browse/ISIS-1277 > Project: Isis > Issue Type: Task > Components: Core >Affects Versions: 1.10.0 >Reporter: Jörg Rade >Priority: Minor > Fix For: 2.0.0-M2 > > > https://github.com/apache/isis/search?utf8=%E2%9C%93=setAccessible%28%29 > yields 9 hits. > According to [1] this will be a problem with Java 9. > [1] > https://jaxenter.de/java-9-release-verschoben-warum-jigsaw-noch-nicht-fertig-ist-31687 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-1894) [WONT-FIX] Resteasy: Reactivate PrettyPrinting
[ https://issues.apache.org/jira/browse/ISIS-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-1894: - Summary: [WONT-FIX] Resteasy: Reactivate PrettyPrinting (was: Resteasy: Reactivate PrettyPrinting ) > [WONT-FIX] Resteasy: Reactivate PrettyPrinting > --- > > Key: ISIS-1894 > URL: https://issues.apache.org/jira/browse/ISIS-1894 > Project: Isis > Issue Type: Sub-task > Components: Core Plugins >Reporter: Andi Huber >Priority: Minor > Fix For: 2.0.0-M2 > > > When splitting resteasy specific classes into the new > isis/plugins/jaxrs-resteasy-3 plugin I deactivated the PrettyPrinting > integration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-1894) [WONT-FIX] Resteasy: Reactivate PrettyPrinting
[ https://issues.apache.org/jira/browse/ISIS-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-1894: - Fix Version/s: (was: 2.0.0) 2.0.0-M2 > [WONT-FIX] Resteasy: Reactivate PrettyPrinting > --- > > Key: ISIS-1894 > URL: https://issues.apache.org/jira/browse/ISIS-1894 > Project: Isis > Issue Type: Sub-task > Components: Core Plugins >Reporter: Andi Huber >Priority: Minor > Fix For: 2.0.0-M2 > > > When splitting resteasy specific classes into the new > isis/plugins/jaxrs-resteasy-3 plugin I deactivated the PrettyPrinting > integration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ISIS-1277) Prepare for JDK 11
[ https://issues.apache.org/jira/browse/ISIS-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber closed ISIS-1277. Resolution: Fixed All subtasks finished. Status: Isis does build on JDK 11. Integration Tests do run on JDK 11 JVM. Module Path support is not planned yet. But is tracked with a new issue number. > Prepare for JDK 11 > -- > > Key: ISIS-1277 > URL: https://issues.apache.org/jira/browse/ISIS-1277 > Project: Isis > Issue Type: Task > Components: Core >Affects Versions: 1.10.0 >Reporter: Jörg Rade >Assignee: Andi Huber >Priority: Minor > Fix For: 2.0.0-M2 > > > https://github.com/apache/isis/search?utf8=%E2%9C%93=setAccessible%28%29 > yields 9 hits. > According to [1] this will be a problem with Java 9. > [1] > https://jaxenter.de/java-9-release-verschoben-warum-jigsaw-noch-nicht-fertig-ist-31687 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ISIS-1962) [WONT-FIX] Introduce an alternative core-plugin for sub class discovery
[ https://issues.apache.org/jira/browse/ISIS-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber closed ISIS-1962. Resolution: Won't Fix > [WONT-FIX] Introduce an alternative core-plugin for sub class discovery > --- > > Key: ISIS-1962 > URL: https://issues.apache.org/jira/browse/ISIS-1962 > Project: Isis > Issue Type: Improvement > Components: Core Plugins >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M2 > > > We try to get rid of javassist dependencies. > But currently we depend on 'swagger.io' and 'reflections.org' which both have > javassist dependencies. > With core-plugin 'discovery-reflections' we depend on 'reflections.org' which > seems no longer actively maintained. > I'm thinking of introducing a new core-plugin 'discovery-cdi' that does not > depend on 'reflections.org' but instead utilizes CDI's class discovery > mechanics. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ISIS-1962) Introduce an alternative core-plugin for sub class discovery
[ https://issues.apache.org/jira/browse/ISIS-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber reopened ISIS-1962: -- reopened just change title [WONT-FIX] > Introduce an alternative core-plugin for sub class discovery > > > Key: ISIS-1962 > URL: https://issues.apache.org/jira/browse/ISIS-1962 > Project: Isis > Issue Type: Improvement > Components: Core Plugins >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M2 > > > We try to get rid of javassist dependencies. > But currently we depend on 'swagger.io' and 'reflections.org' which both have > javassist dependencies. > With core-plugin 'discovery-reflections' we depend on 'reflections.org' which > seems no longer actively maintained. > I'm thinking of introducing a new core-plugin 'discovery-cdi' that does not > depend on 'reflections.org' but instead utilizes CDI's class discovery > mechanics. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ISIS-1277) Prepare for JDK 11
[ https://issues.apache.org/jira/browse/ISIS-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber reassigned ISIS-1277: Assignee: Andi Huber > Prepare for JDK 11 > -- > > Key: ISIS-1277 > URL: https://issues.apache.org/jira/browse/ISIS-1277 > Project: Isis > Issue Type: Task > Components: Core >Affects Versions: 1.10.0 >Reporter: Jörg Rade >Assignee: Andi Huber >Priority: Minor > Fix For: 2.0.0-M2 > > > https://github.com/apache/isis/search?utf8=%E2%9C%93=setAccessible%28%29 > yields 9 hits. > According to [1] this will be a problem with Java 9. > [1] > https://jaxenter.de/java-9-release-verschoben-warum-jigsaw-noch-nicht-fertig-ist-31687 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-1962) [WONT-FIX] Introduce an alternative core-plugin for sub class discovery
[ https://issues.apache.org/jira/browse/ISIS-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-1962: - Summary: [WONT-FIX] Introduce an alternative core-plugin for sub class discovery (was: Introduce an alternative core-plugin for sub class discovery) > [WONT-FIX] Introduce an alternative core-plugin for sub class discovery > --- > > Key: ISIS-1962 > URL: https://issues.apache.org/jira/browse/ISIS-1962 > Project: Isis > Issue Type: Improvement > Components: Core Plugins >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M2 > > > We try to get rid of javassist dependencies. > But currently we depend on 'swagger.io' and 'reflections.org' which both have > javassist dependencies. > With core-plugin 'discovery-reflections' we depend on 'reflections.org' which > seems no longer actively maintained. > I'm thinking of introducing a new core-plugin 'discovery-cdi' that does not > depend on 'reflections.org' but instead utilizes CDI's class discovery > mechanics. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ISIS-1983) [WONT-FIX] UI: upgrade to bootstrap 4
[ https://issues.apache.org/jira/browse/ISIS-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber closed ISIS-1983. Resolution: Won't Fix bootstrap 4 might naturally come with future versions of wicket; not a priority right now > [WONT-FIX] UI: upgrade to bootstrap 4 > - > > Key: ISIS-1983 > URL: https://issues.apache.org/jira/browse/ISIS-1983 > Project: Isis > Issue Type: Improvement > Components: Core: Viewer: Wicket >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M2 > > > There seems to be a Wicket 8 build for bootstrap 4. > https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/wicket-8.x-bootstrap-4.x -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-1983) [WONT-FIX] UI: upgrade to bootstrap 4
[ https://issues.apache.org/jira/browse/ISIS-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-1983: - Summary: [WONT-FIX] UI: upgrade to bootstrap 4 (was: UI: upgrade to bootstrap 4) > [WONT-FIX] UI: upgrade to bootstrap 4 > - > > Key: ISIS-1983 > URL: https://issues.apache.org/jira/browse/ISIS-1983 > Project: Isis > Issue Type: Improvement > Components: Core: Viewer: Wicket >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M2 > > > There seems to be a Wicket 8 build for bootstrap 4. > https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/wicket-8.x-bootstrap-4.x -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ISIS-1962) Introduce an alternative core-plugin for sub class discovery
[ https://issues.apache.org/jira/browse/ISIS-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber closed ISIS-1962. Resolution: Won't Fix Assignee: Andi Huber > Introduce an alternative core-plugin for sub class discovery > > > Key: ISIS-1962 > URL: https://issues.apache.org/jira/browse/ISIS-1962 > Project: Isis > Issue Type: Improvement > Components: Core Plugins >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0-M2 > > > We try to get rid of javassist dependencies. > But currently we depend on 'swagger.io' and 'reflections.org' which both have > javassist dependencies. > With core-plugin 'discovery-reflections' we depend on 'reflections.org' which > seems no longer actively maintained. > I'm thinking of introducing a new core-plugin 'discovery-cdi' that does not > depend on 'reflections.org' but instead utilizes CDI's class discovery > mechanics. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-2033) IoC Container Integration
[ https://issues.apache.org/jira/browse/ISIS-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-2033: - Description: Dan and I discussed an idea, where there could be a way for the framework to no longer 'care' about the persistence layer, session handling and event handling. Instead delegating this responsibility to an IoC Container. With that have all the domain objects being managed by the container and no longer care about domain-object's life-cycles. Candidates being Spring and JEE. Some inspiring videos (Spring) ... [1] [https://www.youtube.com/watch?v=aA4tfBGY6jY] [2] [https://www.youtube.com/watch?v=jDchAEHIht0] was: Could Spring Boot do the 'runtime' part such that Apache Isis can better focus on its key responsibilities? Some inspiring videos ... [1] https://www.youtube.com/watch?v=aA4tfBGY6jY [2] https://www.youtube.com/watch?v=jDchAEHIht0 > IoC Container Integration > - > > Key: ISIS-2033 > URL: https://issues.apache.org/jira/browse/ISIS-2033 > Project: Isis > Issue Type: Task >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0 > > > Dan and I discussed an idea, where there could be a way for the framework to > no longer 'care' about the persistence layer, session handling and event > handling. Instead delegating this responsibility to an IoC Container. With > that have all the domain objects being managed by the container and no longer > care about domain-object's life-cycles. > Candidates being Spring and JEE. > Some inspiring videos (Spring) ... > [1] [https://www.youtube.com/watch?v=aA4tfBGY6jY] > [2] [https://www.youtube.com/watch?v=jDchAEHIht0] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-2033) IoC Container Integration
[ https://issues.apache.org/jira/browse/ISIS-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-2033: - Summary: IoC Container Integration (was: Spring Boot Integration (investigate)) > IoC Container Integration > - > > Key: ISIS-2033 > URL: https://issues.apache.org/jira/browse/ISIS-2033 > Project: Isis > Issue Type: Task >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0 > > > Could Spring Boot do the 'runtime' part such that Apache Isis can better > focus on its key responsibilities? > Some inspiring videos ... > [1] https://www.youtube.com/watch?v=aA4tfBGY6jY > [2] https://www.youtube.com/watch?v=jDchAEHIht0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-1952) Java Module Path Support
[ https://issues.apache.org/jira/browse/ISIS-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-1952: - Summary: Java Module Path Support (was: We need to clean out split packages.) > Java Module Path Support > > > Key: ISIS-1952 > URL: https://issues.apache.org/jira/browse/ISIS-1952 > Project: Isis > Issue Type: Improvement >Reporter: Andi Huber >Priority: Major > Fix For: 3.0.0 > > > The Java module path does no longer allow split packages. > [1] > [https://www.logicbig.com/tutorials/core-java-tutorial/modules/split-packages.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-1952) We need to clean out split packages.
[ https://issues.apache.org/jira/browse/ISIS-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-1952: - Issue Type: Improvement (was: Sub-task) Parent: (was: ISIS-1277) > We need to clean out split packages. > > > Key: ISIS-1952 > URL: https://issues.apache.org/jira/browse/ISIS-1952 > Project: Isis > Issue Type: Improvement >Reporter: Andi Huber >Priority: Major > Fix For: 3.0.0 > > > The Java module path does no longer allow split packages. > [1] > [https://www.logicbig.com/tutorials/core-java-tutorial/modules/split-packages.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-1952) We need to clean out split packages.
[ https://issues.apache.org/jira/browse/ISIS-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-1952: - Fix Version/s: (was: 2.0.0) 3.0.0 > We need to clean out split packages. > > > Key: ISIS-1952 > URL: https://issues.apache.org/jira/browse/ISIS-1952 > Project: Isis > Issue Type: Sub-task >Reporter: Andi Huber >Priority: Major > Fix For: 3.0.0 > > > The Java module path does no longer allow split packages. > [1] > [https://www.logicbig.com/tutorials/core-java-tutorial/modules/split-packages.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-1952) We need to clean out split packages.
[ https://issues.apache.org/jira/browse/ISIS-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-1952: - Description: The Java module path does no longer allow split packages. [1] [https://www.logicbig.com/tutorials/core-java-tutorial/modules/split-packages.html] was: Java 9 does no longer allow split packages. [1] https://www.logicbig.com/tutorials/core-java-tutorial/modules/split-packages.html > We need to clean out split packages. > > > Key: ISIS-1952 > URL: https://issues.apache.org/jira/browse/ISIS-1952 > Project: Isis > Issue Type: Sub-task >Reporter: Andi Huber >Priority: Major > Fix For: 3.0.0 > > > The Java module path does no longer allow split packages. > [1] > [https://www.logicbig.com/tutorials/core-java-tutorial/modules/split-packages.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
