[JBoss JIRA] (DROOLS-4084) Export to Excel for decision tables 7.5
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-4084?page=com.atlassian.jira.plug... ]
Jozef Marko closed DROOLS-4084.
-------------------------------
Resolution: Done
> Export to Excel for decision tables 7.5
> ---------------------------------------
>
> Key: DROOLS-4084
> URL: https://issues.redhat.com/browse/DROOLS-4084
> Project: Drools
> Issue Type: Epic
> Components: Guided Decision Table Editor
> Affects Versions: 7.23.0.Final
> Reporter: Jozef Marko
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> This is a community epic for the BAPL-1169. The epic was created according to the [definition of done|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4o...] that advices what needs to be agreed before each feature implementation.
> h1. Requirement
> - As a user of the feature I want to convert guided decision table by single click to xls (Excel) format.
> - The converted table should have the same format as is supported for importing into business central.
> - The converted table should visually differentiate column and row types (constraint vs. action, metadata vs. data)
> - The conversion should support Simple GDT column
> - The conversion should support Brl GDT column
> - The conversion should support Attribute and Metadata columns
> - The converted table can be opened on Windows and Linux
> - The converted table split lines
> - The converted table support multibyte characters
> - The conversion of GDT graph is possible
> - User is prompted to save changes before conversion
> - Converted table is not stored in kie project, just downloaded via browser
> h1. UX design
> - Placement of the conversion button
> - Text of the conversion button
> - Dialog for case we support save changes before conversion
> h1. Documentation
> - Replace picture of GDT editor where they become obsolete
> - Comprehensive doc is probably not needed
> h1. Acceptance test
> - Convert table that
> -- Has more that 100 lines
> -- Has one Metadata column
> -- Has one Attribute column
> -- Has three constraint columns( two over same fact )
> -- Has three action columns( two over same fact )
> -- Has not all cells filled in
> -- Operates over String, Number, Boolean fields
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-5219) [DMN Designer] Multiple output columns in decision table
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5219?page=com.atlassian.jira.plug... ]
Jozef Marko closed DROOLS-5219.
-------------------------------
Resolution: Duplicate
> [DMN Designer] Multiple output columns in decision table
> --------------------------------------------------------
>
> Key: DROOLS-5219
> URL: https://issues.redhat.com/browse/DROOLS-5219
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.36.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: multicolumn-decision-table.webm
>
>
> The issue is when user tries to create a decision table expression with multiple output columns.
> To achieve this user needs to invoke context menu with items 'Insert left / Insert right'. User has two options. He can invoke such menu from 'data' cell and 'header' cell.
> For data cells the feature works fine, however for header cells the operation fails and an error is shown. For more details see the video.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-13267) Convert EJB3 subsystem transformers to use chained transformers
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFLY-13267?page=com.atlassian.jira.plugi... ]
Richard Achmatowicz commented on WFLY-13267:
--------------------------------------------
I have added transformer tests for EAP 7.0.0, 7.1.0 and 7.2.0 which are long overdue.
I also refactored the transformers to use chained transformers, so that in future, only transformers from current to the most recent version will be required.
> Convert EJB3 subsystem transformers to use chained transformers
> ---------------------------------------------------------------
>
> Key: WFLY-13267
> URL: https://issues.redhat.com/browse/WFLY-13267
> Project: WildFly
> Issue Type: Task
> Components: EJB
> Affects Versions: 19.0.0.Final
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Major
> Fix For: 20.0.0.Beta1
>
>
> The EJB3 subsystem defines its subsystem transformers in the class org.jboss.as.ejb3.subsystem.EJBTransformers.
> This class organizes transformers in 'the old way' (see https://docs.jboss.org/author/display/WFLY/Domain+Mode+Subsystem+Transfor...), so that there is a lot of code duplication.
> This issue will reorganize the transformers to use the chained transformer technique, where only the changes from the current version to the most recent legacy version need be specified.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-13384) Add IIOP Naming View Management Command
by Brad Maxwell (Jira)
Brad Maxwell created WFLY-13384:
-----------------------------------
Summary: Add IIOP Naming View Management Command
Key: WFLY-13384
URL: https://issues.redhat.com/browse/WFLY-13384
Project: WildFly
Issue Type: Feature Request
Components: IIOP
Affects Versions: 19.0.0.Final
Reporter: Brad Maxwell
Assignee: Tomasz Adamski
Currently there is not a way to view the IIOP Naming Bindings.
Similar to the JNDI View shown below, a management command to get a view of the IIOP Naming bindings would be useful.
{code}
/subsystem=naming:jndi-view
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-10612) Include EJB's IIOP Binding when EJB is deployed logging
by Ranabir Chakraborty (Jira)
[ https://issues.redhat.com/browse/WFLY-10612?page=com.atlassian.jira.plugi... ]
Ranabir Chakraborty reassigned WFLY-10612:
------------------------------------------
Assignee: Ranabir Chakraborty (was: Tomasz Adamski)
> Include EJB's IIOP Binding when EJB is deployed logging
> -------------------------------------------------------
>
> Key: WFLY-10612
> URL: https://issues.redhat.com/browse/WFLY-10612
> Project: WildFly
> Issue Type: Enhancement
> Components: IIOP
> Affects Versions: 12.0.0.Final
> Reporter: Brad Maxwell
> Assignee: Ranabir Chakraborty
> Priority: Major
> Attachments: WFLY-10612.jar, java.policy
>
>
> It would be useful when EJBs configured with IIOP enabled or when enabled by default for all, that it log the binding for the IIOP interface as it is different from the JNDI bindings.
> <iiop enable-by-default="true" use-qualified-name="true"/>
> {code}
> INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows:
> java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean
> java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean
> java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean
> java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> {code}
> Something like this when use-qualified-name="true"
> {code}
> IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows:
> iiop-eap7/HelloSessionBean
> {code}
> or use-qualified-name="false"
> {code}
> IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows:
> HelloSessionBean
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-10612) Include EJB's IIOP Binding when EJB is deployed logging
by Brad Maxwell (Jira)
[ https://issues.redhat.com/browse/WFLY-10612?page=com.atlassian.jira.plugi... ]
Brad Maxwell updated WFLY-10612:
--------------------------------
Attachment: WFLY-10612.jar
> Include EJB's IIOP Binding when EJB is deployed logging
> -------------------------------------------------------
>
> Key: WFLY-10612
> URL: https://issues.redhat.com/browse/WFLY-10612
> Project: WildFly
> Issue Type: Enhancement
> Components: IIOP
> Affects Versions: 12.0.0.Final
> Reporter: Brad Maxwell
> Assignee: Tomasz Adamski
> Priority: Major
> Attachments: WFLY-10612.jar, java.policy
>
>
> It would be useful when EJBs configured with IIOP enabled or when enabled by default for all, that it log the binding for the IIOP interface as it is different from the JNDI bindings.
> <iiop enable-by-default="true" use-qualified-name="true"/>
> {code}
> INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows:
> java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean
> java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean
> java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean
> java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> {code}
> Something like this when use-qualified-name="true"
> {code}
> IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows:
> iiop-eap7/HelloSessionBean
> {code}
> or use-qualified-name="false"
> {code}
> IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows:
> HelloSessionBean
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-10612) Include EJB's IIOP Binding when EJB is deployed logging
by Brad Maxwell (Jira)
[ https://issues.redhat.com/browse/WFLY-10612?page=com.atlassian.jira.plugi... ]
Brad Maxwell updated WFLY-10612:
--------------------------------
Attachment: (was: WFLY-10612.jar)
> Include EJB's IIOP Binding when EJB is deployed logging
> -------------------------------------------------------
>
> Key: WFLY-10612
> URL: https://issues.redhat.com/browse/WFLY-10612
> Project: WildFly
> Issue Type: Enhancement
> Components: IIOP
> Affects Versions: 12.0.0.Final
> Reporter: Brad Maxwell
> Assignee: Tomasz Adamski
> Priority: Major
> Attachments: WFLY-10612.jar, java.policy
>
>
> It would be useful when EJBs configured with IIOP enabled or when enabled by default for all, that it log the binding for the IIOP interface as it is different from the JNDI bindings.
> <iiop enable-by-default="true" use-qualified-name="true"/>
> {code}
> INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows:
> java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean
> java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean
> java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean
> java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> {code}
> Something like this when use-qualified-name="true"
> {code}
> IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows:
> iiop-eap7/HelloSessionBean
> {code}
> or use-qualified-name="false"
> {code}
> IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows:
> HelloSessionBean
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-13003) Support the SameSite cookie attribute
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13003?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-13003:
------------------------------------
Fix Version/s: 19.1.0.Final
20.0.0.Beta1
> Support the SameSite cookie attribute
> -------------------------------------
>
> Key: WFLY-13003
> URL: https://issues.redhat.com/browse/WFLY-13003
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Reporter: Stuart Douglas
> Assignee: Flavia Rainone
> Priority: Major
> Fix For: 19.1.0.Final, 20.0.0.Beta1
>
>
> Chrome 80 is going to significantly change how cookies are handled, as per this notice at [1], with a bit of an explanation of what the same site attribute means at [2].
> At the moment the Servlet specification has no way of setting this particular attribute, and it is not possible to configure it via container specific configuration in WildFly at present (it can only be done by writing some Undertow specific code).
> I propose we add a same-site-cookie-attribute predicated handler to undertow, which takes an optional cookie name regex, and the value for the attribute to set.
> This would allow users to configure the SameSite attribute based on cookie name, and also potentially based on any other attributes including user agent, as it sounds like some browsers may have bugs that means this might need to be set on a per user agent basis.
> [1] https://www.chromestatus.com/feature/5088147346030592
> [2] https://web.dev/samesite-cookies-explained/
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-10612) Include EJB's IIOP Binding when EJB is deployed logging
by Brad Maxwell (Jira)
[ https://issues.redhat.com/browse/WFLY-10612?page=com.atlassian.jira.plugi... ]
Brad Maxwell updated WFLY-10612:
--------------------------------
Attachment: (was: WFLY-10612.jar)
> Include EJB's IIOP Binding when EJB is deployed logging
> -------------------------------------------------------
>
> Key: WFLY-10612
> URL: https://issues.redhat.com/browse/WFLY-10612
> Project: WildFly
> Issue Type: Enhancement
> Components: IIOP
> Affects Versions: 12.0.0.Final
> Reporter: Brad Maxwell
> Assignee: Tomasz Adamski
> Priority: Major
> Attachments: WFLY-10612.jar, java.policy
>
>
> It would be useful when EJBs configured with IIOP enabled or when enabled by default for all, that it log the binding for the IIOP interface as it is different from the JNDI bindings.
> <iiop enable-by-default="true" use-qualified-name="true"/>
> {code}
> INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows:
> java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean
> java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean
> java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean
> java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> {code}
> Something like this when use-qualified-name="true"
> {code}
> IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows:
> iiop-eap7/HelloSessionBean
> {code}
> or use-qualified-name="false"
> {code}
> IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows:
> HelloSessionBean
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months