[jira] [Updated] (ISIS-1277) setAccessible() will be gone with JDK 9
[ https://issues.apache.org/jira/browse/ISIS-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1277: -- Fix Version/s: 2.0.0 > setAccessible() will be gone with JDK 9 > --- > > Key: ISIS-1277 > URL: https://issues.apache.org/jira/browse/ISIS-1277 > Project: Isis > Issue Type: Task > Components: Core >Affects Versions: 1.10.0 >Reporter: Jörg Rade >Assignee: Dan Haywood >Priority: Minor > Fix For: 2.0.0 > > > https://github.com/apache/isis/search?utf8=%E2%9C%93&q=setAccessible%28%29 > yields 9 hits. > According to [1] this will be a problem with Java 9. > [1] > https://jaxenter.de/java-9-release-verschoben-warum-jigsaw-noch-nicht-fertig-ist-31687 > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1230) How use SudoService with fixture scripts that themselves are nested?
[
https://issues.apache.org/jira/browse/ISIS-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-1230:
--
Fix Version/s: (was: 1.11.0)
1.12.0
> How use SudoService with fixture scripts that themselves are nested?
>
>
> Key: ISIS-1230
> URL: https://issues.apache.org/jira/browse/ISIS-1230
> Project: Isis
> Issue Type: Improvement
> Components: Core
>Affects Versions: core-1.8.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Minor
> Fix For: 1.12.0
>
>
> As raised by Oscar:
> I’m not sure how to use the SudoService inside a FixtureScript.
> I have the following:
> public class DemoWithAllRecordsFixture extends FixtureScript {
> public DemoWithAllRecordsFixture() {
> this.withDiscoverability(Discoverability.DISCOVERABLE);
> }
> @Override
> protected void execute(
> final ExecutionContext executionContext) {
> executionContext.executeChild(this, new
> ExcelInheritedConditionsSNPGenotypeFixture());
> executionContext.executeChild(this, new
> ExcelDrugsSNPGenotypeFixture());
> executionContext.executeChild(this, new
> ExcelTraitsSNPGenotypeFixture());
> }
> The ExcelInheritedConditionsSNPGenotypeFixture contains many wrapped action
> invocations, so the following exception is thrown:
> Caused by: org.apache.isis.applib.services.wrapper.HiddenException: Reason:
> Could not locate application user for initialisation. Identifier:
> com.tellmegen.domain.model.inheritedconditions.InheritedCondition#upsertSNPGenotype(java.lang.Integer,com.tellmegen.domain.model.AppliesToSex,java.lang.String,java.lang.String,com.tellmegen.domain.model.inheritedconditions.InheritedConditionHeredity,com.tellmegen.domain.model.inheritedconditions.InheritedConditionPhenotype,com.tellmegen.domain.model.inheritedconditions.InheritedConditionStatus,java.lang.String,java.lang.String)
> at
> org.apache.isis.core.wrapper.handlers.DomainObjectInvocationHandler.toException(DomainObjectInvocationHandler.java:732)
> at
> org.apache.isis.core.wrapper.handlers.DomainObjectInvocationHandler.notifyListenersAndVetoIfRequired(DomainObjectInvocationHandler.java:700)
> at
> org.apache.isis.core.wrapper.handlers.DomainObjectInvocationHandler.checkVisibility(DomainObjectInvocationHandler.java:682)
> at
> org.apache.isis.core.wrapper.handlers.DomainObjectInvocationHandler.handleActionMethod(DomainObjectInvocationHandler.java:607)
> at
> org.apache.isis.core.wrapper.handlers.DomainObjectInvocationHandler.invoke(DomainObjectInvocationHandler.java:263)
> at
> org.apache.isis.core.wrapper.proxy.ProxyInstantiatorForJavassist$1.invoke(ProxyInstantiatorForJavassist.java:72)
> at
> com.tellmegen.domain.model.inheritedconditions.InheritedCondition_$$_jvstcc_7.upsertSNPGenotype(InheritedCondition_$$_jvstcc_7.java)
> at
> com.tellmegen.domain.model.importing.ImportInheritedConditionSNPGenotype.saveToDatabase(ImportInheritedConditionSNPGenotype.java:244)
> at
> com.tellmegen.domain.model.importing.ImportInheritedConditionsSNPGenotypeService.importInheritedConditionsSNPGenotypes(ImportInheritedConditionsSNPGenotypeService.java:38)
> at
> com.tellmegen.fixture.model.inheritedconditionsnpgenotype.ExcelInheritedConditionsSNPGenotypeFixture.execute(ExcelInheritedConditionsSNPGenotypeFixture.java:24)
> at
> org.apache.isis.applib.fixturescripts.FixtureScript$ExecutionContext.executeChildIfNotAlready(FixtureScript.java:549)
> at
> org.apache.isis.applib.fixturescripts.FixtureScript$ExecutionContext.executeChildT(FixtureScript.java:528)
> at
> org.apache.isis.applib.fixturescripts.FixtureScript$ExecutionContext.executeChildT(FixtureScript.java:498)
> at
> org.apache.isis.applib.fixturescripts.FixtureScript$ExecutionContext.executeChild(FixtureScript.java:487)
> at
> com.tellmegen.fixture.TellMeGenDemoWithAllRecordsFixture.execute(TellMeGenDemoWithAllRecordsFixture.java:34)
> If try to use them inside a SudoService.sudo(…) call I don’t have access to
> the “executionContext” (it’s private).
> So basically, I would need to make the “executionContext” field of
> FixtureScript “public”, or being able to use SudoService to override the User
> globally, without needing to use a “Callable” construct.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ISIS-1059) Isis restriction of using some characters when the property is a @PrimaryKey
[ https://issues.apache.org/jira/browse/ISIS-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1059: -- Fix Version/s: (was: 1.11.0) 1.12.0 > Isis restriction of using some characters when the property is a @PrimaryKey > > > Key: ISIS-1059 > URL: https://issues.apache.org/jira/browse/ISIS-1059 > Project: Isis > Issue Type: Bug > Components: Core >Affects Versions: core-1.8.0 >Reporter: Martin Grigorov >Assignee: Dan Haywood > Fix For: 1.12.0 > > > If a domain entity uses PersistenceCapable(identityType = > IdentityType.APPLICATION) combined with PrimaryKey annotated property then it > is not allowed to use some symbols like '@'. > The exception is: > Caused by: java.lang.IllegalArgumentException: identifier 's...@email.tld' > contains an '@' symbol > at > org.apache.isis.core.commons.ensure.Ensure.ensureThatArg(Ensure.java:75) > at > org.apache.isis.core.metamodel.adapter.oid.RootOidDefault.(RootOidDefault.java:124) > at > org.apache.isis.core.metamodel.adapter.oid.RootOidDefault.(RootOidDefault.java:92) > at > org.apache.isis.core.runtime.system.persistence.OidGenerator.createPersistentOrViewModelOid(OidGenerator.java:99) > at > org.apache.isis.objectstore.jdo.datanucleus.persistence.FrameworkSynchronizer$3.run(FrameworkSynchronizer.java:203) > at > org.apache.isis.objectstore.jdo.datanucleus.persistence.FrameworkSynchronizer$8.call(FrameworkSynchronizer.java:350) > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1228) Introduce nextTransaction() into fixture scripts.
[ https://issues.apache.org/jira/browse/ISIS-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1228: -- Fix Version/s: (was: 1.11.0) 1.12.0 > Introduce nextTransaction() into fixture scripts. > - > > Key: ISIS-1228 > URL: https://issues.apache.org/jira/browse/ISIS-1228 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: core-1.8.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.12.0 > > > originally raised by Oscar: > When using FixtureScripts, there can be many actions that, on the real world, > are execute in different time contexts. > For example, a user creates an Account on the webapp and after that executes > different actions. > That’s relevant if using the queryResultsCache service (or the new planned > “@Action” annotation extension) because the results previously created (i.e., > the Account) might be available on the cache. > So perhaps some mechanism like the nextTransation() method might be also > introduced on FixtureScripts. > What do you think? > ~~~ > Dan's reply: > Makes sense. > There is a nextTransaction() method in the AbstractIntegTest class, you could > see how that is implemented and see if it can be adapted? > Or, another idea is that the framework could run each FixtureScript > automatically in a separate transaction; that would be a better simulation of > a sequence of user interactions? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1217) Formatting text inside a text field
[ https://issues.apache.org/jira/browse/ISIS-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1217: -- martin-g has implemented this as an addon, see https://github.com/isisaddons/isis-wicket-summernote > Formatting text inside a text field > --- > > Key: ISIS-1217 > URL: https://issues.apache.org/jira/browse/ISIS-1217 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.9.0 >Reporter: Marianne Hagaseth >Assignee: Dan Haywood > Fix For: 1.11.0 > > Attachments: image002.jpg, image004.jpg, image006.jpg > > > It should be possible to format the text inside a text field using Apache > ISIS. > I would like to highlight some words in the text, maybe with different > colors/fonts dependent on their tags/meta data/meaning. > Also, it should be possible to right-click a term/word in the text, and then > get a (list of) functions, and then it should be possible to select on of > these functions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1240) Derive icon from service when not provided
[ https://issues.apache.org/jira/browse/ISIS-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1240: -- Fix Version/s: (was: 1.11.0) 1.12.0 > Derive icon from service when not provided > -- > > Key: ISIS-1240 > URL: https://issues.apache.org/jira/browse/ISIS-1240 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: 1.9.0 >Reporter: Jeroen van der Wal >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.12.0 > > > If no iconName method is provided for a service Isis searches for an icon > equal to the service name. Additional to this behavior we could extend this > search by stripping off know service suffixes like "Service, Menu and > Repository". As an example: the "PersonMenu" service will use the "Person" > icon if no icon has been specified. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1256) Shiro has a vulnerabilty for default rememberMe cookie. We should work around this somehow
[ https://issues.apache.org/jira/browse/ISIS-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1256: -- Fix Version/s: (was: 1.11.0) 1.12.0 > Shiro has a vulnerabilty for default rememberMe cookie. We should work > around this somehow > --- > > Key: ISIS-1256 > URL: https://issues.apache.org/jira/browse/ISIS-1256 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: 1.10.0 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 1.12.0 > > > see https://issues.apache.org/jira/browse/SHIRO-550 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1260) when metamodel validation fails the integ test are executed anyway but all fail because the app is not initialized property
[ https://issues.apache.org/jira/browse/ISIS-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1260: -- Fix Version/s: (was: 1.11.0) 1.12.0 Description: the workaround is to enable metamodel validation for the dom project. > when metamodel validation fails the integ test are executed anyway but all > fail because the app is not initialized property > --- > > Key: ISIS-1260 > URL: https://issues.apache.org/jira/browse/ISIS-1260 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: 1.10.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.12.0 > > > the workaround is to enable metamodel validation for the dom project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1247) .layout.json file not found if i18n is enabled ... uses the translated name to lookup the file.
[ https://issues.apache.org/jira/browse/ISIS-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1247: -- think duplicate of ISIS-1221. > .layout.json file not found if i18n is enabled ... uses the translated name > to lookup the file. > --- > > Key: ISIS-1247 > URL: https://issues.apache.org/jira/browse/ISIS-1247 > Project: Isis > Issue Type: Bug > Components: Core >Affects Versions: 1.10.0 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 1.11.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1261) Provide a mvn -D property (or similar) to allow the .pot translations file either to be generated or not generated as required.
[ https://issues.apache.org/jira/browse/ISIS-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1261: -- Fix Version/s: (was: 1.11.0) 1.12.0 > Provide a mvn -D property (or similar) to allow the .pot translations file > either to be generated or not generated as required. > --- > > Key: ISIS-1261 > URL: https://issues.apache.org/jira/browse/ISIS-1261 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: 1.10.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.12.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1221) JSON Format Layouts not recognized with i18n translations in Wicket Viewer
[ https://issues.apache.org/jira/browse/ISIS-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1221: -- think duplicate of ISIS-1247. > JSON Format Layouts not recognized with i18n translations in Wicket Viewer > -- > > Key: ISIS-1221 > URL: https://issues.apache.org/jira/browse/ISIS-1221 > Project: Isis > Issue Type: Bug > Components: Core: Viewer: Wicket >Affects Versions: 1.9.0 > Environment: Windows Server, HSQLDB >Reporter: Cesar Lugo >Assignee: Dan Haywood > Fix For: 1.11.0 > > > I am working with Apache Isis Wicket viewer 1.9.0, and I have some form > layout json files to define the layout for some domain objects. I also added > a translation file (i18n) with some translations. When running the > application in the browser, when I am in “writing translations” mode it shows > the object form with the layout defined in the json file (ok), but when I > switch to “reading translations”, it goes back to the “default” layout, > ignoring the layout defined in the json file. > In regards to those modes, I am referring to the Apache wicket viewer menu > which, in prototype mode, has a "Prototyping" menu, which has an option > "Switch to Reading Translations". When you select that option and keep using > the application is when it loses the layouts defined in the json layout files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ISIS-1278) Title of choices lnks in RO failing, called incorrectly.
[ https://issues.apache.org/jira/browse/ISIS-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood resolved ISIS-1278. --- Resolution: Fixed > Title of choices lnks in RO failing, called incorrectly. > > > Key: ISIS-1278 > URL: https://issues.apache.org/jira/browse/ISIS-1278 > Project: Isis > Issue Type: Bug > Components: Core: Viewer: RestfulObjects >Affects Versions: 1.10.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.11.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1272) Facet factory for actions called "changeXxx" or "maintainXxx" to be positioned to RIGHT, with dropdown.
[ https://issues.apache.org/jira/browse/ISIS-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1272: -- Fix Version/s: (was: 1.11.0) 1.13.0 > Facet factory for actions called "changeXxx" or "maintainXxx" to be > positioned to RIGHT, with dropdown. > --- > > Key: ISIS-1272 > URL: https://issues.apache.org/jira/browse/ISIS-1272 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.10.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.13.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1118) The Wicket viewer autocomplete could also show recently used objects (eg 5 most recent) as the old HTML viewer used to do.
[ https://issues.apache.org/jira/browse/ISIS-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1118: -- Fix Version/s: (was: 1.11.0) 1.12.0 > The Wicket viewer autocomplete could also show recently used objects (eg 5 > most recent) as the old HTML viewer used to do. > -- > > Key: ISIS-1118 > URL: https://issues.apache.org/jira/browse/ISIS-1118 > Project: Isis > Issue Type: New Feature > Components: Core: Viewer: Wicket >Affects Versions: core-1.8.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.12.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-785) Implement @BulkParam annotation for executing the same action over a Collection of entities
[
https://issues.apache.org/jira/browse/ISIS-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-785:
-
Fix Version/s: (was: 1.11.0)
1.12.0
> Implement @BulkParam annotation for executing the same action over a
> Collection of entities
> ---
>
> Key: ISIS-785
> URL: https://issues.apache.org/jira/browse/ISIS-785
> Project: Isis
> Issue Type: Improvement
> Components: Core, Core: Viewer: Wicket
>Reporter: Oscar Bou
>Assignee: Dan Haywood
> Fix For: 1.12.0
>
>
> (I've cloned this from ISIS-764, which has now been "repurposed" to some
> prereq work that will help in implementing this story).
> As an Isis user
> I want to pass as an action parameter a collection of entities
> In order to avoid repetitive work to the end-user
> The idea is to being able to annotate one of the action params with a new
> annotation, named @BulkParam, such as in:
> public class TodoItem {
> ...
> private TodoItem parentTodoItem;
>
> public void addRelatedTodo(@Named("To-Do Item") @BulkParam TodoItem
> todoItem, @Named("Comments") String comments) {
>
> }
> ...
> }
> Where the viewer founds it, instead of asking for one TodoItem, it will allow
> the user to select multiple items.
> Once done, it will execute the action multiple times, passing each time one
> of the TodoItem selected.
> If there are other params, the viewer will pass on each action invokation the
> same value for all them.
> Only one param can be annotated with @BulkParam, for avoiding combinatorial
> explosion (10 items selected of one param, 10 items on the other param would
> require to be execute 100 times, one for each combination).
> The User Interface could be adapted to the choices or autocomplete parameter
> facets, for easing the work of the user.
> If "choices", there can be alternative displays (see
> https://plugins.jquery.com/tag/multiselect/):
> 1. the viewer can present the user a grid or checkbox (like the one in
> http://liveline.github.io/jquery-checkallbox/) with all choices, and the user
> can check any of them. Alternative:
> http://www.ryancramer.com/journal/entries/select_multiple/
> 2. multi-select drop-down, like this ones:
> http://ivaynberg.github.io/select2/, http://harvesthq.github.io/chosen/,
> https://github.com/ehynds/jquery-ui-multiselect-widget,
> http://www.droplist.vinmein.com/. They require minimal changes on the current
> actions dialog, but does not allow to always view all choices selected (I
> could live with it).
> If "autocomplete":
> 1. It could be based on a two panels disposition, left and right, where the
> user incrementally searches on an edit box placed over the left panel,
> similar to current autocomplete implementation, but placing on the left panel
> : http://quasipartikel.at/multiselect_next/
> 2. Similar approach to the "choices" one, also with this same widget that
> admits remote dataset loading and min number of chars entered:
> http://ivaynberg.github.io/select2/
> As seen, a widget like http://ivaynberg.github.io/select2/ would allow to
> solve both situations without requiring much changes on the viewer’s action
> dialog.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ISIS-1023) Allow actions to be invoked on entity when rendered within a table.
[ https://issues.apache.org/jira/browse/ISIS-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1023: -- Fix Version/s: (was: 1.11.0) 1.12.0 > Allow actions to be invoked on entity when rendered within a table. > --- > > Key: ISIS-1023 > URL: https://issues.apache.org/jira/browse/ISIS-1023 > Project: Isis > Issue Type: New Feature > Components: Core, Core: Viewer: Wicket >Affects Versions: viewer-wicket-1.7.0, core-1.7.0 >Reporter: Dan Haywood >Priority: Minor > Fix For: 1.12.0 > > > Enhance the Wicket viewer (with corresponding metadata annotations) to render > an entity's actions as drop-down menu when that entity is rendered as a row > of a table. > There's probably no need to introduce additional annotations; the > @ActionLayout(hidden=...) indicates whether an action is hidden in various > contexts, one of these being it being hidden (or not) within tables. > My idea therefore is that, unless every action of an entity is indicated as > hidden for a table, that there is an additional column that includes a > drop-down and that allows the actions to be invoked (bringing up the dialog). > Once the action is invoked (like bulk actions) the table should be reloaded > (rather than, say, navigate to the object returned by the action). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-709) Support multi-select for the drop-down box
[ https://issues.apache.org/jira/browse/ISIS-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-709: - Fix Version/s: (was: 1.11.0) 1.12.0 > Support multi-select for the drop-down box > -- > > Key: ISIS-709 > URL: https://issues.apache.org/jira/browse/ISIS-709 > Project: Isis > Issue Type: New Feature > Components: Core, Core: Viewer: Wicket >Affects Versions: viewer-wicket-1.3.1, core-1.3.0 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 1.12.0 > > > Possibly re-implement using > https://github.com/wicketstuff/core/tree/master/wicketstuff-selectize-parent > See also ISIS-1225. > ~~~ > ISIS-778 (now implemented) is a prereq to this. (NB: ISIS-764 is a duplicate > of ISIS-778). > ISIS-785 is also a prereq, I think. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1225) [WON'T FIX] Replace select2 with selectize
[
https://issues.apache.org/jira/browse/ISIS-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-1225:
--
Summary: [WON'T FIX] Replace select2 with selectize (was: Replace select2
with selectize)
> [WON'T FIX] Replace select2 with selectize
> --
>
> Key: ISIS-1225
> URL: https://issues.apache.org/jira/browse/ISIS-1225
> Project: Isis
> Issue Type: Improvement
> Components: Core
>Affects Versions: 1.9.0
>Reporter: Dan Haywood
>Assignee: Martin Grigorov
> Fix For: 1.11.0
>
>
> This may be required if the upgrade to select2 v4 (ISIS-1224) does not
> address the issue originally reported in ISIS-1020 ("drop-down window opens
> top-left of screen").
> details on selectize:
> https://github.com/wicketstuff/core/tree/master/wicketstuff-selectize-parent
> see also ISIS-709 (multi-select).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (ISIS-1225) [WON'T FIX] Replace select2 with selectize
[
https://issues.apache.org/jira/browse/ISIS-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood resolved ISIS-1225.
---
Resolution: Won't Fix
On investigation, we've decided that selectize isn't production-ready enough to
use,
> [WON'T FIX] Replace select2 with selectize
> --
>
> Key: ISIS-1225
> URL: https://issues.apache.org/jira/browse/ISIS-1225
> Project: Isis
> Issue Type: Improvement
> Components: Core
>Affects Versions: 1.9.0
>Reporter: Dan Haywood
>Assignee: Martin Grigorov
> Fix For: 1.11.0
>
>
> This may be required if the upgrade to select2 v4 (ISIS-1224) does not
> address the issue originally reported in ISIS-1020 ("drop-down window opens
> top-left of screen").
> details on selectize:
> https://github.com/wicketstuff/core/tree/master/wicketstuff-selectize-parent
> see also ISIS-709 (multi-select).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ISIS-1223) Upgrade Wicket to 7.x
[ https://issues.apache.org/jira/browse/ISIS-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1223: -- Fix Version/s: (was: 1.11.0) 1.12.0 > Upgrade Wicket to 7.x > - > > Key: ISIS-1223 > URL: https://issues.apache.org/jira/browse/ISIS-1223 > Project: Isis > Issue Type: Dependency upgrade > Components: Core >Affects Versions: 1.9.0 >Reporter: Dan Haywood >Assignee: Martin Grigorov > Fix For: 1.12.0 > > > to keep up to date, and as a prereq for ISIS-1224. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ISIS-1275) Configuration property for RO viewer to relax Accept header checking.
[ https://issues.apache.org/jira/browse/ISIS-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood resolved ISIS-1275. --- Resolution: Fixed > Configuration property for RO viewer to relax Accept header checking. > - > > Key: ISIS-1275 > URL: https://issues.apache.org/jira/browse/ISIS-1275 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: 1.10.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.11.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ISIS-1273) Enhance RO viewer so that the default RO v1 representations are implemented as a ContentNegotiationService
[ https://issues.apache.org/jira/browse/ISIS-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood resolved ISIS-1273. --- Resolution: Fixed > Enhance RO viewer so that the default RO v1 representations are implemented > as a ContentNegotiationService > -- > > Key: ISIS-1273 > URL: https://issues.apache.org/jira/browse/ISIS-1273 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: 1.10.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.11.0 > > > So that all requests are handled through the same conneg mechanism. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ISIS-1237) Integrate with swagger for REST APIs
[ https://issues.apache.org/jira/browse/ISIS-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood resolved ISIS-1237. --- Resolution: Fixed > Integrate with swagger for REST APIs > > > Key: ISIS-1237 > URL: https://issues.apache.org/jira/browse/ISIS-1237 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: 1.9.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.11.0 > > Attachments: hand-crafted-swagger-spec-for-simpleapp.yaml > > > as per Oscar's mail: > You know we're using Wavemaker for the front-end. > Most recent version 7 uses Swagger as the way to document the auto-generated > APIs [1], but all JavaScript widgets can be render any JSON representation > with limitations detailed in [2], [3]. > [1] > http://www.wavemaker.com/latest/wavemaker-api-designer-brings-api-driven-development-to-custom-built-enterprise-applications/ > [2] http://www.wavemaker.com/learn/topics/studio/integrate/external-services/ > [3] > http://www.wavemaker.com/learn/docs/importing-web-services/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ISIS-1274) ContentNegotiationService for simplified representations for custom RO clients
[ https://issues.apache.org/jira/browse/ISIS-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood resolved ISIS-1274. --- Resolution: Fixed > ContentNegotiationService for simplified representations for custom RO clients > -- > > Key: ISIS-1274 > URL: https://issues.apache.org/jira/browse/ISIS-1274 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.10.0 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: 1.11.0 > > > based on a new Accept header value, specific to org.apache.isis -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1237) Integrate with swagger for REST APIs
[ https://issues.apache.org/jira/browse/ISIS-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067207#comment-15067207 ] ASF subversion and git services commented on ISIS-1237: --- Commit 5e50f84f3a255fea4eaddbdd5f4a54d624a00307 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=5e50f84 ] ISIS-1237: some public actions not being recognized as such. > Integrate with swagger for REST APIs > > > Key: ISIS-1237 > URL: https://issues.apache.org/jira/browse/ISIS-1237 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: 1.9.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.11.0 > > Attachments: hand-crafted-swagger-spec-for-simpleapp.yaml > > > as per Oscar's mail: > You know we're using Wavemaker for the front-end. > Most recent version 7 uses Swagger as the way to document the auto-generated > APIs [1], but all JavaScript widgets can be render any JSON representation > with limitations detailed in [2], [3]. > [1] > http://www.wavemaker.com/latest/wavemaker-api-designer-brings-api-driven-development-to-custom-built-enterprise-applications/ > [2] http://www.wavemaker.com/learn/topics/studio/integrate/external-services/ > [3] > http://www.wavemaker.com/learn/docs/importing-web-services/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
