[jira] [Created] (ISIS-2048) Update Wicket 8.1.0 -> 8.2.0
Andi Huber created ISIS-2048:
Summary: Update Wicket 8.1.0 -> 8.2.0
Key: ISIS-2048
URL: https://issues.apache.org/jira/browse/ISIS-2048
Project: Isis
Issue Type: Improvement
Components: Core: Viewer: Wicket
Reporter: Andi Huber
Assignee: Andi Huber
Fix For: 2.0.0-M2
{noformat}
Release Notes - Wicket - Version 8.2.0
** Bug
* [WICKET-4423] - Modal Window dragging failes with iframe
* [WICKET-5552] - Events to close pop-up on Modal Window are not propagated
* [WICKET-6586] - Broken JavaScript due to fix charsetName in
JavaScriptPackageResource
* [WICKET-6588] - Under Tomcat (ver. >= 8.5) BaseWebSocketBehavior can't
find session id cookie
* [WICKET-6589] - ClientInfo fails with NumberFormatException for unusual
browser versions
* [WICKET-6599] - ResponseIOException should never escape from WicketFilter
* [WICKET-6602] - AuthenticatedWebApplication login Workflow broken with
replaceSession
* [WICKET-6603] - WicketTester.destroy sometimes hangs
* [WICKET-6604] - Ajax repaint is not correctly handled when component
being repainted has an enclosure associated with it and is not a child of the
enclosure
* [WICKET-6606] - data-wicket-placeholder is invalid XHTML
* [WICKET-6607] - NoSuchMethodError when using Spring-Beans with
constructor injection in an AjaxLink#onClick
* [WICKET-6608] - Stateless page, mix of queue and add can cause unforseen
consequences
* [WICKET-6610] - Incorrect Javadoc: Refering to specific page in
Application properties file is not possible
** Improvement
* [WICKET-6435] - WicketTester should provide assertExists and
assertNotExists methods
* [WICKET-6600] - Error logging in AjaxRequestHandler is too strict
* [WICKET-6601] - Events to close pop-up on Modal Window are not propagated
from caption bar
* [WICKET-6605] - Allow AjaxFallbackButton to be stateless
** Task
* [WICKET-6594] - JavaDoc of redirectToInterceptPage in Component urges to
use redirectTo method when in a constructor
* [WICKET-6609] - Update Guice from 4.1.0 to 4.2.2
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ISIS-2039) Redesign of Configuration
[ https://issues.apache.org/jira/browse/ISIS-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16718165#comment-16718165 ] ASF subversion and git services commented on ISIS-2039: --- Commit b9b0925332d84256fc7517fdba8f04d46dff571d in isis's branch refs/heads/v2 from [~hobrom] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=b9b0925 ] ISIS-2039 minor cleanup > Redesign of Configuration > - > > Key: ISIS-2039 > URL: https://issues.apache.org/jira/browse/ISIS-2039 > Project: Isis > Issue Type: Improvement > Components: Core >Reporter: Andi Huber >Assignee: Andi Huber >Priority: Major > Fix For: 2.0.0 > > > Goals: > 1) the framework shall provide a singleton instance of IsisConfiguration, > which is an interface that provides immutable/readonly access to the config > key/value pairs > 2) the framework provides IsisConfigurationBuilder once during the > early-bootstrap phase for r/w access to the config key/value pairs > 3) first time any module requests access to IsisConfiguration, a singleton > instance IsisConfiguration is built using the builder and the builder itself > is no longer valid, meaning the framework denies any caller access to the > builder > A benefit of this design is, that it is no longer required to pass around or > hold instances of IsisConfiguration, because the framework provides a static > means to get the current life-cycle's singletons for configuration. > Side-effects ... > 1) cleanup and simplify bootstrapping code > 2) no more configuration mocking for JUnit tests, instead use new internal > Config API > 3) removal of @PostConstruct methods that take arguments > 4) removal of apache commons dependencies (really only required by the > WebServer tool) -- 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)
[jira] [Updated] (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:all-tabpanel ] Dan Haywood updated ISIS-1999: -- Description: 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 * was: 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). > 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)
[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=16716890#comment-16716890
]
Dan Haywood commented on ISIS-1999:
---
I also like the idea. It wouldn't be a change, this is instead about the
implementation of the DescribedAsFacet. I see it being implemented similar to
MustSatisfyFacet which instantiates a specification in order to potentially
invalidate.
We could therefore have:
{code}
@PropertyLayout(describedWith=FirstNameDescriber.class)
private String firstName;
{code}
where:
{code}
public static class FirstNameDescribed implements Describer {
String description(Object domainObject, String memberId);
}
{code}
probably with an optional Describer2 for i18n:
{code}
public static class FirstNameDescriber2 implements Describer2 {
TranslatableString description(Object domainObject, String memberId);
}
{code}
> 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)
