[
https://issues.jboss.org/browse/WFLY-3625?page=com.atlassian.jira.plugin....
]
Lyle Wang commented on WFLY-3625:
---------------------------------
Source code see "TestJMX.java" and "TestJMXMBean.java" in the
attachment, we use an invalid JNDI name to "lookup" the @Resource
[lookup="java:global:/" +] , which should be [lookup="java:global/"
+]
@Resources //EAP6
(
{
@Resource(name="java:jboss/" +
TestJMXMBean.JNDI_NAME,
lookup="java:global:/" +
"dsc" + '/' +
"tpapps-common-testdeploy" + '/' +
"TestJMX" + '!' +
TestJMXMBean.JNDI_NAME
)
}
)
Inconsistent deployment status when deploy an EJB containing wrong
dependencies
-------------------------------------------------------------------------------
Key: WFLY-3625
URL:
https://issues.jboss.org/browse/WFLY-3625
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Server
Affects Versions: 8.1.0.Final
Reporter: Lyle Wang
Assignee: Jason Greene
Attachments: WFLY-3625.zip
On deploying an EJB (in exploded ear) which has wrong @Resource/"lookup" JNDI
names, it gives ERROR log. The marker file is changed to "***.ear.failed", but
in web console "http://localhost:9990" the deployment is displayed in
"Manage Deployments" page and shows deployed.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)