[JBoss JIRA] (WFLY-12274) EJB Bean with mappedName is not binding
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-12274?page=com.atlassian.jira.plugin... ]
Cheng Fang commented on WFLY-12274:
-----------------------------------
[~jaikiran] thanks for the background info. We'll likely preserve the current behavior and may add a warning message for `mappedName` on component declaration annotation.
> EJB Bean with mappedName is not binding
> ---------------------------------------
>
> Key: WFLY-12274
> URL: https://issues.jboss.org/browse/WFLY-12274
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 16.0.0.Final, 17.0.0.Beta1, 17.0.1.Final
> Reporter: Cheng Fang
> Assignee: Cheng Fang
> Priority: Major
> Attachments: mapped-name.jar
>
>
> EJB Bean with mappedName is not binding , the mappedName is vendor specific, it is not portable, however @EJB(mappedName=...) is expecting a global JNDI path, but @Stateless(mappedName=...) does not appear to be binding anything.
> {code}
> @Stateless(name="HelloBean", mappedName="MappedHelloBean")
> public class HelloBean implements Hello {
> ...
> {code}
> {code}
> @Startup
> @Singleton
> public class TestSingleton {
> @EJB(mappedName="MappedHelloBean")
> private Hello ejb;
> ...
> {code}
> So the @EJB causes the TestSingleton to fail.
> {code}
> 22:12:55,637 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 72) MSC000001: Failed to start service jboss.deployment.unit."mapped-name.jar".component.TestSingleton.START: org.jboss.msc.service.StartException in service jboss.deployment.unit."mapped-name.jar".component.TestSingleton.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance
> ...
> Caused by: javax.ejb.EJBException: java.lang.RuntimeException: WFLYNAM0059: Resource lookup for injection failed: env/com.jboss.examples.ejb.TestSingleton/ejb
> ...
> Caused by: java.lang.RuntimeException: WFLYNAM0059: Resource lookup for injection failed: env/com.jboss.examples.ejb.TestSingleton/ejb
> ...
> Caused by: javax.naming.NamingException: WFLYNAM0062: Failed to lookup env/com.jboss.examples.ejb.TestSingleton/ejb [Root exception is java.lang.RuntimeException: javax.naming.NameNotFoundException: MappedHelloBean -- service jboss.naming.context.java.MappedHelloBean]
> ...
> Caused by: java.lang.RuntimeException: javax.naming.NameNotFoundException: MappedHelloBean -- service jboss.naming.context.java.MappedHelloBean
> ...
> Caused by: javax.naming.NameNotFoundException: MappedHelloBean -- service jboss.naming.context.java.MappedHelloBean
> ...
> {code}
> [1] https://docs.oracle.com/javaee/6/api/javax/ejb/EJB.html#mappedName()
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4102) Persist/reload Test Scenario table width/height
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-4102?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-4102:
----------------------------------
Sprint: 2019 Week 23-25 (was: 2019 Week 23-25, 2019 Week 26-28)
> Persist/reload Test Scenario table width/height
> -----------------------------------------------
>
> Key: DROOLS-4102
> URL: https://issues.jboss.org/browse/DROOLS-4102
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Yeser Amer
> Priority: Major
> Labels: ScenarioSimulation
>
> Implement a mechanism to store/restore column width ({{FactMapping}}) and row height ({{Scenario}}) for the table in Test Scenario.
> Please consider:
> - Create/save a simulation (default column width/row height in scesim)
> - Rename a simulation (it perform a save/reload)
> - Change column type (recreate the column)
> - Duplicate column (preserve same size)
> - Duplicate row (preserve same size)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-3953) DMN UX - overlay validation error reporting
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-3953?page=com.atlassian.jira.plugi... ]
Daniele Zonca commented on DROOLS-3953:
---------------------------------------
[~kkufova]
I have updated the description to better match the requirement in DMN context
> DMN UX - overlay validation error reporting
> -------------------------------------------
>
> Key: DROOLS-3953
> URL: https://issues.jboss.org/browse/DROOLS-3953
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Tao Zhu
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam, drools-tools
> Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png, ux-decision button.png, ux-decision table.png
>
>
> As user during DMN model editing, I want to see validation errors on the model in case of wrong FEEL expression or invalid decision table.
> I want to see this kind of errors in the decisions and at diagram level.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months