[JBoss JIRA] (DROOLS-4073) Scenario throw an error for columns bound to collection field
by Yeser Amer (Jira)
[ https://issues.jboss.org/browse/DROOLS-4073?page=com.atlassian.jira.plugi... ]
Yeser Amer reassigned DROOLS-4073:
----------------------------------
Assignee: Yeser Amer (was: Daniele Zonca)
> Scenario throw an error for columns bound to collection field
> -------------------------------------------------------------
>
> Key: DROOLS-4073
> URL: https://issues.jboss.org/browse/DROOLS-4073
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.23.0.Final
> Reporter: Jozef Marko
> Assignee: Yeser Amer
> Priority: Critical
> Labels: ScenarioSimulation
> Attachments: Screenshot from 2019-05-23 14-40-23.png, collections.zip
>
>
> If the column is bound to a collection field and user tries to edit some data cell, an error is thrown.
> The issue was spotted during DROOLS-3855 review however not sure if that one is the root cause.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (ELY-1784) Allow using custom executors in SaslAuthenticationFactory
by Farah Juma (Jira)
[ https://issues.jboss.org/browse/ELY-1784?page=com.atlassian.jira.plugin.s... ]
Farah Juma reassigned ELY-1784:
-------------------------------
Assignee: Ashley Abdel-Sayed
> Allow using custom executors in SaslAuthenticationFactory
> ---------------------------------------------------------
>
> Key: ELY-1784
> URL: https://issues.jboss.org/browse/ELY-1784
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: SASL
> Reporter: Tristan Tarrant
> Assignee: Ashley Abdel-Sayed
> Priority: Major
>
> The SaslAuthenticationFactory.Builder uses a hardcoded ScheduledExecutor which adds an implicit dependency on jboss-threads. It would be nice if the builder allowed a user-provided executor.
> Discussion from Zulip:
> {quote}
> Tristan Tarrant: @Darran Lofthouse I have a request: in https://github.com/wildfly-security/wildfly-elytron/blob/1.x/auth/server/... would it be possible to pass in a custom scheduled executor and possibly forgo the dependency on jboss-threads. I have my own executors/pool and I'd rather use those instead.
> Darran Lofthouse: @Farah Juma FYI ^^^
> @Tristan Tarrant Sounds reasonable, we may need to look at how the SecurityDomain loads the class ScheduledExecutorServiceProvider as I suspect you don't want the JBossThreads impls loading at all.
> Farah Juma: +1, sounds ok
> Farah Juma: @Tristan Tarrant Please create an ELY JIRA issue to track this
> Darran Lofthouse: I suspect in other cases it will be beneficial to drop the JBoss Threads dependency
> David Lloyd: probably in most cases; it just thinly wraps the standard ScheduledThreadPoolExecutor
> Darran Lofthouse: So maybe better then for Elytron to use the standard ScheduledThreadPoolExector add an override as Tristan suggests and then if anyone really wants JBossThreads they can add it in using the override.
> {quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-7395) Allow to provide deployment dependency to JNDI resource
by Andrew Schmidt (Jira)
[ https://issues.jboss.org/browse/WFLY-7395?page=com.atlassian.jira.plugin.... ]
Andrew Schmidt edited comment on WFLY-7395 at 5/23/19 10:50 AM:
----------------------------------------------------------------
Any update on this issue? We are experiencing the same problem.
Is there possibly a workaround?
was (Author: gabboflabbo):
Any update on this issue? We are experience the same problem.
Is there possibly a workaround?
> Allow to provide deployment dependency to JNDI resource
> -------------------------------------------------------
>
> Key: WFLY-7395
> URL: https://issues.jboss.org/browse/WFLY-7395
> Project: WildFly
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 10.1.0.Final
> Reporter: Miroslav Novak
> Assignee: Jason Greene
> Priority: Major
> Labels: user_experience
>
> For JBoss AS 6 there was ejb annotation @org.jboss.annotation.ejb.Depends which allowed to set dependency to JNDI resource. Currently there seems to be no replacement in Wildfly 10.x
> For example if EJB contains dependency to queue registered in JNDI:
> {code}
> @Resource(mappedName = "java:/jms/queue/OutQueue")
> private Queue outQueue;
> {code}
> then it would not get deployed when OutQueue is not present. Purpose of this feature request is to add possibility to provide such dependency in the way as @org.jboss.annotation.ejb.Depends did.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-7395) Allow to provide deployment dependency to JNDI resource
by Andrew Schmidt (Jira)
[ https://issues.jboss.org/browse/WFLY-7395?page=com.atlassian.jira.plugin.... ]
Andrew Schmidt commented on WFLY-7395:
--------------------------------------
Any update on this issue? We are experience the same problem.
Is there possibly a workaround?
> Allow to provide deployment dependency to JNDI resource
> -------------------------------------------------------
>
> Key: WFLY-7395
> URL: https://issues.jboss.org/browse/WFLY-7395
> Project: WildFly
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 10.1.0.Final
> Reporter: Miroslav Novak
> Assignee: Jason Greene
> Priority: Major
> Labels: user_experience
>
> For JBoss AS 6 there was ejb annotation @org.jboss.annotation.ejb.Depends which allowed to set dependency to JNDI resource. Currently there seems to be no replacement in Wildfly 10.x
> For example if EJB contains dependency to queue registered in JNDI:
> {code}
> @Resource(mappedName = "java:/jms/queue/OutQueue")
> private Queue outQueue;
> {code}
> then it would not get deployed when OutQueue is not present. Purpose of this feature request is to add possibility to provide such dependency in the way as @org.jboss.annotation.ejb.Depends did.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3976) [DMN Designer] edit cell by enter in Context, Function and Invocation
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3976?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3976:
--------------------------------
Description:
Issue revealed during DROOLS-3895 review, however it is probaly caused by DROOLS-3438.
User can not start edit mode by *Key.Enter* press if he wants to edit nested *Literal Expression* grid and this nested grid has parent *Context*, *Function* or *Invocation* grid.
h3. Acceptance test
||#||Edit cell using mouse||Edit cell using keyboard||
|Literal Expression grid|||
|Context grid|||
|Invocation grid|||
|Relation grid|||
|Decision table grid|||
was:
Issue revealed during DROOLS-3895 review, however it is probaly caused by DROOLS-3438.
User can not start edit mode by *Key.Enter* press if he wants to edit nested *Literal Expression* grid and this nested grid has parent *Context*, *Function* or *Invocation* grid.
> [DMN Designer] edit cell by enter in Context, Function and Invocation
> ---------------------------------------------------------------------
>
> Key: DROOLS-3976
> URL: https://issues.jboss.org/browse/DROOLS-3976
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.21.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
>
> Issue revealed during DROOLS-3895 review, however it is probaly caused by DROOLS-3438.
> User can not start edit mode by *Key.Enter* press if he wants to edit nested *Literal Expression* grid and this nested grid has parent *Context*, *Function* or *Invocation* grid.
> h3. Acceptance test
> ||#||Edit cell using mouse||Edit cell using keyboard||
> |Literal Expression grid|||
> |Context grid|||
> |Invocation grid|||
> |Relation grid|||
> |Decision table grid|||
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3976) [DMN Designer] edit cell by enter in Context, Function and Invocation
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3976?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3976:
--------------------------------
Description:
Issue revealed during DROOLS-3895 review, however it is probaly caused by DROOLS-3438.
User can not start edit mode by *Key.Enter* press if he wants to edit nested *Literal Expression* grid and this nested grid has parent *Context*, *Function* or *Invocation* grid.
h3. Acceptance test
||#||Edit cell using mouse||Edit cell using keyboard||
|Literal Expression grid|(?)|(?)|
|Context grid|||
|Invocation grid|||
|Relation grid|||
|Decision table grid|||
was:
Issue revealed during DROOLS-3895 review, however it is probaly caused by DROOLS-3438.
User can not start edit mode by *Key.Enter* press if he wants to edit nested *Literal Expression* grid and this nested grid has parent *Context*, *Function* or *Invocation* grid.
h3. Acceptance test
||#||Edit cell using mouse||Edit cell using keyboard||
|Literal Expression grid|||
|Context grid|||
|Invocation grid|||
|Relation grid|||
|Decision table grid|||
> [DMN Designer] edit cell by enter in Context, Function and Invocation
> ---------------------------------------------------------------------
>
> Key: DROOLS-3976
> URL: https://issues.jboss.org/browse/DROOLS-3976
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.21.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
>
> Issue revealed during DROOLS-3895 review, however it is probaly caused by DROOLS-3438.
> User can not start edit mode by *Key.Enter* press if he wants to edit nested *Literal Expression* grid and this nested grid has parent *Context*, *Function* or *Invocation* grid.
> h3. Acceptance test
> ||#||Edit cell using mouse||Edit cell using keyboard||
> |Literal Expression grid|(?)|(?)|
> |Context grid|||
> |Invocation grid|||
> |Relation grid|||
> |Decision table grid|||
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months