2 Replies Latest reply on Apr 15, 2008 2:23 AM by starksm64

    EJBTHREE-1278, fixing jbossas5/mc integration code

    starksm64
    starksm64 Apr 14, 2008 11:54 AM

      The current direct installation of the ejb container into the mc kernel bypasses the depedency failure error reporting mechanism. We need to update the integration to:

      1. Have jbossas integration provide an implementation of org.jboss.ejb3.KernelAbstraction

      2. Update the org.jboss.ejb3.DeploymentUnit

      The KernelAbstraction would simply add the AbstractBeanMetaData to the unit as an attachment so it would be properly integrated into the jbossas deployers.

      • 3637 Views
      • Tags:
        • 1. Re: EJBTHREE-1278, fixing jbossas5/mc integration code
          starksm64
          starksm64 Apr 15, 2008 2:22 AM (in response to starksm64)

          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);


          and unsatisfied deployments show an error when the new JBossASKernel implementation of KernelAbstraction is used. We need a new release of ejb3 core to allow the server code to be in synch.


            • Actions
          • 2. Re: EJBTHREE-1278, fixing jbossas5/mc integration code
            starksm64
            starksm64 Apr 15, 2008 2:23 AM (in response to starksm64)

            For example:

            11:32:52,683 WARN [MainDeployer] Failed to deploy: file:/Users/svn/JBossHead/jboss-head/testsuite/output/lib/refs.ear
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

*** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}

jboss.j2ee:ear=refs.ear,jar=refs-ejb2.jar,name=StatelessBean2,service=EJB3
 -> <UNKNOWN jboss.j2ee:ear=refs.ear,jar=refs-ejb2.jar,name=StatelessBean2,service=EJB3>{Described:** UNRESOLVED Demands 'jboss.j2ee:ear=refs.ear,jar=StatelessBean,name=refs-ejb.jar,service=EJB3' **}


*** CONTEXTS IN ERROR: Name -> Error

<UNKNOWN jboss.j2ee:ear=refs.ear,jar=refs-ejb2.jar,name=StatelessBean2,service=EJB3> -> ** UNRESOLVED Demands 'jboss.j2ee:ear=refs.ear,jar=StatelessBean,name=refs-ejb.jar,service=EJB3' **


 at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:806)
 at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:752)



              • Actions