[jira] [Created] (ISIS-1761) Hiding empty fieldset + similar issues with contributed props/colls.
Dan Haywood created ISIS-1761: - Summary: Hiding empty fieldset + similar issues with contributed props/colls. Key: ISIS-1761 URL: https://issues.apache.org/jira/browse/ISIS-1761 Project: Isis Issue Type: Bug Affects Versions: 1.15.0 Reporter: Dan Haywood Fix For: 1.16.0 as per https://lists.apache.org/thread.html/b4e2d76d8da40e26df142d239eed37ca807e8694d13dd472a3858f5e@%3Cusers.isis.apache.org%3E see also ISIS-1739. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1636) Support for Java 8 Time API
[ https://issues.apache.org/jira/browse/ISIS-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-1636: - Flagged: (was: Impediment) > Support for Java 8 Time API > --- > > Key: ISIS-1636 > URL: https://issues.apache.org/jira/browse/ISIS-1636 > Project: Isis > Issue Type: Improvement > Components: Core: Viewer: Wicket >Reporter: Andi Huber >Priority: Minor > Fix For: 2.0.0 > > > ISIS should support domain object properties of type > * java.time.LocalDate > * java.time.LocalDateTime > * java.time.OffsetDateTime > Sooner or later the new Java 8 time API will conquer the developers minds and > those using ISIS will demand ISIS built-in support for these basic types. > Note: JDO support for the types listed above is already there (via plugin). > So the persistence part of the problem is solved, only the UI part is missing. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1636) Support for Java 8 Time API
[ https://issues.apache.org/jira/browse/ISIS-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber updated ISIS-1636: - Flagged: Impediment > Support for Java 8 Time API > --- > > Key: ISIS-1636 > URL: https://issues.apache.org/jira/browse/ISIS-1636 > Project: Isis > Issue Type: Improvement > Components: Core: Viewer: Wicket >Reporter: Andi Huber >Priority: Minor > Fix For: 2.0.0 > > > ISIS should support domain object properties of type > * java.time.LocalDate > * java.time.LocalDateTime > * java.time.OffsetDateTime > Sooner or later the new Java 8 time API will conquer the developers minds and > those using ISIS will demand ISIS built-in support for these basic types. > Note: JDO support for the types listed above is already there (via plugin). > So the persistence part of the problem is solved, only the UI part is missing. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ISIS-1760) Integration of Apache Isis and Ignite
Dan Haywood created ISIS-1760: - Summary: Integration of Apache Isis and Ignite Key: ISIS-1760 URL: https://issues.apache.org/jira/browse/ISIS-1760 Project: Isis Issue Type: New Feature Affects Versions: 1.15.1 Reporter: Dan Haywood Fix For: 1.16.0 as per https://lists.apache.org/thread.html/2f6a146ff2a2b623d6006ced32ad8c86c521dafe9b15af64522940a7@%3Cusers.isis.apache.org%3E example app: https://bitbucket.org/dhamapurkar/isisignitesample -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ISIS-1756) JEE Support - IsisContext requires proper lifecycling.
[ https://issues.apache.org/jira/browse/ISIS-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber reassigned ISIS-1756: Assignee: Andi Huber > JEE Support - IsisContext requires proper lifecycling. > -- > > Key: ISIS-1756 > URL: https://issues.apache.org/jira/browse/ISIS-1756 > Project: Isis > Issue Type: Improvement >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Andi Huber > Fix For: 2.0.0 > > > as per > https://lists.apache.org/thread.html/a815c6d3e50c02111d0cd3df93b70b529c18193f321e613b116119b4@%3Cdev.isis.apache.org%3E > The isis-context needs a proper lifecycling, meaning a deploy/undeploy cycle > should properly invalidate any state. (e.g meta model validation is currently > not cleared after an undeploy, in my case after calling > IsisContext.testReset()) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ISIS-1759) Always calling getXxx() and hideXxx() both decreases performance of application (?)
Dan Haywood created ISIS-1759: - Summary: Always calling getXxx() and hideXxx() both decreases performance of application (?) Key: ISIS-1759 URL: https://issues.apache.org/jira/browse/ISIS-1759 Project: Isis Issue Type: Improvement Affects Versions: 1.15.1 Reporter: Dan Haywood Fix For: 1.16.0 as per https://lists.apache.org/thread.html/6eb586e378bf239891189791b214f0a4b44e12ae4f1ddd0c49478d78@%3Cusers.isis.apache.org%3E -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ISIS-1755) JEE Support - dummy bean as workaround for CDI
[ https://issues.apache.org/jira/browse/ISIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber reassigned ISIS-1755: Assignee: Andi Huber > JEE Support - dummy bean as workaround for CDI > -- > > Key: ISIS-1755 > URL: https://issues.apache.org/jira/browse/ISIS-1755 > Project: Isis > Issue Type: Improvement >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Andi Huber > Fix For: 2.0.0 > > > as per > https://lists.apache.org/thread.html/a815c6d3e50c02111d0cd3df93b70b529c18193f321e613b116119b4@%3Cdev.isis.apache.org%3E > During JEE-Application bootstrapping the JEE container identifies a > list of Isis classes it feels responsible for, but does not know how to > instantiate; so errors are thrown. For me it was sufficient to provide a > single stateless JEE bean that states, that it produces all these > classes. As long as you deploy your Isis application including this > dummy-bean, CDI does not complain. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
***UNCHECKED*** Re: 'Where am I' feature
binaSJOi8vUV5.bin Description: PGP/MIME version identification
[jira] [Created] (ISIS-1758) cssClass() not working any more if css class definition exists on DomainObjectLayout
Dan Haywood created ISIS-1758: - Summary: cssClass() not working any more if css class definition exists on DomainObjectLayout Key: ISIS-1758 URL: https://issues.apache.org/jira/browse/ISIS-1758 Project: Isis Issue Type: Improvement Affects Versions: 1.15.1 Reporter: Dan Haywood Priority: Minor Fix For: 1.16.0 as per https://lists.apache.org/thread.html/2f228e10680b7f65a520c1bf47042ec8bba14602e61b9b56d90393b3@%3Cusers.isis.apache.org%3E -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (ISIS-383) [OUT OF SCOPE] Integrate Apache Lucene or ElasticSearch
[
https://issues.apache.org/jira/browse/ISIS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood closed ISIS-383.
Resolution: Fixed
> [OUT OF SCOPE] Integrate Apache Lucene or ElasticSearch
> ---
>
> Key: ISIS-383
> URL: https://issues.apache.org/jira/browse/ISIS-383
> Project: Isis
> Issue Type: New Feature
> Components: Core
>Affects Versions: core-1.1.0
>Reporter: Dan Haywood
> Fix For: 1.16.0
>
> Attachments: isis-lucene.zip
>
>
> Isis is most often used with its JDO integration, a fairly conventional ORM.
> Searching for existing domain objects therefore requires a query to be
> defined. But sometimes users want to just search for any object (like
> searching the web). This ticket is to integrate Isis so that its domain
> objects can be indexed by Lucene and thus provide a generic search capability.
> As of 1.10.0 this could be implemented using a subscriber:
> {code}
> @DomainService(nature=DOMAIN)
> public class LuceneSubscriber extends AbstractSubscriber {
> @Subscribe public void on(ObjectPersistingEvent ev) { ... }
> @Subscribe public void on(ObjectUpdatingEvent ev) { ... }
> @Subscribe public void on(ObjectRemovingEvent ev) { ... }
> }
> {code}
> Then one would also provide some sort of repository to query the Lucene
> datastore:
> {code}
> @DomainService(nature=DOMAIN)
> public class LuceneRepository {
> @Action(semantics=SAFE)
> List find(String text) { ... }
> }
> {code}
> There is also an attachment to this ticket, based on an earlier spike by
> Maurizio. Note that that was done before the subscribers were available.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ISIS-383) [OUT OF SCOPE] Integrate Apache Lucene or ElasticSearch
[
https://issues.apache.org/jira/browse/ISIS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-383:
-
Summary: [OUT OF SCOPE] Integrate Apache Lucene or ElasticSearch (was:
[WON'T FIX] Integrate Apache Lucene or ElasticSearch (nb: recommend this is an
isisaddon rather than built-in))
> [OUT OF SCOPE] Integrate Apache Lucene or ElasticSearch
> ---
>
> Key: ISIS-383
> URL: https://issues.apache.org/jira/browse/ISIS-383
> Project: Isis
> Issue Type: New Feature
> Components: Core
>Affects Versions: core-1.1.0
>Reporter: Dan Haywood
> Fix For: 1.16.0
>
> Attachments: isis-lucene.zip
>
>
> Isis is most often used with its JDO integration, a fairly conventional ORM.
> Searching for existing domain objects therefore requires a query to be
> defined. But sometimes users want to just search for any object (like
> searching the web). This ticket is to integrate Isis so that its domain
> objects can be indexed by Lucene and thus provide a generic search capability.
> As of 1.10.0 this could be implemented using a subscriber:
> {code}
> @DomainService(nature=DOMAIN)
> public class LuceneSubscriber extends AbstractSubscriber {
> @Subscribe public void on(ObjectPersistingEvent ev) { ... }
> @Subscribe public void on(ObjectUpdatingEvent ev) { ... }
> @Subscribe public void on(ObjectRemovingEvent ev) { ... }
> }
> {code}
> Then one would also provide some sort of repository to query the Lucene
> datastore:
> {code}
> @DomainService(nature=DOMAIN)
> public class LuceneRepository {
> @Action(semantics=SAFE)
> List find(String text) { ... }
> }
> {code}
> There is also an attachment to this ticket, based on an earlier spike by
> Maurizio. Note that that was done before the subscribers were available.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ISIS-383) [WON'T FIX] Integrate Apache Lucene or ElasticSearch (nb: recommend this is an isisaddon rather than built-in)
[
https://issues.apache.org/jira/browse/ISIS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219685#comment-16219685
]
Dan Haywood commented on ISIS-383:
--
to be implemented as part of the Incode Platform:
https://github.com/incodehq/incode-platform/issues/58
> [WON'T FIX] Integrate Apache Lucene or ElasticSearch (nb: recommend this is
> an isisaddon rather than built-in)
> --
>
> Key: ISIS-383
> URL: https://issues.apache.org/jira/browse/ISIS-383
> Project: Isis
> Issue Type: New Feature
> Components: Core
>Affects Versions: core-1.1.0
>Reporter: Dan Haywood
> Fix For: 1.16.0
>
> Attachments: isis-lucene.zip
>
>
> Isis is most often used with its JDO integration, a fairly conventional ORM.
> Searching for existing domain objects therefore requires a query to be
> defined. But sometimes users want to just search for any object (like
> searching the web). This ticket is to integrate Isis so that its domain
> objects can be indexed by Lucene and thus provide a generic search capability.
> As of 1.10.0 this could be implemented using a subscriber:
> {code}
> @DomainService(nature=DOMAIN)
> public class LuceneSubscriber extends AbstractSubscriber {
> @Subscribe public void on(ObjectPersistingEvent ev) { ... }
> @Subscribe public void on(ObjectUpdatingEvent ev) { ... }
> @Subscribe public void on(ObjectRemovingEvent ev) { ... }
> }
> {code}
> Then one would also provide some sort of repository to query the Lucene
> datastore:
> {code}
> @DomainService(nature=DOMAIN)
> public class LuceneRepository {
> @Action(semantics=SAFE)
> List find(String text) { ... }
> }
> {code}
> There is also an attachment to this ticket, based on an earlier spike by
> Maurizio. Note that that was done before the subscribers were available.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ISIS-383) [WON'T FIX] Integrate Apache Lucene or ElasticSearch (nb: recommend this is an isisaddon rather than built-in)
[
https://issues.apache.org/jira/browse/ISIS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-383:
-
Summary: [WON'T FIX] Integrate Apache Lucene or ElasticSearch (nb:
recommend this is an isisaddon rather than built-in) (was: [WON'T FIX
Integrate Apache Lucene or ElasticSearch (nb: recommend this is an isisaddon
rather than built-in))
> [WON'T FIX] Integrate Apache Lucene or ElasticSearch (nb: recommend this is
> an isisaddon rather than built-in)
> --
>
> Key: ISIS-383
> URL: https://issues.apache.org/jira/browse/ISIS-383
> Project: Isis
> Issue Type: New Feature
> Components: Core
>Affects Versions: core-1.1.0
>Reporter: Dan Haywood
> Fix For: 1.16.0
>
> Attachments: isis-lucene.zip
>
>
> Isis is most often used with its JDO integration, a fairly conventional ORM.
> Searching for existing domain objects therefore requires a query to be
> defined. But sometimes users want to just search for any object (like
> searching the web). This ticket is to integrate Isis so that its domain
> objects can be indexed by Lucene and thus provide a generic search capability.
> As of 1.10.0 this could be implemented using a subscriber:
> {code}
> @DomainService(nature=DOMAIN)
> public class LuceneSubscriber extends AbstractSubscriber {
> @Subscribe public void on(ObjectPersistingEvent ev) { ... }
> @Subscribe public void on(ObjectUpdatingEvent ev) { ... }
> @Subscribe public void on(ObjectRemovingEvent ev) { ... }
> }
> {code}
> Then one would also provide some sort of repository to query the Lucene
> datastore:
> {code}
> @DomainService(nature=DOMAIN)
> public class LuceneRepository {
> @Action(semantics=SAFE)
> List find(String text) { ... }
> }
> {code}
> There is also an attachment to this ticket, based on an earlier spike by
> Maurizio. Note that that was done before the subscribers were available.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ISIS-383) [WON'T FIX Integrate Apache Lucene or ElasticSearch (nb: recommend this is an isisaddon rather than built-in)
[
https://issues.apache.org/jira/browse/ISIS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-383:
-
Summary: [WON'T FIX Integrate Apache Lucene or ElasticSearch (nb: recommend
this is an isisaddon rather than built-in) (was: Integrate Apache Lucene or
ElasticSearch (nb: recommend this is an isisaddon rather than built-in))
> [WON'T FIX Integrate Apache Lucene or ElasticSearch (nb: recommend this is an
> isisaddon rather than built-in)
> -
>
> Key: ISIS-383
> URL: https://issues.apache.org/jira/browse/ISIS-383
> Project: Isis
> Issue Type: New Feature
> Components: Core
>Affects Versions: core-1.1.0
>Reporter: Dan Haywood
> Fix For: 1.16.0
>
> Attachments: isis-lucene.zip
>
>
> Isis is most often used with its JDO integration, a fairly conventional ORM.
> Searching for existing domain objects therefore requires a query to be
> defined. But sometimes users want to just search for any object (like
> searching the web). This ticket is to integrate Isis so that its domain
> objects can be indexed by Lucene and thus provide a generic search capability.
> As of 1.10.0 this could be implemented using a subscriber:
> {code}
> @DomainService(nature=DOMAIN)
> public class LuceneSubscriber extends AbstractSubscriber {
> @Subscribe public void on(ObjectPersistingEvent ev) { ... }
> @Subscribe public void on(ObjectUpdatingEvent ev) { ... }
> @Subscribe public void on(ObjectRemovingEvent ev) { ... }
> }
> {code}
> Then one would also provide some sort of repository to query the Lucene
> datastore:
> {code}
> @DomainService(nature=DOMAIN)
> public class LuceneRepository {
> @Action(semantics=SAFE)
> List find(String text) { ... }
> }
> {code}
> There is also an attachment to this ticket, based on an earlier spike by
> Maurizio. Note that that was done before the subscribers were available.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (ISIS-1740) New Feature: Where am I
[
https://issues.apache.org/jira/browse/ISIS-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andi Huber reassigned ISIS-1740:
Assignee: Andi Huber
> New Feature: Where am I
> ---
>
> Key: ISIS-1740
> URL: https://issues.apache.org/jira/browse/ISIS-1740
> Project: Isis
> Issue Type: New Feature
> Components: Core
>Reporter: Andi Huber
>Assignee: Andi Huber
> Fix For: 2.0.0
>
> Attachments: Clipboard01.png, Clipboard02.png, Clipboard03.png,
> Clipboard04.png
>
>
> Its common practice to display a navigation hint somewhere at top of an
> application's page or below the main menu, indicating where the user
> currently has navigated to. (Typically within a navigable tree-structure.)
> Let's call this the *WhereAmI hint*. We could integrate such a feature into
> ISIS.
> +Examples+
> [^Clipboard01.png]
> [^Clipboard02.png]
> [^Clipboard03.png]
> Note: we could optionally include the DomainObject's icons
> +Proposal+
> For any DomainObject/View currently displayed ISIS would need to know its
> corresponding
> navigable tree-structure. Let's call this the DomainObject's *WhereAmI tree*.
> All the framework needs to known to build the relevant sub-tree, is to know
> the parent node of any DomainObject/View that 'takes part' in the tree.
> We could provide this 'who is your parent' meta information similar to the
> existing 'what is your title' mechanism:
> {code:java}
> // Who is your parent? if null there is none
> public AnyDomainObjectOrView parent()
> {
> return foo;
> }
> {code}
> or
> {code:java}
> // Who is your parent? if null there is none
> @Parent
> public AnyDomainObjectOrView anyMethodName()
> {
> return foo;
> }
> {code}
> The typical layout.xml could look like this:
> {code:xml}
>
>
>
>
>
> ...
>
>
> ...
>
> {code}
> +Implementation Notes+
> # The framework needs to ensure that the chain of parent references starting
> at the current DomainObject/View is finite. (No circular or self references.)
> If it detects a circle, be nice and just stop the 'tree-up' traversal there.
> # For standalone Collection Views we could display a WhereAmI hint that
> allows back navigation to the DomainObject/View that had produced the
> collection.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (ISIS-1754) JEE Support - replace Class.forName with TCL.loadClass (+ patching DN)
[ https://issues.apache.org/jira/browse/ISIS-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Huber reassigned ISIS-1754: Assignee: Andi Huber > JEE Support - replace Class.forName with TCL.loadClass (+ patching DN) > -- > > Key: ISIS-1754 > URL: https://issues.apache.org/jira/browse/ISIS-1754 > Project: Isis > Issue Type: Improvement >Reporter: Dan Haywood >Assignee: Andi Huber > Fix For: 2.0.0 > > > as per > https://lists.apache.org/thread.html/a815c6d3e50c02111d0cd3df93b70b529c18193f321e613b116119b4@%3Cdev.isis.apache.org%3E > Class.forName(...), so we need a plug-able class-loading mechanism. > (What worked for me is > Thread.currentThread().getContextClassLoader().loadClass(...)). > Unfortunately this applies also to DataNucleus. So I had to patch their > class loading mechanism. (Sounds dramatic, but was just a single line of > code.) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Re: 'Where am I' feature
Hi Andi cc'ing dev@ on this... On Tue, 24 Oct 2017 at 21:22 Andi Huber wrote: > Hi Dan, > > I could start with work on the integration of the 'Where am I' feature > (ISIS-1740) into core. > > Cool. I've slotted the ticket into the 2.0.0 release. > With that I'd like to add some utility classes, that utilize Java 8 > features (Streams and Lamdas). Those are utilities like Reflection > Helper, Bean Utility, Weak Reference Cache, Null Safe Utilities, etc. I > would call these internal utilities, not meant to contribute to the > public API. (But I think I will put some work into javadoc completeness > and treat them like they where public API, just in case.) > > Great stuff. Do you have a designated project/package where to put these? Maybe under > org.apache.isis.applib.util? > > If this isn't intended to be public API, then it shouldn't go in isis-core-applib. Instead, I think the place to put this stuff is in isis-core-metamodel, I think, probably under the o.a.i.core.commons package. Create subpackages under there as you see fit, eg o.a.i.core.commons.streams. > I guess its Ok, if I branch this new feature off on > dev/2.0.0/ISIS-1276-dn-5-1. > > I've done more work on the dev/2.0.0/ISIS-1742-remove-deprecations branch, so I suggest you branch from there. What I'm thinking of doing is to do an "2.0.0-M1" milestone release based on that branch, which will be basically 1.15.1 release but updated to Java 8 + removed deprecations but NOT upgraded to DN 5.1. Later on an M2 milestone would merge in the DN 5.1 upgrade. (In fact, I think I might do a rebase of the ISIS-1276-dn-5-1 branch on top of ISIS-1742). > --- > > I'm also eager to help with the JEE roadmap. First we could extract > ToDos from our last conversation and organize them into Jira Issues. I > could do that if you like. First goal could be to provide an 'works out > of the box' experience for users with Isis on JEE 7+ servers. Subsequent > goals like CDI managed Domain Objects or deprecation of Rest Easy would > follow later. (The hard part to solve for the first goal is > class-loading, which also affects Data-Nucleus.) > > Great. I've gone ahead and created tickets, ISIS-1754 through ISIS-1757. I've put them into 2.0.0 release as well. Again, suggest create branches from the dev/2.0.0/ISIS-1742-remove-deprecations brac. > In Jira I'm not allowed to assign tasks to myself yet. Not sure whom to > contact, to get the permission. Had a look, seems like I had the karma to grant out permissions, so you should be set to go. Alternatively, what's the progress on > the idea of using github's issue tracking? > > The github integration simplifies applying pull requests, and it means that we push directly to github of course as well, but we've not discussed whether to leverage any of it other features. While I'm not a huge fan of JIRA (who is?), I'm not sure that there's a lot of benefit in transferring all of our backlog over to github... and we might well miss some of JIRA's features once there. Any other views on this? Cheers Dan > Cheers Andi > > > > > > > > > > >
[jira] [Updated] (ISIS-1739) DisableXxx() method is always called while hideXxx() returns true
[
https://issues.apache.org/jira/browse/ISIS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-1739:
--
I think that Erik also reported (on mailing list?) that he's seeing getXxx()
being called even when hideXxx() returns true.
> DisableXxx() method is always called while hideXxx() returns true
> -
>
> Key: ISIS-1739
> URL: https://issues.apache.org/jira/browse/ISIS-1739
> Project: Isis
> Issue Type: Bug
> Components: Core: Viewer: Wicket
>Affects Versions: 1.15.0
>Reporter: Erik de Hair
> Fix For: 1.16.0
>
>
> I have a contributed action that must be rendered on the first parameter's
> page (OrderAbstract) on top of the page but shouldn't be rendered on the
> other parameter's page.
> public Blob downloadDealerQuotationAsPdf(final OrderAbstract order, final
> Contact recipient){
> Blob quotation = ...
> return quotation;
> }
> public String disableDownloadDealerQuotationAsPdf(final OrderAbstract order,
> final Contact recipient){
> if(order.getOrderLines().isEmpty()){
> return "No orderline added yet");
> }
> return null;
> }
> public boolean hideDownloadDealerQuotationAsPdf(final OrderAbstract order,
> final Contact recipient) {
> return order == null || !order.getCompany().hasDealer();
> }
> As far as I can see the disableXXX method wouldn't be called in Apache Isis
> 1.14.x when the Contact page was rendered, because this was suppressed by the
> fact that the action was already hidden by the hiddenXXX method. But now
> they're both called but when rendering the
> Contact page it will fail due to a NPE on the first line of the disableXXX
> method so I have to change this method to
> public String disableDownloadDealerQuotationAsPdf(final OrderAbstract order,
> final Contact recipient){
> if(order == null){
> return "Some dummy reason";
> }
> // actual disable conditions
> ...
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ISIS-1741) ConcurrentModificationException during startup when launching packaged webapp with jetty
[ https://issues.apache.org/jira/browse/ISIS-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1741: -- Fix Version/s: 1.16.0 > ConcurrentModificationException during startup when launching packaged webapp > with jetty > > > Key: ISIS-1741 > URL: https://issues.apache.org/jira/browse/ISIS-1741 > Project: Isis > Issue Type: Bug >Affects Versions: 1.15.0 >Reporter: Vladimir Nisevic > Fix For: 1.16.0 > > Attachments: 1741_applog.txt > > > I get this exception (see attachment [^1741_applog.txt]) only when launching > the version packaged with jetty, exception doesn't occur when launching > within IDE (IntelliJ). > Maybe any idea? Not sure how could I reproduce it with simpleapp -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-814) [WON'T FIX] Provide a better way to handle polymorphic relationships, eg implement a "PolymorphicNavigator service"
[ https://issues.apache.org/jira/browse/ISIS-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-814: - Fix Version/s: (was: 3.0.0) 1.16.0 Summary: [WON'T FIX] Provide a better way to handle polymorphic relationships, eg implement a "PolymorphicNavigator service" (was: Provide a better way to handle polymorphic relationships, eg implement a "PolymorphicNavigator service") Support for this in the Incode platform (lib-poly module, or just as a a design pattern). > [WON'T FIX] Provide a better way to handle polymorphic relationships, eg > implement a "PolymorphicNavigator service" > --- > > Key: ISIS-814 > URL: https://issues.apache.org/jira/browse/ISIS-814 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: core-1.5.0 >Reporter: Dan Haywood >Priority: Minor > Fix For: 1.16.0 > > > We'd like to be able to decouple modules (eg from Estatio or wherever) and > make them reusable for others. > For example, Estatio has "CommunicationChannel", where its owner is of type > CommunicationChannelOwner. We currently use DataNucleus' support for > interface mappings, but (because we use annotations) this requires us to list > the fully qualified class names of the implementations in the > CommunicationChannel; hardly reusable code. > Naked Objects MVC has a service called the PolymorphicNavigator [1], a > mechanism to handle relationships between different Entity Framework > contexts, typically via an interface. > The PolymorphicNavigator requires that all implementations use an int (or > long) as their primary key. It then stores the relationship in a separate > table, qualified by the object type. This is a bit like DataNucleus' > "identity" strategy for mapping interfaces [2], except that: > - two columns are used, not one (for object type, and object PK > - the link is held separately from the rest of the object's data. > [1] > https://github.com/NakedObjectsGroup/NakedObjectsFramework/blob/4e860789ad115a38cd3348ceb5c0b141fb0e0d7b/Programming%20Model/NakedObjects.Helpers/Services/PolymorphicNavigator.cs > [2] http://www.datanucleus.org/products/datanucleus/jdo/orm/interfaces.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (ISIS-814) [WON'T FIX] Provide a better way to handle polymorphic relationships, eg implement a "PolymorphicNavigator service"
[ https://issues.apache.org/jira/browse/ISIS-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood closed ISIS-814. Resolution: Fixed > [WON'T FIX] Provide a better way to handle polymorphic relationships, eg > implement a "PolymorphicNavigator service" > --- > > Key: ISIS-814 > URL: https://issues.apache.org/jira/browse/ISIS-814 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: core-1.5.0 >Reporter: Dan Haywood >Priority: Minor > Fix For: 1.16.0 > > > We'd like to be able to decouple modules (eg from Estatio or wherever) and > make them reusable for others. > For example, Estatio has "CommunicationChannel", where its owner is of type > CommunicationChannelOwner. We currently use DataNucleus' support for > interface mappings, but (because we use annotations) this requires us to list > the fully qualified class names of the implementations in the > CommunicationChannel; hardly reusable code. > Naked Objects MVC has a service called the PolymorphicNavigator [1], a > mechanism to handle relationships between different Entity Framework > contexts, typically via an interface. > The PolymorphicNavigator requires that all implementations use an int (or > long) as their primary key. It then stores the relationship in a separate > table, qualified by the object type. This is a bit like DataNucleus' > "identity" strategy for mapping interfaces [2], except that: > - two columns are used, not one (for object type, and object PK > - the link is held separately from the rest of the object's data. > [1] > https://github.com/NakedObjectsGroup/NakedObjectsFramework/blob/4e860789ad115a38cd3348ceb5c0b141fb0e0d7b/Programming%20Model/NakedObjects.Helpers/Services/PolymorphicNavigator.cs > [2] http://www.datanucleus.org/products/datanucleus/jdo/orm/interfaces.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1739) DisableXxx() method is always called while hideXxx() returns true
[
https://issues.apache.org/jira/browse/ISIS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-1739:
--
Fix Version/s: 1.16.0
> DisableXxx() method is always called while hideXxx() returns true
> -
>
> Key: ISIS-1739
> URL: https://issues.apache.org/jira/browse/ISIS-1739
> Project: Isis
> Issue Type: Bug
> Components: Core: Viewer: Wicket
>Affects Versions: 1.15.0
>Reporter: Erik de Hair
> Fix For: 1.16.0
>
>
> I have a contributed action that must be rendered on the first parameter's
> page (OrderAbstract) on top of the page but shouldn't be rendered on the
> other parameter's page.
> public Blob downloadDealerQuotationAsPdf(final OrderAbstract order, final
> Contact recipient){
> Blob quotation = ...
> return quotation;
> }
> public String disableDownloadDealerQuotationAsPdf(final OrderAbstract order,
> final Contact recipient){
> if(order.getOrderLines().isEmpty()){
> return "No orderline added yet");
> }
> return null;
> }
> public boolean hideDownloadDealerQuotationAsPdf(final OrderAbstract order,
> final Contact recipient) {
> return order == null || !order.getCompany().hasDealer();
> }
> As far as I can see the disableXXX method wouldn't be called in Apache Isis
> 1.14.x when the Contact page was rendered, because this was suppressed by the
> fact that the action was already hidden by the hiddenXXX method. But now
> they're both called but when rendering the
> Contact page it will fail due to a NPE on the first line of the disableXXX
> method so I have to change this method to
> public String disableDownloadDealerQuotationAsPdf(final OrderAbstract order,
> final Contact recipient){
> if(order == null){
> return "Some dummy reason";
> }
> // actual disable conditions
> ...
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ISIS-743) Remove the concept of transient objects and of @NotPersistable; instead we have view models.
[ https://issues.apache.org/jira/browse/ISIS-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-743: - Fix Version/s: (was: 3.0.0) 2.2.0 > Remove the concept of transient objects and of @NotPersistable; instead we > have view models. > > > Key: ISIS-743 > URL: https://issues.apache.org/jira/browse/ISIS-743 > Project: Isis > Issue Type: Wish > Components: Core >Reporter: Dan Haywood > Fix For: 2.2.0 > > Attachments: Design-1.PNG, Design-2.PNG > > > For discussion; but think that view models supercede our earlier ideas of > transient objects etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-790) Replace DN Blob/Clob Mappings with Blob/Clob converters
[ https://issues.apache.org/jira/browse/ISIS-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-790: - Fix Version/s: (was: 3.0.0) 2.1.0 > Replace DN Blob/Clob Mappings with Blob/Clob converters > --- > > Key: ISIS-790 > URL: https://issues.apache.org/jira/browse/ISIS-790 > Project: Isis > Issue Type: Improvement > Components: Core: Objectstore: JDO >Affects Versions: objectstore-jdo-1.4.1 >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.1.0 > > > See ISIS-788 for background on the Blob/Clob converters. > ISIS-789 (upgrade to DN 4.0) is a prereq (meaning ISIS-568 for JDK is also). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-724) [WON'T FIX] Support HTML file format as a way of specifying dynamic layout facets (similar to .layout.json files currently)
[ https://issues.apache.org/jira/browse/ISIS-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-724: - Fix Version/s: (was: 3.0.0) 1.16.0 Summary: [WON'T FIX] Support HTML file format as a way of specifying dynamic layout facets (similar to .layout.json files currently) (was: Support HTML file format as a way of specifying dynamic layout facets (similar to .layout.json files currently)) the .layout.xml files we have are good enough, I think. > [WON'T FIX] Support HTML file format as a way of specifying dynamic layout > facets (similar to .layout.json files currently) > --- > > Key: ISIS-724 > URL: https://issues.apache.org/jira/browse/ISIS-724 > Project: Isis > Issue Type: New Feature > Components: Core >Reporter: Dan Haywood > Fix For: 1.16.0 > > > The HTML could have some supporting CSS so that the layout file when viewed > in a browser, would also provide some sort of indication as to the rendered > UI. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-722) For 2.0.0, should we get rid of the identity map, and simply "new up" PojoAdapters around pojos as-and-when?
[ https://issues.apache.org/jira/browse/ISIS-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-722: - Fix Version/s: (was: 3.0.0) 2.2.0 > For 2.0.0, should we get rid of the identity map, and simply "new up" > PojoAdapters around pojos as-and-when? > > > Key: ISIS-722 > URL: https://issues.apache.org/jira/browse/ISIS-722 > Project: Isis > Issue Type: Question > Components: Core >Reporter: Dan Haywood > Fix For: 2.2.0 > > > If we did this, then the next obvious improvement would be to use a javassist > to proxy every pojo, so that the pojo itself could provide its own > (single-use) PojoAadapter. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (ISIS-724) [WON'T FIX] Support HTML file format as a way of specifying dynamic layout facets (similar to .layout.json files currently)
[ https://issues.apache.org/jira/browse/ISIS-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood closed ISIS-724. Resolution: Fixed > [WON'T FIX] Support HTML file format as a way of specifying dynamic layout > facets (similar to .layout.json files currently) > --- > > Key: ISIS-724 > URL: https://issues.apache.org/jira/browse/ISIS-724 > Project: Isis > Issue Type: New Feature > Components: Core >Reporter: Dan Haywood > Fix For: 1.16.0 > > > The HTML could have some supporting CSS so that the layout file when viewed > in a browser, would also provide some sort of indication as to the rendered > UI. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ISIS-678) When invoke action in Wicket viewer, prefer redirect-after-post to be to a deep link.
[ https://issues.apache.org/jira/browse/ISIS-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood reassigned ISIS-678: Assignee: (was: Dan Haywood) > When invoke action in Wicket viewer, prefer redirect-after-post to be to a > deep link. > - > > Key: ISIS-678 > URL: https://issues.apache.org/jira/browse/ISIS-678 > Project: Isis > Issue Type: Improvement > Components: Core: Viewer: Wicket >Affects Versions: viewer-wicket-1.3.1 >Reporter: Dan Haywood >Priority: Minor > Fix For: 3.0.0 > > > .. so that the user can easily copy the URL out of the browser address bar. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-383) Integrate Apache Lucene or ElasticSearch (nb: recommend this is an isisaddon rather than built-in)
[
https://issues.apache.org/jira/browse/ISIS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-383:
-
Fix Version/s: (was: 3.0.0)
1.16.0
> Integrate Apache Lucene or ElasticSearch (nb: recommend this is an isisaddon
> rather than built-in)
> --
>
> Key: ISIS-383
> URL: https://issues.apache.org/jira/browse/ISIS-383
> Project: Isis
> Issue Type: New Feature
> Components: Core
>Affects Versions: core-1.1.0
>Reporter: Dan Haywood
> Fix For: 1.16.0
>
> Attachments: isis-lucene.zip
>
>
> Isis is most often used with its JDO integration, a fairly conventional ORM.
> Searching for existing domain objects therefore requires a query to be
> defined. But sometimes users want to just search for any object (like
> searching the web). This ticket is to integrate Isis so that its domain
> objects can be indexed by Lucene and thus provide a generic search capability.
> As of 1.10.0 this could be implemented using a subscriber:
> {code}
> @DomainService(nature=DOMAIN)
> public class LuceneSubscriber extends AbstractSubscriber {
> @Subscribe public void on(ObjectPersistingEvent ev) { ... }
> @Subscribe public void on(ObjectUpdatingEvent ev) { ... }
> @Subscribe public void on(ObjectRemovingEvent ev) { ... }
> }
> {code}
> Then one would also provide some sort of repository to query the Lucene
> datastore:
> {code}
> @DomainService(nature=DOMAIN)
> public class LuceneRepository {
> @Action(semantics=SAFE)
> List find(String text) { ... }
> }
> {code}
> There is also an attachment to this ticket, based on an earlier spike by
> Maurizio. Note that that was done before the subscribers were available.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ISIS-399) LogonFixture does not work in wicket viewer
[ https://issues.apache.org/jira/browse/ISIS-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-399: - Fix Version/s: (was: 3.0.0) 2.0.0 > LogonFixture does not work in wicket viewer > --- > > Key: ISIS-399 > URL: https://issues.apache.org/jira/browse/ISIS-399 > Project: Isis > Issue Type: Bug > Components: Core: Viewer: Wicket >Affects Versions: viewer-wicket-1.1.0 >Reporter: Christian Steinebach >Priority: Minor > Labels: login > Fix For: 2.0.0 > > > Adding LogonAsSvenFixture to isis.properties does not log on Sven. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ISIS-1757) JEE Support - container-provided connection pools
Dan Haywood created ISIS-1757: - Summary: JEE Support - container-provided connection pools Key: ISIS-1757 URL: https://issues.apache.org/jira/browse/ISIS-1757 Project: Isis Issue Type: Improvement Affects Versions: 1.15.1 Reporter: Dan Haywood Fix For: 2.0.0 as per https://lists.apache.org/thread.html/a815c6d3e50c02111d0cd3df93b70b529c18193f321e613b116119b4@%3Cdev.isis.apache.org%3E I use JEE container provided connection pools and bind them to Isis/JDO via JNDI. I'm not an expert on this, but I believe this works totally sane. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1756) JEE Support - IsisContext requires proper lifecycling.
[ https://issues.apache.org/jira/browse/ISIS-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1756: -- Affects Version/s: 1.15.1 Fix Version/s: 2.0.0 Description: as per https://lists.apache.org/thread.html/a815c6d3e50c02111d0cd3df93b70b529c18193f321e613b116119b4@%3Cdev.isis.apache.org%3E The isis-context needs a proper lifecycling, meaning a deploy/undeploy cycle should properly invalidate any state. (e.g meta model validation is currently not cleared after an undeploy, in my case after calling IsisContext.testReset()) was:as per https://lists.apache.org/thread.html/a815c6d3e50c02111d0cd3df93b70b529c18193f321e613b116119b4@%3Cdev.isis.apache.org%3E Summary: JEE Support - IsisContext requires proper lifecycling. (was: JEE Support - ) > JEE Support - IsisContext requires proper lifecycling. > -- > > Key: ISIS-1756 > URL: https://issues.apache.org/jira/browse/ISIS-1756 > Project: Isis > Issue Type: Improvement >Affects Versions: 1.15.1 >Reporter: Dan Haywood > Fix For: 2.0.0 > > > as per > https://lists.apache.org/thread.html/a815c6d3e50c02111d0cd3df93b70b529c18193f321e613b116119b4@%3Cdev.isis.apache.org%3E > The isis-context needs a proper lifecycling, meaning a deploy/undeploy cycle > should properly invalidate any state. (e.g meta model validation is currently > not cleared after an undeploy, in my case after calling > IsisContext.testReset()) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ISIS-1756) JEE Support -
Dan Haywood created ISIS-1756: - Summary: JEE Support - Key: ISIS-1756 URL: https://issues.apache.org/jira/browse/ISIS-1756 Project: Isis Issue Type: Improvement Reporter: Dan Haywood as per https://lists.apache.org/thread.html/a815c6d3e50c02111d0cd3df93b70b529c18193f321e613b116119b4@%3Cdev.isis.apache.org%3E -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ISIS-1755) JEE Support - dummy bean as workaround for CDI
Dan Haywood created ISIS-1755: - Summary: JEE Support - dummy bean as workaround for CDI Key: ISIS-1755 URL: https://issues.apache.org/jira/browse/ISIS-1755 Project: Isis Issue Type: Improvement Affects Versions: 1.15.1 Reporter: Dan Haywood Fix For: 2.0.0 as per https://lists.apache.org/thread.html/a815c6d3e50c02111d0cd3df93b70b529c18193f321e613b116119b4@%3Cdev.isis.apache.org%3E During JEE-Application bootstrapping the JEE container identifies a list of Isis classes it feels responsible for, but does not know how to instantiate; so errors are thrown. For me it was sufficient to provide a single stateless JEE bean that states, that it produces all these classes. As long as you deploy your Isis application including this dummy-bean, CDI does not complain. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ISIS-1754) JEE Support - replace Class.forName with TCL.loadClass (+ patching DN)
Dan Haywood created ISIS-1754: - Summary: JEE Support - replace Class.forName with TCL.loadClass (+ patching DN) Key: ISIS-1754 URL: https://issues.apache.org/jira/browse/ISIS-1754 Project: Isis Issue Type: Improvement Reporter: Dan Haywood Fix For: 2.0.0 as per https://lists.apache.org/thread.html/a815c6d3e50c02111d0cd3df93b70b529c18193f321e613b116119b4@%3Cdev.isis.apache.org%3E Class.forName(...), so we need a plug-able class-loading mechanism. (What worked for me is Thread.currentThread().getContextClassLoader().loadClass(...)). Unfortunately this applies also to DataNucleus. So I had to patch their class loading mechanism. (Sounds dramatic, but was just a single line of code.) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1740) New Feature: Where am I
[
https://issues.apache.org/jira/browse/ISIS-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-1740:
--
Fix Version/s: (was: 2.2.0)
2.0.0
> New Feature: Where am I
> ---
>
> Key: ISIS-1740
> URL: https://issues.apache.org/jira/browse/ISIS-1740
> Project: Isis
> Issue Type: New Feature
> Components: Core
>Reporter: Andi Huber
> Fix For: 2.0.0
>
> Attachments: Clipboard01.png, Clipboard02.png, Clipboard03.png,
> Clipboard04.png
>
>
> Its common practice to display a navigation hint somewhere at top of an
> application's page or below the main menu, indicating where the user
> currently has navigated to. (Typically within a navigable tree-structure.)
> Let's call this the *WhereAmI hint*. We could integrate such a feature into
> ISIS.
> +Examples+
> [^Clipboard01.png]
> [^Clipboard02.png]
> [^Clipboard03.png]
> Note: we could optionally include the DomainObject's icons
> +Proposal+
> For any DomainObject/View currently displayed ISIS would need to know its
> corresponding
> navigable tree-structure. Let's call this the DomainObject's *WhereAmI tree*.
> All the framework needs to known to build the relevant sub-tree, is to know
> the parent node of any DomainObject/View that 'takes part' in the tree.
> We could provide this 'who is your parent' meta information similar to the
> existing 'what is your title' mechanism:
> {code:java}
> // Who is your parent? if null there is none
> public AnyDomainObjectOrView parent()
> {
> return foo;
> }
> {code}
> or
> {code:java}
> // Who is your parent? if null there is none
> @Parent
> public AnyDomainObjectOrView anyMethodName()
> {
> return foo;
> }
> {code}
> The typical layout.xml could look like this:
> {code:xml}
>
>
>
>
>
> ...
>
>
> ...
>
> {code}
> +Implementation Notes+
> # The framework needs to ensure that the chain of parent references starting
> at the current DomainObject/View is finite. (No circular or self references.)
> If it detects a circle, be nice and just stop the 'tree-up' traversal there.
> # For standalone Collection Views we could display a WhereAmI hint that
> allows back navigation to the DomainObject/View that had produced the
> collection.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ISIS-1683) Move org.apache.isis.applib.services.timestamp.Timestampable to mixins.timestamp
[ https://issues.apache.org/jira/browse/ISIS-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1683: -- Fix Version/s: (was: 2.2.0) 2.0.0 do as part of ISIS-1742 > Move org.apache.isis.applib.services.timestamp.Timestampable to > mixins.timestamp > > > Key: ISIS-1683 > URL: https://issues.apache.org/jira/browse/ISIS-1683 > Project: Isis > Issue Type: Improvement >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1684) Remove org.apache.isis.applib.fixtures.InstallableFixture, replace with FixtureScripts
[ https://issues.apache.org/jira/browse/ISIS-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1684: -- Fix Version/s: (was: 2.2.0) 2.0.0 > Remove org.apache.isis.applib.fixtures.InstallableFixture, replace with > FixtureScripts > -- > > Key: ISIS-1684 > URL: https://issues.apache.org/jira/browse/ISIS-1684 > Project: Isis > Issue Type: Improvement >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1682) Move org.apache.isis.applib.services.layout.Object_downloadLayoutXml mixins out of services.layout and into mixins.layout
[ https://issues.apache.org/jira/browse/ISIS-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1682: -- Fix Version/s: (was: 2.2.0) 2.0.0 do as part of ISIS-1742 > Move org.apache.isis.applib.services.layout.Object_downloadLayoutXml mixins > out of services.layout and into mixins.layout > - > > Key: ISIS-1682 > URL: https://issues.apache.org/jira/browse/ISIS-1682 > Project: Isis > Issue Type: Improvement >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ISIS-1681) Move wrapper factory events (eg org.apache.isis.applib.events.AccessEvent) to subpackage of services.wrapper
[ https://issues.apache.org/jira/browse/ISIS-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood reassigned ISIS-1681: - Assignee: Dan Haywood > Move wrapper factory events (eg org.apache.isis.applib.events.AccessEvent) to > subpackage of services.wrapper > > > Key: ISIS-1681 > URL: https://issues.apache.org/jira/browse/ISIS-1681 > Project: Isis > Issue Type: Improvement >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1681) Move wrapper factory events (eg org.apache.isis.applib.events.AccessEvent) to subpackage of services.wrapper
[ https://issues.apache.org/jira/browse/ISIS-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1681: -- Fix Version/s: (was: 2.2.0) 2.0.0 done as part of ISIS-1742 > Move wrapper factory events (eg org.apache.isis.applib.events.AccessEvent) to > subpackage of services.wrapper > > > Key: ISIS-1681 > URL: https://issues.apache.org/jira/browse/ISIS-1681 > Project: Isis > Issue Type: Improvement >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1679) Move org.apache.isis.applib.services.dto.Dto to org.apache.isis.applib.mixins
[ https://issues.apache.org/jira/browse/ISIS-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1679: -- Fix Version/s: (was: 2.2.0) 2.0.0 do as part of ISIS-1742 > Move org.apache.isis.applib.services.dto.Dto to org.apache.isis.applib.mixins > - > > Key: ISIS-1679 > URL: https://issues.apache.org/jira/browse/ISIS-1679 > Project: Isis > Issue Type: Improvement >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1678) Remove org.apache.isis.applib.clock.Clock, replace with org.apache.isis.applib.services.clock.ClockService
[ https://issues.apache.org/jira/browse/ISIS-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1678: -- Fix Version/s: (was: 2.2.0) 2.0.0 > Remove org.apache.isis.applib.clock.Clock, replace with > org.apache.isis.applib.services.clock.ClockService > -- > > Key: ISIS-1678 > URL: https://issues.apache.org/jira/browse/ISIS-1678 > Project: Isis > Issue Type: Improvement >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1680) Move event classes (eg org.apache.isis.applib.services.eventbus.AbstractDomainEvent) out of services.eventbus and into applib.events (subpackages thereof)
[ https://issues.apache.org/jira/browse/ISIS-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1680: -- Fix Version/s: (was: 2.2.0) 2.0.0 do as part of ISIS-1742 > Move event classes (eg > org.apache.isis.applib.services.eventbus.AbstractDomainEvent) out of > services.eventbus and into applib.events (subpackages thereof) > -- > > Key: ISIS-1680 > URL: https://issues.apache.org/jira/browse/ISIS-1680 > Project: Isis > Issue Type: Improvement >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.0.0 > > > use subpackages: > * events.domain > * events.ui > * events.lifecycle > nb: there is already an events package, but will be moved, see ISIS-1681 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1677) Move org.apache.isis.applib.conmap.ContentMappingService to org.apache.isis.applib.services.conmap (subpackage of services)
[ https://issues.apache.org/jira/browse/ISIS-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219577#comment-16219577 ] Dan Haywood commented on ISIS-1677: --- done as part of ISIS-1742 > Move org.apache.isis.applib.conmap.ContentMappingService to > org.apache.isis.applib.services.conmap (subpackage of services) > --- > > Key: ISIS-1677 > URL: https://issues.apache.org/jira/browse/ISIS-1677 > Project: Isis > Issue Type: Improvement >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ISIS-1677) Move org.apache.isis.applib.conmap.ContentMappingService to org.apache.isis.applib.services.conmap (subpackage of services)
[ https://issues.apache.org/jira/browse/ISIS-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood reassigned ISIS-1677: - Assignee: Dan Haywood > Move org.apache.isis.applib.conmap.ContentMappingService to > org.apache.isis.applib.services.conmap (subpackage of services) > --- > > Key: ISIS-1677 > URL: https://issues.apache.org/jira/browse/ISIS-1677 > Project: Isis > Issue Type: Improvement >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1530) Introduce @CollectionLayout(title=SHOW|HIDE, ...) similarly for @ActionLayout and @DomainObjectLayout
[ https://issues.apache.org/jira/browse/ISIS-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1530: -- Fix Version/s: (was: 2.2.0) 2.3.0 > Introduce @CollectionLayout(title=SHOW|HIDE, ...) similarly for @ActionLayout > and @DomainObjectLayout > - > > Key: ISIS-1530 > URL: https://issues.apache.org/jira/browse/ISIS-1530 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.13.1 >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.3.0 > > > Introduce @CollectionLayout(title=SHOW|HIDE, ...) for parented collections, > and @ActionLayout(titleInCollection=SHOW|HIDE, ...) for actions returning > collections (ignored otherwise). Could also have > @DomainObjectLayout(titleInCollection=SHOW|HIDE, ...) as a fallback -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1500) ReplayService, to directly execute a previously persisted command
[ https://issues.apache.org/jira/browse/ISIS-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1500: -- Fix Version/s: (was: 2.2.0) 2.1.0 > ReplayService, to directly execute a previously persisted command > - > > Key: ISIS-1500 > URL: https://issues.apache.org/jira/browse/ISIS-1500 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.13.0 >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.1.0 > > > perhaps using something like this... > ... https://gist.github.com/danhaywood/5b3a106ee7c06a53cc33d76f88a04c75 > would need to decide: > (a) is this to act on Command (in which case CommandJdo is impl), or > (b) should this perhaps act on CommandDto? > (c) does it just create a new command/interaction, or somehow correlated? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1677) Move org.apache.isis.applib.conmap.ContentMappingService to org.apache.isis.applib.services.conmap (subpackage of services)
[ https://issues.apache.org/jira/browse/ISIS-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1677: -- Fix Version/s: (was: 2.2.0) 2.0.0 > Move org.apache.isis.applib.conmap.ContentMappingService to > org.apache.isis.applib.services.conmap (subpackage of services) > --- > > Key: ISIS-1677 > URL: https://issues.apache.org/jira/browse/ISIS-1677 > Project: Isis > Issue Type: Improvement >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1636) Support for Java 8 Time API
[ https://issues.apache.org/jira/browse/ISIS-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1636: -- Fix Version/s: (was: 2.2.0) 2.0.0 > Support for Java 8 Time API > --- > > Key: ISIS-1636 > URL: https://issues.apache.org/jira/browse/ISIS-1636 > Project: Isis > Issue Type: Improvement > Components: Core: Viewer: Wicket >Reporter: Andi Huber >Priority: Minor > Fix For: 2.0.0 > > > ISIS should support domain object properties of type > * java.time.LocalDate > * java.time.LocalDateTime > * java.time.OffsetDateTime > Sooner or later the new Java 8 time API will conquer the developers minds and > those using ISIS will demand ISIS built-in support for these basic types. > Note: JDO support for the types listed above is already there (via plugin). > So the persistence part of the problem is solved, only the UI part is missing. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1742) Remove deprecated annotations, methods etc.
[ https://issues.apache.org/jira/browse/ISIS-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1742: -- Fix Version/s: (was: 2.2.0) 2.0.0 > Remove deprecated annotations, methods etc. > --- > > Key: ISIS-1742 > URL: https://issues.apache.org/jira/browse/ISIS-1742 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1736) ConfigurationServiceDefault is inconsistent
[
https://issues.apache.org/jira/browse/ISIS-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-1736:
--
Summary: ConfigurationServiceDefault is inconsistent (was:
ConfigurationServiceDefault has issue)
> ConfigurationServiceDefault is inconsistent
> ---
>
> Key: ISIS-1736
> URL: https://issues.apache.org/jira/browse/ISIS-1736
> Project: Isis
> Issue Type: Bug
> Components: Core
>Affects Versions: 1.15.0
>Reporter: Steve Cameron
>Priority: Critical
> Fix For: 2.0.0
>
>
> This class is confusing, it has its own properties Map which it uses for some
> methods and then defers to an injected ConfigurationServiceInternal
> reference for others.
> I am using it in a fixture and it will not find a property using
> getProperty(String) which is using ConfigurationServiceInternal reference but
> will find it if I use getProperties() and loop through the entries returned
> //doesn't find key
> String xml =
> configurationService.getProperty("au.com.vuse.oneid.fixtures.companyinputfile");
> //does find key
> for (ConfigurationProperty str : configurationService.allProperties()) {
> if (str.getKey().equals("au.com.vuse.oneid.fixtures.companyinputfile"))
> xml = str.getValue();
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ISIS-1702) Infer @Programmatic on methods within @DomainService(nature=DOMAIN)
[ https://issues.apache.org/jira/browse/ISIS-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1702: -- Fix Version/s: (was: 2.0.0) 2.2.0 > Infer @Programmatic on methods within @DomainService(nature=DOMAIN) > --- > > Key: ISIS-1702 > URL: https://issues.apache.org/jira/browse/ISIS-1702 > Project: Isis > Issue Type: Improvement >Affects Versions: 1.15.0 >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.2.0 > > > to remove some boilerplate -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ISIS-1632) Support meta annotations for @Property/@Collection/@Action + @XxxLayout
[ https://issues.apache.org/jira/browse/ISIS-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood reassigned ISIS-1632: - Assignee: Dan Haywood > Support meta annotations for @Property/@Collection/@Action + @XxxLayout > --- > > Key: ISIS-1632 > URL: https://issues.apache.org/jira/browse/ISIS-1632 > Project: Isis > Issue Type: New Feature >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1748) Update HelloWorld & Simpleapp archetype to run under Eclipse
[ https://issues.apache.org/jira/browse/ISIS-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1748: -- Description: add in 1.8 1.8 and also the webserver reference (as per intellij)... maybe an additional mavendeps for this? also https://lists.apache.org/thread.html/1dcb00ab4a36522d113e9294d8f679be88d111c5aa24f20769020fac@%3Cusers.isis.apache.org%3E and https://lists.apache.org/thread.html/9f33738c59472e0e6ea47749e31b3650974bf01a78b84572cfca7620@%3Cusers.isis.apache.org%3E was: add in 1.8 1.8 and also the webserver reference (as per intellij)... maybe an additional mavendeps for this? > Update HelloWorld & Simpleapp archetype to run under Eclipse > > > Key: ISIS-1748 > URL: https://issues.apache.org/jira/browse/ISIS-1748 > Project: Isis > Issue Type: Bug >Affects Versions: 1.15.1 >Reporter: Dan Haywood > Fix For: 1.16.0 > > > add in > 1.8 > 1.8 > and also the webserver reference (as per intellij)... maybe an additional > mavendeps for this? > also > https://lists.apache.org/thread.html/1dcb00ab4a36522d113e9294d8f679be88d111c5aa24f20769020fac@%3Cusers.isis.apache.org%3E > and > https://lists.apache.org/thread.html/9f33738c59472e0e6ea47749e31b3650974bf01a78b84572cfca7620@%3Cusers.isis.apache.org%3E -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1747) Update docs, hints-n-tips for view models
[
https://issues.apache.org/jira/browse/ISIS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-1747:
--
Fix Version/s: (was: 2.0.0)
1.16.0
> Update docs, hints-n-tips for view models
> -
>
> Key: ISIS-1747
> URL: https://issues.apache.org/jira/browse/ISIS-1747
> Project: Isis
> Issue Type: Improvement
>Affects Versions: 1.15.1
>Reporter: Dan Haywood
>Priority: Minor
> Fix For: 1.16.0
>
>
> see https://github.com/incodehq/incode-platform/issues/10
> ~
> here's the text that has been removed
> ## Demo App: Highlighting Current
> As a by-the-by, the demo app has one further "trick up its sleeve".
> If you run the app you'll notice that the currently selected `DemoObject` is
> highlighted in the left-hand table of the `HomePageViewModel`.
> This is accomplished by having the view model collaborate with a subscribing
> domain service that configures a CSS class.
> We start by ensuring that the `DemoObject` emits an event for its CSS class:
> .DemoObject.java
> java
> @DomainObjectLayout(
> ...
> cssClassUiEvent = DemoObject.CssClassUiEvent.class
> )
> public class DemoObject ... {
> public static class CssClassUiEvent
> extends
> org.apache.isis.applib.services.eventbus.CssClassUiEvent {}
> ...
> }
>
> Next, we define the domain service to act as the subscriber.
> Since it will be interact
> .HomePageViewModel.java
> java
> public class HomePageViewModel ... {
> @DomainService(nature = NatureOfService.DOMAIN)
> public static class CssHighlighter extends AbstractSubscriber {
> @EventHandler
> @Subscribe
> public void on(DemoObject.CssClassUiEvent ev) {
> if(getContext() == null) {
> return;
> }
> if(ev.getSource() == getContext().getSelected()) { // <1>
> ev.setCssClass("selected");
> }
> }
> private HomePageViewModel getContext() {// <2>
> return (HomePageViewModel) scratchpad.get("context");
> }
> void setContext(final HomePageViewModel homePageViewModel) {
> scratchpad.put("context", homePageViewModel);
> }
> @Inject
> Scratchpad scratchpad; // <3>
> }
> }
>
> <1> If the domain object is the currently selected then set the CSS class
> <2> Provide methods to set and get the current `HomePageViewModel` (acting as
> the context)
> <3> Store the context using the `Scratchpad` domain service (request-scoped
> so thread-safe).
> The `HomePageViewModel` is responsible for setting itself as the context for
> the domain service:
> .HomePageViewModel.java
> java
> public class HomePageViewModel ... {
> ...
> public TranslatableString title() {
> cssHighlighter.setContext(this);// <1>
> ...
> }
> ...
> @javax.inject.Inject
> CssHighlighter cssHighlighter;
> }
>
> <1> set the context on the domain service
> Finally we just need some CSS, in the `application.css` file:
> .application.css
> css
> .selected {
> font-style: italic;
> font-weight: bolder;
> }
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ISIS-1746) Provide a default implementation of UserProfileService so that don't need special case logic in each viewer.
[ https://issues.apache.org/jira/browse/ISIS-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1746: -- Fix Version/s: (was: 2.0.0) 1.16.0 > Provide a default implementation of UserProfileService so that don't need > special case logic in each viewer. > > > Key: ISIS-1746 > URL: https://issues.apache.org/jira/browse/ISIS-1746 > Project: Isis > Issue Type: Improvement >Affects Versions: 1.15.1 >Reporter: Dan Haywood > Fix For: 1.16.0 > > > currently don't have a default impl; the docs say: > If the method returns null or throws an exception then the framework will > default to using the current user name. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1745) isis maven plugin (validate) swallows NPEs from DN.
[
https://issues.apache.org/jira/browse/ISIS-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-1745:
--
Fix Version/s: (was: 2.0.0)
1.16.0
> isis maven plugin (validate) swallows NPEs from DN.
> ---
>
> Key: ISIS-1745
> URL: https://issues.apache.org/jira/browse/ISIS-1745
> Project: Isis
> Issue Type: Improvement
>Reporter: Dan Haywood
> Fix For: 1.16.0
>
>
> To reproduce:
> due to an error in DN annotations, running mvn validate plugin just gave a
> very minimal exception:
> {code}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 18.576 s
> [INFO] Finished at: 2017-10-11T14:53:44+01:00
> [INFO] Final Memory: 206M/710M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.isis.tool:isis-maven-plugin:1.15.0.20170915-1224:validate
> (default) on project estatio-app: Execution default of goal
> org.apache.isis.tool:isis-maven-plugin:1.15.0.20170915-1224:validate failed:
> java.lang.NullPointerException -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> {code}
> running with -X indicated the problem was in DN annotations somewhere:
> {code}
> [ERROR] Failed to execute goal
> org.apache.isis.tool:isis-maven-plugin:1.15.0.20170915-1224:validate
> (default) on project estatio-app: Execution default of goal
> org.apache.isis.tool:isis-maven-plugin:1.15.0.20170915-1224:validate failed:
> java.lang.NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.isis.tool:isis-maven-plugin:1.15.0.20170915-1224:validate
> (default) on project estatio-app: Execution default of goal
> org.apache.isis.tool:isis-maven-plugin:1.15.0.20170915-1224:validate failed:
> java.lang.NullPointerException
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default of goal
> org.apache.isis.tool:isis-maven-plugin:1.15.0.20170915-1224:validate failed:
> java.lang.NullPointerException
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> Caused by: org.datanucleus.exceptions.NucleusException:
> java.lang.NullPointerException
> at
> org.datanucleus.store.rdbms.RDBMSStoreManager$ClassAdder.run(RDBMSStoreManager.java:2930)
> at
> org.datanucleus.store.rdbms.AbstractSchemaTransaction.execute(AbstractSchemaTransaction.java:119)
> at
> org.datanucleus.store.
[jira] [Updated] (ISIS-1749) Allow domain object nature of XXX_ENTITY to be specified for JAXB view models
[ https://issues.apache.org/jira/browse/ISIS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1749: -- Fix Version/s: (was: 2.0.0) 1.16.0 > Allow domain object nature of XXX_ENTITY to be specified for JAXB view models > - > > Key: ISIS-1749 > URL: https://issues.apache.org/jira/browse/ISIS-1749 > Project: Isis > Issue Type: Bug >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Priority: Minor > Fix For: 1.16.0 > > > as per > https://lists.apache.org/thread.html/0f731129a8975e793eefe16ac66cb0fc02849beab3f4db4daccefc4d@%3Cusers.isis.apache.org%3E -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ISIS-1753) Remove support for guava event bus implementation, make axon mandatory.
Dan Haywood created ISIS-1753: - Summary: Remove support for guava event bus implementation, make axon mandatory. Key: ISIS-1753 URL: https://issues.apache.org/jira/browse/ISIS-1753 Project: Isis Issue Type: Improvement Affects Versions: 1.15.1 Reporter: Dan Haywood Fix For: 2.0.0 Because Axon does not queue dispatching, whereas guava doesn't allow event bus calls to be nested. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1730) Invoking an action button which was rendered enabled but which is actually disabled at point of invocation throws stacktrace.
[ https://issues.apache.org/jira/browse/ISIS-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1730: -- Fix Version/s: (was: 2.0.0) 1.16.0 > Invoking an action button which was rendered enabled but which is actually > disabled at point of invocation throws stacktrace. > - > > Key: ISIS-1730 > URL: https://issues.apache.org/jira/browse/ISIS-1730 > Project: Isis > Issue Type: Bug > Components: Core: Viewer: Wicket >Affects Versions: 1.15.0 >Reporter: Dan Haywood >Priority: Minor > Fix For: 1.16.0 > > > For example, if the domain object is rendered and then some other user > changes its state such that an action is no longer available. > The framework *does* correctly re-check the state of the action, but if now > found to be disabled then we get a stack trace rather than - say - a toast > pop-up with the reason that the action can no longer be invoked. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1729) Auditer Service probably shouldn't submit records for an object that is [new] -> [deleted]
[
https://issues.apache.org/jira/browse/ISIS-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-1729:
--
Fix Version/s: (was: 2.0.0)
1.16.0
> Auditer Service probably shouldn't submit records for an object that is [new]
> -> [deleted]
> ---
>
> Key: ISIS-1729
> URL: https://issues.apache.org/jira/browse/ISIS-1729
> Project: Isis
> Issue Type: Improvement
>Affects Versions: 1.15.0
>Reporter: Dan Haywood
>Priority: Minor
> Fix For: 1.16.0
>
>
> ie is created but then deleted in the same xactn.
> eg
> {code}
> 16:07:18,365 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0:
> payment.PaymentApprovalStateTransition:294 by estatio-admin, transitionType:
> [NEW] -> [DELETED]
> 16:07:18,365 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0:
> payment.PaymentApprovalStateTransition:294 by estatio-admin, task: [NEW] ->
> [DELETED]
> 16:07:18,366 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0:
> payment.PaymentApprovalStateTransition:294 by estatio-admin, createdOn: [NEW]
> -> [DELETED]
> 16:07:18,367 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0:
> payment.PaymentApprovalStateTransition:294 by estatio-admin, paymentBatch:
> [NEW] -> [DELETED]
> 16:07:18,367 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0:
> payment.PaymentApprovalStateTransition:294 by estatio-admin, fromState: [NEW]
> -> [DELETED]
> 16:07:18,368 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0:
> payment.PaymentApprovalStateTransition:294 by estatio-admin, toState: [NEW]
> -> [DELETED]
> 16:07:18,370 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0:
> payment.PaymentApprovalStateTransition:294 by estatio-admin, completed: [NEW]
> -> [DELETED]
> 16:07:18,370 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0:
> payment.PaymentApprovalStateTransition:294 by estatio-admin, completedBy:
> [NEW] -> [DELETED]
> 16:07:18,371 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0:
> payment.PaymentApprovalStateTransition:294 by estatio-admin, completedOn:
> [NEW] -> [DELETED]
> 16:07:18,372 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0:
> payment.PaymentApprovalStateTransition:294 by estatio-admin, comment: [NEW]
> -> [DELETED]
> 16:07:18,372 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0: payment.PaymentBatch:128 by
> estatio-admin, debtorBankAccount: [NEW] -> [DELETED]
> 16:07:18,373 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0: payment.PaymentBatch:128 by
> estatio-admin, createdOn: [NEW] -> [DELETED]
> 16:07:18,374 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0: payment.PaymentBatch:128 by
> estatio-admin, requestedExecutionDate: [NEW] -> [DELETED]
> 16:07:18,375 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0: payment.PaymentBatch:128 by
> estatio-admin, approvalState: [NEW] -> [DELETED]
> 16:07:18,375 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0:
> payment.PaymentApprovalStateTransition:295 by estatio-admin, transitionType:
> [NEW] -> [DELETED]
> 16:07:18,376 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0:
> payment.PaymentApprovalStateTransition:295 by estatio-admin, task: [NEW] ->
> [DELETED]
> 16:07:18,377 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0:
> payment.PaymentApprovalStateTransition:295 by estatio-admin, createdOn: [NEW]
> -> [DELETED]
> 16:07:18,377 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0:
> payment.PaymentApprovalStateTransition:295 by estatio-admin, paymentBatch:
> [NEW] -> [DELETED]
> 16:07:18,378 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0:
> payment.PaymentApprovalStateTransition:295 by estatio-admin, fromState: [NEW]
> -> [DELETED]
> 16:07:18,379 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0:
> payment.PaymentApprovalStateTransition:295 by estatio-admin, toState: [NEW]
> -> [DELETED]
> 16:07:18,379 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0:
> payment.PaymentApprovalStateTransition:295 by estatio-admin, completed: [NEW]
> -> [DELETED]
> 16:07:18,380 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0:
> payment.PaymentApprovalStateTransition:295 by estatio-admin, completedBy:
> [NEW] -> [DELETED]
> 16:07:18,381 [AuditerServiceLogging ]
> 376bb280-73e6-490e-a6a3-b4ff95063229,0:
> payment.PaymentA
[jira] [Updated] (ISIS-1714) AppManifestAbstract#withConfigurationProperty overwrites value set by -D system property.
[ https://issues.apache.org/jira/browse/ISIS-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1714: -- Fix Version/s: (was: 2.0.0) 1.16.0 > AppManifestAbstract#withConfigurationProperty overwrites value set by -D > system property. > - > > Key: ISIS-1714 > URL: https://issues.apache.org/jira/browse/ISIS-1714 > Project: Isis > Issue Type: Bug >Affects Versions: 1.15.0 >Reporter: Dan Haywood >Priority: Minor > Fix For: 1.16.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1700) Enhance ObjectContracts#compare to allow different types of objects to be compared.
[ https://issues.apache.org/jira/browse/ISIS-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1700: -- Fix Version/s: (was: 2.0.0) 1.16.0 > Enhance ObjectContracts#compare to allow different types of objects to be > compared. > --- > > Key: ISIS-1700 > URL: https://issues.apache.org/jira/browse/ISIS-1700 > Project: Isis > Issue Type: Improvement >Affects Versions: 1.15.0 >Reporter: Dan Haywood >Priority: Minor > Fix For: 1.16.0 > > > eg in Estatio, when sorting Task#object column through the UI. > See Estatio codebase for a fix (ObjectContracts2) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1710) AppManifestAbstract#withAdditionalServices replaces rather than appends.
[ https://issues.apache.org/jira/browse/ISIS-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1710: -- Fix Version/s: (was: 2.0.0) 1.16.0 > AppManifestAbstract#withAdditionalServices replaces rather than appends. > > > Key: ISIS-1710 > URL: https://issues.apache.org/jira/browse/ISIS-1710 > Project: Isis > Issue Type: Bug >Affects Versions: 1.15.0 >Reporter: Dan Haywood >Priority: Minor > Fix For: 1.16.0 > > > Unlike withAdditionalModules, that appends. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1663) Metamodel validatoor to check: any method annotated with @Property, @Collection or @Action should be public.
[ https://issues.apache.org/jira/browse/ISIS-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1663: -- Summary: Metamodel validatoor to check: any method annotated with @Property, @Collection or @Action should be public. (was: Any method annotated with @Property, @Collection or @Action should be public.) > Metamodel validatoor to check: any method annotated with @Property, > @Collection or @Action should be public. > > > Key: ISIS-1663 > URL: https://issues.apache.org/jira/browse/ISIS-1663 > Project: Isis > Issue Type: Improvement >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1645) Integrate Kryo as an alternative technology for view models
[ https://issues.apache.org/jira/browse/ISIS-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1645: -- Summary: Integrate Kryo as an alternative technology for view models (was: Integrate Kyro as an alternative technology for view models) > Integrate Kryo 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: 2.2.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-1656) Flush auditing/publishing etc to end of the ACTION phase, rather than end of RENDER phase.
[ https://issues.apache.org/jira/browse/ISIS-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1656: -- Fix Version/s: (was: 2.0.0) 2.1.0 > Flush auditing/publishing etc to end of the ACTION phase, rather than end of > RENDER phase. > -- > > Key: ISIS-1656 > URL: https://issues.apache.org/jira/browse/ISIS-1656 > Project: Isis > Issue Type: Improvement > Components: Core: Viewer: Wicket >Affects Versions: 1.14.0 >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.1.0 > > > cf ISIS=1655, whereby we can only flush QueryResultsCache and not the other > two transaction-scoped services. > I think we should probably bring the hook for the auditing etc forward to the > beginning of the RENDER phase, ie using the same hook that we have installed > TargetRespondListenerToResetQueryResultCache class. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1645) Integrate Kryo as an alternative technology for view models
[ https://issues.apache.org/jira/browse/ISIS-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1645: -- Fix Version/s: (was: 2.0.0) 2.2.0 > Integrate Kryo 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: 2.2.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-1599) "Set" interface does not work as an action parameter's collection type
[
https://issues.apache.org/jira/browse/ISIS-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-1599:
--
Fix Version/s: (was: 2.0.0)
2.2.0
> "Set" interface does not work as an action parameter's collection type
> ---
>
> Key: ISIS-1599
> URL: https://issues.apache.org/jira/browse/ISIS-1599
> Project: Isis
> Issue Type: Bug
> Components: Core
>Affects Versions: 1.14.0
>Reporter: Tadas Giniotis
>Priority: Minor
> Fix For: 2.2.0
>
>
> When using a Set as a parameter for an action -> it throws an
> exception when using that action. The same works correctly when using
> List.
> {quote}
> ...
> java.lang.IllegalArgumentException
> argument type mismatch
> sun.reflect.NativeMethodAccessorImpl#invoke0(null:-2)
> sun.reflect.NativeMethodAccessorImpl#invoke(null:-1)
> sun.reflect.DelegatingMethodAccessorImpl#invoke(null:-1)
> java.lang.reflect.Method#invoke(null:-1)
> org.apache.isis.core.metamodel.facets.actions.action.invocation.ActionInvocationFacetForDomainEventAbstract#invokeMethodElseFromCache(ActionInvocationFacetForDomainEventAbstract.java:408)
> org.apache.isis.core.metamodel.facets.actions.action.invocation.ActionInvocationFacetForDomainEventAbstract$2#execute(ActionInvocationFacetForDomainEventAbstract.java:262)
> org.apache.isis.core.metamodel.facets.actions.action.invocation.ActionInvocationFacetForDomainEventAbstract$2#execute(ActionInvocationFacetForDomainEventAbstract.java:223)
> org.apache.isis.applib.services.iactn.Interaction#executeInternal(Interaction.java:173)
> org.apache.isis.applib.services.iactn.Interaction#execute(Interaction.java:143)
>
> ...
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ISIS-1563) Remove support in Memento (internal class) for transient (JDO) entities
[ https://issues.apache.org/jira/browse/ISIS-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1563: -- Fix Version/s: (was: 2.0.0) 2.2.0 > Remove support in Memento (internal class) for transient (JDO) entities > --- > > Key: ISIS-1563 > URL: https://issues.apache.org/jira/browse/ISIS-1563 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: 1.13.2 >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.2.0 > > > This is a legacy from days gone by, but there is no longer any needed to > handle this. Instead, just fail-fast if attempt to create a Memento for a > domain entity that is not yet persistent. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1530) Introduce @CollectionLayout(title=SHOW|HIDE, ...) similarly for @ActionLayout and @DomainObjectLayout
[ https://issues.apache.org/jira/browse/ISIS-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1530: -- Fix Version/s: (was: 2.0.0) 2.2.0 > Introduce @CollectionLayout(title=SHOW|HIDE, ...) similarly for @ActionLayout > and @DomainObjectLayout > - > > Key: ISIS-1530 > URL: https://issues.apache.org/jira/browse/ISIS-1530 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.13.1 >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.2.0 > > > Introduce @CollectionLayout(title=SHOW|HIDE, ...) for parented collections, > and @ActionLayout(titleInCollection=SHOW|HIDE, ...) for actions returning > collections (ignored otherwise). Could also have > @DomainObjectLayout(titleInCollection=SHOW|HIDE, ...) as a fallback -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1539) Incorporate isisaddons' command module as part of Isis core.
[ https://issues.apache.org/jira/browse/ISIS-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1539: -- Fix Version/s: (was: 2.0.0) 3.0.0 Not sure if this is a good idea, actually. Kicking it down the path for now. > Incorporate isisaddons' command module as part of Isis core. > > > Key: ISIS-1539 > URL: https://issues.apache.org/jira/browse/ISIS-1539 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.13.1 >Reporter: Dan Haywood > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1489) Rename @Property(notPersisted=...) to @Property(notAudited=...)
[ https://issues.apache.org/jira/browse/ISIS-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1489: -- Summary: Rename @Property(notPersisted=...) to @Property(notAudited=...) (was: Deprecate @Property(notPersisted=...) and replace with @Property(notAudited=...)) > Rename @Property(notPersisted=...) to @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 >Priority: Minor > Fix For: 2.0.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.4.14#64029)
[jira] [Updated] (ISIS-1479) DataNucleus data type mapping for streams (to support direct upload of large BLOBs)
[ https://issues.apache.org/jira/browse/ISIS-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1479: -- Fix Version/s: (was: 2.0.0) 2.1.0 > DataNucleus data type mapping for streams (to support direct upload of large > BLOBs) > --- > > Key: ISIS-1479 > URL: https://issues.apache.org/jira/browse/ISIS-1479 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.13.0 >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.1.0 > > > from http://markmail.org/message/64xcc7twcxdrhfqj > > With respect to the storage of the BLOBs themselves, I don't think (at > > least I couldn't find) any datatype mapping to be able to map from a stream > > (obtained from ServletInputStream) into a JDO entity, ie to avoid the > > creation of the BLOB in-memory. If it *were* possible, then I don't think > > Isis would care; just map the property as @Programmatic and Isis would > > ignore it. Perhaps Andy might be able to chip in on this? > java.io.File is currently the only java field type with a mapping that is > streamable. See > http://www.datanucleus.org/products/accessplatform_5_0/jdo/types.html#Other_Types > Somebody could take existing code used for that type and contribute a mapping > for some other java type. > https://github.com/datanucleus/datanucleus-rdbms/blob/master/src/main/java/org/datanucleus/store/rdbms/mapping/datastore/BinaryStreamRDBMSMapping.java -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1488) Blobs and Clobs should be automatically ignored for auditing (also ISIS-1489)
[ https://issues.apache.org/jira/browse/ISIS-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1488: -- Summary: Blobs and Clobs should be automatically ignored for auditing (also ISIS-1489) (was: Blobs and Clobs should be automatically ignored for auditing.) > Blobs and Clobs should be automatically ignored for auditing (also ISIS-1489) > - > > Key: ISIS-1488 > URL: https://issues.apache.org/jira/browse/ISIS-1488 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: 1.13.0 >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.0.0 > > > At the moment the work-around is to annotate with > @Property(notPersisted=true). > See also ISIS-1489 re: the naming of this attribute. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1271) Implement a DataNucleus NamingProvider for Isis apps in order to remove some boilerplate.
[ https://issues.apache.org/jira/browse/ISIS-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1271: -- Fix Version/s: (was: 2.0.0) 2.1.0 > Implement a DataNucleus NamingProvider for Isis apps in order to remove some > boilerplate. > - > > Key: ISIS-1271 > URL: https://issues.apache.org/jira/browse/ISIS-1271 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.10.0 >Reporter: Dan Haywood > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-849) Extend DataNucleus integration to also support the JPA API.
[ https://issues.apache.org/jira/browse/ISIS-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-849: - Fix Version/s: (was: 2.0.0) 2.1.0 > Extend DataNucleus integration to also support the JPA API. > --- > > Key: ISIS-849 > URL: https://issues.apache.org/jira/browse/ISIS-849 > Project: Isis > Issue Type: New Feature > Components: Core: Objectstore: JDO >Affects Versions: core-1.6.0 >Reporter: Dan Haywood > Fix For: 2.1.0 > > > Timebox this; if it turns out to take too long, then punt -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1294) Support Spring.Data like repositories with automatic implemenation of methods such as findByName or findByStartDateAndStatus
[ https://issues.apache.org/jira/browse/ISIS-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1294: -- Fix Version/s: (was: 2.0.0) 2.1.0 > Support Spring.Data like repositories with automatic implemenation of methods > such as findByName or findByStartDateAndStatus > > > Key: ISIS-1294 > URL: https://issues.apache.org/jira/browse/ISIS-1294 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.11.0 >Reporter: Dan Haywood > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1728) Rework helloworld and simpleapp to use typesafe queries.
[ https://issues.apache.org/jira/browse/ISIS-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1728: -- Fix Version/s: (was: 2.0.0) 1.16.0 > Rework helloworld and simpleapp to use typesafe queries. > > > Key: ISIS-1728 > URL: https://issues.apache.org/jira/browse/ISIS-1728 > Project: Isis > Issue Type: Improvement >Affects Versions: 1.15.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.16.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1750) SQL Exception when invoke action (inline prompt) not handled correctly in UI
[
https://issues.apache.org/jira/browse/ISIS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-1750:
--
Fix Version/s: (was: 2.0.0)
1.16.0
> SQL Exception when invoke action (inline prompt) not handled correctly in UI
>
>
> Key: ISIS-1750
> URL: https://issues.apache.org/jira/browse/ISIS-1750
> Project: Isis
> Issue Type: Bug
> Components: Core: Viewer: Wicket
>Affects Versions: 1.15.1
>Reporter: Dan Haywood
> Fix For: 1.16.0
>
>
> Invoked an action that threw SQL exception due to DB constraint being hit.
> reproduce:
> * github shaId: ca2923908b4f2c3f07b088c79e698bdd849fb48d,
> * bitbucket shaId: 3df4e10b5d3f8f584ffb7bb468ebc2c337d659ea
> using org.estatio.app.EstatioEcpAppManifestWithDemoFixture
> http://localhost:8080/wicket/entity/orders.OrderItem:2
> editCharge : WORKS -> MARKETING
> What I see is that the prompt doesn't change when hit OK (this is a single
> autoComplete parameter), and in the browser we see a Javascript error, and
> the following stacktrace server-side:
> {code}
> 14:09:37,954 [TitleFacetViaTitleMethod ] title failure
> javax.jdo.JDODataStoreException: Update of object
> "org.estatio.capex.dom.order.OrderItem@a0ac5fc" using statement "UPDATE
> "dbo"."OrderItem" SET "chargeId"=?, "version"=? WHERE "id"=?" failed :
> java.sql.SQLIntegrityConstraintViolationException: integrity constraint
> violation: unique constraint or index violation; "OrderItem_order_charge_UNQ"
> table: "OrderItem"
> at org.hsqldb.jdbc.JDBCUtil.sqlException(Unknown Source)
> at org.hsqldb.jdbc.JDBCUtil.sqlException(Unknown Source)
> at org.hsqldb.jdbc.JDBCPreparedStatement.fetchResult(Unknown Source)
> at org.hsqldb.jdbc.JDBCPreparedStatement.executeUpdate(Unknown Source)
> at
> com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeUpdate(NewProxyPreparedStatement.java:105)
> at
> org.datanucleus.store.rdbms.ParamLoggingPreparedStatement.executeUpdate(ParamLoggingPreparedStatement.java:393)
> at
> org.datanucleus.store.rdbms.SQLController.executeStatementUpdate(SQLController.java:431)
> at
> org.datanucleus.store.rdbms.request.UpdateRequest.execute(UpdateRequest.java:395)
> at
> org.datanucleus.store.rdbms.RDBMSPersistenceHandler.updateObjectInTable(RDBMSPersistenceHandler.java:409)
> at
> org.datanucleus.store.rdbms.RDBMSPersistenceHandler.updateObject(RDBMSPersistenceHandler.java:383)
> at
> org.datanucleus.state.StateManagerImpl.flush(StateManagerImpl.java:4585)
> at org.datanucleus.flush.FlushOrdered.execute(FlushOrdered.java:106)
> at
> org.datanucleus.ExecutionContextImpl.flushInternal(ExecutionContextImpl.java:4054)
> at org.datanucleus.store.query.Query.prepareDatastore(Query.java:1647)
> at org.datanucleus.store.query.Query.executeQuery(Query.java:1832)
> at org.datanucleus.store.query.Query.executeWithMap(Query.java:1762)
> at org.datanucleus.api.jdo.JDOQuery.executeWithMap(JDOQuery.java:346)
> at
> org.apache.isis.objectstore.jdo.datanucleus.persistence.queries.PersistenceQueryFindUsingApplibQueryProcessor.getResults(PersistenceQueryFindUsingApplibQueryProcessor.java:117)
> at
> org.apache.isis.objectstore.jdo.datanucleus.persistence.queries.PersistenceQueryFindUsingApplibQueryProcessor.process(PersistenceQueryFindUsingApplibQueryProcessor.java:57)
> at
> org.apache.isis.objectstore.jdo.datanucleus.persistence.queries.PersistenceQueryFindUsingApplibQueryProcessor.process(PersistenceQueryFindUsingApplibQueryProcessor.java:41)
> at
> org.apache.isis.core.runtime.system.persistence.PersistenceSession.processPersistenceQuery(PersistenceSession.java:606)
> at
> org.apache.isis.core.runtime.system.persistence.PersistenceSession.access$000(PersistenceSession.java:147)
> at
> org.apache.isis.core.runtime.system.persistence.PersistenceSession$1.execute(PersistenceSession.java:567)
> at
> org.apache.isis.core.runtime.system.persistence.PersistenceSession$1.execute(PersistenceSession.java:564)
> at
> org.apache.isis.core.runtime.system.transaction.IsisTransactionManager.executeWithinTransaction(IsisTransactionManager.java:188)
> at
> org.apache.isis.core.runtime.system.transaction.IsisTransactionManager.executeWithinTransaction(IsisTransactionManager.java:178)
> at
> org.apache.isis.core.runtime.system.persistence.PersistenceSession.findInstancesInTransaction(PersistenceSession.java:563)
> at
> org.apache.isis.core.runtime.system.persistence.PersistenceSession.allMatchingQuery(PersistenceSession.java:530)
> at
> org.apache.isis.core.runtime.services.persistsession.PersistenceSessionServiceInternalDefault.allMatchingQuery(Persisten
[jira] [Updated] (ISIS-1752) Extend RO viewer, return a menu.layout.xml resource
[ https://issues.apache.org/jira/browse/ISIS-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1752: -- Fix Version/s: (was: 2.0.0) 1.16.0 > Extend RO viewer, return a menu.layout.xml resource > --- > > Key: ISIS-1752 > URL: https://issues.apache.org/jira/browse/ISIS-1752 > Project: Isis > Issue Type: New Feature > Components: Core: Viewer: RestfulObjects >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 1.16.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1748) Update HelloWorld & Simpleapp archetype to run under Eclipse
[ https://issues.apache.org/jira/browse/ISIS-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1748: -- Fix Version/s: (was: 2.0.0) 1.16.0 > Update HelloWorld & Simpleapp archetype to run under Eclipse > > > Key: ISIS-1748 > URL: https://issues.apache.org/jira/browse/ISIS-1748 > Project: Isis > Issue Type: Bug >Affects Versions: 1.15.1 >Reporter: Dan Haywood > Fix For: 1.16.0 > > > add in > 1.8 > 1.8 > and also the webserver reference (as per intellij)... maybe an additional > mavendeps for this? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1500) ReplayService, to directly execute a previously persisted command
[ https://issues.apache.org/jira/browse/ISIS-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1500: -- Fix Version/s: (was: 2.0.0) 2.1.0 > ReplayService, to directly execute a previously persisted command > - > > Key: ISIS-1500 > URL: https://issues.apache.org/jira/browse/ISIS-1500 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.13.0 >Reporter: Dan Haywood >Priority: Minor > Fix For: 2.1.0 > > > perhaps using something like this... > ... https://gist.github.com/danhaywood/5b3a106ee7c06a53cc33d76f88a04c75 > would need to decide: > (a) is this to act on Command (in which case CommandJdo is impl), or > (b) should this perhaps act on CommandDto? > (c) does it just create a new command/interaction, or somehow correlated? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1465) Release activities for 1.16.0
[ https://issues.apache.org/jira/browse/ISIS-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1465: -- Fix Version/s: (was: 2.0.0) 1.16.0 > Release activities for 1.16.0 > - > > Key: ISIS-1465 > URL: https://issues.apache.org/jira/browse/ISIS-1465 > Project: Isis > Issue Type: Task > Components: Core >Affects Versions: 1.15.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.16.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1752) Extend RO viewer, return a menu.layout.xml resource
[ https://issues.apache.org/jira/browse/ISIS-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219183#comment-16219183 ] ASF subversion and git services commented on ISIS-1752: --- Commit 1b9db57f9ad8529b0b18db3eb0ee8fa4c297cbb0 in isis's branch refs/heads/master from [~danhaywood] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=1b9db57 ] ISIS-1752: removes unused import > Extend RO viewer, return a menu.layout.xml resource > --- > > Key: ISIS-1752 > URL: https://issues.apache.org/jira/browse/ISIS-1752 > Project: Isis > Issue Type: New Feature > Components: Core: Viewer: RestfulObjects >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 1.16.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1744) Update DataNucleus to the latest version
[ https://issues.apache.org/jira/browse/ISIS-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Sverdlov updated ISIS-1744: -- Fix Version/s: 1.16.0 > Update DataNucleus to the latest version > > > Key: ISIS-1744 > URL: https://issues.apache.org/jira/browse/ISIS-1744 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: 1.15.1 >Reporter: Sergey Sverdlov > Fix For: 1.16.0 > > > Please update dependencies to DataNucleus to the latest available versions: > org.datanucleus:datanucleus-api-jdo ...4.1.1 -> 5.1.3 > org.datanucleus:datanucleus-core .. 4.1.7 -> 5.1.3 > org.datanucleus:datanucleus-jdo-query ...4.0.5 -> 5.0.2 > org.datanucleus:datanucleus-jodatime 4.1.0-release -> > 5.1.0-release > org.datanucleus:datanucleus-rdbms 4.1.9 -> 5.1.3 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ISIS-1744) Update DataNucleus to the latest version
[ https://issues.apache.org/jira/browse/ISIS-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Sverdlov updated ISIS-1744: -- Description: Please update dependencies to DataNucleus to the latest available versions: org.datanucleus:datanucleus-api-jdo ...4.1.1 -> 5.1.3 org.datanucleus:datanucleus-core .. 4.1.7 -> 5.1.3 org.datanucleus:datanucleus-jdo-query ...4.0.5 -> 5.0.2 org.datanucleus:datanucleus-jodatime 4.1.0-release -> 5.1.0-release org.datanucleus:datanucleus-rdbms 4.1.9 -> 5.1.3 was: Please update dependencies to DataNucleus to the latest available versions: org.datanucleus:datanucleus-api-jdo ...4.1.1 -> 5.1.2 org.datanucleus:datanucleus-core .. 4.1.7 -> 5.1.2 org.datanucleus:datanucleus-jdo-query ...4.0.5 -> 5.0.2 org.datanucleus:datanucleus-jodatime 4.1.0-release -> 5.1.0-release org.datanucleus:datanucleus-rdbms 4.1.9 -> 5.1.2 > Update DataNucleus to the latest version > > > Key: ISIS-1744 > URL: https://issues.apache.org/jira/browse/ISIS-1744 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: 1.15.1 >Reporter: Sergey Sverdlov > > Please update dependencies to DataNucleus to the latest available versions: > org.datanucleus:datanucleus-api-jdo ...4.1.1 -> 5.1.3 > org.datanucleus:datanucleus-core .. 4.1.7 -> 5.1.3 > org.datanucleus:datanucleus-jdo-query ...4.0.5 -> 5.0.2 > org.datanucleus:datanucleus-jodatime 4.1.0-release -> > 5.1.0-release > org.datanucleus:datanucleus-rdbms 4.1.9 -> 5.1.3 -- 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&focusedCommentId=16219044#comment-16219044
]
ASF subversion and git services commented on ISIS-1572:
---
Commit 0b7f44552d81ac7aa0172b1c6cad6d24778db518 in isis's branch
refs/heads/master from [~danhaywood]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=0b7f445 ]
ISIS-1572: adds outline docs for MenuBarsService
> 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-1752) Extend RO viewer, return a menu.layout.xml resource
[ https://issues.apache.org/jira/browse/ISIS-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219045#comment-16219045 ] ASF subversion and git services commented on ISIS-1752: --- Commit bc5fdbe8de369c6e8c45d38992000f242812be4e in isis's branch refs/heads/master from [~danhaywood] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=bc5fdbe ] ISIS-1752: fixes unit test > Extend RO viewer, return a menu.layout.xml resource > --- > > Key: ISIS-1752 > URL: https://issues.apache.org/jira/browse/ISIS-1752 > Project: Isis > Issue Type: New Feature > Components: Core: Viewer: RestfulObjects >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 1.16.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1752) Extend RO viewer, return a menu.layout.xml resource
[ https://issues.apache.org/jira/browse/ISIS-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219042#comment-16219042 ] ASF subversion and git services commented on ISIS-1752: --- Commit d70337f97c1cfd347ea7515d58b736651d4ff74e in isis's branch refs/heads/master from [~danhaywood] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=d70337f ] ISIS-1752: factors out MenuBarsService, refactors Wicket UI to use MenuBarsService. > Extend RO viewer, return a menu.layout.xml resource > --- > > Key: ISIS-1752 > URL: https://issues.apache.org/jira/browse/ISIS-1752 > Project: Isis > Issue Type: New Feature > Components: Core: Viewer: RestfulObjects >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 1.16.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1752) Extend RO viewer, return a menu.layout.xml resource
[ https://issues.apache.org/jira/browse/ISIS-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219043#comment-16219043 ] ASF subversion and git services commented on ISIS-1752: --- Commit 1360bc36c90f9c7368d0a261d26ce8498fe58f78 in isis's branch refs/heads/master from [~danhaywood] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=1360bc3 ] ISIS-1752: deletes unused methods in ServiceActionUtil (now within MenuBarsServiceDefault). Also tested whether can support nested items (ans: sort-of, though CSS is broken). ... hence new HTML for tertiary. > Extend RO viewer, return a menu.layout.xml resource > --- > > Key: ISIS-1752 > URL: https://issues.apache.org/jira/browse/ISIS-1752 > Project: Isis > Issue Type: New Feature > Components: Core: Viewer: RestfulObjects >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 1.16.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1752) Extend RO viewer, return a menu.layout.xml resource
[ https://issues.apache.org/jira/browse/ISIS-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218917#comment-16218917 ] ASF subversion and git services commented on ISIS-1752: --- Commit b6e96dbf1427b4b027fa1727b95bbd2bba038b98 in isis's branch refs/heads/master from [~danhaywood] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=b6e96db ] ISIS-1752: adds new 'menuBars' resource to RO viewer > Extend RO viewer, return a menu.layout.xml resource > --- > > Key: ISIS-1752 > URL: https://issues.apache.org/jira/browse/ISIS-1752 > Project: Isis > Issue Type: New Feature > Components: Core: Viewer: RestfulObjects >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 1.16.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1752) Extend RO viewer, return a menu.layout.xml resource
[ https://issues.apache.org/jira/browse/ISIS-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218918#comment-16218918 ] ASF subversion and git services commented on ISIS-1752: --- Commit b08d3c267477d08f559dded5875564ab457e297c in isis's branch refs/heads/master from [~danhaywood] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=b08d3c2 ] ISIS-1752: moves oid from MenuSection down into ActionLayout, so that could support custom menus in the future. > Extend RO viewer, return a menu.layout.xml resource > --- > > Key: ISIS-1752 > URL: https://issues.apache.org/jira/browse/ISIS-1752 > Project: Isis > Issue Type: New Feature > Components: Core: Viewer: RestfulObjects >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 1.16.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ISIS-1752) Extend RO viewer, return a menu.layout.xml resource
Dan Haywood created ISIS-1752: - Summary: Extend RO viewer, return a menu.layout.xml resource Key: ISIS-1752 URL: https://issues.apache.org/jira/browse/ISIS-1752 Project: Isis Issue Type: New Feature Components: Core: Viewer: RestfulObjects Affects Versions: 1.15.1 Reporter: Dan Haywood Assignee: Dan Haywood Fix For: 1.16.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1465) Release activities for 1.16.0
[ https://issues.apache.org/jira/browse/ISIS-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218783#comment-16218783 ] ASF subversion and git services commented on ISIS-1465: --- Commit aed996d603bf4dd304fbfd1f994c9b3f0fe6dfae in isis's branch refs/heads/master from [~danhaywood] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=aed996d ] ISIS-1465: adds stuff on cgcom rel process > Release activities for 1.16.0 > - > > Key: ISIS-1465 > URL: https://issues.apache.org/jira/browse/ISIS-1465 > Project: Isis > Issue Type: Task > Components: Core >Affects Versions: 1.15.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.16.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1742) Remove deprecated annotations, methods etc.
[ https://issues.apache.org/jira/browse/ISIS-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218771#comment-16218771 ] ASF subversion and git services commented on ISIS-1742: --- Commit a5d371c261ece3d6d25d8f5ab44c13aa5b8c6557 in isis's branch refs/heads/ISIS-1632-meta-annotations from [~danhaywood] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=a5d371c ] ISIS-1742: updates todo list > Remove deprecated annotations, methods etc. > --- > > Key: ISIS-1742 > URL: https://issues.apache.org/jira/browse/ISIS-1742 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1742) Remove deprecated annotations, methods etc.
[ https://issues.apache.org/jira/browse/ISIS-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218770#comment-16218770 ] ASF subversion and git services commented on ISIS-1742: --- Commit 6b72d79da5243652a89c31939e1e1e319f45305a in isis's branch refs/heads/ISIS-1632-meta-annotations from [~danhaywood] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=6b72d79 ] ISIS-1742: removes stale unit test (referencing facet factory long since deleted...) > Remove deprecated annotations, methods etc. > --- > > Key: ISIS-1742 > URL: https://issues.apache.org/jira/browse/ISIS-1742 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1742) Remove deprecated annotations, methods etc.
[ https://issues.apache.org/jira/browse/ISIS-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218768#comment-16218768 ] ASF subversion and git services commented on ISIS-1742: --- Commit 575a3135a6143584e488400dade52b64aa1ce8d2 in isis's branch refs/heads/ISIS-1632-meta-annotations from [~danhaywood] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=575a313 ] ISIS-1742: removes support for exploration prefix for actions > Remove deprecated annotations, methods etc. > --- > > Key: ISIS-1742 > URL: https://issues.apache.org/jira/browse/ISIS-1742 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ISIS-1742) Remove deprecated annotations, methods etc.
[ https://issues.apache.org/jira/browse/ISIS-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218769#comment-16218769 ] ASF subversion and git services commented on ISIS-1742: --- Commit 4cac2bc500dbcec673d3422a3ed9fb54331f8945 in isis's branch refs/heads/ISIS-1632-meta-annotations from [~danhaywood] [ https://gitbox.apache.org/repos/asf?p=isis.git;h=4cac2bc ] ISIS-1742: deletes unused OptionHandlerXxx classes (Debug, Quiet, Verbose) > Remove deprecated annotations, methods etc. > --- > > Key: ISIS-1742 > URL: https://issues.apache.org/jira/browse/ISIS-1742 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: 1.15.1 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
