[jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1278) Ejb3Deployments are not properly installed into mc to allow for dependency error reporting
[ http://jira.jboss.com/jira/browse/EJBTHREE-1278?page=all ]
Scott M Stark updated EJBTHREE-1278:
------------------------------------
JBoss Forum Reference:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=133687
The DeploymentUnit now has attachment support:
public interface DeploymentUnit
{
Object addAttachment(String name, Object attachment);
throws IllegalArgumentException for a null name
Object getAttachment(String name);
Object removeAttachment(String name);
...
and the KernelAbstraction install now has a DeploymentUnit parameter:
public interface KernelAbstraction extends ClientKernelAbstraction
{
public void install(String name, DependencyPolicy dependencies, DeploymentUnit unit,
Object service);
Ejb3Deployments are not properly installed into mc to allow for
dependency error reporting
------------------------------------------------------------------------------------------
Key: EJBTHREE-1278
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1278
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: AS 5.0.0.Beta4
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: AS 5.0.0.CR1
The current direct installation of the ejb3 beans into the mc kernel bypasses the
dependency error reporting mechanism associated with the deployers. All that should be
happening is that the AbstractBeanMetaData that described the bean be added as an
attachment to the deployment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira