[Design the new POJO MicroContainer] - Re: Abstractions again - MDR - sigh!
by adrian＠jboss.org
I'm going to delete jboss cache from the jboss-mdr project.
If you want to create a seperate project to implement CacheFactory
on top of JBossCache then go ahead.
It's a good job I was awake while trying to rebuild jboss-mdr:
| [INFO] ------------------------------------------------------------------------
| [INFO] Building JBoss MetaData Repository
| [INFO] task-segment: [clean, install]
| [INFO] ------------------------------------------------------------------------
| [INFO] [clean:clean]
| [INFO] Deleting directory /home/ejort/jboss-mdr/target
| [INFO] [resources:resources]
| [INFO] Using default encoding to copy filtered resources.
| [INFO] snapshot org.jboss.cache:jbosscache-common-parent:1.3-SNAPSHOT: checking for updates from repository.jboss.org
| [INFO] snapshot org.jboss.cache:jbosscache-common-parent:1.3-SNAPSHOT: checking for updates from snapshots.jboss.org
| [INFO] snapshot org.jboss.cache:jbosscache-support:1.3-SNAPSHOT: checking for updates from repository.jboss.org
| [INFO] snapshot org.jboss.cache:jbosscache-support:1.3-SNAPSHOT: checking for updates from snapshots.jboss.org
| Downloading: http://repository.jboss.org/maven2/org/jboss/jboss-common-core/2.2.3.GA/j...
| 3K downloaded
| Downloading: http://repository.jboss.org/maven2/org/jboss/javaee/jboss-javaee/5.0.0.Be...
| 270K downloaded
|
| [INFO] ------------------------------------------------------------------------
| [INFO] Building JBoss MetaData Repository
| [INFO] task-segment: [dependency:list]
| [INFO] ------------------------------------------------------------------------
| [INFO] [dependency:list]
| [INFO]
| [INFO] The following files have been resolved:
| [INFO] commons-logging:commons-logging:jar:1.0.4:compile
| [INFO] jgroups:jgroups:jar:2.6.2:compile (WRONG!!!!!!!!!)
| [INFO] junit:junit:jar:4.4:test
| [INFO] org.jboss:javassist:jar:3.7.1.GA:compile
| [INFO] org.jboss:jboss-common-core:jar:2.2.5.GA:compile
| [INFO] org.jboss:jboss-reflect:jar:2.0.0.Beta12:compile
| [INFO] org.jboss:jboss-test:jar:1.0.5.GA:test
| [INFO] org.jboss.cache:jbosscache-core:jar:2.1.1.GA:compile (WRONG!!!!!!!!!)
| [INFO] org.jboss.javaee:jboss-javaee:jar:5.0.0.Beta3:compile (WRONG!!!!!!)
| [INFO] org.jboss.logging:jboss-logging-spi:jar:2.0.5.GA:compile
|
I'm also going to deploy the updated snapshot into the repository
so the MC project builds.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162816#4162816
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162816
17 years, 9 months
[Design of AOP on JBoss (Aspects/JBoss)] - ejb3 aop config not getting undeployed correctly
by adrian＠jboss.org
If you start jboss then run smoke-tests-raw in jboss-head
you get the following error message during server shutdown.
Looks like the ejb3 config is not getting undeployed properly:
| 11:56:49,788 WARN [AspectDeployer] Error undeploying xml ejb3-interceptors-aop.xml from org.jboss.aop.AspectManager@1b2c86e
| java.lang.RuntimeException: java.lang.IllegalStateException: BaseClassLoader@ea520f{vfszip:/home/ejort/jboss-head/testsuite/output/lib/simple-session.jar} classLoader is not connected to a domain (probably undeployed?) for class org.jboss.ejb3.annotation.SecurityDomain
| at org.jboss.aop.pointcut.Util.matchesClassExpr(Util.java:137)
| at org.jboss.aop.pointcut.MethodMatcher.matchesClass(MethodMatcher.java:264)
| at org.jboss.aop.pointcut.MethodMatcher.matches(MethodMatcher.java:106)
| at org.jboss.aop.pointcut.MethodMatcher.visit(MethodMatcher.java:100)
| at org.jboss.aop.pointcut.ast.ASTMethod.jjtAccept(ASTMethod.java:44)
| at org.jboss.aop.pointcut.ExecutionMethodMatcher.visit(ExecutionMethodMatcher.java:58)
| at org.jboss.aop.pointcut.ast.ASTExecution.jjtAccept(ASTExecution.java:37)
| at org.jboss.aop.pointcut.MatcherHelper.visit(MatcherHelper.java:89)
| at org.jboss.aop.pointcut.MatcherHelper.matches(MatcherHelper.java:83)
| at org.jboss.aop.pointcut.PointcutExpression.matchesExecution(PointcutExpression.java:119)
| at org.jboss.aop.Advisor.resolveMethodPointcut(Advisor.java:1149)
| at org.jboss.aop.ClassAdvisor.resolvePointcuts(ClassAdvisor.java:700)
| at org.jboss.aop.ClassAdvisor.updateInterceptorChains(ClassAdvisor.java:629)
| at org.jboss.aop.ClassAdvisor.doRebuildInterceptors(ClassAdvisor.java:1137)
| at org.jboss.aop.ClassAdvisor$RebuildInterceptorsAction$2.rebuildInterceptors(ClassAdvisor.java:2358)
| at org.jboss.aop.ClassAdvisor.rebuildInterceptors(ClassAdvisor.java:1117)
| at org.jboss.aop.ClassAdvisor.removeAdviceBindings(ClassAdvisor.java:427)
| at org.jboss.aop.AspectManager.removeBindings(AspectManager.java:1422)
| at org.jboss.aop.Domain.removeBindings(Domain.java:198)
| at org.jboss.aop.AspectXmlLoader.bulkUndeploy(AspectXmlLoader.java:1220)
| at org.jboss.aop.AspectXmlLoader.undeployDomain(AspectXmlLoader.java:1091)
| at org.jboss.aop.AspectXmlLoader.undeployTopElements(AspectXmlLoader.java:1305)
| at org.jboss.aop.AspectXmlLoader.undeployXML(AspectXmlLoader.java:1209)
| at org.jboss.aop.deployers.AspectDeployer.undeployXml(AspectDeployer.java:205)
| at org.jboss.aop.deployers.AspectDeployer.undeployXml(AspectDeployer.java:189)
| at org.jboss.aop.deployers.AspectDeployer.undeploy(AspectDeployer.java:134)
| at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internalUndeploy(AbstractVFSRealDeployer.java:54)
| at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.undeploy(AbstractRealDeployer.java:112)
| at org.jboss.deployers.plugins.deployers.DeployerWrapper.undeploy(DeployerWrapper.java:197)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doUninstallParentLast(DeployersImpl.java:1189)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.uninstall(DeployersImpl.java:1144)
| at org.jboss.dependency.plugins.AbstractControllerContext.uninstall(AbstractControllerContext.java:354)
| at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:1406)
| at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1064)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:677)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:455)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:510)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.unload(ProfileServiceBootstrap.java:371)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.unloadProfile(ProfileServiceBootstrap.java:332)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.shutdown(ProfileServiceBootstrap.java:160)
| at org.jboss.bootstrap.AbstractServerImpl.shutdownServer(AbstractServerImpl.java:508)
| at org.jboss.bootstrap.AbstractServerImpl$ShutdownHook.run(AbstractServerImpl.java:827)
| Caused by: java.lang.IllegalStateException: BaseClassLoader@ea520f{vfszip:/home/ejort/jboss-head/testsuite/output/lib/simple-session.jar} classLoader is not connected to a domain (probably undeployed?) for class org.jboss.ejb3.annotation.SecurityDomain
| at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:723)
| at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:372)
| at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
| at org.jboss.ejb3.metadata.annotation.AnnotationRepositoryToMetaData.loadClass(AnnotationRepositoryToMetaData.java:209)
| at org.jboss.ejb3.metadata.annotation.AnnotationRepositoryToMetaData.hasClassAnnotation(AnnotationRepositoryToMetaData.java:328)
| at org.jboss.aop.Advisor.hasAnnotation(Advisor.java:603)
| at org.jboss.aop.Advisor.hasAnnotation(Advisor.java:569)
| at org.jboss.aop.pointcut.Util.matchesClassExpr(Util.java:115)
| ... 42 more
|
Or is this an ejb3 issue?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162797#4162797
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162797
17 years, 9 months
[Design the new POJO MicroContainer] - Re: JBMICROCONT-309; aliases and scoping
by alesj
I've added this
| public interface GraphController
| {
| /**
| * Get the context.
| *
| * @param name the context name
| * @param state the required state
| * @param info the seatch info
| * @return found context or null if not available
| * @throws Throwable for any error
| */
| ControllerContext getContext(Object name, ControllerState state, SearchInfo info) throws Throwable;
|
where normally Controller(Impl) would implement this interface.
And then decide on passed SearchInfo param what to do.
e.g. implement the SearchInfo::type itself - due to some private/protected modifiers, internal info
or let SearchInfo's strategy handle the lookup.
In my current impl, I let strategy handle all different lookups.
| DEFAULT(new DefaultSearchInfoWrapper()),
| LOCAL(new LocalLookupStrategy()),
| TOP(new TopLevelLookupStrategy()),
| PARENT(new ParentOnlyLookupStrategy()),
| DEPTH(new DepthLookupStrategy()),
| LEAVES(new LeavesFirstLookupStrategy()),
| WIDTH(new WidthLookupStrategy()),
| CHILD_ONLY_DEPTH(new ChildrenOnlyDepthLookupStrategy()),
| CHILD_ONLY_LEAVES(new ChildrenOnlyLeavesFirstLookupStrategy()),
| CHILD_ONLY_WIDTH(new ChildrenOnlyWidthLookupStrategy());
|
But I still don't see where to pass-in this search type info?
I could add new annotation (@SearchType(Search)), which I would only handle in my annotation plugins, but not in XML (too much hassle to get ValueMetaData owner for this simple use case).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162794#4162794
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162794
17 years, 9 months