[jira] [Created] (ISIS-1722) Upgrade to Wicket 7.9.0 once available
Dan Haywood created ISIS-1722: - Summary: Upgrade to Wicket 7.9.0 once available Key: ISIS-1722 URL: https://issues.apache.org/jira/browse/ISIS-1722 Project: Isis Issue Type: Dependency upgrade Affects Versions: 1.15.0 Reporter: Dan Haywood Fix For: 1.15.1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (ISIS-1082) Documentation fixes
[ https://issues.apache.org/jira/browse/ISIS-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood closed ISIS-1082. - > Documentation fixes > --- > > Key: ISIS-1082 > URL: https://issues.apache.org/jira/browse/ISIS-1082 > Project: Isis > Issue Type: Improvement >Affects Versions: core-1.8.0 >Reporter: Dan Haywood >Priority: Minor > Fix For: 1.10.0 > > > Original text of this ticket moved to ISIS-1721, since this ticket was > incorrectly used as the target of commits for unrelated documentation fixes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1082) Documentation fixes
[
https://issues.apache.org/jira/browse/ISIS-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-1082:
--
Fix Version/s: (was: 1.16.0)
1.10.0
Reporter: Dan Haywood (was: Martin Grigorov)
Description: Original text of this ticket moved to ISIS-1721, since this
ticket was incorrectly used as the target of commits for unrelated
documentation fixes. (was: In a domain entity I wanted to use a property with
a default value:
{code}
private boolean flag = true;
// getter & setter
{code}
Surprisingly Isis re-initialized its value to 'false' after creating the
instance by using the setter.
http://isis.apache.org/more-advanced-topics/how-to-07-010-How-to-set-up-the-initial-value-of-a-property-programmatically.html
explains the behavior but maybe we should rething whether Isis should
initialize the properties at all.)
Component/s: (was: Core)
Issue Type: Improvement (was: Brainstorming)
Summary: Documentation fixes (was: Isis overrides the default values
of domain entities)
> Documentation fixes
> ---
>
> Key: ISIS-1082
> URL: https://issues.apache.org/jira/browse/ISIS-1082
> Project: Isis
> Issue Type: Improvement
>Affects Versions: core-1.8.0
>Reporter: Dan Haywood
>Priority: Minor
> Fix For: 1.10.0
>
>
> Original text of this ticket moved to ISIS-1721, since this ticket was
> incorrectly used as the target of commits for unrelated documentation fixes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (ISIS-1082) Documentation fixes
[ https://issues.apache.org/jira/browse/ISIS-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood resolved ISIS-1082. --- Resolution: Fixed > Documentation fixes > --- > > Key: ISIS-1082 > URL: https://issues.apache.org/jira/browse/ISIS-1082 > Project: Isis > Issue Type: Improvement >Affects Versions: core-1.8.0 >Reporter: Dan Haywood >Priority: Minor > Fix For: 1.10.0 > > > Original text of this ticket moved to ISIS-1721, since this ticket was > incorrectly used as the target of commits for unrelated documentation fixes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1721) Isis should optionally not override the default values of entities.
[
https://issues.apache.org/jira/browse/ISIS-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-1721:
--
Affects Version/s: 1.10.0
Fix Version/s: 1.16.0
Reporter: Martin Grigorov (was: Dan Haywood)
Description:
(recreated from ISIS-1082, which has got incorrect commits against it).
In a domain entity I wanted to use a property with a default value:
{code}
private boolean flag = true;
// getter & setter
{code}
Surprisingly Isis re-initialized its value to 'false' after creating the
instance by using the setter.
http://isis.apache.org/more-advanced-topics/how-to-07-010-How-to-set-up-the-initial-value-of-a-property-programmatically.html
explains the behavior but maybe we should rething whether Isis should
initialize the properties at all.
was:(recreated from ISIS-1082, which has got incorrect commits against it).
> Isis should optionally not override the default values of entities.
> ---
>
> Key: ISIS-1721
> URL: https://issues.apache.org/jira/browse/ISIS-1721
> Project: Isis
> Issue Type: Bug
>Affects Versions: 1.10.0
>Reporter: Martin Grigorov
>Priority: Minor
> Fix For: 1.16.0
>
>
> (recreated from ISIS-1082, which has got incorrect commits against it).
> In a domain entity I wanted to use a property with a default value:
> {code}
> private boolean flag = true;
> // getter & setter
> {code}
> Surprisingly Isis re-initialized its value to 'false' after creating the
> instance by using the setter.
> http://isis.apache.org/more-advanced-topics/how-to-07-010-How-to-set-up-the-initial-value-of-a-property-programmatically.html
> explains the behavior but maybe we should rething whether Isis should
> initialize the properties at all.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ISIS-1721) Isis should optionally not override the default values of entities.
Dan Haywood created ISIS-1721: - Summary: Isis should optionally not override the default values of entities. Key: ISIS-1721 URL: https://issues.apache.org/jira/browse/ISIS-1721 Project: Isis Issue Type: Bug Reporter: Dan Haywood Priority: Minor (recreated from ISIS-1082, which has got incorrect commits against it). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ISIS-1706) Add 'username' config parameter to email service
[ https://issues.apache.org/jira/browse/ISIS-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood resolved ISIS-1706. --- Resolution: Fixed > Add 'username' config parameter to email service > > > Key: ISIS-1706 > URL: https://issues.apache.org/jira/browse/ISIS-1706 > Project: Isis > Issue Type: Improvement > Components: Core >Reporter: Steve Cameron >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.15.1 > > Attachments: EmailServiceDefault.java > > > Currently the EmailService requires two configuration parameters: > isis.service.email.sender.address > isis.service.email.sender.password > with three optional: > isis.service.email.sender.hostname > isis.service.email.port > isis.service.email.tls.enabled > Another optional one is needed: > isis.service.email.sender.username > Currently when logging on to an email server the > isis.service.email.sender.address value is used as an account username, in > addition to also being used as the 'sent-by' email address, if you don't have > a choice as to the username this is problematic, such as with Amazon Simple > Email Service (SES). > With the additional config parameter, when present this value should override > the isis.service.email.sender.address value as the account username, when not > present the present arrangement should be used. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (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 ] Dan Haywood resolved ISIS-1708. --- Resolution: Fixed > 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 > Fix For: 1.15.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, see attachment. > grtnx -j -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1708) Broken Links according to W3C checker
[ https://issues.apache.org/jira/browse/ISIS-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169828#comment-16169828 ] ASF subversion and git services commented on ISIS-1708: --- Commit 4912a4d9367b733b461212b36d07db6a68b47ab3 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=4912a4d ] ISIS-1708: fixes some broken links > 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 > Fix For: 1.15.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, see attachment. > grtnx -j -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1698) CollectionLayout.defaultView not honored
[
https://issues.apache.org/jira/browse/ISIS-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-1698:
--
Fix Version/s: (was: 1.15.1)
2.1.0
> CollectionLayout.defaultView not honored
>
>
> Key: ISIS-1698
> URL: https://issues.apache.org/jira/browse/ISIS-1698
> Project: Isis
> Issue Type: Bug
> Components: Core
>Affects Versions: 1.15.0
>Reporter: Andi Huber
>Assignee: Dan Haywood
> Fix For: 2.1.0
>
> Attachments: ISIS-1698.png
>
>
> It seems setting the defaultView for Collections does no longer work. (Since
> release 1.15.0)
> The collection's view instead always defaults to "table", no matter if set
> via Annotation or layout.xml.
> However the 'hinting mechanism' does work. The framework remembers the last
> view as selected via user-interface . ('table, 'excel, ...')
> Steps to reproduce ...
> Take the SimpleObject demo app and test the following snipped:
> {code:java}
> @javax.inject.Inject
> SimpleObjectRepository simpleObjectRepository;
> @CollectionLayout(defaultView="hidden")
> public List getAll(){
> return simpleObjectRepository.listAll();
> }
> {code}
> The collection should default to view type 'hidden' but renders as 'table'.
> (Same applies if we try to default to 'excel', in case the excel-addon is
> available.)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ISIS-1720) Add a namedXxx() supporting method to allow actions to be renamed dynamically.
[ https://issues.apache.org/jira/browse/ISIS-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1720: -- Fix Version/s: (was: 1.15.1) 2.1.0 > Add a namedXxx() supporting method to allow actions to be renamed dynamically. > -- > > Key: ISIS-1720 > URL: https://issues.apache.org/jira/browse/ISIS-1720 > Project: Isis > Issue Type: Improvement >Affects Versions: 1.15.0 >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1706) Add 'username' config parameter to email service
[ https://issues.apache.org/jira/browse/ISIS-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169791#comment-16169791 ] ASF subversion and git services commented on ISIS-1706: --- Commit 7d06ccc50a5857ecfe95f1dedf98b8310e335783 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=7d06ccc ] ISIS-1706: adds support to use a different username than the sender address when authenticating with the Email SMTP service > Add 'username' config parameter to email service > > > Key: ISIS-1706 > URL: https://issues.apache.org/jira/browse/ISIS-1706 > Project: Isis > Issue Type: Improvement > Components: Core >Reporter: Steve Cameron >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.15.1 > > Attachments: EmailServiceDefault.java > > > Currently the EmailService requires two configuration parameters: > isis.service.email.sender.address > isis.service.email.sender.password > with three optional: > isis.service.email.sender.hostname > isis.service.email.port > isis.service.email.tls.enabled > Another optional one is needed: > isis.service.email.sender.username > Currently when logging on to an email server the > isis.service.email.sender.address value is used as an account username, in > addition to also being used as the 'sent-by' email address, if you don't have > a choice as to the username this is problematic, such as with Amazon Simple > Email Service (SES). > With the additional config parameter, when present this value should override > the isis.service.email.sender.address value as the account username, when not > present the present arrangement should be used. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1706) Add 'username' config parameter to email service
[ https://issues.apache.org/jira/browse/ISIS-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169788#comment-16169788 ] Dan Haywood commented on ISIS-1706: --- Also... I noticed this ticket in the "resolved/done" state, so almost slipped by without the change being applied. Please make sure stays in the "to do" column so I know it's there to be looked at. thx > Add 'username' config parameter to email service > > > Key: ISIS-1706 > URL: https://issues.apache.org/jira/browse/ISIS-1706 > Project: Isis > Issue Type: Improvement > Components: Core >Reporter: Steve Cameron >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.15.1 > > Attachments: EmailServiceDefault.java > > > Currently the EmailService requires two configuration parameters: > isis.service.email.sender.address > isis.service.email.sender.password > with three optional: > isis.service.email.sender.hostname > isis.service.email.port > isis.service.email.tls.enabled > Another optional one is needed: > isis.service.email.sender.username > Currently when logging on to an email server the > isis.service.email.sender.address value is used as an account username, in > addition to also being used as the 'sent-by' email address, if you don't have > a choice as to the username this is problematic, such as with Amazon Simple > Email Service (SES). > With the additional config parameter, when present this value should override > the isis.service.email.sender.address value as the account username, when not > present the present arrangement should be used. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ISIS-1706) Add 'username' config parameter to email service
[ https://issues.apache.org/jira/browse/ISIS-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood reassigned ISIS-1706: - Assignee: Dan Haywood > Add 'username' config parameter to email service > > > Key: ISIS-1706 > URL: https://issues.apache.org/jira/browse/ISIS-1706 > Project: Isis > Issue Type: Improvement > Components: Core >Reporter: Steve Cameron >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.15.1 > > Attachments: EmailServiceDefault.java > > > Currently the EmailService requires two configuration parameters: > isis.service.email.sender.address > isis.service.email.sender.password > with three optional: > isis.service.email.sender.hostname > isis.service.email.port > isis.service.email.tls.enabled > Another optional one is needed: > isis.service.email.sender.username > Currently when logging on to an email server the > isis.service.email.sender.address value is used as an account username, in > addition to also being used as the 'sent-by' email address, if you don't have > a choice as to the username this is problematic, such as with Amazon Simple > Email Service (SES). > With the additional config parameter, when present this value should override > the isis.service.email.sender.address value as the account username, when not > present the present arrangement should be used. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ISIS-1719) QueryResultsCache should be disable when running fixture scripts.
[
https://issues.apache.org/jira/browse/ISIS-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood resolved ISIS-1719.
---
Resolution: Fixed
> QueryResultsCache should be disable when running fixture scripts.
> -
>
> Key: ISIS-1719
> URL: https://issues.apache.org/jira/browse/ISIS-1719
> Project: Isis
> Issue Type: Improvement
>Affects Versions: 1.15.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Minor
> Fix For: 1.15.1
>
>
> This is currently done if invoked via the FixtureScripts menu service, but
> not automatically for integration tests.
> Suggest that this can be disabled, in case it starts breaking tests for folk.
> see (IsisSessionFactory):
> {code}
> @Programmatic
> public void constructServices() {
> ...
> //
> // installFixturesIfRequired
> //
> final FixturesInstallerFromConfiguration fixtureInstaller =
> new FixturesInstallerFromConfiguration(this);
> fixtureInstaller.installFixtures();
> ...
>
> }
> {code}
> and (in FixtureScriptsDefault):
> {code}
> public List runFixtureScript(
> final FixtureScript fixtureScript,
> @ParameterLayout(
> named = "Parameters",
> describedAs =
> "Script-specific parameters (if any). The format
> depends on the script implementation (eg key=value, CSV, JSON, XML etc)",
> multiLine = 10)
> @Parameter(optionality = Optionality.OPTIONAL)
> final String parameters) {
> try {
> eventBusService.post(new FixturesInstallingEvent(this));
> return super.runFixtureScript(fixtureScript, parameters);
> } finally {
> eventBusService.post(new FixturesInstalledEvent(this));
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ISIS-1719) QueryResultsCache should be disable when running fixture scripts.
[
https://issues.apache.org/jira/browse/ISIS-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169775#comment-16169775
]
ASF subversion and git services commented on ISIS-1719:
---
Commit bf056704a3b4d839887750a2a6073db76ad741dc in isis's branch
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=bf05670 ]
ISIS-1719: fires events while installing fixtures
(for QueryResultsCache to listen to).
> QueryResultsCache should be disable when running fixture scripts.
> -
>
> Key: ISIS-1719
> URL: https://issues.apache.org/jira/browse/ISIS-1719
> Project: Isis
> Issue Type: Improvement
>Affects Versions: 1.15.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Minor
> Fix For: 1.15.1
>
>
> This is currently done if invoked via the FixtureScripts menu service, but
> not automatically for integration tests.
> Suggest that this can be disabled, in case it starts breaking tests for folk.
> see (IsisSessionFactory):
> {code}
> @Programmatic
> public void constructServices() {
> ...
> //
> // installFixturesIfRequired
> //
> final FixturesInstallerFromConfiguration fixtureInstaller =
> new FixturesInstallerFromConfiguration(this);
> fixtureInstaller.installFixtures();
> ...
>
> }
> {code}
> and (in FixtureScriptsDefault):
> {code}
> public List runFixtureScript(
> final FixtureScript fixtureScript,
> @ParameterLayout(
> named = "Parameters",
> describedAs =
> "Script-specific parameters (if any). The format
> depends on the script implementation (eg key=value, CSV, JSON, XML etc)",
> multiLine = 10)
> @Parameter(optionality = Optionality.OPTIONAL)
> final String parameters) {
> try {
> eventBusService.post(new FixturesInstallingEvent(this));
> return super.runFixtureScript(fixtureScript, parameters);
> } finally {
> eventBusService.post(new FixturesInstalledEvent(this));
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ISIS-1706) Add 'username' config parameter to email service
[
https://issues.apache.org/jira/browse/ISIS-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169703#comment-16169703
]
Dan Haywood commented on ISIS-1706:
---
to get your fork up to current assuming you don't care about any local
changes ...
{code}
git checkout master
git fetch
git reset --hard origin/master
{code}
> Add 'username' config parameter to email service
>
>
> Key: ISIS-1706
> URL: https://issues.apache.org/jira/browse/ISIS-1706
> Project: Isis
> Issue Type: Improvement
> Components: Core
>Reporter: Steve Cameron
>Priority: Minor
> Fix For: 1.15.1
>
> Attachments: EmailServiceDefault.java
>
>
> Currently the EmailService requires two configuration parameters:
> isis.service.email.sender.address
> isis.service.email.sender.password
> with three optional:
> isis.service.email.sender.hostname
> isis.service.email.port
> isis.service.email.tls.enabled
> Another optional one is needed:
> isis.service.email.sender.username
> Currently when logging on to an email server the
> isis.service.email.sender.address value is used as an account username, in
> addition to also being used as the 'sent-by' email address, if you don't have
> a choice as to the username this is problematic, such as with Amazon Simple
> Email Service (SES).
> With the additional config parameter, when present this value should override
> the isis.service.email.sender.address value as the account username, when not
> present the present arrangement should be used.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Reopened] (ISIS-1706) Add 'username' config parameter to email service
[ https://issues.apache.org/jira/browse/ISIS-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood reopened ISIS-1706: --- > Add 'username' config parameter to email service > > > Key: ISIS-1706 > URL: https://issues.apache.org/jira/browse/ISIS-1706 > Project: Isis > Issue Type: Improvement > Components: Core >Reporter: Steve Cameron >Priority: Minor > Fix For: 1.15.1 > > Attachments: EmailServiceDefault.java > > > Currently the EmailService requires two configuration parameters: > isis.service.email.sender.address > isis.service.email.sender.password > with three optional: > isis.service.email.sender.hostname > isis.service.email.port > isis.service.email.tls.enabled > Another optional one is needed: > isis.service.email.sender.username > Currently when logging on to an email server the > isis.service.email.sender.address value is used as an account username, in > addition to also being used as the 'sent-by' email address, if you don't have > a choice as to the username this is problematic, such as with Amazon Simple > Email Service (SES). > With the additional config parameter, when present this value should override > the isis.service.email.sender.address value as the account username, when not > present the present arrangement should be used. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ISIS-1719) QueryResultsCache should be disable when running fixture scripts.
[
https://issues.apache.org/jira/browse/ISIS-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood reassigned ISIS-1719:
-
Assignee: Dan Haywood
> QueryResultsCache should be disable when running fixture scripts.
> -
>
> Key: ISIS-1719
> URL: https://issues.apache.org/jira/browse/ISIS-1719
> Project: Isis
> Issue Type: Improvement
>Affects Versions: 1.15.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Minor
> Fix For: 1.15.1
>
>
> This is currently done if invoked via the FixtureScripts menu service, but
> not automatically for integration tests.
> Suggest that this can be disabled, in case it starts breaking tests for folk.
> see (IsisSessionFactory):
> {code}
> @Programmatic
> public void constructServices() {
> ...
> //
> // installFixturesIfRequired
> //
> final FixturesInstallerFromConfiguration fixtureInstaller =
> new FixturesInstallerFromConfiguration(this);
> fixtureInstaller.installFixtures();
> ...
>
> }
> {code}
> and (in FixtureScriptsDefault):
> {code}
> public List runFixtureScript(
> final FixtureScript fixtureScript,
> @ParameterLayout(
> named = "Parameters",
> describedAs =
> "Script-specific parameters (if any). The format
> depends on the script implementation (eg key=value, CSV, JSON, XML etc)",
> multiLine = 10)
> @Parameter(optionality = Optionality.OPTIONAL)
> final String parameters) {
> try {
> eventBusService.post(new FixturesInstallingEvent(this));
> return super.runFixtureScript(fixtureScript, parameters);
> } finally {
> eventBusService.post(new FixturesInstalledEvent(this));
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (ISIS-1707) Suppress mandatory red-star on read-only properties
[ https://issues.apache.org/jira/browse/ISIS-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood resolved ISIS-1707. --- Resolution: Fixed > Suppress mandatory red-star on read-only properties > --- > > Key: ISIS-1707 > URL: https://issues.apache.org/jira/browse/ISIS-1707 > Project: Isis > Issue Type: Improvement > Components: Core: Viewer: Wicket >Affects Versions: 1.15.0 >Reporter: Steve Cameron >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.15.1 > > > Mandatory red-star indicator isn't needed when the user cannot change a > property value. > For example if the following is used: > @DomainObject(objectType = "XXX", nature = Nature.VIEW_MODEL, editing = > Editing.DISABLED) > It seems a View Model will by default have all mandatory properties ( > @Column(allowsNull="false")?), so the class level attribute 'editing = > Editing.DISABLED' is useful to suppress that. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1707) Suppress mandatory red-star on read-only properties
[
https://issues.apache.org/jira/browse/ISIS-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169701#comment-16169701
]
ASF subversion and git services commented on ISIS-1707:
---
Commit 81a7a462a44f52631019f90ddf49ad4192158ca3 in isis's branch
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=81a7a46 ]
ISIS-1707: suppresses mandatory indicator ("red star") for read-only properties.
> Suppress mandatory red-star on read-only properties
> ---
>
> Key: ISIS-1707
> URL: https://issues.apache.org/jira/browse/ISIS-1707
> Project: Isis
> Issue Type: Improvement
> Components: Core: Viewer: Wicket
>Affects Versions: 1.15.0
>Reporter: Steve Cameron
>Assignee: Dan Haywood
>Priority: Minor
> Fix For: 1.15.1
>
>
> Mandatory red-star indicator isn't needed when the user cannot change a
> property value.
> For example if the following is used:
> @DomainObject(objectType = "XXX", nature = Nature.VIEW_MODEL, editing =
> Editing.DISABLED)
> It seems a View Model will by default have all mandatory properties (
> @Column(allowsNull="false")?), so the class level attribute 'editing =
> Editing.DISABLED' is useful to suppress that.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (ISIS-1707) Suppress mandatory red-star on read-only properties
[ https://issues.apache.org/jira/browse/ISIS-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood reassigned ISIS-1707: - Assignee: Dan Haywood > Suppress mandatory red-star on read-only properties > --- > > Key: ISIS-1707 > URL: https://issues.apache.org/jira/browse/ISIS-1707 > Project: Isis > Issue Type: Improvement > Components: Core: Viewer: Wicket >Affects Versions: 1.15.0 >Reporter: Steve Cameron >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.15.1 > > > Mandatory red-star indicator isn't needed when the user cannot change a > property value. > For example if the following is used: > @DomainObject(objectType = "XXX", nature = Nature.VIEW_MODEL, editing = > Editing.DISABLED) > It seems a View Model will by default have all mandatory properties ( > @Column(allowsNull="false")?), so the class level attribute 'editing = > Editing.DISABLED' is useful to suppress that. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
