[jboss-jira] [JBoss JIRA] (AS7-5452) env-entry-type should not be mandatory
[
https://issues.jboss.org/browse/AS7-5452?page=com.atlassian.jira.plugin.s...
]
Cheng Fang edited comment on AS7-5452 at 8/30/12 7:41 AM:
----------------------------------------------------------
This is from the same javaee_6.xsd ( http://java.sun.com/xml/ns/javaee/javaee_6.xsd ),
the description of element <env-entry>:
{quote}
The env-entryType is used to declare an application's
environment entry. The declaration consists of an optional
description, the name of the environment entry, a type
(optional if the value is injected, otherwise required), and
an optional value.
{quote}
This is consistent with what you've quoted above for <env-entry-type>.
This is the same issue as AS7-1876, which was fixed before. So we need to keep this fix
in new versions as well.
AS7-1876 has a test app attached and can be used to reproduce the problem.
was (Author: cfang):
This is from the same javaee_6.xsd ( http://java.sun.com/xml/ns/javaee/javaee_6.xsd ),
the description of element <env-entry>:
{quote}
The env-entryType is used to declare an application's
environment entry. The declaration consists of an optional
description, the name of the environment entry, a type
(optional if the value is injected, otherwise required), and
an optional value.
{quote}
This is consistent with what you've quoted above for <env-entry-type>.
This is the same issue as AS7-1876, which was fixed before. So we need to keep this fix
in new versions as well.
env-entry-type should not be mandatory
--------------------------------------
Key: AS7-5452
URL: https://issues.jboss.org/browse/AS7-5452
Project: Application Server 7
Issue Type: Bug
Components: EE
Affects Versions: 7.2.0.Alpha1
Reporter: Cheng Fang
Assignee: David Lloyd
similar to issue AS7-1876, but I couldn't reopen it.
My app declares <env-entry> without <env-entry-type>, but also injects the
same resource into java class with the correct field type. It failed to deploy:
{noformat}
21:57:58,318 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC00001:
Failed to start service jboss.deployment.unit."ENVTestAS7.jar".POST_MODULE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."ENVTestAS7.jar".POST_MODULE: JBAS018733: Failed to
process phase POST_MODULE of deployment "ENVTestAS7.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123)
[jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[classes.jar:1.6.0_33]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[classes.jar:1.6.0_33]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_33]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011032:
Could not determine type for <env-entry> java:comp/env/myEntry please specify the
<env-entry-type>.
at
org.jboss.as.ee.component.deployers.ResourceReferenceProcessor.getEnvironmentEntries(ResourceReferenceProcessor.java:267)
at
org.jboss.as.ee.component.deployers.ResourceReferenceProcessor.processDescriptorEntries(ResourceReferenceProcessor.java:71)
at
org.jboss.as.ee.component.deployers.AbstractDeploymentDescriptorBindingsProcessor.deploy(AbstractDeploymentDescriptorBindingsProcessor.java:100)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116)
[jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
... 5 more
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira