[
https://issues.jboss.org/browse/AS7-1927?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky reassigned AS7-1927:
----------------------------------
Assignee: David Lloyd (was: Ivo Studensky)
:)
Well, I would expect the deployment of a jboss-beans.xml with an invalid namespace to
fail. Right now it looks like the jboss-beans.xml is not processed/read at all by manual
deployment, otherwise it should fail.
Is it correct that AS7 can eat every deployment even if the deployment is not valid?
But maybe I am wrong in that the 'urn:jboss:bean-deployer:2.0' namespace is no
longer valid now.
An EAR with 'urn:jboss:bean-deployer:2.0' namespace in
META-INF/jboss-beans.xml can be deloyed to AS7 without any error
-----------------------------------------------------------------------------------------------------------------------
Key: AS7-1927
URL:
https://issues.jboss.org/browse/AS7-1927
Project: Application Server 7
Issue Type: Bug
Components: POJO
Affects Versions: 7.1.0.Alpha1
Reporter: Ivo Studensky
Assignee: David Lloyd
An ear with no longer supported 'urn:jboss:bean-deployer:2.0' namespace in
META-INF/jboss-beans.xml can be deployed to AS7 without any error. I tried to deploy it
via command line copy and via web admin console. Both of them passed which is weird,
because the same ear failed to deploy by Arquillian.
If I modified the namespace to 'urn:jboss:pojo:7.0' then deployment by Arquillian
passed too.
It seems like META-INF/jboss-beans.xml is not fully processed if deployed by command line
copy or by web admin console.
Note: it was tried with the latest master of AS7.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira