[JBoss JIRA] (DROOLS-1811) [Guided Decision Table] Column Wizard usability improvements
by Matthew Stevens (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1811?page=com.atlassian.jira.plugi... ]
Matthew Stevens commented on DROOLS-1811:
-----------------------------------------
Thank you [~jomarko].
I'll have to rely on your expertise for the organization. If the recommendation above makes sense to you, then it sounds good to me.
> [Guided Decision Table] Column Wizard usability improvements
> ------------------------------------------------------------
>
> Key: DROOLS-1811
> URL: https://issues.jboss.org/browse/DROOLS-1811
> Project: Drools
> Issue Type: Enhancement
> Components: Guided Decision Table Editor
> Affects Versions: 7.2.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Labels: UX
> Fix For: 7.5.0.Final
>
> Attachments: Screenshot from 2017-11-08 10-34-17.png
>
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> On the _BRMS 7.0 - Getting Started Experience_ meeting, there were mentioned these points that could improve the column wizard:
> - Placement of input fields
> -- *Field binding* should be on the same page as *Field*
> -- Pages like *Operator* and *Field* could be merged or at least recapitulate what was selected on previous pages of the wizard
> - *[UPDATED SOLVED]* Input fields should be explained somehow. For newbies it is really hard to understand what is the *Calculation Type* or *Value List*. I liked concept of small _i_ in blue circle that shows hint after mouse is over this info sign.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (DROOLS-2114) [XLS Score Card] Version is not refreshed after upload
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2114?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2114:
--------------------------------
Description: User can upload new version of sxls score card, however the toolbar menu with version is not refreshed. User has to reopen the editor to see correct (up to date) list of versions. (was: User can upload new version of xls decision table, however the toolbar menu with version is not refreshed. User has to reopen the editor to see correct (up to date) list of versions.)
> [XLS Score Card] Version is not refreshed after upload
> ------------------------------------------------------
>
> Key: DROOLS-2114
> URL: https://issues.jboss.org/browse/DROOLS-2114
> Project: Drools
> Issue Type: Bug
> Components: Guided Score Card Editor
> Affects Versions: 7.5.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
>
> User can upload new version of sxls score card, however the toolbar menu with version is not refreshed. User has to reopen the editor to see correct (up to date) list of versions.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (DROOLS-2114) [SXLS Score Card] Version is not refreshed after upload
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2114?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2114:
--------------------------------
Steps to Reproduce:
# Navigate into workbench, any project
# Create new SXLS Score Card asset
# Upload new version of the asset
# See the Version toolbar menu, there is just one version
# Reopen the SXLS editor, there will be two versions in the Version asset toolbar
was:
# Navigate into workbench, any project
# Create new XLS Score Card asset
# Upload new version of the asset
# See the Version toolbar menu, there is just one version
# Reopen the XLS editor, there will be two versions in the Version asset toolbar
> [SXLS Score Card] Version is not refreshed after upload
> -------------------------------------------------------
>
> Key: DROOLS-2114
> URL: https://issues.jboss.org/browse/DROOLS-2114
> Project: Drools
> Issue Type: Bug
> Components: Guided Score Card Editor
> Affects Versions: 7.5.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
>
> User can upload new version of sxls score card, however the toolbar menu with version is not refreshed. User has to reopen the editor to see correct (up to date) list of versions.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (DROOLS-2114) [XLS Score Card] Version is not refreshed after upload
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2114?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2114:
--------------------------------
Steps to Reproduce:
# Navigate into workbench, any project
# Create new XLS Score Card asset
# Upload new version of the asset
# See the Version toolbar menu, there is just one version
# Reopen the XLS editor, there will be two versions in the Version asset toolbar
was:
# Navigate into workbench, any project
# Create new XLS Decision table asset
# Upload new version of the asset
# See the Version toolbar menu, there is just one version
# Reopen the XLS editor, there will be two versions in the Version asset toolbar
> [XLS Score Card] Version is not refreshed after upload
> ------------------------------------------------------
>
> Key: DROOLS-2114
> URL: https://issues.jboss.org/browse/DROOLS-2114
> Project: Drools
> Issue Type: Bug
> Components: Guided Score Card Editor
> Affects Versions: 7.5.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
>
> User can upload new version of xls decision table, however the toolbar menu with version is not refreshed. User has to reopen the editor to see correct (up to date) list of versions.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (DROOLS-2114) [XLS Score Card] Version is not refreshed after upload
by Jozef Marko (JIRA)
Jozef Marko created DROOLS-2114:
-----------------------------------
Summary: [XLS Score Card] Version is not refreshed after upload
Key: DROOLS-2114
URL: https://issues.jboss.org/browse/DROOLS-2114
Project: Drools
Issue Type: Bug
Components: XLS Decision Table Editor
Affects Versions: 7.5.0.Final
Reporter: Jozef Marko
Assignee: Jozef Marko
User can upload new version of xls decision table, however the toolbar menu with version is not refreshed. User has to reopen the editor to see correct (up to date) list of versions.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-9488) WeldDeployment initialisation error causes session fail-over to fail.
by Martin Kouba (JIRA)
[ https://issues.jboss.org/browse/WFLY-9488?page=com.atlassian.jira.plugin.... ]
Martin Kouba commented on WFLY-9488:
------------------------------------
Yes, that is possible. Wicket's {{NonContextual}} may perform {{CDI.current().getBeanManager()}} which ultimately attempts to find a bean archive for {{NonContextual.class}} but since wicket-cdi-1.1 declares {{annotated}} bean discovery, Weld is not able to find the correct bean archive ({{BeanDeploymentArchive.getBeanClasses()}} only returns all the types found in the archive which are annotated with a bean defining annotation). This should be fixed once WildFly switches to Weld 3 and WFLY-9536 is implemented.
Nevertheless, we should also incorporate the proposed fix - I'll send a PR based on the patch.
> WeldDeployment initialisation error causes session fail-over to fail.
> ---------------------------------------------------------------------
>
> Key: WFLY-9488
> URL: https://issues.jboss.org/browse/WFLY-9488
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 11.0.0.Final
> Environment: Testen on OS X Sierra with Oracle JDK 1.8.0_152
> Reporter: Klaasjan Brand
> Assignee: Martin Kouba
> Attachments: serviceregistry.patch
>
>
> At Topicus we've tested one of our Java EE applications to check compatibility with Wildfly session replication. This resulted in deserialization errors when performing a failover test.
> (WELD-001122: Failed to deserialize annotated type identified with AnnotatedTypeIdentifier)
> The application is deployed as an EAR archive containing several modules, one of them a WAR which hosts the main web frontend.
> Point of interest is our application uses Wicket (with Wicket-CDI) to inject CDI resources in Wicket pages.
> After a debugging session we concluded the "tryToLoadUnknownBackedAnnotatedType" method in the Weld class "SlimAnnotatedType" uses the wrong ResourceLoader when trying to load the class containing an injected object.
> Further debugging proved the initialisation in the WeldDeployment method "createAndRegisterAdditionalBeanDeploymentArchive" copies all of the ServiceRegistry entries of the parent BeanDeployment to the child, overwriting the already set ResourceLoader.
> I've attached a patch which prevents the overwriting of the deployment's already set entries. This fixed the replication problems with our application.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months