[jira] [Commented] (ISIS-369) For GSOC: Kemble: A domain-specific language aligned with the Apache Isis programming conventions.
[
https://issues.apache.org/jira/browse/ISIS-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14253088#comment-14253088
]
Jörg Rade commented on ISIS-369:
Thee seems to be some overlap with Sculptor Generator [1], an OS DSL for DDD.
[1] http://sculptorgenerator.org/
For GSOC: Kemble: A domain-specific language aligned with the Apache Isis
programming conventions.
--
Key: ISIS-369
URL: https://issues.apache.org/jira/browse/ISIS-369
Project: Isis
Issue Type: New Feature
Components: ZZZ: GSOC
Reporter: Dan Haywood
Labels: ddd, domain-driven-design, dsl, framework, gsoc,
gsoc2014, nakedobjects
The obvious technology to use is Eclipse's XText
[http://www.eclipse.org/Xtext/]. The grammar can be based on Xbase, which
provides full Java type compatibility and extended language constructs (in
common with in XTend, [http://www.eclipse.org/xtend/]).
NB: xtext now has an FX-based UML integration; see: http://vimeo.com/104115680
~~~
grammar org.apache.isis.kemble.Kemble
with org.eclipse.xtext.xbase.annotations.XbaseWithAnnotations
Below is a sketch of what that DSL might look like.
For entities:
@... // Isis and selected JDO annotations here
entity Customer {
...
inject ProductRepository products;
inject OrderRepository orders;
}
where:
- the products, orders imply an instance variable and a setter to allow
services to be injected into
- DomainObjectContainer container is provided automatically as a field
For entity properties:
entity Customer {
@ ... // annotations here
[derived] property String firstName {
modify;
clear;
default;
choices;
hide;
disable;
validate;
}
}
where
- property is a keyword
- String firstName
- implies the instance variable and the getter
- annotations can be specified, apply to the getter
- derived is an optional keyword
- if present, then only the hide keyword may be used
- if present, then the getter is in the business logic interface, not
structural.
- modify;
- is optional
- if present, implies the modifyXxx(String value) method
- clear;
- is optional
- if present, implies the void clearXxx() method
- default;
- is optional
- if present, implies the String defaultXxx() method
- choices;
- is optional
- if present, implies the CollectionString choicesXxx() method
- hide;
- is optional
- if present, implies the boolean hideXxx() method
- disable;
- is optional
- if present, implies the String disableXxx() method
- validate;
- is optional
- if present, implies the String validateXxx(String value) method
similarly for entity collections:
entity Customer {
@ ... // annotations here
[derived] collection ListOrder orders {
addTo;
removeFrom;
hide;
disable;
validateAddTo;
validateRemoveFrom;
}
}
where
- collection is a keyword
- derived is an optional keyword
- if present, then only the hide keyword may be used
- if present, then the getter is in the business logic interface, not
structural.
- addTo;
- is optional
- if present ,implies void addTo(Order o) { }
- removeFrom;
- is optional
- if present ,implies void removeFrom(Order o) { }
- hide;
- as properties
- disable;
- as properties
- validateAddTo;
- is optional
- if present ,implies String validateAddToXxx(Order o) { ... }
- validateRemoveFrom;
- is optional
- if present ,implies String validateRemoveFromXxx(Order o) { ... }
and similarly for entity actions:
entity Customer {
@... // annotations here
action Order placeOrder {
param Product product {
default;
choices;
autoComplete;
validate;
},
param int quantity {
default;
choices;
autoComplete;
validate;
},
param String description {
default;
choices;
autoComplete;
validate;
}
}
hide;
disable;
validate;
}
}
where
- the name of the parameter would imply @Named(...)
- param's default:
- is optional
- corresponds to: Product default0PlaceOrder() { ... }
or: int default1PlaceOrder() { ... }
or: String default2PlaceOrder() { ... }
- param's choices
- is optional
- corresponds to: CollectionProduct default0PlaceOrder() { ... }
or: CollectionInteger
choices1PlaceOrder(Product p) { ... }
or: CollectionString choices2PlaceOrder(Product
p, int quantity) { ... }
- note how the Nth method has N-1 params
- ALSO: cannot have both choices
[jira] [Comment Edited] (ISIS-369) For GSOC: Kemble: A domain-specific language aligned with the Apache Isis programming conventions.
[
https://issues.apache.org/jira/browse/ISIS-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14253088#comment-14253088
]
Jörg Rade edited comment on ISIS-369 at 12/19/14 7:18 AM:
--
There seems to be some overlap with Sculptor Generator [1], an OS DSL for DDD.
[1] http://sculptorgenerator.org/
was (Author: joerg.rade):
Thee seems to be some overlap with Sculptor Generator [1], an OS DSL for DDD.
[1] http://sculptorgenerator.org/
For GSOC: Kemble: A domain-specific language aligned with the Apache Isis
programming conventions.
--
Key: ISIS-369
URL: https://issues.apache.org/jira/browse/ISIS-369
Project: Isis
Issue Type: New Feature
Components: ZZZ: GSOC
Reporter: Dan Haywood
Labels: ddd, domain-driven-design, dsl, framework, gsoc,
gsoc2014, nakedobjects
The obvious technology to use is Eclipse's XText
[http://www.eclipse.org/Xtext/]. The grammar can be based on Xbase, which
provides full Java type compatibility and extended language constructs (in
common with in XTend, [http://www.eclipse.org/xtend/]).
NB: xtext now has an FX-based UML integration; see: http://vimeo.com/104115680
~~~
grammar org.apache.isis.kemble.Kemble
with org.eclipse.xtext.xbase.annotations.XbaseWithAnnotations
Below is a sketch of what that DSL might look like.
For entities:
@... // Isis and selected JDO annotations here
entity Customer {
...
inject ProductRepository products;
inject OrderRepository orders;
}
where:
- the products, orders imply an instance variable and a setter to allow
services to be injected into
- DomainObjectContainer container is provided automatically as a field
For entity properties:
entity Customer {
@ ... // annotations here
[derived] property String firstName {
modify;
clear;
default;
choices;
hide;
disable;
validate;
}
}
where
- property is a keyword
- String firstName
- implies the instance variable and the getter
- annotations can be specified, apply to the getter
- derived is an optional keyword
- if present, then only the hide keyword may be used
- if present, then the getter is in the business logic interface, not
structural.
- modify;
- is optional
- if present, implies the modifyXxx(String value) method
- clear;
- is optional
- if present, implies the void clearXxx() method
- default;
- is optional
- if present, implies the String defaultXxx() method
- choices;
- is optional
- if present, implies the CollectionString choicesXxx() method
- hide;
- is optional
- if present, implies the boolean hideXxx() method
- disable;
- is optional
- if present, implies the String disableXxx() method
- validate;
- is optional
- if present, implies the String validateXxx(String value) method
similarly for entity collections:
entity Customer {
@ ... // annotations here
[derived] collection ListOrder orders {
addTo;
removeFrom;
hide;
disable;
validateAddTo;
validateRemoveFrom;
}
}
where
- collection is a keyword
- derived is an optional keyword
- if present, then only the hide keyword may be used
- if present, then the getter is in the business logic interface, not
structural.
- addTo;
- is optional
- if present ,implies void addTo(Order o) { }
- removeFrom;
- is optional
- if present ,implies void removeFrom(Order o) { }
- hide;
- as properties
- disable;
- as properties
- validateAddTo;
- is optional
- if present ,implies String validateAddToXxx(Order o) { ... }
- validateRemoveFrom;
- is optional
- if present ,implies String validateRemoveFromXxx(Order o) { ... }
and similarly for entity actions:
entity Customer {
@... // annotations here
action Order placeOrder {
param Product product {
default;
choices;
autoComplete;
validate;
},
param int quantity {
default;
choices;
autoComplete;
validate;
},
param String description {
default;
choices;
autoComplete;
validate;
}
}
hide;
disable;
validate;
}
}
where
- the name of the parameter would imply @Named(...)
- param's default:
- is optional
- corresponds to: Product default0PlaceOrder() { ... }
or: int default1PlaceOrder() { ... }
or: String default2PlaceOrder() { ... }
- param's choices
- is optional
- corresponds to: CollectionProduct default0PlaceOrder() { ... }
or: CollectionInteger
choices1PlaceOrder(Product p
[jira] [Closed] (ISIS-1019) Upgrade dependencies to javassist, org.reflections
[ https://issues.apache.org/jira/browse/ISIS-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade closed ISIS-1019. --- Thx - the log messsages are gone now! I assume the creator is responsible for closing issues? If not, please reopen. -j Upgrade dependencies to javassist, org.reflections -- Key: ISIS-1019 URL: https://issues.apache.org/jira/browse/ISIS-1019 Project: Isis Issue Type: Improvement Components: Core Affects Versions: core-1.8.0 Reporter: Jörg Rade Assignee: Martin Grigorov Priority: Minor Fix For: core-1.8.0 Original Estimate: 1h Remaining Estimate: 1h Hi, as Mike Burton already pointed out [1] there is an issue with Java 8 (possibly interaction with eclipse). $mvn dependency:tree shows that there are two versions included via: javassist:javassist:jar:3.12.1.GA - org.reflections:reflections:jar:0.9.8 org.javassist:javassist:jar:3.18.1-GA - isis-core-unittestsupport, isis-core-metamodel According to [2], 3.18.2-GA should work with Java 8. [3] shows that reflections 0.9.9 uses 3.18.2 as well. Please update the dependencies if possible. Best regards Jörg [1] https://www.mail-archive.com/users@isis.apache.org/msg01966.html [2] http://stackoverflow.com/questions/25184467/javassist-in-sync-with-java-8 [3] http://search.maven.org/#artifactdetails%7Corg.reflections%7Creflections%7C0.9.9%7Cjar -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ISIS-1026) Upgrade jetty-console-maven-plugin to 1.56
Jörg Rade created ISIS-1026: --- Summary: Upgrade jetty-console-maven-plugin to 1.56 Key: ISIS-1026 URL: https://issues.apache.org/jira/browse/ISIS-1026 Project: Isis Issue Type: Improvement Components: Website/Other Environment: Java 8 Reporter: Jörg Rade Assignee: Dan Haywood Priority: Trivial Hi, I saw the comment in the (generated) pom.xml - for me (I'm on Java 8) 1.56 works and is ~50% faster in the build. Best regards Jörg [1] http://search.maven.org/#artifactdetails|org.simplericity.jettyconsole|jetty-console-maven-plugin|1.56|maven-plugin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1026) Upgrade jetty-console-maven-plugin to 1.56
[ https://issues.apache.org/jira/browse/ISIS-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade updated ISIS-1026: Environment: Java 8 Maven 3.2.5 Eclipse 4.3.2 m2eclipse 1.5.0.20140606-0033 was:Java 8 Upgrade jetty-console-maven-plugin to 1.56 -- Key: ISIS-1026 URL: https://issues.apache.org/jira/browse/ISIS-1026 Project: Isis Issue Type: Improvement Components: Website/Other Environment: Java 8 Maven 3.2.5 Eclipse 4.3.2 m2eclipse 1.5.0.20140606-0033 Reporter: Jörg Rade Assignee: Dan Haywood Priority: Trivial Hi, I saw the comment in the (generated) pom.xml - for me (I'm on Java 8) 1.56 works and is ~50% faster in the build. Best regards Jörg [1] http://search.maven.org/#artifactdetails|org.simplericity.jettyconsole|jetty-console-maven-plugin|1.56|maven-plugin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ISIS-1017) @PreDestroy annotated method is not called
Peter Brückler created ISIS-1017:
Summary: @PreDestroy annotated method is not called
Key: ISIS-1017
URL: https://issues.apache.org/jira/browse/ISIS-1017
Project: Isis
Issue Type: Bug
Components: Core
Affects Versions: archetype-simpleapp-1.7.0, archetype-simpleapp-1.8.0
Environment: Windows 7
Reporter: Peter Brückler
Assignee: Dan Haywood
Priority: Critical
Fix For: core-1.7.0
When annotating the DomainService SimpleObjects with
...
@PostConstruct
@Programmatic
public void init() {
System.out.println( @PostConstruct init called );
}
@PreDestroy
@Programmatic
public void shutdown() {
System.out.println( @PreDestroy shutdown called );
}
...
only the @PostConstruct method will be called out of the box.
Unfortunately, the annotated @PreDestroy method not.
How to reproduce:
1) Checkout, build and check that Simpleapp 1.7.0 or 1.8.0-Snapshot is running.
2) Introduce the mentioned @PostConstruct and @PreDestroy methods
an go sure, that a message will be logged when message is called.
3) build and deploy simpleapp-webapp.war to Tomcat v7.x or Tomcat v8.x
4) See log / use breakpoints to see that @PostConstruct method will be
successfully called.
15:40:18,311 [Schema Thread-2 DEBUG] Schema Transaction
closing with connection
org.datanucleus.store.rdbms.datasource.dbcp.PoolingDataSource$PoolGuardConnectionWrapper@74ce8acd
@PostConstruct init called
15:40:24,504 [Reflections Thread-2 INFO ] Reflections took 3181 ms
to scan 125 urls, producing 9629 keys and 59986 values
5) Stop simpleapp-webapp or redeploy it or even stop tomcat
6) See log / breakpoints and realize that no @PreDestroy method was called.
Negativ side effect is, that every associated connection to JMS / Elastic
Search, ... in @PostConstruct cannot be disconnected easily and cleanly.
As a workaround I have tried to activate the section in web.xml:
!--
THE FOLLOWING CONFIGURATION IS NOT REQUIRED IF THE WICKET VIEWER IS IN USE.
IF THE WICKET VIEWER CONFIGURATION IS REMOVED, THEN UNCOMMENT
--
listener
listener-classorg.apache.isis.core.webapp.IsisWebAppBootstrapper/listener-class
/listener
context-param
param-namedeploymentType/param-name
param-valueSERVER_EXPLORATION/param-value
/context-param
context-param
param-nameisis.viewers/param-name
param-valuerestfulobjects/param-value
/context-param
even this is not my scenario. Doing this the annotated methods gets called, but
I hit the IsisWicketApplication Error:
Failed to initialize
com.google.inject.ProvisionException: Guice provision errors:
1) Error in custom provider,
org.apache.isis.core.commons.exceptions.IsisException: Isis Context already set
up and cannot be replaced
at
org.apache.isis.core.runtime.runner.IsisInjectModule.provideIsisSystem(IsisInjectModule.java:132)
at
org.apache.isis.core.runtime.runner.IsisInjectModule.provideIsisSystem(IsisInjectModule.java:132)
while locating org.apache.isis.core.runtime.system.IsisSystem
for field at
org.apache.isis.viewer.wicket.viewer.IsisWicketApplication.system(IsisWicketApplication.java:140)
while locating webapp.SimpleApplication
The cool thing is, that this time both annotated method are called:
16:16:37,713 [Schema Thread-2 DEBUG] Schema Transaction
closing with connection
org.datanucleus.store.rdbms.datasource.dbcp.PoolingDataSource$PoolGuardConnectionWrapper@2339e31f
@PostConstruct init called
16:16:45,196 [Reflections Thread-2 INFO ] Reflections took 3259 ms
to scan 125 urls, producing 9629 keys and 59986 values
...
INFORMATION: Cleaning up Shiro Environment
@PreDestroy shutdown called
16:16:53,198 [IsisContext main INFO ] closing all instances
16:16:53,198 [IsisWebAppBootstrapper main INFO ] server shut down
Please fix that issue or assist me in creating a workaround.
Thanks,
Peter
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ISIS-1017) @PreDestroy annotated method is not called
[
https://issues.apache.org/jira/browse/ISIS-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Brückler updated ISIS-1017:
-
Attachment:
Tracelog2_PostConstruct_and_PreDestroy_called_but_with_IsisWicketApplication_error.txt
Tracelog1_only_PostConstruct_called.txt
Search for
@PostConstruct init called
@PreDestroy shutdown called
in tracelogs.
@PreDestroy annotated method is not called
--
Key: ISIS-1017
URL: https://issues.apache.org/jira/browse/ISIS-1017
Project: Isis
Issue Type: Bug
Components: Core
Affects Versions: archetype-simpleapp-1.7.0, archetype-simpleapp-1.8.0
Environment: Windows 7
Reporter: Peter Brückler
Assignee: Dan Haywood
Priority: Critical
Fix For: core-1.7.0
Attachments: Tracelog1_only_PostConstruct_called.txt,
Tracelog2_PostConstruct_and_PreDestroy_called_but_with_IsisWicketApplication_error.txt
When annotating the DomainService SimpleObjects with
...
@PostConstruct
@Programmatic
public void init() {
System.out.println( @PostConstruct init called );
}
@PreDestroy
@Programmatic
public void shutdown() {
System.out.println( @PreDestroy shutdown called );
}
...
only the @PostConstruct method will be called out of the box.
Unfortunately, the annotated @PreDestroy method not.
How to reproduce:
1) Checkout, build and check that Simpleapp 1.7.0 or 1.8.0-Snapshot is
running.
2) Introduce the mentioned @PostConstruct and @PreDestroy methods
an go sure, that a message will be logged when message is called.
3) build and deploy simpleapp-webapp.war to Tomcat v7.x or Tomcat v8.x
4) See log / use breakpoints to see that @PostConstruct method will be
successfully called.
15:40:18,311 [Schema Thread-2 DEBUG] Schema Transaction
closing with connection
org.datanucleus.store.rdbms.datasource.dbcp.PoolingDataSource$PoolGuardConnectionWrapper@74ce8acd
@PostConstruct init called
15:40:24,504 [Reflections Thread-2 INFO ] Reflections took 3181
ms to scan 125 urls, producing 9629 keys and 59986 values
5) Stop simpleapp-webapp or redeploy it or even stop tomcat
6) See log / breakpoints and realize that no @PreDestroy method was called.
Negativ side effect is, that every associated connection to JMS / Elastic
Search, ... in @PostConstruct cannot be disconnected easily and cleanly.
As a workaround I have tried to activate the section in web.xml:
!--
THE FOLLOWING CONFIGURATION IS NOT REQUIRED IF THE WICKET VIEWER IS IN
USE.
IF THE WICKET VIEWER CONFIGURATION IS REMOVED, THEN UNCOMMENT
--
listener
listener-classorg.apache.isis.core.webapp.IsisWebAppBootstrapper/listener-class
/listener
context-param
param-namedeploymentType/param-name
param-valueSERVER_EXPLORATION/param-value
/context-param
context-param
param-nameisis.viewers/param-name
param-valuerestfulobjects/param-value
/context-param
even this is not my scenario. Doing this the annotated methods gets called,
but I hit the IsisWicketApplication Error:
Failed to initialize
com.google.inject.ProvisionException: Guice provision errors:
1) Error in custom provider,
org.apache.isis.core.commons.exceptions.IsisException: Isis Context already
set up and cannot be replaced
at
org.apache.isis.core.runtime.runner.IsisInjectModule.provideIsisSystem(IsisInjectModule.java:132)
at
org.apache.isis.core.runtime.runner.IsisInjectModule.provideIsisSystem(IsisInjectModule.java:132)
while locating org.apache.isis.core.runtime.system.IsisSystem
for field at
org.apache.isis.viewer.wicket.viewer.IsisWicketApplication.system(IsisWicketApplication.java:140)
while locating webapp.SimpleApplication
The cool thing is, that this time both annotated method are called:
16:16:37,713 [Schema Thread-2 DEBUG] Schema Transaction
closing with connection
org.datanucleus.store.rdbms.datasource.dbcp.PoolingDataSource$PoolGuardConnectionWrapper@2339e31f
@PostConstruct init called
16:16:45,196 [Reflections Thread-2 INFO ] Reflections took 3259
ms to scan 125 urls, producing 9629 keys and 59986 values
...
INFORMATION: Cleaning up Shiro Environment
@PreDestroy shutdown called
16:16:53,198 [IsisContext main INFO ] closing all instances
16:16:53,198 [IsisWebAppBootstrapper main INFO ] server shut down
Please fix that issue or assist me in creating a workaround.
Thanks,
Peter
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (ISIS-1017) @PreDestroy annotated method is not called
[
https://issues.apache.org/jira/browse/ISIS-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295285#comment-14295285
]
Peter Brückler edited comment on ISIS-1017 at 1/28/15 3:27 PM:
---
Search for
@PostConstruct init called
@PreDestroy shutdown called
in attached tracelogs.
was (Author: bruecp):
Search for
@PostConstruct init called
@PreDestroy shutdown called
in tracelogs.
@PreDestroy annotated method is not called
--
Key: ISIS-1017
URL: https://issues.apache.org/jira/browse/ISIS-1017
Project: Isis
Issue Type: Bug
Components: Core
Affects Versions: archetype-simpleapp-1.7.0, archetype-simpleapp-1.8.0
Environment: Windows 7
Reporter: Peter Brückler
Assignee: Dan Haywood
Priority: Critical
Fix For: core-1.7.0
Attachments: Tracelog1_only_PostConstruct_called.txt,
Tracelog2_PostConstruct_and_PreDestroy_called_but_with_IsisWicketApplication_error.txt
When annotating the DomainService SimpleObjects with
...
@PostConstruct
@Programmatic
public void init() {
System.out.println( @PostConstruct init called );
}
@PreDestroy
@Programmatic
public void shutdown() {
System.out.println( @PreDestroy shutdown called );
}
...
only the @PostConstruct method will be called out of the box.
Unfortunately, the annotated @PreDestroy method not.
How to reproduce:
1) Checkout, build and check that Simpleapp 1.7.0 or 1.8.0-Snapshot is
running.
2) Introduce the mentioned @PostConstruct and @PreDestroy methods
an go sure, that a message will be logged when message is called.
3) build and deploy simpleapp-webapp.war to Tomcat v7.x or Tomcat v8.x
4) See log / use breakpoints to see that @PostConstruct method will be
successfully called.
15:40:18,311 [Schema Thread-2 DEBUG] Schema Transaction
closing with connection
org.datanucleus.store.rdbms.datasource.dbcp.PoolingDataSource$PoolGuardConnectionWrapper@74ce8acd
@PostConstruct init called
15:40:24,504 [Reflections Thread-2 INFO ] Reflections took 3181
ms to scan 125 urls, producing 9629 keys and 59986 values
5) Stop simpleapp-webapp or redeploy it or even stop tomcat
6) See log / breakpoints and realize that no @PreDestroy method was called.
Negativ side effect is, that every associated connection to JMS / Elastic
Search, ... in @PostConstruct cannot be disconnected easily and cleanly.
As a workaround I have tried to activate the section in web.xml:
!--
THE FOLLOWING CONFIGURATION IS NOT REQUIRED IF THE WICKET VIEWER IS IN
USE.
IF THE WICKET VIEWER CONFIGURATION IS REMOVED, THEN UNCOMMENT
--
listener
listener-classorg.apache.isis.core.webapp.IsisWebAppBootstrapper/listener-class
/listener
context-param
param-namedeploymentType/param-name
param-valueSERVER_EXPLORATION/param-value
/context-param
context-param
param-nameisis.viewers/param-name
param-valuerestfulobjects/param-value
/context-param
even this is not my scenario. Doing this the annotated methods gets called,
but I hit the IsisWicketApplication Error:
Failed to initialize
com.google.inject.ProvisionException: Guice provision errors:
1) Error in custom provider,
org.apache.isis.core.commons.exceptions.IsisException: Isis Context already
set up and cannot be replaced
at
org.apache.isis.core.runtime.runner.IsisInjectModule.provideIsisSystem(IsisInjectModule.java:132)
at
org.apache.isis.core.runtime.runner.IsisInjectModule.provideIsisSystem(IsisInjectModule.java:132)
while locating org.apache.isis.core.runtime.system.IsisSystem
for field at
org.apache.isis.viewer.wicket.viewer.IsisWicketApplication.system(IsisWicketApplication.java:140)
while locating webapp.SimpleApplication
The cool thing is, that this time both annotated method are called:
16:16:37,713 [Schema Thread-2 DEBUG] Schema Transaction
closing with connection
org.datanucleus.store.rdbms.datasource.dbcp.PoolingDataSource$PoolGuardConnectionWrapper@2339e31f
@PostConstruct init called
16:16:45,196 [Reflections Thread-2 INFO ] Reflections took 3259
ms to scan 125 urls, producing 9629 keys and 59986 values
...
INFORMATION: Cleaning up Shiro Environment
@PreDestroy shutdown called
16:16:53,198 [IsisContext main INFO ] closing all instances
16:16:53,198 [IsisWebAppBootstrapper main INFO ] server shut down
Please fix that issue or assist me in creating a workaround.
Thanks,
Peter
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ISIS-690) 'Show all' button for tables.
[ https://issues.apache.org/jira/browse/ISIS-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14318295#comment-14318295 ] Jörg Rade commented on ISIS-690: IMHO is this solved by the 'show all' link. 'Show all' button for tables. - Key: ISIS-690 URL: https://issues.apache.org/jira/browse/ISIS-690 Project: Isis Issue Type: New Feature Components: Viewer: Wicket Affects Versions: viewer-wicket-1.3.1 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor Fix For: viewer-wicket-1.8.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-171) Add-on module to allow domain entities to send emails.
[
https://issues.apache.org/jira/browse/ISIS-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14318307#comment-14318307
]
Jörg Rade commented on ISIS-171:
Isn't this solved with 1.8.0?
Add-on module to allow domain entities to send emails.
--
Key: ISIS-171
URL: https://issues.apache.org/jira/browse/ISIS-171
Project: Isis
Issue Type: New Feature
Components: Add-ons
Reporter: Dan Haywood
Priority: Minor
Fix For: core-2.0.0
Provide a standalone implementation of an email service that can be
registered as a hidden service, and injected into domain objects so that they
are able to send emails.
The signature of the interface would be something like:
[Hidden]
public interface EmailService {
void sendEmail(MessageDetails details) throws MessageException;
}
where MessageDetails holds the from, to, cc, bcc, the subject, the content,
any attachments etc
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (ISIS-1017) @PreDestroy annotated method is not called
[
https://issues.apache.org/jira/browse/ISIS-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Brückler closed ISIS-1017.
With actual 1.8.0-SNAPSHOT also @PreDestroy annotated method is called on
shutdown.
@PreDestroy annotated method is not called
--
Key: ISIS-1017
URL: https://issues.apache.org/jira/browse/ISIS-1017
Project: Isis
Issue Type: Bug
Components: Core
Affects Versions: core-1.7.0
Environment: Windows 7
Reporter: Peter Brückler
Assignee: Dan Haywood
Priority: Critical
Fix For: core-1.8.0
Attachments: Tracelog1_only_PostConstruct_called.txt,
Tracelog2_PostConstruct_and_PreDestroy_called_but_with_IsisWicketApplication_error.txt
When annotating the DomainService SimpleObjects with
...
@PostConstruct
@Programmatic
public void init() {
System.out.println( @PostConstruct init called );
}
@PreDestroy
@Programmatic
public void shutdown() {
System.out.println( @PreDestroy shutdown called );
}
...
only the @PostConstruct method will be called out of the box.
Unfortunately, the annotated @PreDestroy method not.
How to reproduce:
1) Checkout, build and check that Simpleapp 1.7.0 or 1.8.0-Snapshot is
running.
2) Introduce the mentioned @PostConstruct and @PreDestroy methods
an go sure, that a message will be logged when message is called.
3) build and deploy simpleapp-webapp.war to Tomcat v7.x or Tomcat v8.x
4) See log / use breakpoints to see that @PostConstruct method will be
successfully called.
15:40:18,311 [Schema Thread-2 DEBUG] Schema Transaction
closing with connection
org.datanucleus.store.rdbms.datasource.dbcp.PoolingDataSource$PoolGuardConnectionWrapper@74ce8acd
@PostConstruct init called
15:40:24,504 [Reflections Thread-2 INFO ] Reflections took 3181
ms to scan 125 urls, producing 9629 keys and 59986 values
5) Stop simpleapp-webapp or redeploy it or even stop tomcat
6) See log / breakpoints and realize that no @PreDestroy method was called.
Negativ side effect is, that every associated connection to JMS / Elastic
Search, ... in @PostConstruct cannot be disconnected easily and cleanly.
As a workaround I have tried to activate the section in web.xml:
!--
THE FOLLOWING CONFIGURATION IS NOT REQUIRED IF THE WICKET VIEWER IS IN
USE.
IF THE WICKET VIEWER CONFIGURATION IS REMOVED, THEN UNCOMMENT
--
listener
listener-classorg.apache.isis.core.webapp.IsisWebAppBootstrapper/listener-class
/listener
context-param
param-namedeploymentType/param-name
param-valueSERVER_EXPLORATION/param-value
/context-param
context-param
param-nameisis.viewers/param-name
param-valuerestfulobjects/param-value
/context-param
even this is not my scenario. Doing this the annotated methods gets called,
but I hit the IsisWicketApplication Error:
Failed to initialize
com.google.inject.ProvisionException: Guice provision errors:
1) Error in custom provider,
org.apache.isis.core.commons.exceptions.IsisException: Isis Context already
set up and cannot be replaced
at
org.apache.isis.core.runtime.runner.IsisInjectModule.provideIsisSystem(IsisInjectModule.java:132)
at
org.apache.isis.core.runtime.runner.IsisInjectModule.provideIsisSystem(IsisInjectModule.java:132)
while locating org.apache.isis.core.runtime.system.IsisSystem
for field at
org.apache.isis.viewer.wicket.viewer.IsisWicketApplication.system(IsisWicketApplication.java:140)
while locating webapp.SimpleApplication
The cool thing is, that this time both annotated method are called:
16:16:37,713 [Schema Thread-2 DEBUG] Schema Transaction
closing with connection
org.datanucleus.store.rdbms.datasource.dbcp.PoolingDataSource$PoolGuardConnectionWrapper@2339e31f
@PostConstruct init called
16:16:45,196 [Reflections Thread-2 INFO ] Reflections took 3259
ms to scan 125 urls, producing 9629 keys and 59986 values
...
INFORMATION: Cleaning up Shiro Environment
@PreDestroy shutdown called
16:16:53,198 [IsisContext main INFO ] closing all instances
16:16:53,198 [IsisWebAppBootstrapper main INFO ] server shut down
Please fix that issue or assist me in creating a workaround.
Thanks,
Peter
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ISIS-1085) Add cssClassFa to DomainObjectLayout
[ https://issues.apache.org/jira/browse/ISIS-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365686#comment-14365686 ] Jörg Rade commented on ISIS-1085: - Party and PartyType didn*t work. I could not spot any differences in their implementations as compared to 'Application'. Should I attach sources? Add cssClassFa to DomainObjectLayout Key: ISIS-1085 URL: https://issues.apache.org/jira/browse/ISIS-1085 Project: Isis Issue Type: Improvement Components: Core Affects Versions: core-1.8.0 Reporter: Jörg Rade Assignee: Dan Haywood Priority: Minor Fix For: 1.9.0 Attachments: ScreenShot 090 SALOG 2.5.6.0 -_ 2.6.0.0-SNAPSHOT - Mozilla Firefox.png, ScreenShot 091 IfcMgmt - Bndtools - sdm-dom_src_main_java_sdm_dom_Application.java - Eclipse SDK.png * @CssClassFa is deprecated but is able to decorate DomainObjects with font awesome icons. * this feature does not work reliably (in my app it works with 11 out 13 classes). * @DomainObjectLayout does not support cssClassFa currently # add attribute to @DomainObjectLayout, move/copy implementation # eventually fix bug # eventually remove deprecated annotation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1085) Add cssClassFa to DomainObjectLayout
[ https://issues.apache.org/jira/browse/ISIS-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365059#comment-14365059 ] Jörg Rade commented on ISIS-1085: - Hi Martin, they show the intrended cssClassFa icon - I'll attach some screenshots. Best regards Jörg Add cssClassFa to DomainObjectLayout Key: ISIS-1085 URL: https://issues.apache.org/jira/browse/ISIS-1085 Project: Isis Issue Type: Improvement Components: Core Affects Versions: core-1.8.0 Reporter: Jörg Rade Assignee: Dan Haywood Priority: Minor Fix For: 1.9.0 * @CssClassFa is deprecated but is able to decorate DomainObjects with font awesome icons. * this feature does not work reliably (in my app it works with 11 out 13 classes). * @DomainObjectLayout does not support cssClassFa currently # add attribute to @DomainObjectLayout, move/copy implementation # eventually fix bug # eventually remove deprecated annotation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1085) Add cssClassFa to DomainObjectLayout
[ https://issues.apache.org/jira/browse/ISIS-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade updated ISIS-1085: Attachment: ScreenShot 091 IfcMgmt - Bndtools - sdm-dom_src_main_java_sdm_dom_Application.java - Eclipse SDK.png ScreenShot 090 SALOG 2.5.6.0 -_ 2.6.0.0-SNAPSHOT - Mozilla Firefox.png Add cssClassFa to DomainObjectLayout Key: ISIS-1085 URL: https://issues.apache.org/jira/browse/ISIS-1085 Project: Isis Issue Type: Improvement Components: Core Affects Versions: core-1.8.0 Reporter: Jörg Rade Assignee: Dan Haywood Priority: Minor Fix For: 1.9.0 Attachments: ScreenShot 090 SALOG 2.5.6.0 -_ 2.6.0.0-SNAPSHOT - Mozilla Firefox.png, ScreenShot 091 IfcMgmt - Bndtools - sdm-dom_src_main_java_sdm_dom_Application.java - Eclipse SDK.png * @CssClassFa is deprecated but is able to decorate DomainObjects with font awesome icons. * this feature does not work reliably (in my app it works with 11 out 13 classes). * @DomainObjectLayout does not support cssClassFa currently # add attribute to @DomainObjectLayout, move/copy implementation # eventually fix bug # eventually remove deprecated annotation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ISIS-1085) Add cssClassFa to DomainObjectLayout
[ https://issues.apache.org/jira/browse/ISIS-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365059#comment-14365059 ] Jörg Rade edited comment on ISIS-1085 at 3/17/15 12:51 PM: --- Hi Martin, they show the intended cssClassFa icon - I'll attach some screenshots. Best regards Jörg was (Author: joerg.rade): Hi Martin, they show the intrended cssClassFa icon - I'll attach some screenshots. Best regards Jörg Add cssClassFa to DomainObjectLayout Key: ISIS-1085 URL: https://issues.apache.org/jira/browse/ISIS-1085 Project: Isis Issue Type: Improvement Components: Core Affects Versions: core-1.8.0 Reporter: Jörg Rade Assignee: Dan Haywood Priority: Minor Fix For: 1.9.0 Attachments: ScreenShot 090 SALOG 2.5.6.0 -_ 2.6.0.0-SNAPSHOT - Mozilla Firefox.png, ScreenShot 091 IfcMgmt - Bndtools - sdm-dom_src_main_java_sdm_dom_Application.java - Eclipse SDK.png * @CssClassFa is deprecated but is able to decorate DomainObjects with font awesome icons. * this feature does not work reliably (in my app it works with 11 out 13 classes). * @DomainObjectLayout does not support cssClassFa currently # add attribute to @DomainObjectLayout, move/copy implementation # eventually fix bug # eventually remove deprecated annotation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1136) Use maven-javadoc-plugin with doclet apiviz to generate javadoc with diagrams
[ https://issues.apache.org/jira/browse/ISIS-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade updated ISIS-1136: Attachment: apache_isis_applib-apiviz.log Use maven-javadoc-plugin with doclet apiviz to generate javadoc with diagrams - Key: ISIS-1136 URL: https://issues.apache.org/jira/browse/ISIS-1136 Project: Isis Issue Type: Improvement Reporter: Jörg Rade Assignee: Dan Haywood Priority: Trivial Attachments: apache_isis_applib-apiviz.log see https://code.google.com/p/apiviz/ and http://docs.jboss.org/netty/3.0/api/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1136) Use maven-javadoc-plugin with doclet apiviz to generate javadoc with diagrams
[ https://issues.apache.org/jira/browse/ISIS-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14511226#comment-14511226 ] Jörg Rade commented on ISIS-1136: - Asciidoc sounds promising. And it is indeed questionable wether automatically generated static diagrams will be helpful to deepen the understanding of dynamic interactions in isis. If you don't mind assign it to me - there isn't much to do but adding something to the pom(s) and stop javadoc complaining about some formal things - see the attachment. Best regards Jörg Use maven-javadoc-plugin with doclet apiviz to generate javadoc with diagrams - Key: ISIS-1136 URL: https://issues.apache.org/jira/browse/ISIS-1136 Project: Isis Issue Type: Improvement Reporter: Jörg Rade Assignee: Dan Haywood Priority: Trivial Attachments: apache_isis_applib-apiviz.log see https://code.google.com/p/apiviz/ and http://docs.jboss.org/netty/3.0/api/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1136) Use maven-javadoc-plugin with doclet apiviz to generate javadoc with diagrams
[ https://issues.apache.org/jira/browse/ISIS-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14521649#comment-14521649 ] Jörg Rade commented on ISIS-1136: - I surrender ;-), ie. please set to Won't Fix I was fooled by the warning limitation set to 100 - there would be much too much places to fix, repectivly to add these brainless @return and @param tags. Nevertheless I found a couple of places where ,,@ are not HTML escaped and a couple of dead links. Should I prepare a separate pull request? Best regards Jörg Use maven-javadoc-plugin with doclet apiviz to generate javadoc with diagrams - Key: ISIS-1136 URL: https://issues.apache.org/jira/browse/ISIS-1136 Project: Isis Issue Type: Improvement Reporter: Jörg Rade Assignee: Dan Haywood Priority: Trivial Attachments: apache_isis_applib-apiviz.log see https://code.google.com/p/apiviz/ and http://docs.jboss.org/netty/3.0/api/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1085) Add cssClassFa to DomainObjectLayout
[ https://issues.apache.org/jira/browse/ISIS-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494285#comment-14494285 ] Jörg Rade commented on ISIS-1085: - Done - please review. Add cssClassFa to DomainObjectLayout Key: ISIS-1085 URL: https://issues.apache.org/jira/browse/ISIS-1085 Project: Isis Issue Type: Improvement Components: Core Affects Versions: core-1.8.0 Reporter: Jörg Rade Assignee: Dan Haywood Priority: Minor Fix For: 1.9.0 Attachments: ScreenShot 090 SALOG 2.5.6.0 -_ 2.6.0.0-SNAPSHOT - Mozilla Firefox.png, ScreenShot 091 IfcMgmt - Bndtools - sdm-dom_src_main_java_sdm_dom_Application.java - Eclipse SDK.png * @CssClassFa is deprecated but is able to decorate DomainObjects with font awesome icons. * this feature does not work reliably (in my app it works with 11 out 13 classes). * @DomainObjectLayout does not support cssClassFa currently # add attribute to @DomainObjectLayout, move/copy implementation # eventually fix bug # eventually remove deprecated annotation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ISIS-1136) Use maven-javadoc-plugin with doclet apiviz to generate javadoc with diagrams
Jörg Rade created ISIS-1136: --- Summary: Use maven-javadoc-plugin with doclet apiviz to generate javadoc with diagrams Key: ISIS-1136 URL: https://issues.apache.org/jira/browse/ISIS-1136 Project: Isis Issue Type: Improvement Reporter: Jörg Rade Assignee: Dan Haywood Priority: Trivial see https://code.google.com/p/apiviz/ and http://docs.jboss.org/netty/3.0/api/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1085) Add cssClassFa to DomainObjectLayout
[ https://issues.apache.org/jira/browse/ISIS-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14483322#comment-14483322 ] Jörg Rade commented on ISIS-1085: - OK - I'll amend that Add cssClassFa to DomainObjectLayout Key: ISIS-1085 URL: https://issues.apache.org/jira/browse/ISIS-1085 Project: Isis Issue Type: Improvement Components: Core Affects Versions: core-1.8.0 Reporter: Jörg Rade Assignee: Dan Haywood Priority: Minor Fix For: 1.9.0 Attachments: ScreenShot 090 SALOG 2.5.6.0 -_ 2.6.0.0-SNAPSHOT - Mozilla Firefox.png, ScreenShot 091 IfcMgmt - Bndtools - sdm-dom_src_main_java_sdm_dom_Application.java - Eclipse SDK.png * @CssClassFa is deprecated but is able to decorate DomainObjects with font awesome icons. * this feature does not work reliably (in my app it works with 11 out 13 classes). * @DomainObjectLayout does not support cssClassFa currently # add attribute to @DomainObjectLayout, move/copy implementation # eventually fix bug # eventually remove deprecated annotation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1085) Add cssClassFa to DomainObjectLayout
[
https://issues.apache.org/jira/browse/ISIS-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392862#comment-14392862
]
Jörg Rade commented on ISIS-1085:
-
Is position required as in
{code}
assertThat(cssClassFacetAbstract.getPosition(),
is(ActionLayout.CssClassFaPosition.RIGHT));
{code}
?
Add cssClassFa to DomainObjectLayout
Key: ISIS-1085
URL: https://issues.apache.org/jira/browse/ISIS-1085
Project: Isis
Issue Type: Improvement
Components: Core
Affects Versions: core-1.8.0
Reporter: Jörg Rade
Assignee: Dan Haywood
Priority: Minor
Fix For: 1.9.0
Attachments: ScreenShot 090 SALOG 2.5.6.0 -_ 2.6.0.0-SNAPSHOT -
Mozilla Firefox.png, ScreenShot 091 IfcMgmt - Bndtools -
sdm-dom_src_main_java_sdm_dom_Application.java - Eclipse SDK.png
* @CssClassFa is deprecated but is able to decorate DomainObjects with font
awesome icons.
* this feature does not work reliably (in my app it works with 11 out 13
classes).
* @DomainObjectLayout does not support cssClassFa currently
# add attribute to @DomainObjectLayout, move/copy implementation
# eventually fix bug
# eventually remove deprecated annotation
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ISIS-1085) Add cssClassFa to DomainObjectLayout
[
https://issues.apache.org/jira/browse/ISIS-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392668#comment-14392668
]
Jörg Rade commented on ISIS-1085:
-
{code}
C:\data_jra\git\isisgit push -u origin ISIS-1085-CssClassFa
Username for 'https://github.com': joerg.r...@kuehne-nagel.com
Password for 'https://joerg.r...@kuehne-nagel.com@github.com':
Counting objects: 1138, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (307/307), done.
Writing objects: 100% (496/496), 59.10 KiB | 0 bytes/s, done.
Total 496 (delta 211), reused 252 (delta 71)
To http://github.com/joerg-rade/isis.git
* [new branch] ISIS-1085-CssClassFa - ISIS-1085-CssClassFa
Branch ISIS-1085-CssClassFa set up to track remote branch ISIS-1085-CssClassFa
from origin.
{code}
Add cssClassFa to DomainObjectLayout
Key: ISIS-1085
URL: https://issues.apache.org/jira/browse/ISIS-1085
Project: Isis
Issue Type: Improvement
Components: Core
Affects Versions: core-1.8.0
Reporter: Jörg Rade
Assignee: Dan Haywood
Priority: Minor
Fix For: 1.9.0
Attachments: ScreenShot 090 SALOG 2.5.6.0 -_ 2.6.0.0-SNAPSHOT -
Mozilla Firefox.png, ScreenShot 091 IfcMgmt - Bndtools -
sdm-dom_src_main_java_sdm_dom_Application.java - Eclipse SDK.png
* @CssClassFa is deprecated but is able to decorate DomainObjects with font
awesome icons.
* this feature does not work reliably (in my app it works with 11 out 13
classes).
* @DomainObjectLayout does not support cssClassFa currently
# add attribute to @DomainObjectLayout, move/copy implementation
# eventually fix bug
# eventually remove deprecated annotation
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ISIS-1238) MetaModel validation for derived properties that have @Property(editing=ENABLED)
[
https://issues.apache.org/jira/browse/ISIS-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14986981#comment-14986981
]
Jörg Rade commented on ISIS-1238:
-
Hi,
instead of notPersisted=true, I would prefer persisted=false
grtnx -j
> MetaModel validation for derived properties that have
> @Property(editing=ENABLED)
>
>
> Key: ISIS-1238
> URL: https://issues.apache.org/jira/browse/ISIS-1238
> Project: Isis
> Issue Type: New Feature
> Components: Core
>Affects Versions: 1.9.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Trivial
> Fix For: 1.11.0
>
>
> for example:
> private String firstName="Anju";
> @Property(editing=Editing.ENABLED,maxLength=9,notPersisted=true)
> public String getFirstName() {
> return firstName;
> }
> // no setter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ISIS-1172) User Guide / Wicket Viewer / Brand logo / Configuration
Jörg Rade created ISIS-1172:
---
Summary: User Guide / Wicket Viewer / Brand logo / Configuration
Key: ISIS-1172
URL: https://issues.apache.org/jira/browse/ISIS-1172
Project: Isis
Issue Type: Bug
Components: Core: Viewer: Wicket
Affects Versions: 1.9.0
Reporter: Jörg Rade
Assignee: Dan Haywood
Priority: Minor
{code}
bind(String.class).annotatedWith(Names.named(brandLogoHeader))
.toInstance(/images/knife-logo-header.png);
{code}
doesn't work for me. I had to specify
/sdm-webapp/images/knife-logo-header.png.
Tried. using images/knife-logo-header.png (-)
Compared generated the simple app from the maven archetype and diffed my
web.xml against the generated and adopted my web.xml to match my
SimpleApplication package name. (-)
Analysis by Martin:
Wicket automatically calculates the context relative path for plain HTML img
elements in your markup.
In the current case the img element is connected to a Java component, i.e. it
has wicket:id attribute, and that's why Wicket doesn't apply any special logic
on it.
IMO we should improve Isis to always calculate context relative path for the
logo url.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ISIS-1277) setAccessible() will be gone with JDK 9
Jörg Rade created ISIS-1277: --- Summary: setAccessible() will be gone with JDK 9 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: Dan Haywood Priority: Critical 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 (v6.3.4#6332)
[jira] [Commented] (ISIS-1284) Fails to render a property with compile-time type of Object but returning a value type (eg joda DateTime).
[ https://issues.apache.org/jira/browse/ISIS-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081087#comment-15081087 ] Jörg Rade commented on ISIS-1284: - No - using Object was an error on my side. > Fails to render a property with compile-time type of Object but returning a > value type (eg joda DateTime). > -- > > Key: ISIS-1284 > URL: https://issues.apache.org/jira/browse/ISIS-1284 > Project: Isis > Issue Type: Bug > Components: Core >Affects Versions: 1.10.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.14.0 > > > Was: "Unable to find component with id 'entityIconAndTitle'" > https://github.com/joerg-rade/myapp110 > see also mailing list thread: http://isis.markmail.org/thread/32umudzsj3p7x7tr -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1303) Rename the project to better describe its values and purpose
[ https://issues.apache.org/jira/browse/ISIS-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15132261#comment-15132261 ] Jörg Rade commented on ISIS-1303: - Very interesting discussion - made me come up to: ProjectNames: * PureObjects * Distill * Acceleration * Allegro * Flux Slogans: * "No Fuss - Just Objects" (cineastic) * "$less buzz | more action" (nerdic) -j > Rename the project to better describe its values and purpose > > > Key: ISIS-1303 > URL: https://issues.apache.org/jira/browse/ISIS-1303 > Project: Isis > Issue Type: Wish >Affects Versions: 1.11.1 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 1.13.0 > > Attachments: ApacheGestalt.jpg > > > In the past there have been a couple of discussions regarding renaming the > project, the reason generally cited being the potential embarrassment of > sharing a name with the jihadist militant group [1] currently prominent in > the headlines. After due discussion on the mailing lists the prevailing view > has been to retain our name: "we were here first". > Until now I've concurred with that view also... after all, I originally came > up with the name "Isis", originally based on the name of the Thames as it > flows through Oxford [2] (many of the original authors of the framework live > within Oxfordshire, UK). > Separately to that discussion, we have the issue of marketing. Originally we > marketed ourselves as a framework implementing the "naked objects" pattern > [3]; the original name of the framework (prior to Apache) was of course the > Naked Objects Framework. However, this pattern is either not well-known or > is misunderstood (only a low proportion of developers that encounter the idea > immediately "get it"). The crudity of the original user interfaces didn't > help. And the name also, of course, can cause embarrassment in some cultures. > Then, when domain-driven design [4] came along as a movement, that seemed an > obvious platform upon which to position the framework: we obviously share the > core belief that the domain is the most important bit of the system. However > - and I still find this surprising - despite attempts otherwise we haven't > really made too much of an impression in that community. The fact that the > DDD community got massively sidetracked for a while by the CQRS pattern is > perhaps part of it. I also often detect the view that DDD should imply not > using a framework. The irony of course is that in rejecting framework such > developers actually have to write more infrastructure code vs business domain > code. > Also, the fit is perhaps not all that good after all. In the DDD community I > don't see anyone talking about modules... one of the named patterns, and a > major focus of our framework, but missing from DDD talks. Instead they get > side-tracked talking only about aggregate roots or bounded contexts; all well > and good, but over-emphasised). > [Aside: Indeed, I raised the topic of modules with Eric Evans himself (in > person), and he agreed there was little emphasis. When I described our > framework's use of domain events to hook modules together (along with vetoing > behaviour we support) he admitted it was a new approach/pattern to him...] > Anyway, so DDD - which looked so promising - hasn't delivered. They might > come around to us one day, but it's probably time to define our own > individual space. Also, in the same way that everyone takes agile > development for granted as the "de facto", we ought to simply take DDD for > granted too... "of course you will be doing DDD, but are you doing it well?" > What we need to better market the framework is some other pattern or concept > or hook, and become known as the framework that best supports that idea. > There are several candidates: > - hexagonal architecture (also called ports and adapters, or the onion > architecture, and related to the clean architecture) > - don't repeat yourself principle > - aspect oriented programming (naked objects pattern is really the > recognition that UI presentation is a cross-cutting concern) > - the general concept of modularity > - DCI (data/context/interactions). > - "clean" "pure" "essential" pojo programming model > - agile, lean > - breaking down barriers between IT and business > Of these, I think that hexagonal architecture looks the best fit; it is well > regarded as a concept among the "cognoscenti&
[jira] [Commented] (ISIS-569) Fix JMock to support JDK7 (JavassistImposteriser)
[ https://issues.apache.org/jira/browse/ISIS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142408#comment-15142408 ] Jörg Rade commented on ISIS-569: 1.11.1 still seems to refer to jmock > Fix JMock to support JDK7 (JavassistImposteriser) > - > > Key: ISIS-569 > URL: https://issues.apache.org/jira/browse/ISIS-569 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: core-1.2.0 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: core-1.5.0 > > > Isis standardized on using JMock a while back, however as a library it > doesn't seem to be keeping up. > Specifically, its mocking of classes depends on cglib 2.x (and therefore asm > 3.x), which conflicts with cglib 3/ asm 4.x (required for JDK 7). > Candidates to replace it are mockito and jmockit. Personally I don't much > like mockito; jmockit comes out well in this comparison: > https://blog.42.nl/articles/mockito-powermock-vs-jmockit/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-569) Fix JMock to support JDK7 (JavassistImposteriser)
[ https://issues.apache.org/jira/browse/ISIS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142432#comment-15142432 ] Jörg Rade commented on ISIS-569: [INFO] [INFO] Building Isis Unit Test Support 1.12.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ isis-core-unittestsupport --- [INFO] org.apache.isis.core:isis-core-unittestsupport:jar:1.12.0-SNAPSHOT [INFO] +- org.ops4j.pax.tipi:org.ops4j.pax.tipi.junit:jar:4.12.0.1:compile [INFO] | \- org.ops4j.pax.tipi:org.ops4j.pax.tipi.hamcrest.core:jar:1.3.0.1:compile [INFO] +- org.picocontainer:picocontainer:jar:2.15:compile [INFO] +- org.jmock:jmock:jar:2.6.0:compile [INFO] | +- org.hamcrest:hamcrest-core:jar:1.1:compile [INFO] | \- org.hamcrest:hamcrest-library:jar:1.1:compile [INFO] +- org.jmock:jmock-junit4:jar:2.6.0:compile > Fix JMock to support JDK7 (JavassistImposteriser) > - > > Key: ISIS-569 > URL: https://issues.apache.org/jira/browse/ISIS-569 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: core-1.2.0 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: core-1.5.0 > > > Isis standardized on using JMock a while back, however as a library it > doesn't seem to be keeping up. > Specifically, its mocking of classes depends on cglib 2.x (and therefore asm > 3.x), which conflicts with cglib 3/ asm 4.x (required for JDK 7). > Candidates to replace it are mockito and jmockit. Personally I don't much > like mockito; jmockit comes out well in this comparison: > https://blog.42.nl/articles/mockito-powermock-vs-jmockit/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1172) Logo in wicket viewer should be calculated relative to context root
[
https://issues.apache.org/jira/browse/ISIS-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Rade updated ISIS-1172:
Summary: Logo in wicket viewer should be calculated relative to context
root (was: Logo in wicket viewer should be calculated relative to contet root.)
> Logo in wicket viewer should be calculated relative to context root
> ---
>
> Key: ISIS-1172
> URL: https://issues.apache.org/jira/browse/ISIS-1172
> Project: Isis
> Issue Type: Bug
> Components: Core: Viewer: Wicket
>Affects Versions: 1.9.0
>Reporter: Jörg Rade
>Priority: Minor
> Fix For: 1.13.0
>
>
> {code}
> bind(String.class).annotatedWith(Names.named("brandLogoHeader"))
> .toInstance("/images/knife-logo-header.png");
> {code}
> doesn't work for me. I had to specify
> "/sdm-webapp/images/knife-logo-header.png".
> Tried. using "images/knife-logo-header.png" (-)
> Compared generated the simple app from the maven archetype and diffed my
> web.xml against the generated and adopted my web.xml to match my
> SimpleApplication package name. (-)
> Analysis by Martin:
> Wicket automatically calculates the context relative path for plain HTML
> elements in your markup.
> In the current case the element is connected to a Java component, i.e.
> it has wicket:id attribute, and that's why Wicket doesn't apply any special
> logic on it.
> IMO we should improve Isis to always calculate context relative path for the
> logo url.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ISIS-1302) Use bundled JARs instead of plain ones
[ https://issues.apache.org/jira/browse/ISIS-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade updated ISIS-1302: Attachment: simpleApp110_not_a_bundle.xlsx List of possible replacements > Use bundled JARs instead of plain ones > -- > > Key: ISIS-1302 > URL: https://issues.apache.org/jira/browse/ISIS-1302 > Project: Isis > Issue Type: Sub-task > Components: Core >Reporter: Jörg Rade >Assignee: Dan Haywood >Priority: Trivial > Attachments: simpleApp110_not_a_bundle.xlsx > > > list of known replacements yet to be attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ISIS-1302) Use bundled JARs instead of plain ones
[
https://issues.apache.org/jira/browse/ISIS-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126279#comment-15126279
]
Jörg Rade edited comment on ISIS-1302 at 2/3/16 8:46 AM:
-
List of jars in ~\simpleapp\webapp\target\simpleapp-webapp-\WEB-INF\lib
checked with {code} java -jar biz.aQute.bnd-3.1 jar verify *.jar{code}
List of possible replacements looked up via
{code}http://jpm4j.org/#!/{code}
was (Author: joerg.rade):
List of jars in ~\simpleapp\webapp\target\simpleapp-webapp-\WEB-INF\lib
checked with {code} java -jar c:\bin\bnd\biz.aQute.bnd-3.1 jar verify
*.jar{code}
List of possible replacements looked up via
{code}http://jpm4j.org/#!/{code}
> Use bundled JARs instead of plain ones
> --
>
> Key: ISIS-1302
> URL: https://issues.apache.org/jira/browse/ISIS-1302
> Project: Isis
> Issue Type: Sub-task
> Components: Core
>Reporter: Jörg Rade
>Assignee: Dan Haywood
>Priority: Trivial
> Attachments: simpleApp110_not_a_bundle.xlsx
>
>
> list of known replacements yet to be attached
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ISIS-1303) Rename the project to better describe its values and purpose
[
https://issues.apache.org/jira/browse/ISIS-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130195#comment-15130195
]
Jörg Rade commented on ISIS-1303:
-
Hi,
{code}We are like dwarfs sitting on the shoulders of giants{code} and
definitely Engelbart is one of them. It would be nice to have all those
influences summarized.
For marketing purposes I think the variants of Hexagonal come in handy, since
they refer to the very expressive overview diagram and some honeycomb logo
could dig into the readers brain.
-j
> Rename the project to better describe its values and purpose
>
>
> Key: ISIS-1303
> URL: https://issues.apache.org/jira/browse/ISIS-1303
> Project: Isis
> Issue Type: Wish
>Affects Versions: 1.11.1
>Reporter: Dan Haywood
>Assignee: Dan Haywood
> Fix For: 1.13.0
>
>
> In the past there have been a couple of discussions regarding renaming the
> project, the reason generally cited being the potential embarrassment of
> sharing a name with the jihadist militant group [1] currently prominent in
> the headlines. After due discussion on the mailing lists the prevailing view
> has been to retain our name: "we were here first".
> Until now I've concurred with that view also... after all, I originally came
> up with the name "Isis", originally based on the name of the Thames as it
> flows through Oxford [2] (many of the original authors of the framework live
> within Oxfordshire, UK).
> Separately to that discussion, we have the issue of marketing. Originally we
> marketed ourselves as a framework implementing the "naked objects" pattern
> [3]; the original name of the framework (prior to Apache) was of course the
> Naked Objects Framework. However, this pattern is either not well-known or
> is misunderstood (only a low proportion of developers that encounter the idea
> immediately "get it"). The crudity of the original user interfaces didn't
> help. And the name also, of course, can cause embarrassment in some cultures.
> Then, when domain-driven design [4] came along as a movement, that seemed an
> obvious platform upon which to position the framework: we obviously share the
> core belief that the domain is the most important bit of the system. However
> - and I still find this surprising - despite attempts otherwise we haven't
> really made too much of an impression in that community. The fact that the
> DDD community got massively sidetracked for a while by the CQRS pattern is
> perhaps part of it. I also often detect the view that DDD should imply not
> using a framework. The irony of course is that in rejecting framework such
> developers actually have to write more infrastructure code vs business domain
> code.
> Also, the fit is perhaps not all that good after all. In the DDD community I
> don't see anyone talking about modules... one of the named patterns, and a
> major focus of our framework, but missing from DDD talks. Instead they get
> side-tracked talking only about aggregate roots or bounded contexts; all well
> and good, but over-emphasised).
> [Aside: Indeed, I raised the topic of modules with Eric Evans himself (in
> person), and he agreed there was little emphasis. When I described our
> framework's use of domain events to hook modules together (along with vetoing
> behaviour we support) he admitted it was a new approach/pattern to him...]
> Anyway, so DDD - which looked so promising - hasn't delivered. They might
> come around to us one day, but it's probably time to define our own
> individual space. Also, in the same way that everyone takes agile
> development for granted as the "de facto", we ought to simply take DDD for
> granted too... "of course you will be doing DDD, but are you doing it well?"
> What we need to better market the framework is some other pattern or concept
> or hook, and become known as the framework that best supports that idea.
> There are several candidates:
> - hexagonal architecture (also called ports and adapters, or the onion
> architecture, and related to the clean architecture)
> - don't repeat yourself principle
> - aspect oriented programming (naked objects pattern is really the
> recognition that UI presentation is a cross-cutting concern)
> - the general concept of modularity
> - DCI (data/context/interactions).
> - "clean" "pure" "essential" pojo programming model
> - agile, lean
> - breaking down barriers between IT and business
> Of these, I think that hexagonal architecture lo
[jira] [Comment Edited] (ISIS-1302) Use bundled JARs instead of plain ones
[
https://issues.apache.org/jira/browse/ISIS-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126279#comment-15126279
]
Jörg Rade edited comment on ISIS-1302 at 2/3/16 8:45 AM:
-
List of jars in ~\simpleapp\webapp\target\simpleapp-webapp-\WEB-INF\lib
checked with {code} java -jar c:\bin\bnd\biz.aQute.bnd-3.1 jar verify
*.jar{code}
List of possible replacements looked up via
{code}http://jpm4j.org/#!/{code}
was (Author: joerg.rade):
List of possible replacements
> Use bundled JARs instead of plain ones
> --
>
> Key: ISIS-1302
> URL: https://issues.apache.org/jira/browse/ISIS-1302
> Project: Isis
> Issue Type: Sub-task
> Components: Core
>Reporter: Jörg Rade
>Assignee: Dan Haywood
>Priority: Trivial
> Attachments: simpleApp110_not_a_bundle.xlsx
>
>
> list of known replacements yet to be attached
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ISIS-1301) Support OSGi Containers
Jörg Rade created ISIS-1301: --- Summary: Support OSGi Containers Key: ISIS-1301 URL: https://issues.apache.org/jira/browse/ISIS-1301 Project: Isis Issue Type: Wish Components: Core Reporter: Jörg Rade Assignee: Dan Haywood Priority: Minor Currently the war artifact contains all jars the application depends on. * Repackeging these unchanged jars over and over takes some time (in my case this is at par with compiling dom). * The footprint of the war when redeploying it over thin connections requires more bandwidth. * Supporting OSGi containers would have the addional benefit that only changed artifacts would have to exchanged in the running container. Production systems could benefit from the possibility of the OSGi lifecycle, ie. replacing artifacts without downtime. This will involve multiple steps, eg. * Using more bundled versions of dependencies (where available - Wicket, DataNucleus, Jetty already are bundled) * Building a bundled war (wab) * Making isis libs conform to OSGi's class loader requirements * Bridging the OSGi ServiceRegistry to use its Servies as DomainServices tbc ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ISIS-1302) Use bundled JARs instead of plain ones
Jörg Rade created ISIS-1302: --- Summary: Use bundled JARs instead of plain ones Key: ISIS-1302 URL: https://issues.apache.org/jira/browse/ISIS-1302 Project: Isis Issue Type: Sub-task Reporter: Jörg Rade Assignee: Dan Haywood Priority: Trivial list of known replacements yet to be attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1303) Rename the project to better describe its values and purpose
[ https://issues.apache.org/jira/browse/ISIS-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade updated ISIS-1303: Attachment: Offset-curves-of-sinus-curve.svg > Rename the project to better describe its values and purpose > > > Key: ISIS-1303 > URL: https://issues.apache.org/jira/browse/ISIS-1303 > Project: Isis > Issue Type: Wish >Affects Versions: 1.11.1 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 1.13.0 > > Attachments: ApacheFarthing.jpg, ApacheFarthing.jpg, > ApacheGestalt.jpg, Offset-curves-of-sinus-curve.svg > > > In the past there have been a couple of discussions regarding renaming the > project, the reason generally cited being the potential embarrassment of > sharing a name with the jihadist militant group [1] currently prominent in > the headlines. After due discussion on the mailing lists the prevailing view > has been to retain our name: "we were here first". > Until now I've concurred with that view also... after all, I originally came > up with the name "Isis", originally based on the name of the Thames as it > flows through Oxford [2] (many of the original authors of the framework live > within Oxfordshire, UK). > Separately to that discussion, we have the issue of marketing. Originally we > marketed ourselves as a framework implementing the "naked objects" pattern > [3]; the original name of the framework (prior to Apache) was of course the > Naked Objects Framework. However, this pattern is either not well-known or > is misunderstood (only a low proportion of developers that encounter the idea > immediately "get it"). The crudity of the original user interfaces didn't > help. And the name also, of course, can cause embarrassment in some cultures. > Then, when domain-driven design [4] came along as a movement, that seemed an > obvious platform upon which to position the framework: we obviously share the > core belief that the domain is the most important bit of the system. However > - and I still find this surprising - despite attempts otherwise we haven't > really made too much of an impression in that community. The fact that the > DDD community got massively sidetracked for a while by the CQRS pattern is > perhaps part of it. I also often detect the view that DDD should imply not > using a framework. The irony of course is that in rejecting framework such > developers actually have to write more infrastructure code vs business domain > code. > Also, the fit is perhaps not all that good after all. In the DDD community I > don't see anyone talking about modules... one of the named patterns, and a > major focus of our framework, but missing from DDD talks. Instead they get > side-tracked talking only about aggregate roots or bounded contexts; all well > and good, but over-emphasised). > [Aside: Indeed, I raised the topic of modules with Eric Evans himself (in > person), and he agreed there was little emphasis. When I described our > framework's use of domain events to hook modules together (along with vetoing > behaviour we support) he admitted it was a new approach/pattern to him...] > Anyway, so DDD - which looked so promising - hasn't delivered. They might > come around to us one day, but it's probably time to define our own > individual space. Also, in the same way that everyone takes agile > development for granted as the "de facto", we ought to simply take DDD for > granted too... "of course you will be doing DDD, but are you doing it well?" > What we need to better market the framework is some other pattern or concept > or hook, and become known as the framework that best supports that idea. > There are several candidates: > - hexagonal architecture (also called ports and adapters, or the onion > architecture, and related to the clean architecture) > - don't repeat yourself principle > - aspect oriented programming (naked objects pattern is really the > recognition that UI presentation is a cross-cutting concern) > - the general concept of modularity > - DCI (data/context/interactions). > - "clean" "pure" "essential" pojo programming model > - agile, lean > - breaking down barriers between IT and business > Of these, I think that hexagonal architecture looks the best fit; it is well > regarded as a concept among the "cognoscenti", but there are surprisingly no > open source frameworks out there (at least in the Java space) that position > themselves as being th
[jira] [Commented] (ISIS-1303) Rename the project to better describe its values and purpose
[ https://issues.apache.org/jira/browse/ISIS-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15154218#comment-15154218 ] Jörg Rade commented on ISIS-1303: - The Rodin Thinker is already used by http://sculptorgenerator.org/ Torsten Juergeleit (from sculptor) contributed https://libraries.io/github/vaulttec/isis-script My current favorites are: Amp, Ippon, Hajime, and Root. An Amp logo could look like [Offset-curves-of-sinus-curve.svg] in Isis or Apache colors. Using an alliteration name gives a push in sorting as well. > Rename the project to better describe its values and purpose > > > Key: ISIS-1303 > URL: https://issues.apache.org/jira/browse/ISIS-1303 > Project: Isis > Issue Type: Wish >Affects Versions: 1.11.1 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 1.13.0 > > Attachments: ApacheFarthing.jpg, ApacheFarthing.jpg, > ApacheGestalt.jpg, Offset-curves-of-sinus-curve.svg > > > In the past there have been a couple of discussions regarding renaming the > project, the reason generally cited being the potential embarrassment of > sharing a name with the jihadist militant group [1] currently prominent in > the headlines. After due discussion on the mailing lists the prevailing view > has been to retain our name: "we were here first". > Until now I've concurred with that view also... after all, I originally came > up with the name "Isis", originally based on the name of the Thames as it > flows through Oxford [2] (many of the original authors of the framework live > within Oxfordshire, UK). > Separately to that discussion, we have the issue of marketing. Originally we > marketed ourselves as a framework implementing the "naked objects" pattern > [3]; the original name of the framework (prior to Apache) was of course the > Naked Objects Framework. However, this pattern is either not well-known or > is misunderstood (only a low proportion of developers that encounter the idea > immediately "get it"). The crudity of the original user interfaces didn't > help. And the name also, of course, can cause embarrassment in some cultures. > Then, when domain-driven design [4] came along as a movement, that seemed an > obvious platform upon which to position the framework: we obviously share the > core belief that the domain is the most important bit of the system. However > - and I still find this surprising - despite attempts otherwise we haven't > really made too much of an impression in that community. The fact that the > DDD community got massively sidetracked for a while by the CQRS pattern is > perhaps part of it. I also often detect the view that DDD should imply not > using a framework. The irony of course is that in rejecting framework such > developers actually have to write more infrastructure code vs business domain > code. > Also, the fit is perhaps not all that good after all. In the DDD community I > don't see anyone talking about modules... one of the named patterns, and a > major focus of our framework, but missing from DDD talks. Instead they get > side-tracked talking only about aggregate roots or bounded contexts; all well > and good, but over-emphasised). > [Aside: Indeed, I raised the topic of modules with Eric Evans himself (in > person), and he agreed there was little emphasis. When I described our > framework's use of domain events to hook modules together (along with vetoing > behaviour we support) he admitted it was a new approach/pattern to him...] > Anyway, so DDD - which looked so promising - hasn't delivered. They might > come around to us one day, but it's probably time to define our own > individual space. Also, in the same way that everyone takes agile > development for granted as the "de facto", we ought to simply take DDD for > granted too... "of course you will be doing DDD, but are you doing it well?" > What we need to better market the framework is some other pattern or concept > or hook, and become known as the framework that best supports that idea. > There are several candidates: > - hexagonal architecture (also called ports and adapters, or the onion > architecture, and related to the clean architecture) > - don't repeat yourself principle > - aspect oriented programming (naked objects pattern is really the > recognition that UI presentation is a cross-cutting concern) > - the general concept of modularity > - DCI (data/context/interactions). > - "clean" "pure" "essential" pojo programmin
[jira] [Comment Edited] (ISIS-1303) Rename the project to better describe its values and purpose
[ https://issues.apache.org/jira/browse/ISIS-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15154218#comment-15154218 ] Jörg Rade edited comment on ISIS-1303 at 2/19/16 1:46 PM: -- The Rodin Thinker is already used by http://sculptorgenerator.org/ Torsten Juergeleit (from sculptor) contributed https://libraries.io/github/vaulttec/isis-script My current favorites are: Amp, Ippon, Hajime, and Root. An Amp logo could look like !Offset-curves-of-sinus-curve.svg! in Isis or Apache colors. Using an alliteration name gives a push in sorting as well. was (Author: joerg.rade): The Rodin Thinker is already used by http://sculptorgenerator.org/ Torsten Juergeleit (from sculptor) contributed https://libraries.io/github/vaulttec/isis-script My current favorites are: Amp, Ippon, Hajime, and Root. An Amp logo could look like [Offset-curves-of-sinus-curve.svg] in Isis or Apache colors. Using an alliteration name gives a push in sorting as well. > Rename the project to better describe its values and purpose > > > Key: ISIS-1303 > URL: https://issues.apache.org/jira/browse/ISIS-1303 > Project: Isis > Issue Type: Wish >Affects Versions: 1.11.1 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 1.13.0 > > Attachments: ApacheFarthing.jpg, ApacheFarthing.jpg, > ApacheGestalt.jpg, Offset-curves-of-sinus-curve.svg > > > In the past there have been a couple of discussions regarding renaming the > project, the reason generally cited being the potential embarrassment of > sharing a name with the jihadist militant group [1] currently prominent in > the headlines. After due discussion on the mailing lists the prevailing view > has been to retain our name: "we were here first". > Until now I've concurred with that view also... after all, I originally came > up with the name "Isis", originally based on the name of the Thames as it > flows through Oxford [2] (many of the original authors of the framework live > within Oxfordshire, UK). > Separately to that discussion, we have the issue of marketing. Originally we > marketed ourselves as a framework implementing the "naked objects" pattern > [3]; the original name of the framework (prior to Apache) was of course the > Naked Objects Framework. However, this pattern is either not well-known or > is misunderstood (only a low proportion of developers that encounter the idea > immediately "get it"). The crudity of the original user interfaces didn't > help. And the name also, of course, can cause embarrassment in some cultures. > Then, when domain-driven design [4] came along as a movement, that seemed an > obvious platform upon which to position the framework: we obviously share the > core belief that the domain is the most important bit of the system. However > - and I still find this surprising - despite attempts otherwise we haven't > really made too much of an impression in that community. The fact that the > DDD community got massively sidetracked for a while by the CQRS pattern is > perhaps part of it. I also often detect the view that DDD should imply not > using a framework. The irony of course is that in rejecting framework such > developers actually have to write more infrastructure code vs business domain > code. > Also, the fit is perhaps not all that good after all. In the DDD community I > don't see anyone talking about modules... one of the named patterns, and a > major focus of our framework, but missing from DDD talks. Instead they get > side-tracked talking only about aggregate roots or bounded contexts; all well > and good, but over-emphasised). > [Aside: Indeed, I raised the topic of modules with Eric Evans himself (in > person), and he agreed there was little emphasis. When I described our > framework's use of domain events to hook modules together (along with vetoing > behaviour we support) he admitted it was a new approach/pattern to him...] > Anyway, so DDD - which looked so promising - hasn't delivered. They might > come around to us one day, but it's probably time to define our own > individual space. Also, in the same way that everyone takes agile > development for granted as the "de facto", we ought to simply take DDD for > granted too... "of course you will be doing DDD, but are you doing it well?" > What we need to better market the framework is some other pattern or concept > or hook, and become known as the framework that best supports that idea. > There are several candidates: > - hexagonal ar
[jira] [Updated] (ISIS-1302) Use bundled JARs instead of plain ones
[ https://issues.apache.org/jira/browse/ISIS-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade updated ISIS-1302: Description: For possible strategies see Managing 'OSGi Transitive Dependencies' [http://web.ist.utl.pt/ist162500/?p=1]. (was: list of known replacements yet to be attached) > Use bundled JARs instead of plain ones > -- > > Key: ISIS-1302 > URL: https://issues.apache.org/jira/browse/ISIS-1302 > Project: Isis > Issue Type: Sub-task > Components: Core >Reporter: Jörg Rade >Assignee: Dan Haywood >Priority: Trivial > Attachments: simpleApp110_not_a_bundle.xlsx > > > For possible strategies see Managing 'OSGi Transitive Dependencies' > [http://web.ist.utl.pt/ist162500/?p=1]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1358) Simpleapp created from archetype and packaged to war fails when deploying to Tomcat
[ https://issues.apache.org/jira/browse/ISIS-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221740#comment-15221740 ] Jörg Rade commented on ISIS-1358: - Hi, if I recall correctly, I had to exclude jetty from the war, since it doesn't make sense to embed a sevletcontainer when deploying to another one. HTH -j > Simpleapp created from archetype and packaged to war fails when deploying to > Tomcat > --- > > Key: ISIS-1358 > URL: https://issues.apache.org/jira/browse/ISIS-1358 > Project: Isis > Issue Type: Bug > Components: Archetype: SimpleApp >Affects Versions: 1.12.0 > Environment: Windows 10, Windows 7 > Tomcat version: Apache Tomcat/8.0.33 > JVM: 1.8.0_77-b03 >Reporter: Vladimir Nisevic >Assignee: Dan Haywood > Attachments: catalina.2016-03-31.log > > > Steps to reproduce: > * Created simpleapp from archetype (Version 1.12.0) > * Execute mvn clean package > * Take the file \webapp\target\simpleapp.war and deploy to tomcat thru e.g. > manager UI (http://localhost:8080/manager/html) > Attached the catalina.log -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1358) Simpleapp created from archetype and packaged to war fails when deploying to Tomcat
[
https://issues.apache.org/jira/browse/ISIS-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223753#comment-15223753
]
Jörg Rade commented on ISIS-1358:
-
Hi Vladimir,
this is from my webapp/pom.xml:
{code}
maven-war-plugin
ife-webapp
false
${maven.build.timestamp}
${agent.name}
${user.name}
Maven ${maven.version}
${java.version}
${os.name}
${project.version}
WEB-INF/lib/isis-core-webserver*.jar,
WEB-INF/lib/javax.servlet-api-*.jar,
WEB-INF/lib/javax.websocket-api-*.jar,
WEB-INF/lib/jetty-all-*.jar
{code}
Try to exclude more JARs from the WAR.
HTH -j
> Simpleapp created from archetype and packaged to war fails when deploying to
> Tomcat
> ---
>
> Key: ISIS-1358
> URL: https://issues.apache.org/jira/browse/ISIS-1358
> Project: Isis
> Issue Type: Bug
> Components: Archetype: SimpleApp
>Affects Versions: 1.12.0
> Environment: Windows 10, Windows 7
> Tomcat version: Apache Tomcat/8.0.33
> JVM: 1.8.0_77-b03
>Reporter: Vladimir Nisevic
>Assignee: Dan Haywood
> Attachments: catalina.2016-03-31.log
>
>
> Steps to reproduce:
> * Created simpleapp from archetype (Version 1.12.0)
> * Execute mvn clean package
> * Take the file \webapp\target\simpleapp.war and deploy to tomcat thru e.g.
> manager UI (http://localhost:8080/manager/html)
> Attached the catalina.log
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ISIS-1572) RestfulObjects viewer - Service members empty
[
https://issues.apache.org/jira/browse/ISIS-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15842999#comment-15842999
]
Jörg Rade commented on ISIS-1572:
-
See eMail thread:
https://lists.apache.org/api/atom.lua?mid=826e2d8ecfd4218d55e22d6e1983c52f549b5fc5dd5c1dd5ddc615f2@%3Cusers.isis.apache.org%3E
> RestfulObjects viewer - Service members empty
> -
>
> Key: ISIS-1572
> URL: https://issues.apache.org/jira/browse/ISIS-1572
> Project: Isis
> Issue Type: Bug
> Components: Core: Viewer: RestfulObjects
>Affects Versions: 1.13.0
> Environment: Web.xml is patched according to
> https://github.com/danhaywood/isis-angularjs-simpleapp in order to cope with
> CORS issues.
>Reporter: Jörg Rade
>
> _Sometimes_ the members section of the response to
> http://localhost:9090/restful/services/Applications/ is empty - sometimes it
> is not:
> {code|language=javascript}
> {
> "links" : [ {
> "rel" : "self",
> "href" : "http://localhost:9090/restful/services/Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/object\"",
> "title" : "Applications"
> }, {
> "rel" : "describedby",
> "href" :
> "http://localhost:9090/restful/domain-types/ife.dep.Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/domain-type\""
> }, {
> "rel" : "up",
> "href" : "http://localhost:9090/restful/services;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/list\""
> } ],
> "extensions" : {
> "oid" : "ife.dep.Applications:1",
> "isService" : true,
> "isPersistent" : true
> },
> "title" : "Applications",
> "serviceId" : "Applications",
> "members" : { }
> }
> {code}
> After some time the app was accessed via the wicket viewer. It first
> delivered the homepage and then I invoked the listAll operation via the
> respective menu item.
> Invoking http://localhost:9090/restful/services/Applications/ afterwards
> showed the expected response including the members.
> In another case there was a difference between:
> * http://localhost:9090/restful/services/Applications/ (with members) and
> * http://localhost:9090/restful/services/Applications (without members)
> In yet another case both URL's delivered a result without 'members' filled,
> even after the 'workaround' described above.
> https://github.com/joerg-rade/isis-app-todoapp shows the same behavior:
> * http://localhost:/restful/services/todo.ToDoItems/ whereas
> * http://localhost:/restful/domain-types/todoapp.dom.todoitem.ToDoItems
> shows the members
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ISIS-1572) RestfulObjects viewer - Service members empty
[
https://issues.apache.org/jira/browse/ISIS-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15885435#comment-15885435
]
Jörg Rade commented on ISIS-1572:
-
The unexpected behavior occurs when:
*
org.apache.isis.viewer.restfulobjects.server.authentication.AuthenticationSessionStrategyTrusted
is used instead of:
*
org.apache.isis.viewer.restfulobjects.server.authentication.AuthenticationSessionStrategyBasicAuth
> RestfulObjects viewer - Service members empty
> -
>
> Key: ISIS-1572
> URL: https://issues.apache.org/jira/browse/ISIS-1572
> Project: Isis
> Issue Type: Bug
> Components: Core: Viewer: RestfulObjects
>Affects Versions: 1.13.0
> Environment: Web.xml is patched according to
> https://github.com/danhaywood/isis-angularjs-simpleapp in order to cope with
> CORS issues.
>Reporter: Jörg Rade
>
> _Sometimes_ the members section of the response to
> http://localhost:9090/restful/services/Applications/ is empty - sometimes it
> is not:
> {code|language=javascript}
> {
> "links" : [ {
> "rel" : "self",
> "href" : "http://localhost:9090/restful/services/Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/object\"",
> "title" : "Applications"
> }, {
> "rel" : "describedby",
> "href" :
> "http://localhost:9090/restful/domain-types/ife.dep.Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/domain-type\""
> }, {
> "rel" : "up",
> "href" : "http://localhost:9090/restful/services;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/list\""
> } ],
> "extensions" : {
> "oid" : "ife.dep.Applications:1",
> "isService" : true,
> "isPersistent" : true
> },
> "title" : "Applications",
> "serviceId" : "Applications",
> "members" : { }
> }
> {code}
> After some time the app was accessed via the wicket viewer. It first
> delivered the homepage and then I invoked the listAll operation via the
> respective menu item.
> Invoking http://localhost:9090/restful/services/Applications/ afterwards
> showed the expected response including the members.
> In another case there was a difference between:
> * http://localhost:9090/restful/services/Applications/ (with members) and
> * http://localhost:9090/restful/services/Applications (without members)
> In yet another case both URL's delivered a result without 'members' filled,
> even after the 'workaround' described above.
> https://github.com/joerg-rade/isis-app-todoapp shows the same behavior:
> * http://localhost:/restful/services/todo.ToDoItems/ whereas
> * http://localhost:/restful/domain-types/todoapp.dom.todoitem.ToDoItems
> shows the members
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (ISIS-1489) Deprecate @Property(notPersisted=...) and replace with @Property(notAudited=...)
[
https://issues.apache.org/jira/browse/ISIS-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15522291#comment-15522291
]
Jörg Rade edited comment on ISIS-1489 at 9/26/16 7:08 AM:
--
How about
{code} audited=false{code}
instead of
{code} notAudited=true{code}
?
It saves 3 keypresses and and a half brain twist ;-)
was (Author: joerg.rade):
How about
{code} audited=false{code}
instead of
{code} notAudited=true{code}
?
It saves 4 keypresses and and a half brain twist ;-)
> Deprecate @Property(notPersisted=...) and replace with
> @Property(notAudited=...)
>
>
> Key: ISIS-1489
> URL: https://issues.apache.org/jira/browse/ISIS-1489
> Project: Isis
> Issue Type: Improvement
> Components: Core
>Affects Versions: 1.13.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Minor
> Fix For: 1.14.0
>
>
> In which case, the attribute should be deprecated, and a new
> @Property(notAudited=true) be introduced to replace it.
> It's used by:
> - ChangedObjectServiceInternal to determine if a property has changed;
> marking it as notPersisted means this functionality is skipped.
> - Memento (which you almost certainly don't use, I think is only used in
> anger by the Wicket viewer).
> It used to be used by the object persistor for persistence-by-reachability
> (if notPersisted then don't follow the graph), but I *think* that
> responsibility is now entirely that of JDO/DN.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ISIS-1489) Deprecate @Property(notPersisted=...) and replace with @Property(notAudited=...)
[
https://issues.apache.org/jira/browse/ISIS-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15522291#comment-15522291
]
Jörg Rade commented on ISIS-1489:
-
How about
{code} audited=false{code}
instead of
{code} notAudited=true{code}
?
It saves 4 keypresses and and a half brain twist ;-)
> Deprecate @Property(notPersisted=...) and replace with
> @Property(notAudited=...)
>
>
> Key: ISIS-1489
> URL: https://issues.apache.org/jira/browse/ISIS-1489
> Project: Isis
> Issue Type: Improvement
> Components: Core
>Affects Versions: 1.13.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Minor
> Fix For: 1.14.0
>
>
> In which case, the attribute should be deprecated, and a new
> @Property(notAudited=true) be introduced to replace it.
> It's used by:
> - ChangedObjectServiceInternal to determine if a property has changed;
> marking it as notPersisted means this functionality is skipped.
> - Memento (which you almost certainly don't use, I think is only used in
> anger by the Wicket viewer).
> It used to be used by the object persistor for persistence-by-reachability
> (if notPersisted then don't follow the graph), but I *think* that
> responsibility is now entirely that of JDO/DN.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ISIS-1572) RestfulObjects viewer - Service members empty
[
https://issues.apache.org/jira/browse/ISIS-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976197#comment-15976197
]
Jörg Rade commented on ISIS-1572:
-
https://mortoray.com/2014/04/09/allowing-unlimited-access-with-cors/ may shed
some light.
> RestfulObjects viewer - Service members empty
> -
>
> Key: ISIS-1572
> URL: https://issues.apache.org/jira/browse/ISIS-1572
> Project: Isis
> Issue Type: Bug
> Components: Core: Viewer: RestfulObjects
>Affects Versions: 1.13.0
> Environment: Web.xml is patched according to
> https://github.com/danhaywood/isis-angularjs-simpleapp in order to cope with
> CORS issues.
>Reporter: Jörg Rade
> Fix For: 1.15.0
>
>
> _Sometimes_ the members section of the response to
> http://localhost:9090/restful/services/Applications/ is empty - sometimes it
> is not:
> {code|language=javascript}
> {
> "links" : [ {
> "rel" : "self",
> "href" : "http://localhost:9090/restful/services/Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/object\"",
> "title" : "Applications"
> }, {
> "rel" : "describedby",
> "href" :
> "http://localhost:9090/restful/domain-types/ife.dep.Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/domain-type\""
> }, {
> "rel" : "up",
> "href" : "http://localhost:9090/restful/services;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/list\""
> } ],
> "extensions" : {
> "oid" : "ife.dep.Applications:1",
> "isService" : true,
> "isPersistent" : true
> },
> "title" : "Applications",
> "serviceId" : "Applications",
> "members" : { }
> }
> {code}
> After some time the app was accessed via the wicket viewer. It first
> delivered the homepage and then I invoked the listAll operation via the
> respective menu item.
> Invoking http://localhost:9090/restful/services/Applications/ afterwards
> showed the expected response including the members.
> In another case there was a difference between:
> * http://localhost:9090/restful/services/Applications/ (with members) and
> * http://localhost:9090/restful/services/Applications (without members)
> In yet another case both URL's delivered a result without 'members' filled,
> even after the 'workaround' described above.
> https://github.com/joerg-rade/isis-app-todoapp shows the same behavior:
> * http://localhost:/restful/services/todo.ToDoItems/ whereas
> * http://localhost:/restful/domain-types/todoapp.dom.todoitem.ToDoItems
> shows the members
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (ISIS-1572) RestfulObjects viewer - Service members empty
[
https://issues.apache.org/jira/browse/ISIS-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Rade resolved ISIS-1572.
-
Resolution: Cannot Reproduce
> RestfulObjects viewer - Service members empty
> -
>
> Key: ISIS-1572
> URL: https://issues.apache.org/jira/browse/ISIS-1572
> Project: Isis
> Issue Type: Bug
> Components: Core: Viewer: RestfulObjects
>Affects Versions: 1.13.0
> Environment: Web.xml is patched according to
> https://github.com/danhaywood/isis-angularjs-simpleapp in order to cope with
> CORS issues.
>Reporter: Jörg Rade
> Fix For: 1.15.0
>
>
> _Sometimes_ the members section of the response to
> http://localhost:9090/restful/services/Applications/ is empty - sometimes it
> is not:
> {code|language=javascript}
> {
> "links" : [ {
> "rel" : "self",
> "href" : "http://localhost:9090/restful/services/Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/object\"",
> "title" : "Applications"
> }, {
> "rel" : "describedby",
> "href" :
> "http://localhost:9090/restful/domain-types/ife.dep.Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/domain-type\""
> }, {
> "rel" : "up",
> "href" : "http://localhost:9090/restful/services;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/list\""
> } ],
> "extensions" : {
> "oid" : "ife.dep.Applications:1",
> "isService" : true,
> "isPersistent" : true
> },
> "title" : "Applications",
> "serviceId" : "Applications",
> "members" : { }
> }
> {code}
> After some time the app was accessed via the wicket viewer. It first
> delivered the homepage and then I invoked the listAll operation via the
> respective menu item.
> Invoking http://localhost:9090/restful/services/Applications/ afterwards
> showed the expected response including the members.
> In another case there was a difference between:
> * http://localhost:9090/restful/services/Applications/ (with members) and
> * http://localhost:9090/restful/services/Applications (without members)
> In yet another case both URL's delivered a result without 'members' filled,
> even after the 'workaround' described above.
> https://github.com/joerg-rade/isis-app-todoapp shows the same behavior:
> * http://localhost:/restful/services/todo.ToDoItems/ whereas
> * http://localhost:/restful/domain-types/todoapp.dom.todoitem.ToDoItems
> shows the members
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ISIS-1572) RestfulObjects viewer - Service members empty
[
https://issues.apache.org/jira/browse/ISIS-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16070167#comment-16070167
]
Jörg Rade commented on ISIS-1572:
-
In [1] a different CORS filter and configuration
(org.ebaysf.web.cors.CORSFilter) is suggested.
Seems to solve the issue.
[1] https://qnalist.com/questions/6453447/problems-with-isis-rest
> RestfulObjects viewer - Service members empty
> -
>
> Key: ISIS-1572
> URL: https://issues.apache.org/jira/browse/ISIS-1572
> Project: Isis
> Issue Type: Bug
> Components: Core: Viewer: RestfulObjects
>Affects Versions: 1.13.0
> Environment: Web.xml is patched according to
> https://github.com/danhaywood/isis-angularjs-simpleapp in order to cope with
> CORS issues.
>Reporter: Jörg Rade
> Fix For: 1.15.0
>
>
> _Sometimes_ the members section of the response to
> http://localhost:9090/restful/services/Applications/ is empty - sometimes it
> is not:
> {code|language=javascript}
> {
> "links" : [ {
> "rel" : "self",
> "href" : "http://localhost:9090/restful/services/Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/object\"",
> "title" : "Applications"
> }, {
> "rel" : "describedby",
> "href" :
> "http://localhost:9090/restful/domain-types/ife.dep.Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/domain-type\""
> }, {
> "rel" : "up",
> "href" : "http://localhost:9090/restful/services;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/list\""
> } ],
> "extensions" : {
> "oid" : "ife.dep.Applications:1",
> "isService" : true,
> "isPersistent" : true
> },
> "title" : "Applications",
> "serviceId" : "Applications",
> "members" : { }
> }
> {code}
> After some time the app was accessed via the wicket viewer. It first
> delivered the homepage and then I invoked the listAll operation via the
> respective menu item.
> Invoking http://localhost:9090/restful/services/Applications/ afterwards
> showed the expected response including the members.
> In another case there was a difference between:
> * http://localhost:9090/restful/services/Applications/ (with members) and
> * http://localhost:9090/restful/services/Applications (without members)
> In yet another case both URL's delivered a result without 'members' filled,
> even after the 'workaround' described above.
> https://github.com/joerg-rade/isis-app-todoapp shows the same behavior:
> * http://localhost:/restful/services/todo.ToDoItems/ whereas
> * http://localhost:/restful/domain-types/todoapp.dom.todoitem.ToDoItems
> shows the members
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ISIS-1572) RestfulObjects viewer - Service members empty
[
https://issues.apache.org/jira/browse/ISIS-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16070176#comment-16070176
]
Jörg Rade commented on ISIS-1572:
-
Maybe update https://github.com/danhaywood/isis-angularjs-simpleapp ?
> RestfulObjects viewer - Service members empty
> -
>
> Key: ISIS-1572
> URL: https://issues.apache.org/jira/browse/ISIS-1572
> Project: Isis
> Issue Type: Bug
> Components: Core: Viewer: RestfulObjects
>Affects Versions: 1.13.0
> Environment: Web.xml is patched according to
> https://github.com/danhaywood/isis-angularjs-simpleapp in order to cope with
> CORS issues.
>Reporter: Jörg Rade
> Fix For: 1.15.0
>
>
> _Sometimes_ the members section of the response to
> http://localhost:9090/restful/services/Applications/ is empty - sometimes it
> is not:
> {code|language=javascript}
> {
> "links" : [ {
> "rel" : "self",
> "href" : "http://localhost:9090/restful/services/Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/object\"",
> "title" : "Applications"
> }, {
> "rel" : "describedby",
> "href" :
> "http://localhost:9090/restful/domain-types/ife.dep.Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/domain-type\""
> }, {
> "rel" : "up",
> "href" : "http://localhost:9090/restful/services;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/list\""
> } ],
> "extensions" : {
> "oid" : "ife.dep.Applications:1",
> "isService" : true,
> "isPersistent" : true
> },
> "title" : "Applications",
> "serviceId" : "Applications",
> "members" : { }
> }
> {code}
> After some time the app was accessed via the wicket viewer. It first
> delivered the homepage and then I invoked the listAll operation via the
> respective menu item.
> Invoking http://localhost:9090/restful/services/Applications/ afterwards
> showed the expected response including the members.
> In another case there was a difference between:
> * http://localhost:9090/restful/services/Applications/ (with members) and
> * http://localhost:9090/restful/services/Applications (without members)
> In yet another case both URL's delivered a result without 'members' filled,
> even after the 'workaround' described above.
> https://github.com/joerg-rade/isis-app-todoapp shows the same behavior:
> * http://localhost:/restful/services/todo.ToDoItems/ whereas
> * http://localhost:/restful/domain-types/todoapp.dom.todoitem.ToDoItems
> shows the members
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ISIS-1644) Broken Links
[ https://issues.apache.org/jira/browse/ISIS-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade updated ISIS-1644: Description: A couple of links into the documentation are broken: | Source | Link Label | Broken | Existing | | https://github.com/apache/isis/tree/master/example/application/simpleapp | simpleapp archetype | http://isis.apache.org/guides/ugfun.html#_ugfun_getting-started_simpleapp-archetype | http://isis.apache.org/guides/ugfun/ugfun.html#_ugfun_getting-started_simpleapp-archetype | was: A couple of links into the documentation are broken: | Source | Link Label | Target | | https://github.com/apache/isis/tree/master/example/application/simpleapp | simpleapp archetype | http://isis.apache.org/guides/ugfun.html#_ugfun_getting-started_simpleapp-archetype | > Broken Links > > > Key: ISIS-1644 > URL: https://issues.apache.org/jira/browse/ISIS-1644 > Project: Isis > Issue Type: Documentation >Reporter: Jörg Rade > > A couple of links into the documentation are broken: > | Source | Link Label | Broken | Existing | > | https://github.com/apache/isis/tree/master/example/application/simpleapp | > simpleapp archetype | > http://isis.apache.org/guides/ugfun.html#_ugfun_getting-started_simpleapp-archetype > | > http://isis.apache.org/guides/ugfun/ugfun.html#_ugfun_getting-started_simpleapp-archetype > | -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ISIS-1644) Broken Links
Jörg Rade created ISIS-1644: --- Summary: Broken Links Key: ISIS-1644 URL: https://issues.apache.org/jira/browse/ISIS-1644 Project: Isis Issue Type: Documentation Reporter: Jörg Rade A couple of links into the documentation are broken: | Source | Link Label | Target | | https://github.com/apache/isis/tree/master/example/application/simpleapp | simpleapp archetype | http://isis.apache.org/guides/ugfun.html#_ugfun_getting-started_simpleapp-archetype | -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1643) NPE on SimpleApp about
[ https://issues.apache.org/jira/browse/ISIS-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072009#comment-16072009 ] Jörg Rade commented on ISIS-1643: - Hi Curt, when I click on 'Jar Manifest Attributes' a list of Jar's is shown. I' m on Windows7/FireFox though. Did you change the theme? Best regards Jörg > NPE on SimpleApp about > -- > > Key: ISIS-1643 > URL: https://issues.apache.org/jira/browse/ISIS-1643 > Project: Isis > Issue Type: Bug > Components: Archetype: SimpleApp >Affects Versions: 1.14.0 > Environment: Mac >Reporter: Curt Cox > Labels: newbie > > The SimpleApp about screen throws an NPE and doesn't show anything under "Jar > Manifest Attributes". Actually, some information flickers in the browser and > can still be inspected, but isn't visible to the user. > The exception starts with: > java.lang.NullPointerException > at > org.apache.isis.viewer.wicket.ui.panels.PanelAbstract.getAuthenticationSession(PanelAbstract.java:138) > at > org.apache.isis.viewer.wicket.ui.components.header.HeaderPanel$1.userProfileName(HeaderPanel.java:122) > at > org.apache.isis.viewer.wicket.ui.components.header.HeaderPanel.addUserName(HeaderPanel.java:106) > at > org.apache.isis.viewer.wicket.ui.components.header.HeaderPanel.onInitialize(HeaderPanel.java:79) > at org.apache.wicket.Component.fireInitialize(Component.java:877) > at > org.apache.wicket.MarkupContainer$3.component(MarkupContainer.java:967) > at > org.apache.wicket.MarkupContainer$3.component(MarkupContainer.java:963) > at org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:144) > at org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:162) > at org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:123) > at org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:192) > at > org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:875) > at > org.apache.wicket.MarkupContainer.internalInitialize(MarkupContainer.java:962) > at org.apache.wicket.Page.internalPrepareForRender(Page.java:238) > at org.apache.wicket.Component.render(Component.java:2290) > at org.apache.wicket.Page.renderPage(Page.java:1024) > Complete log is below: > === > ccox:gymclass curt.cox$ mvn -pl webapp jetty:run > [INFO] Scanning for projects... > [INFO] mixin-maven-plugin: Merging Mixins > [INFO] mixin-maven-plugin: Mixins were merged > [INFO] > [INFO] > > [INFO] Building SimpleApp Webapp 1.0-SNAPSHOT > [INFO] > > [INFO] > [INFO] >>> jetty-maven-plugin:9.3.5.v20151012:run (default-cli) > > test-compile @ gymclass-webapp >>> > Downloading: > https://oss.sonatype.org/content/repositories/snapshots/com/danhaywood/apps/gymclass-application/1.0-SNAPSHOT/maven-metadata.xml > Downloading: > https://repository.apache.org/content/repositories/snapshots/com/danhaywood/apps/gymclass-application/1.0-SNAPSHOT/maven-metadata.xml > Downloading: > https://repository.apache.org/content/repositories/snapshots/com/danhaywood/apps/gymclass/1.0-SNAPSHOT/maven-metadata.xml > Downloading: > https://oss.sonatype.org/content/repositories/snapshots/com/danhaywood/apps/gymclass/1.0-SNAPSHOT/maven-metadata.xml > Downloading: > https://oss.sonatype.org/content/repositories/snapshots/com/danhaywood/apps/gymclass-module-simple/1.0-SNAPSHOT/maven-metadata.xml > Downloading: > https://repository.apache.org/content/repositories/snapshots/com/danhaywood/apps/gymclass-module-simple/1.0-SNAPSHOT/maven-metadata.xml > [INFO] > [INFO] --- buildnumber-maven-plugin:1.4:create (default) @ gymclass-webapp --- > [INFO] Executing: /bin/sh -c cd '/Users/curt.cox/work/isis/gymclass/webapp' > && 'git' 'rev-parse' '--verify' 'HEAD' > [INFO] Working directory: /Users/curt.cox/work/isis/gymclass/webapp > [INFO] Storing buildNumber: null at timestamp: 1498862942921 > [WARNING] Cannot get the branch information from the git repository: > Detecting the current branch failed: fatal: Not a git repository (or any of > the parent directories): .git > [INFO] Executing: /bin/sh -c cd '/Users/curt.cox/work/isis/gymclass/webapp' > && 'git' 'rev-parse' '--verify' 'HEAD' > [INFO] Working directory: /Users/curt.cox/work/isis/gymclass/webapp > [INFO] Storing buildScmBranch: UNKNOWN_BRANCH > [INFO]
[jira] [Updated] (ISIS-1604) Extend support for SVG
[
https://issues.apache.org/jira/browse/ISIS-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Rade updated ISIS-1604:
Description:
Currently SVG images can be used:
* as Logo in the upper left corner (Wicket Menubar)
* on the Login Page (login.html)
* as favicon ("image/svg+xml", cf. [ISIS-1115])
SVGs are not displayed
* on the welcome page
SVGs can be attached as Blobs, but they are displayed as bitmaps (by means of
the Batik rasterizer) and do not scale. The rasterizer (of course) can not deal
with animations (cf. attachment).
See:
https://lists.apache.org/thread.html/68f16dd0306a8101c1cde06e5e6309b8d1b81b388a1f59e123cfc2f3@%3Cusers.isis.apache.org%3E
{code}
com.twelvemonkeys.imageio
imageio-batik
3.3.2
com.twelvemonkeys.imageio
imageio-batik
3.3.2
test-jar
test
org.apache.xmlgraphics
batik-transcoder
1.8
{code}
was:
Currently SVG images can only be used:
* as Logo in the upper left corner (Wicket Menubar)
* on the Login Page (login.html)
SVGs are not displayed
* on the welcome page
SVGs can be attached as Blobs, but they are displayed as bitmaps (by means of
the Batik rasterizer) and do not scale. The rasterizer (of course) can not deal
with animations (cf. attachment).
See:
https://lists.apache.org/thread.html/68f16dd0306a8101c1cde06e5e6309b8d1b81b388a1f59e123cfc2f3@%3Cusers.isis.apache.org%3E
{code}
com.twelvemonkeys.imageio
imageio-batik
3.3.2
com.twelvemonkeys.imageio
imageio-batik
3.3.2
test-jar
test
org.apache.xmlgraphics
batik-transcoder
1.8
{code}
> Extend support for SVG
> --
>
> Key: ISIS-1604
> URL: https://issues.apache.org/jira/browse/ISIS-1604
> Project: Isis
> Issue Type: Wish
> Components: Core: Viewer: Wicket
>Affects Versions: 1.14.0
>Reporter: Jörg Rade
>Priority: Minor
> Attachments: knife-logo-header.svg
>
>
> Currently SVG images can be used:
> * as Logo in the upper left corner (Wicket Menubar)
> * on the Login Page (login.html)
> * as favicon ("image/svg+xml", cf. [ISIS-1115])
> SVGs are not displayed
> * on the welcome page
> SVGs can be attached as Blobs, but they are displayed as bitmaps (by means of
> the Batik rasterizer) and do not scale. The rasterizer (of course) can not
> deal with animations (cf. attachment).
> See:
> https://lists.apache.org/thread.html/68f16dd0306a8101c1cde06e5e6309b8d1b81b388a1f59e123cfc2f3@%3Cusers.isis.apache.org%3E
> {code}
>
> com.twelvemonkeys.imageio
> imageio-batik
> 3.3.2
>
>
> com.twelvemonkeys.imageio
> imageio-batik
> 3.3.2
> test-jar
> test
>
>
> org.apache.xmlgraphics
> batik-transcoder
> 1.8
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ISIS-1604) Extend support for SVG
Jörg Rade created ISIS-1604:
---
Summary: Extend support for SVG
Key: ISIS-1604
URL: https://issues.apache.org/jira/browse/ISIS-1604
Project: Isis
Issue Type: Wish
Components: Core: Viewer: Wicket
Affects Versions: 1.14.0
Reporter: Jörg Rade
Priority: Minor
Attachments: knife-logo-header.svg
Currently SVG images can only be used:
* as Logo in the upper left corner (Wicket Menubar)
* on the Login Page (login.html)
SVGs are not displayed
* on the welcome page
SVGs can be attached as Blobs, but they are displayed as bitmaps (by means of
the Batik rasterizer) and do not scale. The rasterizer (of course) can not deal
with animations (cf. attachment).
See:
https://lists.apache.org/thread.html/68f16dd0306a8101c1cde06e5e6309b8d1b81b388a1f59e123cfc2f3@%3Cusers.isis.apache.org%3E
{code}
com.twelvemonkeys.imageio
imageio-batik
3.3.2
com.twelvemonkeys.imageio
imageio-batik
3.3.2
test-jar
test
org.apache.xmlgraphics
batik-transcoder
1.8
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ISIS-1635) Upgrade dependency to resteasy
[
https://issues.apache.org/jira/browse/ISIS-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Rade updated ISIS-1635:
Attachment: Dependency-Check.png
> Upgrade dependency to resteasy
> --
>
> Key: ISIS-1635
> URL: https://issues.apache.org/jira/browse/ISIS-1635
> Project: Isis
> Issue Type: Improvement
> Components: Core: Viewer: RestfulObjects
>Reporter: Jörg Rade
> Attachments: Dependency-Check.png
>
>
> org.codehaus.jackson brings in some vulnerabilities:
> !ScreenShot 757 Dependency-Check Report - Mozilla Firefox.pngl!
> {code}
> [INFO] | +-
> org.apache.isis.core:isis-core-viewer-restfulobjects-server:jar:1.14.0:compile
> [INFO] | | +-
> org.apache.isis.core:isis-core-viewer-restfulobjects-rendering:jar:1.14.0:compile
> [INFO] | | | +-
> org.jboss.resteasy:resteasy-jaxb-provider:jar:3.0.14.Final:compile
> [INFO] | | | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.7:compile
> [INFO] | | | | | +- com.sun.xml.bind:jaxb-core:jar:2.2.7:compile
> [INFO] | | | | | | +- javax.xml.bind:jaxb-api:jar:2.2.7:compile
> [INFO] | | | | | | \-
> com.sun.istack:istack-commons-runtime:jar:2.16:compile
> [INFO] | | | | | \-
> com.sun.xml.fastinfoset:FastInfoset:jar:1.2.12:compile
> [INFO] | | | | | \- javax.xml.bind:jsr173_api:jar:1.0:compile
> [INFO] | | | | \- org.jboss.logging:jboss-logging:jar:3.1.4.GA:compile
> [INFO] | | | +-
> org.jboss.resteasy:resteasy-jackson-provider:jar:3.0.14.Final:compile
> [INFO] | | | | +- org.codehaus.jackson:jackson-core-asl:jar:1.9.12:compile
> [INFO] | | | | +-
> org.codehaus.jackson:jackson-mapper-asl:jar:1.9.12:compile
> [INFO] | | | | +- org.codehaus.jackson:jackson-jaxrs:jar:1.9.12:compile
> [INFO] | | | | \- org.codehaus.jackson:jackson-xc:jar:1.9.12:compile
> {code}
> Please upgrade to 3.1.3Final if feasible:
> {code}
>
> org.jboss.resteasy
> resteasy-jackson-provider
> 3.1.3.Final
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ISIS-1635) Upgrade dependency to resteasy
Jörg Rade created ISIS-1635:
---
Summary: Upgrade dependency to resteasy
Key: ISIS-1635
URL: https://issues.apache.org/jira/browse/ISIS-1635
Project: Isis
Issue Type: Improvement
Components: Core: Viewer: RestfulObjects
Reporter: Jörg Rade
Attachments: ScreenShot 757 Dependency-Check Report - Mozilla
Firefox.png
org.codehaus.jackson brings in some vulnerabilities:
!ScreenShot 757 Dependency-Check Report - Mozilla Firefox.png|thumbnail!
{code}
[INFO] | +-
org.apache.isis.core:isis-core-viewer-restfulobjects-server:jar:1.14.0:compile
[INFO] | | +-
org.apache.isis.core:isis-core-viewer-restfulobjects-rendering:jar:1.14.0:compile
[INFO] | | | +-
org.jboss.resteasy:resteasy-jaxb-provider:jar:3.0.14.Final:compile
[INFO] | | | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.7:compile
[INFO] | | | | | +- com.sun.xml.bind:jaxb-core:jar:2.2.7:compile
[INFO] | | | | | | +- javax.xml.bind:jaxb-api:jar:2.2.7:compile
[INFO] | | | | | | \-
com.sun.istack:istack-commons-runtime:jar:2.16:compile
[INFO] | | | | | \- com.sun.xml.fastinfoset:FastInfoset:jar:1.2.12:compile
[INFO] | | | | | \- javax.xml.bind:jsr173_api:jar:1.0:compile
[INFO] | | | | \- org.jboss.logging:jboss-logging:jar:3.1.4.GA:compile
[INFO] | | | +-
org.jboss.resteasy:resteasy-jackson-provider:jar:3.0.14.Final:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-core-asl:jar:1.9.12:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.12:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-jaxrs:jar:1.9.12:compile
[INFO] | | | | \- org.codehaus.jackson:jackson-xc:jar:1.9.12:compile
{code}
Please upgrade to 3.1.3Final if feasible:
{code}
org.jboss.resteasy
resteasy-jackson-provider
3.1.3.Final
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ISIS-1635) Upgrade dependency to resteasy
[
https://issues.apache.org/jira/browse/ISIS-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Rade updated ISIS-1635:
Description:
org.codehaus.jackson brings in some vulnerabilities:
!Dependency-Check.png|thumbnail!
{code}
[INFO] | +-
org.apache.isis.core:isis-core-viewer-restfulobjects-server:jar:1.14.0:compile
[INFO] | | +-
org.apache.isis.core:isis-core-viewer-restfulobjects-rendering:jar:1.14.0:compile
[INFO] | | | +-
org.jboss.resteasy:resteasy-jaxb-provider:jar:3.0.14.Final:compile
[INFO] | | | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.7:compile
[INFO] | | | | | +- com.sun.xml.bind:jaxb-core:jar:2.2.7:compile
[INFO] | | | | | | +- javax.xml.bind:jaxb-api:jar:2.2.7:compile
[INFO] | | | | | | \-
com.sun.istack:istack-commons-runtime:jar:2.16:compile
[INFO] | | | | | \- com.sun.xml.fastinfoset:FastInfoset:jar:1.2.12:compile
[INFO] | | | | | \- javax.xml.bind:jsr173_api:jar:1.0:compile
[INFO] | | | | \- org.jboss.logging:jboss-logging:jar:3.1.4.GA:compile
[INFO] | | | +-
org.jboss.resteasy:resteasy-jackson-provider:jar:3.0.14.Final:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-core-asl:jar:1.9.12:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.12:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-jaxrs:jar:1.9.12:compile
[INFO] | | | | \- org.codehaus.jackson:jackson-xc:jar:1.9.12:compile
{code}
Please upgrade to 3.1.3Final if feasible:
{code}
org.jboss.resteasy
resteasy-jaxb-provider
3.1.3.Final
org.jboss.resteasy
resteasy-jackson-provider
3.1.3.Final
{code}
was:
org.codehaus.jackson brings in some vulnerabilities:
!Dependency-Check.png|thumbnail!
{code}
[INFO] | +-
org.apache.isis.core:isis-core-viewer-restfulobjects-server:jar:1.14.0:compile
[INFO] | | +-
org.apache.isis.core:isis-core-viewer-restfulobjects-rendering:jar:1.14.0:compile
[INFO] | | | +-
org.jboss.resteasy:resteasy-jaxb-provider:jar:3.0.14.Final:compile
[INFO] | | | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.7:compile
[INFO] | | | | | +- com.sun.xml.bind:jaxb-core:jar:2.2.7:compile
[INFO] | | | | | | +- javax.xml.bind:jaxb-api:jar:2.2.7:compile
[INFO] | | | | | | \-
com.sun.istack:istack-commons-runtime:jar:2.16:compile
[INFO] | | | | | \- com.sun.xml.fastinfoset:FastInfoset:jar:1.2.12:compile
[INFO] | | | | | \- javax.xml.bind:jsr173_api:jar:1.0:compile
[INFO] | | | | \- org.jboss.logging:jboss-logging:jar:3.1.4.GA:compile
[INFO] | | | +-
org.jboss.resteasy:resteasy-jackson-provider:jar:3.0.14.Final:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-core-asl:jar:1.9.12:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.12:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-jaxrs:jar:1.9.12:compile
[INFO] | | | | \- org.codehaus.jackson:jackson-xc:jar:1.9.12:compile
{code}
Please upgrade to 3.1.3Final if feasible:
{code}
org.jboss.resteasy
resteasy-jaxb-provider
3.1.3.Final
{code}
> Upgrade dependency to resteasy
> --
>
> Key: ISIS-1635
> URL: https://issues.apache.org/jira/browse/ISIS-1635
> Project: Isis
> Issue Type: Improvement
> Components: Core: Viewer: RestfulObjects
>Affects Versions: 1.14.0
>Reporter: Jörg Rade
> Attachments: Dependency-Check.png
>
>
> org.codehaus.jackson brings in some vulnerabilities:
> !Dependency-Check.png|thumbnail!
> {code}
> [INFO] | +-
> org.apache.isis.core:isis-core-viewer-restfulobjects-server:jar:1.14.0:compile
> [INFO] | | +-
> org.apache.isis.core:isis-core-viewer-restfulobjects-rendering:jar:1.14.0:compile
> [INFO] | | | +-
> org.jboss.resteasy:resteasy-jaxb-provider:jar:3.0.14.Final:compile
> [INFO] | | | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.7:compile
> [INFO] | | | | | +- com.sun.xml.bind:jaxb-core:jar:2.2.7:compile
> [INFO] | | | | | | +- javax.xml.bind:jaxb-api:jar:2.2.7:compile
> [INFO] | | | | | | \-
> com.sun.istack:istack-commons-runtime:jar:2.16:compile
> [INFO] | | | | | \-
> com.sun.xml.fastinfoset:FastInfoset:jar:1.2.12:compile
> [INFO] | | | | | \- javax.xml.bind:jsr173_api:jar:1.0:compile
> [INFO] | | | | \- org.jboss.logging:jboss-logging:jar:3.1.4.GA:compile
> [INFO] | | | +-
> org.jboss.resteasy:resteasy-jackson-provider:jar:3.0.14.Final:compile
> [INFO] | | | | +- org.codehaus.jackson:jackson-core-asl:jar:1.9.12:compile
> [INFO] | | | | +-
> org.codehaus.jackson:jackson-mapper-asl:jar:1.9.12:compile
> [INFO] | | | | +- org.codehaus.jackson:jackson-jaxrs:jar:1.9.12:compile
> [INFO] | | | | \- org.codehaus.jackson:jackson-xc:jar:1.9.12:compile
> {code}
> Pleas
[jira] [Updated] (ISIS-1635) Upgrade dependency to resteasy
[
https://issues.apache.org/jira/browse/ISIS-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Rade updated ISIS-1635:
Affects Version/s: 1.14.0
> Upgrade dependency to resteasy
> --
>
> Key: ISIS-1635
> URL: https://issues.apache.org/jira/browse/ISIS-1635
> Project: Isis
> Issue Type: Improvement
> Components: Core: Viewer: RestfulObjects
>Affects Versions: 1.14.0
>Reporter: Jörg Rade
> Attachments: Dependency-Check.png
>
>
> org.codehaus.jackson brings in some vulnerabilities:
> !Dependency-Check.png|thumbnail!
> {code}
> [INFO] | +-
> org.apache.isis.core:isis-core-viewer-restfulobjects-server:jar:1.14.0:compile
> [INFO] | | +-
> org.apache.isis.core:isis-core-viewer-restfulobjects-rendering:jar:1.14.0:compile
> [INFO] | | | +-
> org.jboss.resteasy:resteasy-jaxb-provider:jar:3.0.14.Final:compile
> [INFO] | | | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.7:compile
> [INFO] | | | | | +- com.sun.xml.bind:jaxb-core:jar:2.2.7:compile
> [INFO] | | | | | | +- javax.xml.bind:jaxb-api:jar:2.2.7:compile
> [INFO] | | | | | | \-
> com.sun.istack:istack-commons-runtime:jar:2.16:compile
> [INFO] | | | | | \-
> com.sun.xml.fastinfoset:FastInfoset:jar:1.2.12:compile
> [INFO] | | | | | \- javax.xml.bind:jsr173_api:jar:1.0:compile
> [INFO] | | | | \- org.jboss.logging:jboss-logging:jar:3.1.4.GA:compile
> [INFO] | | | +-
> org.jboss.resteasy:resteasy-jackson-provider:jar:3.0.14.Final:compile
> [INFO] | | | | +- org.codehaus.jackson:jackson-core-asl:jar:1.9.12:compile
> [INFO] | | | | +-
> org.codehaus.jackson:jackson-mapper-asl:jar:1.9.12:compile
> [INFO] | | | | +- org.codehaus.jackson:jackson-jaxrs:jar:1.9.12:compile
> [INFO] | | | | \- org.codehaus.jackson:jackson-xc:jar:1.9.12:compile
> {code}
> Please upgrade to 3.1.3Final if feasible:
> {code}
>
> org.jboss.resteasy
> resteasy-jackson-provider
> 3.1.3.Final
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ISIS-1635) Upgrade dependency to resteasy
[
https://issues.apache.org/jira/browse/ISIS-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Rade updated ISIS-1635:
Description:
org.codehaus.jackson brings in some vulnerabilities:
!Dependency-Check.png|thumbnail!
{code}
[INFO] | +-
org.apache.isis.core:isis-core-viewer-restfulobjects-server:jar:1.14.0:compile
[INFO] | | +-
org.apache.isis.core:isis-core-viewer-restfulobjects-rendering:jar:1.14.0:compile
[INFO] | | | +-
org.jboss.resteasy:resteasy-jaxb-provider:jar:3.0.14.Final:compile
[INFO] | | | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.7:compile
[INFO] | | | | | +- com.sun.xml.bind:jaxb-core:jar:2.2.7:compile
[INFO] | | | | | | +- javax.xml.bind:jaxb-api:jar:2.2.7:compile
[INFO] | | | | | | \-
com.sun.istack:istack-commons-runtime:jar:2.16:compile
[INFO] | | | | | \- com.sun.xml.fastinfoset:FastInfoset:jar:1.2.12:compile
[INFO] | | | | | \- javax.xml.bind:jsr173_api:jar:1.0:compile
[INFO] | | | | \- org.jboss.logging:jboss-logging:jar:3.1.4.GA:compile
[INFO] | | | +-
org.jboss.resteasy:resteasy-jackson-provider:jar:3.0.14.Final:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-core-asl:jar:1.9.12:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.12:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-jaxrs:jar:1.9.12:compile
[INFO] | | | | \- org.codehaus.jackson:jackson-xc:jar:1.9.12:compile
{code}
Please upgrade to 3.1.3Final if feasible:
{code}
org.jboss.resteasy
resteasy-jaxb-provider
3.1.3.Final
{code}
was:
org.codehaus.jackson brings in some vulnerabilities:
!Dependency-Check.png|thumbnail!
{code}
[INFO] | +-
org.apache.isis.core:isis-core-viewer-restfulobjects-server:jar:1.14.0:compile
[INFO] | | +-
org.apache.isis.core:isis-core-viewer-restfulobjects-rendering:jar:1.14.0:compile
[INFO] | | | +-
org.jboss.resteasy:resteasy-jaxb-provider:jar:3.0.14.Final:compile
[INFO] | | | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.7:compile
[INFO] | | | | | +- com.sun.xml.bind:jaxb-core:jar:2.2.7:compile
[INFO] | | | | | | +- javax.xml.bind:jaxb-api:jar:2.2.7:compile
[INFO] | | | | | | \-
com.sun.istack:istack-commons-runtime:jar:2.16:compile
[INFO] | | | | | \- com.sun.xml.fastinfoset:FastInfoset:jar:1.2.12:compile
[INFO] | | | | | \- javax.xml.bind:jsr173_api:jar:1.0:compile
[INFO] | | | | \- org.jboss.logging:jboss-logging:jar:3.1.4.GA:compile
[INFO] | | | +-
org.jboss.resteasy:resteasy-jackson-provider:jar:3.0.14.Final:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-core-asl:jar:1.9.12:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.12:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-jaxrs:jar:1.9.12:compile
[INFO] | | | | \- org.codehaus.jackson:jackson-xc:jar:1.9.12:compile
{code}
Please upgrade to 3.1.3Final if feasible:
{code}
org.jboss.resteasy
resteasy-jackson-provider
3.1.3.Final
{code}
> Upgrade dependency to resteasy
> --
>
> Key: ISIS-1635
> URL: https://issues.apache.org/jira/browse/ISIS-1635
> Project: Isis
> Issue Type: Improvement
> Components: Core: Viewer: RestfulObjects
>Affects Versions: 1.14.0
>Reporter: Jörg Rade
> Attachments: Dependency-Check.png
>
>
> org.codehaus.jackson brings in some vulnerabilities:
> !Dependency-Check.png|thumbnail!
> {code}
> [INFO] | +-
> org.apache.isis.core:isis-core-viewer-restfulobjects-server:jar:1.14.0:compile
> [INFO] | | +-
> org.apache.isis.core:isis-core-viewer-restfulobjects-rendering:jar:1.14.0:compile
> [INFO] | | | +-
> org.jboss.resteasy:resteasy-jaxb-provider:jar:3.0.14.Final:compile
> [INFO] | | | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.7:compile
> [INFO] | | | | | +- com.sun.xml.bind:jaxb-core:jar:2.2.7:compile
> [INFO] | | | | | | +- javax.xml.bind:jaxb-api:jar:2.2.7:compile
> [INFO] | | | | | | \-
> com.sun.istack:istack-commons-runtime:jar:2.16:compile
> [INFO] | | | | | \-
> com.sun.xml.fastinfoset:FastInfoset:jar:1.2.12:compile
> [INFO] | | | | | \- javax.xml.bind:jsr173_api:jar:1.0:compile
> [INFO] | | | | \- org.jboss.logging:jboss-logging:jar:3.1.4.GA:compile
> [INFO] | | | +-
> org.jboss.resteasy:resteasy-jackson-provider:jar:3.0.14.Final:compile
> [INFO] | | | | +- org.codehaus.jackson:jackson-core-asl:jar:1.9.12:compile
> [INFO] | | | | +-
> org.codehaus.jackson:jackson-mapper-asl:jar:1.9.12:compile
> [INFO] | | | | +- org.codehaus.jackson:jackson-jaxrs:jar:1.9.12:compile
> [INFO] | | | | \- org.codehaus.jackson:jackson-xc:jar:1.9.12:compile
> {code}
> Please upgrade to 3.1.3Final if feasible:
> {code}
>
> org
[jira] [Updated] (ISIS-1635) Upgrade dependency to resteasy
[
https://issues.apache.org/jira/browse/ISIS-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Rade updated ISIS-1635:
Description:
org.codehaus.jackson brings in some vulnerabilities:
!Dependency-Check.png|thumbnail!
{code}
[INFO] | +-
org.apache.isis.core:isis-core-viewer-restfulobjects-server:jar:1.14.0:compile
[INFO] | | +-
org.apache.isis.core:isis-core-viewer-restfulobjects-rendering:jar:1.14.0:compile
[INFO] | | | +-
org.jboss.resteasy:resteasy-jaxb-provider:jar:3.0.14.Final:compile
[INFO] | | | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.7:compile
[INFO] | | | | | +- com.sun.xml.bind:jaxb-core:jar:2.2.7:compile
[INFO] | | | | | | +- javax.xml.bind:jaxb-api:jar:2.2.7:compile
[INFO] | | | | | | \-
com.sun.istack:istack-commons-runtime:jar:2.16:compile
[INFO] | | | | | \- com.sun.xml.fastinfoset:FastInfoset:jar:1.2.12:compile
[INFO] | | | | | \- javax.xml.bind:jsr173_api:jar:1.0:compile
[INFO] | | | | \- org.jboss.logging:jboss-logging:jar:3.1.4.GA:compile
[INFO] | | | +-
org.jboss.resteasy:resteasy-jackson-provider:jar:3.0.14.Final:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-core-asl:jar:1.9.12:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.12:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-jaxrs:jar:1.9.12:compile
[INFO] | | | | \- org.codehaus.jackson:jackson-xc:jar:1.9.12:compile
{code}
Please upgrade to 3.1.3Final if feasible:
{code}
org.jboss.resteasy
resteasy-jackson-provider
3.1.3.Final
{code}
was:
org.codehaus.jackson brings in some vulnerabilities:
!ScreenShot 757 Dependency-Check Report - Mozilla Firefox.pngl!
{code}
[INFO] | +-
org.apache.isis.core:isis-core-viewer-restfulobjects-server:jar:1.14.0:compile
[INFO] | | +-
org.apache.isis.core:isis-core-viewer-restfulobjects-rendering:jar:1.14.0:compile
[INFO] | | | +-
org.jboss.resteasy:resteasy-jaxb-provider:jar:3.0.14.Final:compile
[INFO] | | | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.7:compile
[INFO] | | | | | +- com.sun.xml.bind:jaxb-core:jar:2.2.7:compile
[INFO] | | | | | | +- javax.xml.bind:jaxb-api:jar:2.2.7:compile
[INFO] | | | | | | \-
com.sun.istack:istack-commons-runtime:jar:2.16:compile
[INFO] | | | | | \- com.sun.xml.fastinfoset:FastInfoset:jar:1.2.12:compile
[INFO] | | | | | \- javax.xml.bind:jsr173_api:jar:1.0:compile
[INFO] | | | | \- org.jboss.logging:jboss-logging:jar:3.1.4.GA:compile
[INFO] | | | +-
org.jboss.resteasy:resteasy-jackson-provider:jar:3.0.14.Final:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-core-asl:jar:1.9.12:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.12:compile
[INFO] | | | | +- org.codehaus.jackson:jackson-jaxrs:jar:1.9.12:compile
[INFO] | | | | \- org.codehaus.jackson:jackson-xc:jar:1.9.12:compile
{code}
Please upgrade to 3.1.3Final if feasible:
{code}
org.jboss.resteasy
resteasy-jackson-provider
3.1.3.Final
{code}
> Upgrade dependency to resteasy
> --
>
> Key: ISIS-1635
> URL: https://issues.apache.org/jira/browse/ISIS-1635
> Project: Isis
> Issue Type: Improvement
> Components: Core: Viewer: RestfulObjects
>Reporter: Jörg Rade
> Attachments: Dependency-Check.png
>
>
> org.codehaus.jackson brings in some vulnerabilities:
> !Dependency-Check.png|thumbnail!
> {code}
> [INFO] | +-
> org.apache.isis.core:isis-core-viewer-restfulobjects-server:jar:1.14.0:compile
> [INFO] | | +-
> org.apache.isis.core:isis-core-viewer-restfulobjects-rendering:jar:1.14.0:compile
> [INFO] | | | +-
> org.jboss.resteasy:resteasy-jaxb-provider:jar:3.0.14.Final:compile
> [INFO] | | | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.7:compile
> [INFO] | | | | | +- com.sun.xml.bind:jaxb-core:jar:2.2.7:compile
> [INFO] | | | | | | +- javax.xml.bind:jaxb-api:jar:2.2.7:compile
> [INFO] | | | | | | \-
> com.sun.istack:istack-commons-runtime:jar:2.16:compile
> [INFO] | | | | | \-
> com.sun.xml.fastinfoset:FastInfoset:jar:1.2.12:compile
> [INFO] | | | | | \- javax.xml.bind:jsr173_api:jar:1.0:compile
> [INFO] | | | | \- org.jboss.logging:jboss-logging:jar:3.1.4.GA:compile
> [INFO] | | | +-
> org.jboss.resteasy:resteasy-jackson-provider:jar:3.0.14.Final:compile
> [INFO] | | | | +- org.codehaus.jackson:jackson-core-asl:jar:1.9.12:compile
> [INFO] | | | | +-
> org.codehaus.jackson:jackson-mapper-asl:jar:1.9.12:compile
> [INFO] | | | | +- org.codehaus.jackson:jackson-jaxrs:jar:1.9.12:compile
> [INFO] | | | | \- org.codehaus.jackson:jackson-xc:jar:1.9.12:compile
> {code}
> Please upgrade to 3.1.3Final if feasible:
> {code}
>
>
[jira] [Commented] (ISIS-1303) Rename the project to better describe its values and purpose
[ https://issues.apache.org/jira/browse/ISIS-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057069#comment-16057069 ] Jörg Rade commented on ISIS-1303: - +1 Apache Alma > Rename the project to better describe its values and purpose > > > Key: ISIS-1303 > URL: https://issues.apache.org/jira/browse/ISIS-1303 > Project: Isis > Issue Type: Wish >Affects Versions: 1.11.1 >Reporter: Dan Haywood > Fix For: 1.20.0 > > Attachments: ApacheFarthing.jpg, ApacheFarthing.jpg, > ApacheGestalt.jpg, Offset-curves-of-sinus-curve.svg > > > In the past there have been a couple of discussions regarding renaming the > project, the reason generally cited being the potential embarrassment of > sharing a name with the jihadist militant group [1] currently prominent in > the headlines. After due discussion on the mailing lists the prevailing view > has been to retain our name: "we were here first". > Until now I've concurred with that view also... after all, I originally came > up with the name "Isis", originally based on the name of the Thames as it > flows through Oxford [2] (many of the original authors of the framework live > within Oxfordshire, UK). > Separately to that discussion, we have the issue of marketing. Originally we > marketed ourselves as a framework implementing the "naked objects" pattern > [3]; the original name of the framework (prior to Apache) was of course the > Naked Objects Framework. However, this pattern is either not well-known or > is misunderstood (only a low proportion of developers that encounter the idea > immediately "get it"). The crudity of the original user interfaces didn't > help. And the name also, of course, can cause embarrassment in some cultures. > Then, when domain-driven design [4] came along as a movement, that seemed an > obvious platform upon which to position the framework: we obviously share the > core belief that the domain is the most important bit of the system. However > - and I still find this surprising - despite attempts otherwise we haven't > really made too much of an impression in that community. The fact that the > DDD community got massively sidetracked for a while by the CQRS pattern is > perhaps part of it. I also often detect the view that DDD should imply not > using a framework. The irony of course is that in rejecting framework such > developers actually have to write more infrastructure code vs business domain > code. > Also, the fit is perhaps not all that good after all. In the DDD community I > don't see anyone talking about modules... one of the named patterns, and a > major focus of our framework, but missing from DDD talks. Instead they get > side-tracked talking only about aggregate roots or bounded contexts; all well > and good, but over-emphasised). > [Aside: Indeed, I raised the topic of modules with Eric Evans himself (in > person), and he agreed there was little emphasis. When I described our > framework's use of domain events to hook modules together (along with vetoing > behaviour we support) he admitted it was a new approach/pattern to him...] > Anyway, so DDD - which looked so promising - hasn't delivered. They might > come around to us one day, but it's probably time to define our own > individual space. Also, in the same way that everyone takes agile > development for granted as the "de facto", we ought to simply take DDD for > granted too... "of course you will be doing DDD, but are you doing it well?" > What we need to better market the framework is some other pattern or concept > or hook, and become known as the framework that best supports that idea. > There are several candidates: > - hexagonal architecture (also called ports and adapters, or the onion > architecture, and related to the clean architecture) > - don't repeat yourself principle > - aspect oriented programming (naked objects pattern is really the > recognition that UI presentation is a cross-cutting concern) > - the general concept of modularity > - DCI (data/context/interactions). > - "clean" "pure" "essential" pojo programming model > - agile, lean > - breaking down barriers between IT and business > Of these, I think that hexagonal architecture looks the best fit; it is well > regarded as a concept among the "cognoscenti", but there are surprisingly no > open source frameworks out there (at least in the Java space) that position > themselves as being the natural choice. > Therefore
[jira] [Comment Edited] (ISIS-1572) RestfulObjects viewer - Service members empty
[
https://issues.apache.org/jira/browse/ISIS-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16034733#comment-16034733
]
Jörg Rade edited comment on ISIS-1572 at 6/2/17 2:02 PM:
-
If I recall correctly, I could reproduce it with
https://github.com/joerg-rade/isis-app-todoapp
Cheers -j
PS: I'll add a README
was (Author: joerg.rade):
If I recall correctly, I could reproduce it with
https://github.com/joerg-rade/isis-app-todoapp
Cheers -j
> RestfulObjects viewer - Service members empty
> -
>
> Key: ISIS-1572
> URL: https://issues.apache.org/jira/browse/ISIS-1572
> Project: Isis
> Issue Type: Bug
> Components: Core: Viewer: RestfulObjects
>Affects Versions: 1.13.0
> Environment: Web.xml is patched according to
> https://github.com/danhaywood/isis-angularjs-simpleapp in order to cope with
> CORS issues.
>Reporter: Jörg Rade
> Fix For: 1.15.0
>
>
> _Sometimes_ the members section of the response to
> http://localhost:9090/restful/services/Applications/ is empty - sometimes it
> is not:
> {code|language=javascript}
> {
> "links" : [ {
> "rel" : "self",
> "href" : "http://localhost:9090/restful/services/Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/object\"",
> "title" : "Applications"
> }, {
> "rel" : "describedby",
> "href" :
> "http://localhost:9090/restful/domain-types/ife.dep.Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/domain-type\""
> }, {
> "rel" : "up",
> "href" : "http://localhost:9090/restful/services;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/list\""
> } ],
> "extensions" : {
> "oid" : "ife.dep.Applications:1",
> "isService" : true,
> "isPersistent" : true
> },
> "title" : "Applications",
> "serviceId" : "Applications",
> "members" : { }
> }
> {code}
> After some time the app was accessed via the wicket viewer. It first
> delivered the homepage and then I invoked the listAll operation via the
> respective menu item.
> Invoking http://localhost:9090/restful/services/Applications/ afterwards
> showed the expected response including the members.
> In another case there was a difference between:
> * http://localhost:9090/restful/services/Applications/ (with members) and
> * http://localhost:9090/restful/services/Applications (without members)
> In yet another case both URL's delivered a result without 'members' filled,
> even after the 'workaround' described above.
> https://github.com/joerg-rade/isis-app-todoapp shows the same behavior:
> * http://localhost:/restful/services/todo.ToDoItems/ whereas
> * http://localhost:/restful/domain-types/todoapp.dom.todoitem.ToDoItems
> shows the members
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (ISIS-1572) RestfulObjects viewer - Service members empty
[
https://issues.apache.org/jira/browse/ISIS-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16034733#comment-16034733
]
Jörg Rade commented on ISIS-1572:
-
If I recall correctly, I could reproduce it with
https://github.com/joerg-rade/isis-app-todoapp
Cheers -j
> RestfulObjects viewer - Service members empty
> -
>
> Key: ISIS-1572
> URL: https://issues.apache.org/jira/browse/ISIS-1572
> Project: Isis
> Issue Type: Bug
> Components: Core: Viewer: RestfulObjects
>Affects Versions: 1.13.0
> Environment: Web.xml is patched according to
> https://github.com/danhaywood/isis-angularjs-simpleapp in order to cope with
> CORS issues.
>Reporter: Jörg Rade
> Fix For: 1.15.0
>
>
> _Sometimes_ the members section of the response to
> http://localhost:9090/restful/services/Applications/ is empty - sometimes it
> is not:
> {code|language=javascript}
> {
> "links" : [ {
> "rel" : "self",
> "href" : "http://localhost:9090/restful/services/Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/object\"",
> "title" : "Applications"
> }, {
> "rel" : "describedby",
> "href" :
> "http://localhost:9090/restful/domain-types/ife.dep.Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/domain-type\""
> }, {
> "rel" : "up",
> "href" : "http://localhost:9090/restful/services;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/list\""
> } ],
> "extensions" : {
> "oid" : "ife.dep.Applications:1",
> "isService" : true,
> "isPersistent" : true
> },
> "title" : "Applications",
> "serviceId" : "Applications",
> "members" : { }
> }
> {code}
> After some time the app was accessed via the wicket viewer. It first
> delivered the homepage and then I invoked the listAll operation via the
> respective menu item.
> Invoking http://localhost:9090/restful/services/Applications/ afterwards
> showed the expected response including the members.
> In another case there was a difference between:
> * http://localhost:9090/restful/services/Applications/ (with members) and
> * http://localhost:9090/restful/services/Applications (without members)
> In yet another case both URL's delivered a result without 'members' filled,
> even after the 'workaround' described above.
> https://github.com/joerg-rade/isis-app-todoapp shows the same behavior:
> * http://localhost:/restful/services/todo.ToDoItems/ whereas
> * http://localhost:/restful/domain-types/todoapp.dom.todoitem.ToDoItems
> shows the members
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (ISIS-1572) RestfulObjects viewer - Service members empty
[
https://issues.apache.org/jira/browse/ISIS-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16040706#comment-16040706
]
Jörg Rade edited comment on ISIS-1572 at 6/7/17 3:56 PM:
-
Update of the example app and README will take some more time.
I tried setting
{code} isis.viewer.restfulobjects.objectPropertyValuesOnly=false {code}
and it appears to have the following effect:
On the first invocation members are empty and CrossOriginFilter is not passed -
at least according to log output.
The next invocation includes the members as expected and the CrossOrigin filter
is passed with output, e.g.
{code}
12:52:53,239 [CrossOriginFilterqtp974747823-32 DEBUG] Cross-origin
request to /restful/services/isisApplib.ConfigurationServiceMenu is a simple
cross-origin request
12:52:53,244 [i18n qtp974747823-32 DEBUG] RESTEASY002315:
PathInfo: /services/isisApplib.ConfigurationServiceMenu
{code}
(!) not reproducible
was (Author: joerg.rade):
Update of the example app and README will take some more time.
I tried setting
{code} isis.viewer.restfulobjects.objectPropertyValuesOnly=false {code}
and it appears to have the following effect:
On the first invocation members are empty and CrossOriginFilter is not passed -
at least according to log output.
The next invocation includes the members as expected and the CrossOrigin filter
is passed with output, e.g.
{code}
12:52:53,239 [CrossOriginFilterqtp974747823-32 DEBUG] Cross-origin
request to /restful/services/isisApplib.ConfigurationServiceMenu is a simple
cross-origin request
12:52:53,244 [i18n qtp974747823-32 DEBUG] RESTEASY002315:
PathInfo: /services/isisApplib.ConfigurationServiceMenu
{code}
> RestfulObjects viewer - Service members empty
> -
>
> Key: ISIS-1572
> URL: https://issues.apache.org/jira/browse/ISIS-1572
> Project: Isis
> Issue Type: Bug
> Components: Core: Viewer: RestfulObjects
>Affects Versions: 1.13.0
> Environment: Web.xml is patched according to
> https://github.com/danhaywood/isis-angularjs-simpleapp in order to cope with
> CORS issues.
>Reporter: Jörg Rade
> Fix For: 1.15.0
>
>
> _Sometimes_ the members section of the response to
> http://localhost:9090/restful/services/Applications/ is empty - sometimes it
> is not:
> {code|language=javascript}
> {
> "links" : [ {
> "rel" : "self",
> "href" : "http://localhost:9090/restful/services/Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/object\"",
> "title" : "Applications"
> }, {
> "rel" : "describedby",
> "href" :
> "http://localhost:9090/restful/domain-types/ife.dep.Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/domain-type\""
> }, {
> "rel" : "up",
> "href" : "http://localhost:9090/restful/services;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/list\""
> } ],
> "extensions" : {
> "oid" : "ife.dep.Applications:1",
> "isService" : true,
> "isPersistent" : true
> },
> "title" : "Applications",
> "serviceId" : "Applications",
> "members" : { }
> }
> {code}
> After some time the app was accessed via the wicket viewer. It first
> delivered the homepage and then I invoked the listAll operation via the
> respective menu item.
> Invoking http://localhost:9090/restful/services/Applications/ afterwards
> showed the expected response including the members.
> In another case there was a difference between:
> * http://localhost:9090/restful/services/Applications/ (with members) and
> * http://localhost:9090/restful/services/Applications (without members)
> In yet another case both URL's delivered a result without 'members' filled,
> even after the 'workaround' described above.
> https://github.com/joerg-rade/isis-app-todoapp shows the same behavior:
> * http://localhost:/restful/services/todo.ToDoItems/ whereas
> * http://localhost:/restful/domain-types/todoapp.dom.todoitem.ToDoItems
> shows the members
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (ISIS-1572) RestfulObjects viewer - Service members empty
[
https://issues.apache.org/jira/browse/ISIS-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16040706#comment-16040706
]
Jörg Rade edited comment on ISIS-1572 at 6/7/17 11:01 AM:
--
Update of the example app and README will take some more time.
I tried setting
{code} isis.viewer.restfulobjects.objectPropertyValuesOnly=false {code}
and it appears to have the following effect:
On the first invocation members are empty and CrossOriginFilter is not passed -
at least according to log output.
The next invocation includes the members as expected and the CrossOrigin filter
is passed with output, e.g.
{code}
12:52:53,239 [CrossOriginFilterqtp974747823-32 DEBUG] Cross-origin
request to /restful/services/isisApplib.ConfigurationServiceMenu is a simple
cross-origin request
12:52:53,244 [i18n qtp974747823-32 DEBUG] RESTEASY002315:
PathInfo: /services/isisApplib.ConfigurationServiceMenu
{code}
was (Author: joerg.rade):
Update of the example app and README will take some more time.
I tried setting
{code} isis.viewer.restfulobjects.objectPropertyValuesOnly=false {code}
and it appears to have the following effect:
On the first invocation members are empty and CrossOriginFilter is not passed -
at least according to log output.
The next incocation includes the members as expected and the CrossOrigin filter
is passed with output, e.g.
{code}
12:52:53,239 [CrossOriginFilterqtp974747823-32 DEBUG] Cross-origin
request to /restful/services/isisApplib.ConfigurationServiceMenu is a simple
cross-origin request
12:52:53,244 [i18n qtp974747823-32 DEBUG] RESTEASY002315:
PathInfo: /services/isisApplib.ConfigurationServiceMenu
{code}
> RestfulObjects viewer - Service members empty
> -
>
> Key: ISIS-1572
> URL: https://issues.apache.org/jira/browse/ISIS-1572
> Project: Isis
> Issue Type: Bug
> Components: Core: Viewer: RestfulObjects
>Affects Versions: 1.13.0
> Environment: Web.xml is patched according to
> https://github.com/danhaywood/isis-angularjs-simpleapp in order to cope with
> CORS issues.
>Reporter: Jörg Rade
> Fix For: 1.15.0
>
>
> _Sometimes_ the members section of the response to
> http://localhost:9090/restful/services/Applications/ is empty - sometimes it
> is not:
> {code|language=javascript}
> {
> "links" : [ {
> "rel" : "self",
> "href" : "http://localhost:9090/restful/services/Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/object\"",
> "title" : "Applications"
> }, {
> "rel" : "describedby",
> "href" :
> "http://localhost:9090/restful/domain-types/ife.dep.Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/domain-type\""
> }, {
> "rel" : "up",
> "href" : "http://localhost:9090/restful/services;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/list\""
> } ],
> "extensions" : {
> "oid" : "ife.dep.Applications:1",
> "isService" : true,
> "isPersistent" : true
> },
> "title" : "Applications",
> "serviceId" : "Applications",
> "members" : { }
> }
> {code}
> After some time the app was accessed via the wicket viewer. It first
> delivered the homepage and then I invoked the listAll operation via the
> respective menu item.
> Invoking http://localhost:9090/restful/services/Applications/ afterwards
> showed the expected response including the members.
> In another case there was a difference between:
> * http://localhost:9090/restful/services/Applications/ (with members) and
> * http://localhost:9090/restful/services/Applications (without members)
> In yet another case both URL's delivered a result without 'members' filled,
> even after the 'workaround' described above.
> https://github.com/joerg-rade/isis-app-todoapp shows the same behavior:
> * http://localhost:/restful/services/todo.ToDoItems/ whereas
> * http://localhost:/restful/domain-types/todoapp.dom.todoitem.ToDoItems
> shows the members
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (ISIS-1572) RestfulObjects viewer - Service members empty
[
https://issues.apache.org/jira/browse/ISIS-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16040706#comment-16040706
]
Jörg Rade commented on ISIS-1572:
-
Update of the example app and README will take some more time.
I tried setting
{code} isis.viewer.restfulobjects.objectPropertyValuesOnly=false {code}
and it appears to have the following effect:
On the first invocation members are empty and CrossOriginFilter is not passed -
at least according to log output.
The next incocation includes the members as expected and the CrossOrigin filter
is passed with output, e.g.
{code}
12:52:53,239 [CrossOriginFilterqtp974747823-32 DEBUG] Cross-origin
request to /restful/services/isisApplib.ConfigurationServiceMenu is a simple
cross-origin request
12:52:53,244 [i18n qtp974747823-32 DEBUG] RESTEASY002315:
PathInfo: /services/isisApplib.ConfigurationServiceMenu
{code}
> RestfulObjects viewer - Service members empty
> -
>
> Key: ISIS-1572
> URL: https://issues.apache.org/jira/browse/ISIS-1572
> Project: Isis
> Issue Type: Bug
> Components: Core: Viewer: RestfulObjects
>Affects Versions: 1.13.0
> Environment: Web.xml is patched according to
> https://github.com/danhaywood/isis-angularjs-simpleapp in order to cope with
> CORS issues.
>Reporter: Jörg Rade
> Fix For: 1.15.0
>
>
> _Sometimes_ the members section of the response to
> http://localhost:9090/restful/services/Applications/ is empty - sometimes it
> is not:
> {code|language=javascript}
> {
> "links" : [ {
> "rel" : "self",
> "href" : "http://localhost:9090/restful/services/Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/object\"",
> "title" : "Applications"
> }, {
> "rel" : "describedby",
> "href" :
> "http://localhost:9090/restful/domain-types/ife.dep.Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/domain-type\""
> }, {
> "rel" : "up",
> "href" : "http://localhost:9090/restful/services;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/list\""
> } ],
> "extensions" : {
> "oid" : "ife.dep.Applications:1",
> "isService" : true,
> "isPersistent" : true
> },
> "title" : "Applications",
> "serviceId" : "Applications",
> "members" : { }
> }
> {code}
> After some time the app was accessed via the wicket viewer. It first
> delivered the homepage and then I invoked the listAll operation via the
> respective menu item.
> Invoking http://localhost:9090/restful/services/Applications/ afterwards
> showed the expected response including the members.
> In another case there was a difference between:
> * http://localhost:9090/restful/services/Applications/ (with members) and
> * http://localhost:9090/restful/services/Applications (without members)
> In yet another case both URL's delivered a result without 'members' filled,
> even after the 'workaround' described above.
> https://github.com/joerg-rade/isis-app-todoapp shows the same behavior:
> * http://localhost:/restful/services/todo.ToDoItems/ whereas
> * http://localhost:/restful/domain-types/todoapp.dom.todoitem.ToDoItems
> shows the members
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (ISIS-1604) Extend support for SVG (3 additional dependencies, it seems)
[
https://issues.apache.org/jira/browse/ISIS-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16046375#comment-16046375
]
Jörg Rade commented on ISIS-1604:
-
The Batik versions used have high CVE values - they should rather not be
included.
Since in some places the browsers native support for SVG's seems to be used -
maybe this can be here as well?
> Extend support for SVG (3 additional dependencies, it seems)
>
>
> Key: ISIS-1604
> URL: https://issues.apache.org/jira/browse/ISIS-1604
> Project: Isis
> Issue Type: Wish
> Components: Core: Viewer: Wicket
>Affects Versions: 1.14.0
>Reporter: Jörg Rade
>Priority: Minor
> Fix For: 1.15.0
>
> Attachments: knife-logo-header.svg
>
>
> Currently SVG images can be used:
> * as Logo in the upper left corner (Wicket Menubar)
> * on the Login Page (login.html)
> * as favicon ("image/svg+xml", cf. [ISIS-1115])
> SVGs are not displayed
> * on the welcome page
> SVGs can be attached as Blobs, but they are displayed as bitmaps (by means of
> the Batik rasterizer) and do not scale. The rasterizer (of course) can not
> deal with animations (cf. attachment).
> See:
> https://lists.apache.org/thread.html/68f16dd0306a8101c1cde06e5e6309b8d1b81b388a1f59e123cfc2f3@%3Cusers.isis.apache.org%3E
> {code}
>
> com.twelvemonkeys.imageio
> imageio-batik
> 3.3.2
>
>
> com.twelvemonkeys.imageio
> imageio-batik
> 3.3.2
> test-jar
> test
>
>
> org.apache.xmlgraphics
> batik-transcoder
> 1.8
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ISIS-1572) RestfulObjects viewer - Service members empty
[
https://issues.apache.org/jira/browse/ISIS-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Rade updated ISIS-1572:
I suspect it's authentication / CORS related
> RestfulObjects viewer - Service members empty
> -
>
> Key: ISIS-1572
> URL: https://issues.apache.org/jira/browse/ISIS-1572
> Project: Isis
> Issue Type: Bug
> Components: Core: Viewer: RestfulObjects
>Affects Versions: 1.13.0
> Environment: Web.xml is patched according to
> https://github.com/danhaywood/isis-angularjs-simpleapp in order to cope with
> CORS issues.
>Reporter: Jörg Rade
> Fix For: 1.15.0
>
>
> _Sometimes_ the members section of the response to
> http://localhost:9090/restful/services/Applications/ is empty - sometimes it
> is not:
> {code|language=javascript}
> {
> "links" : [ {
> "rel" : "self",
> "href" : "http://localhost:9090/restful/services/Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/object\"",
> "title" : "Applications"
> }, {
> "rel" : "describedby",
> "href" :
> "http://localhost:9090/restful/domain-types/ife.dep.Applications;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/domain-type\""
> }, {
> "rel" : "up",
> "href" : "http://localhost:9090/restful/services;,
> "method" : "GET",
> "type" :
> "application/json;profile=\"urn:org.restfulobjects:repr-types/list\""
> } ],
> "extensions" : {
> "oid" : "ife.dep.Applications:1",
> "isService" : true,
> "isPersistent" : true
> },
> "title" : "Applications",
> "serviceId" : "Applications",
> "members" : { }
> }
> {code}
> After some time the app was accessed via the wicket viewer. It first
> delivered the homepage and then I invoked the listAll operation via the
> respective menu item.
> Invoking http://localhost:9090/restful/services/Applications/ afterwards
> showed the expected response including the members.
> In another case there was a difference between:
> * http://localhost:9090/restful/services/Applications/ (with members) and
> * http://localhost:9090/restful/services/Applications (without members)
> In yet another case both URL's delivered a result without 'members' filled,
> even after the 'workaround' described above.
> https://github.com/joerg-rade/isis-app-todoapp shows the same behavior:
> * http://localhost:/restful/services/todo.ToDoItems/ whereas
> * http://localhost:/restful/domain-types/todoapp.dom.todoitem.ToDoItems
> shows the members
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (ISIS-1277) setAccessible() will be gone with JDK 9
[ https://issues.apache.org/jira/browse/ISIS-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176247#comment-16176247 ] Jörg Rade commented on ISIS-1277: - The hibernate ways: http://in.relation.to/2017/04/11/accessing-private-state-of-java-9-modules/ > setAccessible() will be gone with JDK 9 > --- > > 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: 3.0.0 > > > 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 (v6.4.14#64029)
[jira] [Commented] (ISIS-1645) Integrate Kyro as an alternative technology for view models
[ https://issues.apache.org/jira/browse/ISIS-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176050#comment-16176050 ] Jörg Rade commented on ISIS-1645: - Project name was changed from Kyro to Kryo ... > Integrate Kyro as an alternative technology for view models > --- > > Key: ISIS-1645 > URL: https://issues.apache.org/jira/browse/ISIS-1645 > Project: Isis > Issue Type: New Feature >Reporter: Dan Haywood >Priority: Minor > Fix For: 1.16.0 > > > as per discussion at > https://lists.apache.org/thread.html/c71a9e277b4cb76ca32f166268e5fb7c2376ed6f5da3fcab0e850b5b@%3Cusers.isis.apache.org%3E > see also > https://github.com/datanucleus/datanucleus-typeconverter-kryo/tree/master/src/main/resources -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1708) Broken Links according to W3C checker
[ https://issues.apache.org/jira/browse/ISIS-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade updated ISIS-1708: Description: According to https://validator.w3.org/checklink?uri=https%3A%2F%2Fisis.apache.org%2F=on_type=all=on=3=nochanges=Check there are some problems with fragments, see attchment. grtnx -j was: A couple of links into the documentation are broken: | Source | Link Label | Broken | Existing | | https://github.com/apache/isis/tree/master/example/application/simpleapp | simpleapp archetype | http://isis.apache.org/guides/ugfun.html#_ugfun_getting-started_simpleapp-archetype | http://isis.apache.org/guides/ugfun/ugfun.html#_ugfun_getting-started_simpleapp-archetype | > Broken Links according to W3C checker > - > > Key: ISIS-1708 > URL: https://issues.apache.org/jira/browse/ISIS-1708 > Project: Isis > Issue Type: Documentation >Reporter: Jörg Rade >Assignee: Dan Haywood > > According to > https://validator.w3.org/checklink?uri=https%3A%2F%2Fisis.apache.org%2F=on_type=all=on=3=nochanges=Check > > there are some problems with fragments, see attchment. > grtnx -j -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ISIS-1708) Broken Links according to W3C checker
Jörg Rade created ISIS-1708: --- Summary: Broken Links according to W3C checker Key: ISIS-1708 URL: https://issues.apache.org/jira/browse/ISIS-1708 Project: Isis Issue Type: Documentation Reporter: Jörg Rade Assignee: Dan Haywood Fix For: 1.15.0 A couple of links into the documentation are broken: | Source | Link Label | Broken | Existing | | https://github.com/apache/isis/tree/master/example/application/simpleapp | simpleapp archetype | http://isis.apache.org/guides/ugfun.html#_ugfun_getting-started_simpleapp-archetype | http://isis.apache.org/guides/ugfun/ugfun.html#_ugfun_getting-started_simpleapp-archetype | -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1708) Broken Links according to W3C checker
[ https://issues.apache.org/jira/browse/ISIS-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade updated ISIS-1708: Attachment: W3C Link Checker https _isis.apache.org_.htm > Broken Links according to W3C checker > - > > Key: ISIS-1708 > URL: https://issues.apache.org/jira/browse/ISIS-1708 > Project: Isis > Issue Type: Documentation >Reporter: Jörg Rade >Assignee: Dan Haywood > Attachments: W3C Link Checker https _isis.apache.org_.htm > > > According to > https://validator.w3.org/checklink?uri=https%3A%2F%2Fisis.apache.org%2F=on_type=all=on=3=nochanges=Check > > there are some problems with fragments, see attchment. > grtnx -j -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1708) Broken Links according to W3C checker
[ https://issues.apache.org/jira/browse/ISIS-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade updated ISIS-1708: Fix Version/s: (was: 1.15.0) > Broken Links according to W3C checker > - > > Key: ISIS-1708 > URL: https://issues.apache.org/jira/browse/ISIS-1708 > Project: Isis > Issue Type: Documentation >Reporter: Jörg Rade >Assignee: Dan Haywood > > A couple of links into the documentation are broken: > | Source | Link Label | Broken | Existing | > | https://github.com/apache/isis/tree/master/example/application/simpleapp | > simpleapp archetype | > http://isis.apache.org/guides/ugfun.html#_ugfun_getting-started_simpleapp-archetype > | > http://isis.apache.org/guides/ugfun/ugfun.html#_ugfun_getting-started_simpleapp-archetype > | -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1708) Broken Links according to W3C checker
[ https://issues.apache.org/jira/browse/ISIS-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade updated ISIS-1708: Priority: Minor (was: Major) > Broken Links according to W3C checker > - > > Key: ISIS-1708 > URL: https://issues.apache.org/jira/browse/ISIS-1708 > Project: Isis > Issue Type: Documentation >Reporter: Jörg Rade >Assignee: Dan Haywood >Priority: Minor > Attachments: W3C Link Checker https _isis.apache.org_.htm > > > According to > https://validator.w3.org/checklink?uri=https%3A%2F%2Fisis.apache.org%2F=on_type=all=on=3=nochanges=Check > > there are some 404 errors, see attachment. > grtnx -j -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1767) JEE 7+ Support
[
https://issues.apache.org/jira/browse/ISIS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16247188#comment-16247188
]
Jörg Rade commented on ISIS-1767:
-
Hi Andi,
maybe https://github.com/javaee/glassfish/issues/22270 contains some hints.
HTH -j
> 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
> 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)
> * 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: use mysql db connection pool managed by the JEE
> container and provided via JNDI
> ||server||fat-war||skinny-war||restEasy||managed connection pool||
> |Payara (web-profile 4.1.2.173)|FAILED(1)|OK|OK|OK|
> |TomEE (plume 7.0.4)|OK(2)|todo|OK|todo|
> |Wildfly (tbd)|todo|todo|todo|todo|
> |Glassfish (full 5.0)|FAILED(3)|todo|todo|todo|
> Notes:
> (1)
> * WicketFilter does not respond
> (2)
> * requires CXF to be disabled, see
> https://stackoverflow.com/questions/41496204/tomee-7-0-2-how-to-disable-cxf-rs
> * throws exceptions on undeploy
> (3)
> * strange class-loading issues, though library is included in war ...
> java.lang.ClassNotFoundException: org.joda.time.ReadableInstant
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (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:comment-tabpanel=16258919#comment-16258919 ] Jörg Rade commented on ISIS-1779: - My2C: Since JEE conformance is a new feature for the framework, it should be OK to just support JEE8. > 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 > > > Dedicated Branch > dev/2.0.0/ISIS-1779-jax-rs-2 > 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] [Created] (ISIS-1953) @NotPersistable is deprecated but javadoc is missing instructions
Jörg Rade created ISIS-1953: --- Summary: @NotPersistable is deprecated but javadoc is missing instructions Key: ISIS-1953 URL: https://issues.apache.org/jira/browse/ISIS-1953 Project: Isis Issue Type: Improvement Affects Versions: 1.16.0 Reporter: Jörg Rade -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ISIS-1960) Action background execution: provide built-in default implementation
[
https://issues.apache.org/jira/browse/ISIS-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524682#comment-16524682
]
Jörg Rade commented on ISIS-1960:
-
eventually related to
https://lists.apache.org/thread.html/32b70e0a949ac1f149c4ce031b0a28874cc0f2f48b2d4954692ceb87@%3Cusers.isis.apache.org%3E
?
> Action background execution: provide built-in default implementation
>
>
> Key: ISIS-1960
> URL: https://issues.apache.org/jira/browse/ISIS-1960
> Project: Isis
> Issue Type: Improvement
> Components: Core
>Reporter: Andi Huber
>Assignee: Andi Huber
>Priority: Major
> Fix For: 2.0.0-M2
>
>
> We want this code to run out-of the box (without the need for developers to
> provide their own implementation of *BackgroundCommandService*) ...
> {code:java}
> @Inject private BackgroundService2 backgroundService;
> @Action
> public SimpleObject runSlowlyInBackground(){
> backgroundService.execute(this).runSlowly();
> return this;
> }
>
> @Action
> public SimpleObject runSlowly(){
> try {
> Thread.sleep(8000); // wait 8s
> } catch (InterruptedException e) {
> e.printStackTrace();
> }
>
> val dummy = new SimpleObject();
> dummy.setName("Dummy");
>
> repositoryService.persist(dummy);
>
> return this;
> }
> {code}
> We solve this using a default ExecutorService to run Action invocations in
> the background.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ISIS-1777) swagger-ui/index.html in helloworld and simpleapp needs to honor context paths
[
https://issues.apache.org/jira/browse/ISIS-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301060#comment-16301060
]
Jörg Rade commented on ISIS-1777:
-
related to [ISIS-1172]?
> swagger-ui/index.html in helloworld and simpleapp needs to honor context paths
> --
>
> Key: ISIS-1777
> URL: https://issues.apache.org/jira/browse/ISIS-1777
> Project: Isis
> Issue Type: Bug
>Reporter: Andi Huber
>Assignee: Dan Haywood
> Fix For: 1.16.0
>
>
> As soon as we deploy helloworld or simpleapp with web-app context path the
> absolute links (/restful/...) provided in
> {{webapp/swagger-ui/index.html}}
> will not work.
> Proposed fix:
> https://issues.apache.org/jira/browse/ISIS-1775?focusedCommentId=16248942=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16248942
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ISIS-1850) Rename 'default' in JSON Response
Jörg Rade created ISIS-1850:
---
Summary: Rename 'default' in JSON Response
Key: ISIS-1850
URL: https://issues.apache.org/jira/browse/ISIS-1850
Project: Isis
Issue Type: Improvement
Components: Core: Viewer: RestfulObjects
Affects Versions: 1.16.0
Reporter: Jörg Rade
Invoking
{code:java}
http://localhost:8080/restful/services/isisApplib.FixtureScriptsDefault/actions/runFixtureScript{code}
answers:
{code}
"parameters": {
"script": {
"num": 0,
"id": "script",
"name": "Script",
"description": "",
"choices": [
{
"rel": "urn:org.restfulobjects:rels/value",
"href":
"http://localhost:8080/restful/objects/domainapp.application.fixture.scenarios.DomainAppDemo/PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPG1lbWVudG8-PHBhdGg-PC9wYXRoPjwvbWVtZW50bz4=;,
"method": "GET",
"type":
"application/json;profile=\"urn:org.restfulobjects:repr-types/object\"",
"title": "Domain App Demo"
}
],
"default": {
"rel": "urn:org.restfulobjects:rels/value",
"href":
"http://localhost:8080/restful/objects/domainapp.application.fixture.scenarios.DomainAppDemo/PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPG1lbWVudG8-PHBhdGg-PC9wYXRoPjwvbWVtZW50bz4=;,
"method": "GET",
"type":
"application/json;profile=\"urn:org.restfulobjects:repr-types/object\"",
"title": "Domain App Demo"
}
},
{code}
default is a keyword in ActionScript and converting JSON to AS like in
https://github.com/joerg-rade/roViz/blob/master/src/main/flex/org/ro/to/AbstractTransferObject.as#L10
is not possible since 'public var default:Object' is illegal.
Please rename 'default' into eg. defaultChoice
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ISIS-1849) 1.16.0 - Broken Links according to W3C checker
Jörg Rade created ISIS-1849: --- Summary: 1.16.0 - Broken Links according to W3C checker Key: ISIS-1849 URL: https://issues.apache.org/jira/browse/ISIS-1849 Project: Isis Issue Type: Documentation Reporter: Jörg Rade Assignee: Dan Haywood Fix For: 1.15.1 According to https://validator.w3.org/checklink?uri=https%3A%2F%2Fisis.apache.org%2F=on_type=all=on=3=nochanges=Check there are some 404 errors, see attachment. grtnx -j -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-1849) 1.16.0 - Broken Links according to W3C checker
[ https://issues.apache.org/jira/browse/ISIS-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade updated ISIS-1849: Attachment: W3C Link Checker https _isis.apache.org_.htm > 1.16.0 - Broken Links according to W3C checker > -- > > Key: ISIS-1849 > URL: https://issues.apache.org/jira/browse/ISIS-1849 > Project: Isis > Issue Type: Documentation >Reporter: Jörg Rade >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.16.1 > > Attachments: W3C Link Checker https _isis.apache.org_.htm > > > According to > [https://validator.w3.org/checklink?uri=https%3A%2F%2Fisis.apache.org%2F=on_type=all=on=3=nochanges=Check] > > there are some 404 errors: > [https://isis.apache.org/guides/cgcom/cgcom.html] (probably on purpose) > Line: 2321 > https://git-wip-us.apache.org/repos/asf/isis/repo?p=isis.git;a=blob_plain;f=STATUS;hb=HEAD > Line: 3512 http://people.apache.org/~/.asc > https://isis.apache.org/guides/rgcms/rgcms.html > Line: 5198 https://isis.apache.org/guides/rgcms/images/value-types/markup/.png > Line: 6378 http://isis.apache.org/applib/layout/menus/menubars.xsd > https://isis.apache.org/guides/ugtst/ugtst.html > Line: 2276 https://isis.apache.org/guides/ugtst/rgsvc.html > https://isis.apache.org/migration-notes/migration-notes.html > Line: 619 https://isis.apache.org/rgcms/rgcms.html > Lines: 464, 564, 565 https://isis.apache.org/ugfun/ugfun.html > Line: 1072 https://isis.apache.org/migration-notes/rgsvc.html > Line: 572 https://isis.apache.org/rgcfg.html > Line: 552 https://isis.apache.org/ugfun.html > Line: 619 https://isis.apache.org/ugtst/ugtst.html > https://isis.apache.org/guides/dg/dg.html > Line: 4441 https://isis.apache.org/setting-up/concepts/concepts.html > Lines: 4412, 4426 https://isis.apache.org/guides/dg/_images/vscode.png > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-1849) 1.16.0 - Broken Links according to W3C checker
[ https://issues.apache.org/jira/browse/ISIS-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade updated ISIS-1849: Description: According to [https://validator.w3.org/checklink?uri=https%3A%2F%2Fisis.apache.org%2F=on_type=all=on=3=nochanges=Check] there are some 404 errors: [https://isis.apache.org/guides/cgcom/cgcom.html] (probably on purpose) Line: 2321 https://git-wip-us.apache.org/repos/asf/isis/repo?p=isis.git;a=blob_plain;f=STATUS;hb=HEAD Line: 3512 http://people.apache.org/~/.asc https://isis.apache.org/guides/rgcms/rgcms.html Line: 5198 https://isis.apache.org/guides/rgcms/images/value-types/markup/.png Line: 6378 http://isis.apache.org/applib/layout/menus/menubars.xsd https://isis.apache.org/guides/ugtst/ugtst.html Line: 2276 https://isis.apache.org/guides/ugtst/rgsvc.html https://isis.apache.org/migration-notes/migration-notes.html Line: 619 https://isis.apache.org/rgcms/rgcms.html Lines: 464, 564, 565 https://isis.apache.org/ugfun/ugfun.html Line: 1072 https://isis.apache.org/migration-notes/rgsvc.html Line: 572 https://isis.apache.org/rgcfg.html Line: 552 https://isis.apache.org/ugfun.html Line: 619 https://isis.apache.org/ugtst/ugtst.html https://isis.apache.org/guides/dg/dg.html Line: 4441 https://isis.apache.org/setting-up/concepts/concepts.html Lines: 4412, 4426 https://isis.apache.org/guides/dg/_images/vscode.png was: According to https://validator.w3.org/checklink?uri=https%3A%2F%2Fisis.apache.org%2F=on_type=all=on=3=nochanges=Check there are some 404 errors, see attachment. grtnx -j > 1.16.0 - Broken Links according to W3C checker > -- > > Key: ISIS-1849 > URL: https://issues.apache.org/jira/browse/ISIS-1849 > Project: Isis > Issue Type: Documentation >Reporter: Jörg Rade >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.16.1 > > > According to > [https://validator.w3.org/checklink?uri=https%3A%2F%2Fisis.apache.org%2F=on_type=all=on=3=nochanges=Check] > > there are some 404 errors: > [https://isis.apache.org/guides/cgcom/cgcom.html] (probably on purpose) > Line: 2321 > https://git-wip-us.apache.org/repos/asf/isis/repo?p=isis.git;a=blob_plain;f=STATUS;hb=HEAD > Line: 3512 http://people.apache.org/~/.asc > https://isis.apache.org/guides/rgcms/rgcms.html > Line: 5198 https://isis.apache.org/guides/rgcms/images/value-types/markup/.png > Line: 6378 http://isis.apache.org/applib/layout/menus/menubars.xsd > https://isis.apache.org/guides/ugtst/ugtst.html > Line: 2276 https://isis.apache.org/guides/ugtst/rgsvc.html > https://isis.apache.org/migration-notes/migration-notes.html > Line: 619 https://isis.apache.org/rgcms/rgcms.html > Lines: 464, 564, 565 https://isis.apache.org/ugfun/ugfun.html > Line: 1072 https://isis.apache.org/migration-notes/rgsvc.html > Line: 572 https://isis.apache.org/rgcfg.html > Line: 552 https://isis.apache.org/ugfun.html > Line: 619 https://isis.apache.org/ugtst/ugtst.html > https://isis.apache.org/guides/dg/dg.html > Line: 4441 https://isis.apache.org/setting-up/concepts/concepts.html > Lines: 4412, 4426 https://isis.apache.org/guides/dg/_images/vscode.png > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-1849) 1.16.0 - Broken Links according to W3C checker
[ https://issues.apache.org/jira/browse/ISIS-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade updated ISIS-1849: Fix Version/s: (was: 1.15.1) 1.16.1 > 1.16.0 - Broken Links according to W3C checker > -- > > Key: ISIS-1849 > URL: https://issues.apache.org/jira/browse/ISIS-1849 > Project: Isis > Issue Type: Documentation >Reporter: Jörg Rade >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.16.1 > > > According to > [https://validator.w3.org/checklink?uri=https%3A%2F%2Fisis.apache.org%2F=on_type=all=on=3=nochanges=Check] > > there are some 404 errors: > [https://isis.apache.org/guides/cgcom/cgcom.html] (probably on purpose) > Line: 2321 > https://git-wip-us.apache.org/repos/asf/isis/repo?p=isis.git;a=blob_plain;f=STATUS;hb=HEAD > Line: 3512 http://people.apache.org/~/.asc > https://isis.apache.org/guides/rgcms/rgcms.html > Line: 5198 https://isis.apache.org/guides/rgcms/images/value-types/markup/.png > Line: 6378 http://isis.apache.org/applib/layout/menus/menubars.xsd > https://isis.apache.org/guides/ugtst/ugtst.html > Line: 2276 https://isis.apache.org/guides/ugtst/rgsvc.html > https://isis.apache.org/migration-notes/migration-notes.html > Line: 619 https://isis.apache.org/rgcms/rgcms.html > Lines: 464, 564, 565 https://isis.apache.org/ugfun/ugfun.html > Line: 1072 https://isis.apache.org/migration-notes/rgsvc.html > Line: 572 https://isis.apache.org/rgcfg.html > Line: 552 https://isis.apache.org/ugfun.html > Line: 619 https://isis.apache.org/ugtst/ugtst.html > https://isis.apache.org/guides/dg/dg.html > Line: 4441 https://isis.apache.org/setting-up/concepts/concepts.html > Lines: 4412, 4426 https://isis.apache.org/guides/dg/_images/vscode.png > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ISIS-1808) Let the error page be customisable, eg embed an image from randomkittengenerator.com
[ https://issues.apache.org/jira/browse/ISIS-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16323668#comment-16323668 ] Jörg Rade commented on ISIS-1808: - Cute idea, and getting something from https://samebug.io/ could even provide additional help. > Let the error page be customisable, eg embed an image from > randomkittengenerator.com > > > Key: ISIS-1808 > URL: https://issues.apache.org/jira/browse/ISIS-1808 > Project: Isis > Issue Type: Improvement >Affects Versions: 1.16.0 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 1.16.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1850) [NOT IMPLEMENTED] Rename 'default' in JSON Response
[
https://issues.apache.org/jira/browse/ISIS-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348829#comment-16348829
]
Jörg Rade commented on ISIS-1850:
-
No need to break the spec. I have a workaround.
> [NOT IMPLEMENTED] Rename 'default' in JSON Response
> ---
>
> Key: ISIS-1850
> URL: https://issues.apache.org/jira/browse/ISIS-1850
> Project: Isis
> Issue Type: Improvement
> Components: Core: Viewer: RestfulObjects
>Affects Versions: 1.16.0
>Reporter: Jörg Rade
>Assignee: Dan Haywood
>Priority: Major
> Fix For: 1.16.1
>
>
> Invoking
> {code:java}
> http://localhost:8080/restful/services/isisApplib.FixtureScriptsDefault/actions/runFixtureScript{code}
> answers:
> {code}
> "parameters": {
> "script": {
> "num": 0,
> "id": "script",
> "name": "Script",
> "description": "",
> "choices": [
> {
> "rel": "urn:org.restfulobjects:rels/value",
> "href":
> "http://localhost:8080/restful/objects/domainapp.application.fixture.scenarios.DomainAppDemo/PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPG1lbWVudG8-PHBhdGg-PC9wYXRoPjwvbWVtZW50bz4=;,
> "method": "GET",
> "type":
> "application/json;profile=\"urn:org.restfulobjects:repr-types/object\"",
> "title": "Domain App Demo"
> }
> ],
> "default": {
> "rel": "urn:org.restfulobjects:rels/value",
> "href":
> "http://localhost:8080/restful/objects/domainapp.application.fixture.scenarios.DomainAppDemo/PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPG1lbWVudG8-PHBhdGg-PC9wYXRoPjwvbWVtZW50bz4=;,
> "method": "GET",
> "type":
> "application/json;profile=\"urn:org.restfulobjects:repr-types/object\"",
> "title": "Domain App Demo"
> }
> },
> {code}
> default is a keyword in ActionScript and converting JSON to AS like in
> https://github.com/joerg-rade/roViz/blob/master/src/main/flex/org/ro/to/AbstractTransferObject.as#L10
> is not possible since 'public var default:Object' is illegal.
> Please rename 'default' into eg. defaultChoice
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ISIS-1635) Upgrade dependency to resteasy
[
https://issues.apache.org/jira/browse/ISIS-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Rade resolved ISIS-1635.
-
Resolution: Duplicate
Fix Version/s: (was: 2.4.0)
> Upgrade dependency to resteasy
> --
>
> Key: ISIS-1635
> URL: https://issues.apache.org/jira/browse/ISIS-1635
> Project: Isis
> Issue Type: Improvement
> Components: Core: Viewer: RestfulObjects
>Affects Versions: 1.14.0
>Reporter: Jörg Rade
>Priority: Major
> Attachments: Dependency-Check.png
>
>
> org.codehaus.jackson brings in some vulnerabilities:
> !Dependency-Check.png|thumbnail!
> {code}
> [INFO] | +-
> org.apache.isis.core:isis-core-viewer-restfulobjects-server:jar:1.14.0:compile
> [INFO] | | +-
> org.apache.isis.core:isis-core-viewer-restfulobjects-rendering:jar:1.14.0:compile
> [INFO] | | | +-
> org.jboss.resteasy:resteasy-jaxb-provider:jar:3.0.14.Final:compile
> [INFO] | | | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.7:compile
> [INFO] | | | | | +- com.sun.xml.bind:jaxb-core:jar:2.2.7:compile
> [INFO] | | | | | | +- javax.xml.bind:jaxb-api:jar:2.2.7:compile
> [INFO] | | | | | | \-
> com.sun.istack:istack-commons-runtime:jar:2.16:compile
> [INFO] | | | | | \-
> com.sun.xml.fastinfoset:FastInfoset:jar:1.2.12:compile
> [INFO] | | | | | \- javax.xml.bind:jsr173_api:jar:1.0:compile
> [INFO] | | | | \- org.jboss.logging:jboss-logging:jar:3.1.4.GA:compile
> [INFO] | | | +-
> org.jboss.resteasy:resteasy-jackson-provider:jar:3.0.14.Final:compile
> [INFO] | | | | +- org.codehaus.jackson:jackson-core-asl:jar:1.9.12:compile
> [INFO] | | | | +-
> org.codehaus.jackson:jackson-mapper-asl:jar:1.9.12:compile
> [INFO] | | | | +- org.codehaus.jackson:jackson-jaxrs:jar:1.9.12:compile
> [INFO] | | | | \- org.codehaus.jackson:jackson-xc:jar:1.9.12:compile
> {code}
> Please upgrade to 3.1.3Final if feasible:
> {code}
>
> org.jboss.resteasy
> resteasy-jaxb-provider
> 3.1.3.Final
>
>
> org.jboss.resteasy
> resteasy-jackson-provider
> 3.1.3.Final
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ISIS-1360) Declarative Invariants
[ https://issues.apache.org/jira/browse/ISIS-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16386299#comment-16386299 ] Jörg Rade commented on ISIS-1360: - IMO declaring business rules matches the spirit of the framework. The code now lives at https://sourceforge.net/p/autobuslogic/wiki/Home/ > Declarative Invariants > -- > > Key: ISIS-1360 > URL: https://issues.apache.org/jira/browse/ISIS-1360 > Project: Isis > Issue Type: Proposal > Components: Core, Core: Objectstore: JDO >Affects Versions: 1.12.0 >Reporter: Cesar Lugo >Priority: Minor > Fix For: 3.0.0 > > > I think that one aspect of the amplification concept Apache ISIS provides > might be to allow some degree of declarative business rules / invariants. > There is an interesting open source project (1) that allows a Java > application to define declarative business rules / invariant you might want > to fork. > > The difference between some other business rules engines (say RETE compliant) > is that most business rules engines focus on conditional business rules or > decision business rules only, and work outside the application scope, as an > external API returning results that you must incorporate into your code with > even more code. This one´s focus (ABL) is transactional business rules, which > work through the persistence manager (Hibernate´s JPA in this case), so you > don´t need to call any rules to be triggered, rules are automatically > triggered when you persist data. Thus, it lets you use the previous values > before saving and after saving to trigger rules (update inventory with new > value of received quantity - old value of received quantity + old value of > inventory). > > In summary, it provides: > •Declarative rules, like: > o InvoiceItem.amount = InvoiceItem.quantity * InvoiceItem.unitPrice * (1 + > VAT / 100) > o Invoice.amount = sum(InvoiceItem.amount) if InvoiceItem.status != > “deleted” > o account balance = sum(invoice.amount) if status = “due > •Automatic sequencing of the rules. This is really great, because > instead of sequenced lines of code, you create independent rules, which you > can maintain and change completely separate from all other rules. You can > even have a rules manager and document each rule. > •Automatic execution of the rules every time you do an insert, update > or delete to any of those entity objects. Any change executes the rules > properly. If a new rule implies altering the sequence of the execution of > rules, this happens automatically and seamlessly. > •Extensibility (create your own rules). Create a new weightedAverage > () rule. > •Documentation. You can document your rules, associate rules to topic > or groups, like use cases where they come from. > > > (1)http://www.automatedbusinesslogic.com/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ISIS-2051) Amend ugrov
Jörg Rade created ISIS-2051: --- Summary: Amend ugrov Key: ISIS-2051 URL: https://issues.apache.org/jira/browse/ISIS-2051 Project: Isis Issue Type: Documentation Reporter: Jörg Rade Attachments: _ugvro_hints-and-tips_troubleshooting.adoc Attachment contains adoc formatted example, in short: Exception: 'com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptions' Solution: Add @XmlAccessorType(XmlAccessType.FIELD) to your domain entity -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-2051) Amend ugrov
[ https://issues.apache.org/jira/browse/ISIS-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade updated ISIS-2051: Affects Version/s: 1.16.2 > Amend ugrov > > > Key: ISIS-2051 > URL: https://issues.apache.org/jira/browse/ISIS-2051 > Project: Isis > Issue Type: Documentation >Affects Versions: 1.16.2 >Reporter: Jörg Rade >Priority: Trivial > Fix For: 1.16.3 > > Attachments: _ugvro_hints-and-tips_troubleshooting.adoc > > > Attachment contains adoc formatted example, in short: > Exception: > 'com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of > IllegalAnnotationExceptions' > Solution: > Add @XmlAccessorType(XmlAccessType.FIELD) to your domain entity -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ISIS-2051) Amend ugrov
[ https://issues.apache.org/jira/browse/ISIS-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade updated ISIS-2051: Fix Version/s: 1.16.3 > Amend ugrov > > > Key: ISIS-2051 > URL: https://issues.apache.org/jira/browse/ISIS-2051 > Project: Isis > Issue Type: Documentation >Affects Versions: 1.16.2 >Reporter: Jörg Rade >Priority: Trivial > Fix For: 1.16.3 > > Attachments: _ugvro_hints-and-tips_troubleshooting.adoc > > > Attachment contains adoc formatted example, in short: > Exception: > 'com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of > IllegalAnnotationExceptions' > Solution: > Add @XmlAccessorType(XmlAccessType.FIELD) to your domain entity -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ISIS-1927) Invoking an action returning a non-null Blob via RO results in exception
[
https://issues.apache.org/jira/browse/ISIS-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724245#comment-16724245
]
Jörg Rade commented on ISIS-1927:
-
With 1.16.2 when:
{code:java}
$ curl -H "Content-Type: application/json" -d @input.json -u jenkins:pass
http://localhost:8080/restful/services/ife.cfg.vm.Checks/actions/checkNewEndpoints/invoke
-o output.json{code}
where input json is:
{code:java}
{
"applicationName": {
"value": "SALOG"
},
"applicationVersion": {
"value": "3.12.5.10"
}
}{code}
and Checks.checkNewEndpoints is:
{code:java}
@Action(semantics = SemanticsOf.SAFE)
@ActionLayout(cssClassFa = "bolt", describedAs = "Check if WS endpoints and JMS
topics of new release exist")
public String checkNewEndpoints(
@ParameterLayout(named = "Application Name") String appName,
@ParameterLayout(named = "Application Version") String appVersion) {
applicationReader.init();
final Stage stage = stages.findOrCreate(Constants.PROD);
final Application application = applications.findByName(appName);
final Configuration oldConfig =
configurations.importApplicationStage(application, stage);
final Configuration newConfig =
configurations.importApplicationVersion(application, appVersion);
final ReleaseComparison dashboard =
releaseComparisons.create(oldConfig.getRelease(), newConfig.getRelease());
SortedSet epList =
serviceComparisons.checkNewEndpoints(dashboard);
return toString(epList);
}{code}
then output.json is:
{code}
{
"httpStatusCode": 500,
"message": "objectAdapter must be a root adapter",
"detail": {
"className": "java.lang.IllegalArgumentException",
"message": "objectAdapter must be a root adapter",
"element": [
"org.apache.isis.viewer.restfulobjects.rendering.util.OidUtils.getOidStr(OidUtils.java:52)",
"org.apache.isis.viewer.restfulobjects.rendering.util.OidUtils.getInstanceId(OidUtils.java:43)",
"org.apache.isis.viewer.restfulobjects.rendering.domainobjects.DomainObjectReprRenderer.getInstanceId(DomainObjectReprRenderer.java:250)",
"org.apache.isis.viewer.restfulobjects.rendering.domainobjects.DomainObjectReprRenderer.render(DomainObjectReprRenderer.java:160)",
"org.apache.isis.viewer.restfulobjects.rendering.Responses.ofOk(Responses.java:82)",
"org.apache.isis.viewer.restfulobjects.rendering.Responses.ofOk(Responses.java:63)",
"org.apache.isis.viewer.restfulobjects.rendering.service.conneg.ContentNegotiationServiceForRestfulObjectsV1_0.buildResponseTo(ContentNegotiationServiceForRestfulObjectsV1_0.java:105)",
"org.apache.isis.viewer.restfulobjects.rendering.service.conneg.ContentNegotiationServiceForRestfulObjectsV1_0.buildResponse(ContentNegotiationServiceForRestfulObjectsV1_0.java:86)",
"org.apache.isis.viewer.restfulobjects.rendering.service.conneg.ContentNegotiationServiceForRestfulObjectsV1_0.buildResponse(ContentNegotiationServiceForRestfulObjectsV1_0.java:228)",
"org.apache.isis.viewer.restfulobjects.rendering.service.RepresentationServiceContentNegotiator$5.apply(RepresentationServiceContentNegotiator.java:157)",
"org.apache.isis.viewer.restfulobjects.rendering.service.RepresentationServiceContentNegotiator$5.apply(RepresentationServiceContentNegotiator.java:154)",
"org.apache.isis.viewer.restfulobjects.rendering.service.RepresentationServiceContentNegotiator.buildResponse(RepresentationServiceContentNegotiator.java:195)",
"org.apache.isis.viewer.restfulobjects.rendering.service.RepresentationServiceContentNegotiator.actionResult(RepresentationServiceContentNegotiator.java:154)",
"org.apache.isis.viewer.restfulobjects.server.resources.DomainResourceHelper.invokeActionUsingAdapters(DomainResourceHelper.java:379)",
"org.apache.isis.viewer.restfulobjects.server.resources.DomainResourceHelper.invokeAction(DomainResourceHelper.java:351)",
"org.apache.isis.viewer.restfulobjects.server.resources.DomainServiceResourceServerside.invokeAction(DomainServiceResourceServerside.java:263)",
"sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)",
&quo
[jira] [Resolved] (ISIS-2052) Remove unused private constructors
[ https://issues.apache.org/jira/browse/ISIS-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade resolved ISIS-2052. - Resolution: Invalid This was a false positive! > Remove unused private constructors > -- > > Key: ISIS-2052 > URL: https://issues.apache.org/jira/browse/ISIS-2052 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: 1.16.2 >Reporter: Jörg Rade >Priority: Trivial > Attachments: ScreenShot 182 Remove this unused private > _CssClassFaFacetForDomainObjectLayoutFactory_ constructor. - Apache Isis > (Aggregator) - Google Chrome.png > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ISIS-2052) Remove unused private constructors
[ https://issues.apache.org/jira/browse/ISIS-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Rade closed ISIS-2052. --- > Remove unused private constructors > -- > > Key: ISIS-2052 > URL: https://issues.apache.org/jira/browse/ISIS-2052 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: 1.16.2 >Reporter: Jörg Rade >Priority: Trivial > Attachments: ScreenShot 182 Remove this unused private > _CssClassFaFacetForDomainObjectLayoutFactory_ constructor. - Apache Isis > (Aggregator) - Google Chrome.png > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ISIS-2055) Amend CI Builds by Sonarqube Analysis
Jörg Rade created ISIS-2055: --- Summary: Amend CI Builds by Sonarqube Analysis Key: ISIS-2055 URL: https://issues.apache.org/jira/browse/ISIS-2055 Project: Isis Issue Type: Improvement Components: Website and Docs Reporter: Jörg Rade As discussed in [1], amends the CI build to submit build artefacts to sonar analysis on [2]. Default sonar rule set may need to be customized in order to avoid false positives. [1] https://lists.apache.org/thread.html/30ae8fb467fd76cbb2fc0404198ec369c4d87c14e6cc5df18efe28a6@%3Cdev.isis.apache.org%3E [2] https://builds.apache.org/analysis/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ISIS-2056) Remove unused code (Sonar findings)
Jörg Rade created ISIS-2056: --- Summary: Remove unused code (Sonar findings) Key: ISIS-2056 URL: https://issues.apache.org/jira/browse/ISIS-2056 Project: Isis Issue Type: Improvement Reporter: Jörg Rade -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ISIS-1999) For action mixins, allow read-only properties and collections to be defined, to show useful/relevant context data.
[
https://issues.apache.org/jira/browse/ISIS-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16717066#comment-16717066
]
Jörg Rade commented on ISIS-1999:
-
It would then not result in
{code:java}
"href": "http://localhost:8080/helpUrl; {code}
but in
{code:java}
"helpString": "http://localhost:8080/helpUrl"{code}
It would be left to the client to decide how to render - correct?
> For action mixins, allow read-only properties and collections to be defined,
> to show useful/relevant context data.
> --
>
> Key: ISIS-1999
> URL: https://issues.apache.org/jira/browse/ISIS-1999
> Project: Isis
> Issue Type: New Feature
>Affects Versions: 1.16.2
>Reporter: Dan Haywood
>Priority: Major
> Fix For: 1.16.3
>
> Attachments: sketch.pptx
>
>
> These would simply be rendered underneath the OK/Cancel button.
> One property might also show help markup, or hyperlink to reference guides
> etc.
> As a refinement (perhaps split out to separate story), allow a layout file
> (with same name( as mixin to be specified. Perhaps this might even (through
> some extension to the existing syntax) allow the parameters to be laid out
> differently, eg over multiple columns).
> ~~~
> * https://bootstrapious.com/p/bootstrap-sidebar
> * https://bootsnipp.com/tags/sidebar
> *
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
