[JBoss Microcontainer Development POJO Server] - Implementing a non-flat deployment for Weld Integration
by Flavia Rainone
Flavia Rainone [http://community.jboss.org/people/flavia.rainone%40jboss.com] created the discussion
"Implementing a non-flat deployment for Weld Integration"
To view the discussion, visit: http://community.jboss.org/message/541531#541531
--------------------------------------------------------------
This thread is for https://jira.jboss.org/jira/browse/WELDINT-1 WELDINT-1.
Taking a look at how the deployers are implemented today, I figured I should start by creating a non-flat version of WeldDiscoveryEnvironment first, so we could have a new environment input fot the new non-flat Deployment implementation.
There a few assumptions I'm making right now that I would like to validate:
- the deployment continues to exist per top level only, the only difference we are going to have is in the BeanDeploymentArchives (BDAs)
- if Deployment.loadBeanDeploymentArchive requests for a non-existing BDA, I should search for all archives in the deployment that are not currently BDAs. If one archive containing the requested class is found, I create a BDA for it and return it.
If the assumptions above are correct, the main question I have right now regards two different deployments that can see each other. So, in the scenario described by the Deployment interface javadoc example, whereas we have ejb-jar A and ear B. This is going to be translated in two different deployments, each one containg one or more BDAs (in the case of the ejb-jar, one BDA only). Since those BDAs can see each other, there must be a way for me to reach Deployment A BDAs from Deployment B BDAs. Is there some SPI in the current implementation of weld integration that supports that?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/541531#541531]
Start a new discussion in JBoss Microcontainer Development POJO Server at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 8 months
Re: [jboss-user] [JBoss Microcontainer Development] - ClassPool bootstrap refactoring
by Kabir Khan
Kabir Khan [http://community.jboss.org/people/kabir.khan%40jboss.com] replied to the discussion
"ClassPool bootstrap refactoring"
To view the discussion, visit: http://community.jboss.org/message/541501#541501
--------------------------------------------------------------
I have modified JBoss AOP and my local bootstrap/aop.xml to understand the new classpool setup. AS boots up properly with this and all the aop AS testsuite passes apart from ScopedWovenDependencyTestCase and NotWovenScopedDependencyTestCase. I have reproduced the problem I see for those in kernel with the following test
public void testInstallAndUninstallDependencyWithExtraState() throws Throwable
{
getKernel().getController().addState(ControllerState.newState(), ControllerState.INSTALLED);
installAndUninstallDependencyWithExtraState();
//context2 goes in scoped controller and depends on context1
ControllerContext context2 = assertInstall(offSetNumber(1), "Name2", ControllerState.INSTANTIATED);
//context1 goes in main controller
ControllerContext context1 = assertInstall(offSetNumber(0), "Name1", ControllerState.INSTALLED);
context1 = assertContext("Name1");
context2 = assertContext("Name2");
assertUninstall("Name1"); //Gives error
assertContext("Name2", ControllerState.INSTANTIATED);
assertUninstall("Name2");
assertNotInstalled("Name1");
assertNotInstalled("Name2");
}
The error is
> 1357 WARN [AbstractKernelController] Error uninstalling from Installed: name=Name2 state=Installed
>
> java.lang.NullPointerException
>
> at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1632)
>
> at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1476)
>
> at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1541)
>
> at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1476)
>
> at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:760)
>
> at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:673)
>
> at org.jboss.test.kernel.dependency.support.TestUtil.uninstall(TestUtil.java:110)
>
> at org.jboss.test.kernel.dependency.support.ScopedTestUtil.uninstall(ScopedTestUtil.java:81)
>
> at org.jboss.test.kernel.dependency.test.OldAbstractKernelDependencyTest.uninstall(OldAbstractKernelDependencyTest.java:118)
>
> at org.jboss.test.kernel.dependency.test.OldAbstractKernelDependencyTest.assertUninstall(OldAbstractKernelDependencyTest.java:151)
>
> at org.jboss.test.kernel.dependency.test.ExtraStateTestCase.testInstallAndUninstallDependencyWithExtraState(ExtraStateTestCase.java:95)
>
>
It is getting confused somewhere about the ControllerStateModel.ControllerStateWrappers
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/541501#541501]
Start a new discussion in JBoss Microcontainer Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 8 months