[JBoss JIRA] (WFLY-10833) Wildfly 13.0.0.Final deployment failed due to WELD-001409: Ambiguous dependencies for type CompensationManager with qualifiers @Default
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-10833?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFLY-10833:
---------------------------------------
Component/s: Transactions
Assignee: Tom Jenkinson (was: Jason Greene)
> Wildfly 13.0.0.Final deployment failed due to WELD-001409: Ambiguous dependencies for type CompensationManager with qualifiers @Default
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10833
> URL: https://issues.jboss.org/browse/WFLY-10833
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 13.0.0.Final
> Environment: JDK 8
> Wildfly 13.0.0.Final
> Reporter: Angela Yuan
> Assignee: Tom Jenkinson
>
> Able to deploy the same WAR and EAR to Wildfly 10.0.0.Final but not to 13.0.0.Final with the following error:
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."xxxxx.war".WeldStartService: org.jboss.msc.service.S
> tartException in service jboss.deployment.unit."fwdm-services-1.0-SNAPSHOT.war".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001409: Ambiguous dependencies for type CompensationManager with qualifiers @Default
> at injection point [UnbackedAnnotatedField] @Inject org.jboss.narayana.compensations.impl.CancelOnFailureInterceptor.compensationManager
> at org.jboss.narayana.compensations.impl.CancelOnFailureInterceptor.compensationManager(CancelOnFailureInterceptor.java:0)
> Possible dependencies:
> - Managed Bean [class org.jboss.narayana.compensations.internal.CompensationManagerImpl] with qualifiers [@Any @Default],
> - Managed Bean [class org.jboss.narayana.compensations.impl.CompensationManagerImpl] with qualifiers [@Any @Default]
> at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:386)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:290)
> at org.jboss.weld.bootstrap.Validator.validateInterceptor(Validator.java:564)
> at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:81)
> at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:79)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2888) Data Type UX - dialog enhancements: Add and Reorder
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2888?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2888:
--------------------------------
Description:
*Background*
Persona: Business analyst or Rules practitioner
Use Cases:
As a user I want to:
* Reorder both Fields and Data Types in the Data Types dialog list
* Use Case: As a DMN user I will want to be able to reorder the list of Custom data types, so that I can arrange data types such that they will offer a logical ordering of fields.
* Add list items in such a way that added Fields will be presented at the bottom of a structured list by default.
Functional considerations/ pre conditions:
* Fields will be presented at the bottom of a structured list by default.
* Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
* Drag-n-drop be evaluated with regard to accessibility.
Verification conditions:
* Scrum team and PO review.
was:
*Background*
Persona: Business analyst or Rules practitioner
Use Cases:
As a user I want to:
* Reorder both Fields and Data Types in the Data Types dialog list.
* Add list items in such a way that added Fields will be presented at the bottom of a structured list by default.
Functional considerations/ pre conditions:
* Fields will be presented at the bottom of a structured list by default.
* Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
* Drag-n-drop be evaluated with regard to accessibility.
Verification conditions:
* Scrum team and PO review.
> Data Type UX - dialog enhancements: Add and Reorder
> ----------------------------------------------------
>
> Key: DROOLS-2888
> URL: https://issues.jboss.org/browse/DROOLS-2888
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * Reorder both Fields and Data Types in the Data Types dialog list
> * Use Case: As a DMN user I will want to be able to reorder the list of Custom data types, so that I can arrange data types such that they will offer a logical ordering of fields.
> * Add list items in such a way that added Fields will be presented at the bottom of a structured list by default.
> Functional considerations/ pre conditions:
> * Fields will be presented at the bottom of a structured list by default.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> * Drag-n-drop be evaluated with regard to accessibility.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2889) Research accessibility considerations for Data Type list drag-n-drop.
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2889?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2889:
--------------------------------
Description:
Use Case: As a DMN user I will want to be able to reorder the list of Custom data types so that I can arrange data types in a logical order.
Notes:
* The Data Type dialog leverage the following PR list pattern:
https://www.patternfly.org/pattern-library/content-views/tree-list-view
* The list will need to be re-orderable, there is an open design jira to determine the interaction options for that feature.
* Design is currently being iterated upon, but last iteration wireframes are posted at: https://redhat.invisionapp.com/share/B7NEEUSV539
Verification conditions:
* Research results summarized in the jira or a linked google doc., etc.
was:
Use Case: As a DMN user I will want to be able to reorder the list of Custom data types so that I can arrange data types in a logical order.
Notes:
* The Data Type dialog leverage the following PR list pattern:
https://www.patternfly.org/pattern-library/content-views/tree-list-view
* The list will need to be re-orderable, there is an open design jira to determine the interaction options for that feature.
* Design is currently being iterated upon, but last iteration wireframes are posted at: https://redhat.invisionapp.com/share/B7NEEUSV539
> Research accessibility considerations for Data Type list drag-n-drop.
> ----------------------------------------------------------------------
>
> Key: DROOLS-2889
> URL: https://issues.jboss.org/browse/DROOLS-2889
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Sarah Rambacher
> Labels: UX, UXTeam, drools-tools
> Attachments: Screen Shot 2018-08-13 at 1.42.16 PM.png
>
>
> Use Case: As a DMN user I will want to be able to reorder the list of Custom data types so that I can arrange data types in a logical order.
> Notes:
> * The Data Type dialog leverage the following PR list pattern:
> https://www.patternfly.org/pattern-library/content-views/tree-list-view
> * The list will need to be re-orderable, there is an open design jira to determine the interaction options for that feature.
> * Design is currently being iterated upon, but last iteration wireframes are posted at: https://redhat.invisionapp.com/share/B7NEEUSV539
> Verification conditions:
> * Research results summarized in the jira or a linked google doc., etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10833) Wildfly 13.0.0.Final deployment failed due to WELD-001409: Ambiguous dependencies for type CompensationManager with qualifiers @Default
by Angela Yuan (JIRA)
Angela Yuan created WFLY-10833:
----------------------------------
Summary: Wildfly 13.0.0.Final deployment failed due to WELD-001409: Ambiguous dependencies for type CompensationManager with qualifiers @Default
Key: WFLY-10833
URL: https://issues.jboss.org/browse/WFLY-10833
Project: WildFly
Issue Type: Bug
Affects Versions: 13.0.0.Final
Environment: JDK 8
Wildfly 13.0.0.Final
Reporter: Angela Yuan
Assignee: Jason Greene
Able to deploy the same WAR and EAR to Wildfly 10.0.0.Final but not to 13.0.0.Final with the following error:
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."xxxxx.war".WeldStartService: org.jboss.msc.service.S
tartException in service jboss.deployment.unit."fwdm-services-1.0-SNAPSHOT.war".WeldStartService: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001409: Ambiguous dependencies for type CompensationManager with qualifiers @Default
at injection point [UnbackedAnnotatedField] @Inject org.jboss.narayana.compensations.impl.CancelOnFailureInterceptor.compensationManager
at org.jboss.narayana.compensations.impl.CancelOnFailureInterceptor.compensationManager(CancelOnFailureInterceptor.java:0)
Possible dependencies:
- Managed Bean [class org.jboss.narayana.compensations.internal.CompensationManagerImpl] with qualifiers [@Any @Default],
- Managed Bean [class org.jboss.narayana.compensations.impl.CompensationManagerImpl] with qualifiers [@Any @Default]
at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:386)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:290)
at org.jboss.weld.bootstrap.Validator.validateInterceptor(Validator.java:564)
at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:81)
at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:79)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:485)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10832) Determine the primary provider of Singleton Service using CLI.
by Brad Maxwell (JIRA)
Brad Maxwell created WFLY-10832:
-----------------------------------
Summary: Determine the primary provider of Singleton Service using CLI.
Key: WFLY-10832
URL: https://issues.jboss.org/browse/WFLY-10832
Project: WildFly
Issue Type: Feature Request
Components: Clustering
Affects Versions: 13.0.0.Final
Reporter: Brad Maxwell
Assignee: Paul Ferraro
Currently we do not expose any run-time metrics/statistics for singleton services , User needs to determine the primary provider of Singleton service and would like a CLI command to do so
Currently from CLI we can see that the singleton application is deployed on all the instance of the cluster , but not determine from CLI which node/instance is operating as primary provider of Singleton Service , User would like to give to his operations team a way to check that a certain application is in ha singleton among others which can be in just cluster mode.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months