November 2006 - jboss-dev-forums - Jboss List Archives

[Design of POJO Server] - Re: @JMX aspect and aop/mc integration

by kabir.khan＠jboss.com

"bstansberry(a)jboss.com" wrote : To express my gratitude, here's another one ;-) LOL - I shall attempt to fix View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985625#3985625 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985625

19 years, 5 months

1
0
0 / 0

[Design of JBoss Wiki] - Re: Cannot install JBoss Wiki!! Help Required!

by jeff0672

I too am having the same issue. Brand new jems-install based installation. 4.05 GA, 2.4, EJB3 RC9 Compiles with no errors using maven 1.0.2. Installs by default into $jbossdir/server/all/deploy and is ignored on startup of jboss with run.sh -c default. If I copy over the wiki.ear file to $jbossdir/server/default/deploy I get the same errors as the original poster. Any help or clarification of the install instructions would be appreciated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985622#3985622 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985622

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: EJB References

by bill.burke＠jboss.com

I hope EjbUtil50 is based on the EJB reference stuff I did for the EJB3 codebase. If you want to have *real* dependencies on an EJB container at the MC level, then you'll need the org.jboss.injection codebase. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985621#3985621 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985621

19 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Another problem with jar urls

by scott.stark＠jboss.org

I'm not sold on truzip so whatever works best is what we will use. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985620#3985620 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985620

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: EJB References

by scott.stark＠jboss.org

There are now two EjbUtil and EjbUtil50. The latter Thomas did and may of tested. I just update EjbUtil to get the ejb2 deployers to compile under the vdf. If the EjbUtil50 is correct, we can migrate to it and drop the EjbUtil. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985619#3985619 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985619

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: @JMX aspect and aop/mc integration

by bstansberry＠jboss.com

Thanks, that worked. To express my gratitude, here's another one ;-) Problem now is a bean with a non-default constructor -- the value passed to the c'tor is null if the @JMX annotation is applied. E.g.: <bean name="HAPartition" | class="org.jboss.ha.framework.server.ClusterPartition"> | <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss:service=DefaultPartition", exposedInterface=org.jboss.ha.framework.server.ClusterPartitionMBean.class)</annotation> | | ..... | | </bean> | | <bean name="DistributedReplicantManager" | class="org.jboss.ha.framework.server.DistributedReplicantManagerImpl"> | | <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss:service=DistributedReplicantManager,partition=DefaultPartition", exposedInterface=org.jboss.ha.framework.server.DistributedReplicantManagerImplMBean.class)</annotation> | | <constructor> | <parameter class="org.jboss.ha.framework.server.ClusterPartition"><inject name="HAPartition"/></parameter> | </constructor> | | </bean> Results in: 2006-11-13 15:03:23,906 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Instantiated: name=DistributedReplicantManager state=Described | java.lang.RuntimeException: java.lang.NullPointerException | at org.jboss.aop.proxy.container.GeneratedAOPProxyFactory.getProxy(GeneratedAOPProxyFactory.java:115) | at org.jboss.aop.proxy.container.GeneratedAOPProxyFactory.createAdvisedProxy(GeneratedAOPProxyFactory.java:75) | at org.jboss.aop.proxy.container.GeneratedAOPProxyFactory.createAdvisedProxy(GeneratedAOPProxyFactory.java:39) | at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.dispatch(AOPConstructorJoinpoint.java:82) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:71) | at org.jboss.kernel.plugins.dependency.InstantiateAction.installAction(InstantiateAction.java:52) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.install(KernelControllerContextAction.java:96) | at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:709) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:429) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:538) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:472) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:274) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:177) | at org.jboss.deployers.plugins.deployers.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:67) | at org.jboss.deployers.plugins.deployers.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:42) | at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:53) | at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52) | at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:451) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246) | at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89) | at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401) | at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340) | at org.jboss.Main.boot(Main.java:210) | at org.jboss.Main$1.run(Main.java:508) | at java.lang.Thread.run(Thread.java:595) | Caused by: java.lang.NullPointerException | at org.jboss.ha.framework.server.DistributedReplicantManagerImpl.<init>(DistributedReplicantManagerImpl.java:114) | at org.jboss.ha.framework.server.DistributedReplicantManagerImpl.<init>(DistributedReplicantManagerImpl.java:99) | at AOPContainerProxy$2.<init>(AOPContainerProxy$2.java) | at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) | at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) | at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) | at java.lang.reflect.Constructor.newInstance(Constructor.java:494) | at java.lang.Class.newInstance0(Class.java:350) | at java.lang.Class.newInstance(Class.java:303) | at org.jboss.aop.proxy.container.GeneratedAOPProxyFactory.instantiateAndConfigureProxy(GeneratedAOPProxyFactory.java:128) | at org.jboss.aop.proxy.container.GeneratedAOPProxyFactory.getProxy(GeneratedAOPProxyFactory.java:111) | ... 30 more NPE is because the HAPartition ref passed in to the constructor is null. If I remove the @JMX annotation from the DistributedReplicantManager bean, it deploys fine. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985616#3985616 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985616

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - EJB References

by anil.saldhana＠jboss.com

Scott, the following code in org.jboss.ejb.EjbUtil does not make sense: | private static String resolveLink(MBeanServer server, DeploymentInfo di, String link, boolean isLocal) | { | ... | else | { | // <ejb-link> contains a Bean Name, scan the DeploymentInfo tree | DeploymentInfo top = di; | while (top != null) | { | top = top.getParent(); | } | | return resolveAbsoluteLink(top, link, isLocal); | } | } | | private static String resolveAbsoluteLink(DeploymentContext ctx, String link, boolean isLocal) | { | .... | ApplicationMetaData appMD = ctx.getTransientAttachments().getAttachment(ApplicationMetaData.class); | if (appMD != null) | { | ... | } | | Because of the while loop in the first method, the deployment context passed to the second method is always null. Can you check and fix? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985615#3985615 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985615

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: Update on metadata progress

by scott.stark＠jboss.org

This needs to be merged at the lower jboss parsing deployers. For example, this code to find a web-context default from the ear in the AbstractWarDeployer really needs to be in the JBossWebAppParsingDeployer. | import org.jboss.deployers.plugins.deployers.helpers.AttachmentLocator; | | // Check for an ear level specification | if( webContext == null ) | { | J2eeApplicationMetaData earMetaData = AttachmentLocator.search(unit, J2eeApplicationMetaData.class); | if( earMetaData != null ) | { | String path = unit.getRelativePath(); | J2eeModuleMetaData webModule = earMetaData.getModule(path); | if( webModule != null ) | webContext = webModule.getWebContext(); | } | } | | Something like: | @Override | public void deploy(DeploymentUnit unit) throws DeploymentException | { | log.debug("deploy, unit: "+unit); | createMetaData(unit, webXmlPath, null); | WebMetaData metaData = getMetaData(WebMetaData.class.getName()); | J2eeApplicationMetaData earMetaData = AttachmentLocator.search(unit, J2eeApplicationMetaData.class); | if( earMetaData != null ) | { | String path = unit.getRelativePath(); | J2eeModuleMetaData webModule = earMetaData.getModule(path); | ... | } | | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985604#3985604 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985604

19 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Another problem with jar urls

by bill.burke＠jboss.com

BTW, I'm not a big fan of truzip. It is all java.io.File based and not much different than our VFS implementation other than the VFS being a better abstraction. Yes, they do have the jar compression algorithms available in open source, but it will take a lot of refactoring of truzip to get where we want. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985603#3985603 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985603

19 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Another problem with jar urls

by scott.stark＠jboss.org

Fine. We need the prototype checked in somewhere as well as some point to further validate. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985602#3985602 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985602

19 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums November 2006