[JBoss JIRA] (WFLY-11870) abstract classes with @EJB annotation included in libraries will cause deployment failures
by Tomas Hofman (Jira)
[ https://issues.jboss.org/browse/WFLY-11870?page=com.atlassian.jira.plugin... ]
Tomas Hofman reassigned WFLY-11870:
-----------------------------------
Assignee: Tomas Hofman (was: Brian Stansberry)
> abstract classes with @EJB annotation included in libraries will cause deployment failures
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-11870
> URL: https://issues.jboss.org/browse/WFLY-11870
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Server
> Reporter: Wolf-Dieter Fink
> Assignee: Tomas Hofman
> Priority: Major
> Labels: Regression, deployment, injection
> Attachments: ReproducerInjection.zip
>
>
> If an archive include libraries with interfaces and abstract classes the deployment will fail if there are annotations for injection like @EJB.
> Only if the injected EJB is available within the deployed file (or any other deployment) it is possible to deploy it.
> As the abstract class can not cause any instance the failure does not make sense.
> Also former versions are deploying the same file correct and work fine.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 6 months
[JBoss JIRA] (DROOLS-3702) [Stunner] Arrows are incorrectly positioned when save-open diagram
by Kirill Gaevskii (Jira)
[ https://issues.jboss.org/browse/DROOLS-3702?page=com.atlassian.jira.plugi... ]
Kirill Gaevskii commented on DROOLS-3702:
-----------------------------------------
Hi [~roger600], issue mentioned by you looks different. I think DMN editor is not preserving sequence flows position after save/reopen. In BPMN Designer it affects only Preview panel and always, no need to save and reopen.
> [Stunner] Arrows are incorrectly positioned when save-open diagram
> ------------------------------------------------------------------
>
> Key: DROOLS-3702
> URL: https://issues.jboss.org/browse/DROOLS-3702
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Daniel José dos Santos
> Assignee: Michael Anstis
> Priority: Major
> Labels: Stunner
> Attachments: process-designer-connectors-magnets-issues.png, weird_arrow.gif
>
>
> 1. Add a `Decision Node`
> 2. Add a `Input Data Node` bellow `Decision Node`
> 3. Connect `Input Data Node` to `Decision Node`
> 4. Save
> 5. Close
> 6. Open againThe arrow from `Input Data Node` to `Decision Node` will be at right of the `Decision Node` and if you move the `Input Data Node`, the arrow is not repositioned.
> I noticed this in DMN Showcase and in drools-wb.
> And if you add a new `Decision Node` and a new `Input Data Node`, without save and close, it behaves as expected.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 6 months
[JBoss JIRA] (DROOLS-3702) [Stunner] Arrows are incorrectly positioned when save-open diagram
by Kirill Gaevskii (Jira)
[ https://issues.jboss.org/browse/DROOLS-3702?page=com.atlassian.jira.plugi... ]
Kirill Gaevskii reassigned DROOLS-3702:
---------------------------------------
Assignee: Michael Anstis (was: Roger Martinez)
> [Stunner] Arrows are incorrectly positioned when save-open diagram
> ------------------------------------------------------------------
>
> Key: DROOLS-3702
> URL: https://issues.jboss.org/browse/DROOLS-3702
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Daniel José dos Santos
> Assignee: Michael Anstis
> Priority: Major
> Labels: Stunner
> Attachments: process-designer-connectors-magnets-issues.png, weird_arrow.gif
>
>
> 1. Add a `Decision Node`
> 2. Add a `Input Data Node` bellow `Decision Node`
> 3. Connect `Input Data Node` to `Decision Node`
> 4. Save
> 5. Close
> 6. Open againThe arrow from `Input Data Node` to `Decision Node` will be at right of the `Decision Node` and if you move the `Input Data Node`, the arrow is not repositioned.
> I noticed this in DMN Showcase and in drools-wb.
> And if you add a new `Decision Node` and a new `Input Data Node`, without save and close, it behaves as expected.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 6 months
[JBoss JIRA] (WFLY-11858) [Wildfly16] CDI fails to inject InitialContext during startup
by Ondrej Chaloupka (Jira)
[ https://issues.jboss.org/browse/WFLY-11858?page=com.atlassian.jira.plugin... ]
Ondrej Chaloupka commented on WFLY-11858:
-----------------------------------------
[~rakcheru] we already made the release of Narayana `5.9.5.Final` with the fix and the PR for the component in the new version being involved is created for WildFly (WFLY-11917). WildFly release is done quarterly (http://lists.jboss.org/pipermail/wildfly-dev/2017-December/006250.html) and micro releases are done only in case of some blocker issue.
I assume you would need take the WFLY16 and update the Narayana there or wait for the WFLY17 to be released (I expect the WFLY-11917 will be merged till that time).
> [Wildfly16] CDI fails to inject InitialContext during startup
> -------------------------------------------------------------
>
> Key: WFLY-11858
> URL: https://issues.jboss.org/browse/WFLY-11858
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Transactions
> Affects Versions: 16.0.0.Final
> Reporter: Rakesh Cherukuri
> Assignee: Matěj Novotný
> Priority: Major
> Attachments: stacktrace.log
>
>
> We are in the process of upgrading from 14.0.1.Final. While Wildfly 15.0.1 works fine, 16.0.0.Final is intermittently (3 out of 5 times) failing to start with following error
> _WELD-001334: Unsatisfied dependencies for type InitialContext with qualifiers_
> In our application, a bootstrap servlet startsup services (Stateless EJBs) during server startup. During this process the server fails to start with above error.
> Basically CDI is not able to find the appropriate InitialContext bean *intermittently*. This is not failing in our application code but in the wildfly libraries itself.
> Any pointers on this will be helpful. Don't want to end up with startup issues in stage/production :)
> Unfortunately my efforts to come up with a simplified maven module to showcase the error didn't succeed. So, please let me know if any further information is required and i will be glad to fill it in.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 6 months