December 2007 - jboss-dev-forums - Jboss List Archives

[Design of EJB 3.0] - Re: DefaultJndiBindingPolicy and ReferenceMetaDataResolverDe

by scott.stark＠jboss.org

Its not needed for beta3. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109602#4109602 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109602

17 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: ConcurrentModificationException / Classloading / Deploym

by ALRubinger

Thanks, Scott. Brought in your change; problem still persists, though. Reliably reproduced through the instructions below. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109598#4109598 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109598

17 years

1
0
0 / 0

[Design of EJB 3.0] - Re: DefaultJndiBindingPolicy and ReferenceMetaDataResolverDe

by ALRubinger

http://jira.jboss.com/jira/browse/EJBTHREE-1101?page=all Is this a blocker for Beta 3? If so, I'll prioritize the addition of this element to jboss.xml schema and to the metadata project accordingly. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109588#4109588 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109588

17 years

1
0
0 / 0

[Design of POJO Server] - Re: vfs issue?

by pete.muir＠jboss.org

"alesj" wrote : I was able to get past this vfs issue with this change to the Scanner: I still think a deployer is a better solution as (as I understand it) there should be some speed improvements as Seam doesn't have to scan for annotations as this has been done by the AS. We should consider this issue in conjunction http://jira.jboss.com/jira/browse/JBSEAM-1342 - a way to call a handler based on some other metadata other than the @Name annotation (e.g. other annotation, file name pattern etc.). This obviously need to be portable across app servers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109573#4109573 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109573

17 years

1
0
0 / 0

[Design of POJO Server] - Re: vfs issue?

by pete.muir＠jboss.org

And, obviously, jboss-seam.jar contains the SeamInterceptor class. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109572#4109572 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109572

17 years

1
0
0 / 0

[Design of POJO Server] - Re: vfs issue?

by pete.muir＠jboss.org

There is also this problem with deploying the booking example (this is the example we should concentrate on as it shows most core seam functionality without distractions like jbpm). | 21:06:28,587 INFO [TomcatDeployment] deploy, ctxPath=/invoker, | vfsUrl=http-invoker.sar/invoker.war | 21:06:34,018 ERROR [AbstractKernelController] Error installing to | Real: name=vfsfile:/Users/pmuir/workspace/jbossas/build/output/jboss-5.0.0.Beta3/server/default/deploy/jboss-seam-booking.ear | state=PostClassLoader mode=Manual requiredState=Real | org.jboss.deployers.spi.DeploymentException: Error deploying | jboss-seam-booking.jar: Interceptor class not found: | org.jboss.seam.ejb.SeamInterceptor | at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:158) | at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:88) | at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internalDeploy(AbstractVFSRealDeployer.java:45) | at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:906) | at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) | at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498) | at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131) | at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:408) | at org.jboss.Main.boot(Main.java:208) | at org.jboss.Main$1.run(Main.java:534) | at java.lang.Thread.run(Thread.java:613) | Caused by: java.lang.RuntimeException: Interceptor class not found: | org.jboss.seam.ejb.SeamInterceptor | at org.jboss.ejb3.interceptor.InterceptorInfoRepository.loadClass(InterceptorInfoRepository.java:525) | at org.jboss.ejb3.interceptor.InterceptorInfoRepository.access$100(InterceptorInfoRepository.java:77) | at org.jboss.ejb3.interceptor.InterceptorInfoRepository$AnnotationInitialiser.<init>(InterceptorInfoRepository.java:682) | at org.jboss.ejb3.interceptor.InterceptorInfoRepository$XmlInitialiser.<init>(InterceptorInfoRepository.java:813) | at org.jboss.ejb3.interceptor.InterceptorInfoRepository.initialiseInfosFromXml(InterceptorInfoRepository.java:367) | at org.jboss.ejb3.interceptor.InterceptorInfoRepository.initialise(InterceptorInfoRepository.java:108) | at org.jboss.ejb3.Ejb3HandlerFactory$DDFactory.<init>(Ejb3HandlerFactory.java:48) | at org.jboss.ejb3.Ejb3HandlerFactory.getInstance(Ejb3HandlerFactory.java:83) | at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:431) | at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:375) | at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:145) | ... 22 more | 21:06:34,116 INFO [RARDeployment] Required license terms exist, view | vfsfile:/Users/pmuir/workspace/jbossas/build/output/jboss-5.0.0.Beta3/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml We declare jboss-seam.jar as an ejb module in application.xml - and the SeamInterceptor in ejb-jar.xml. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109571#4109571 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109571

17 years

1
0
0 / 0

[Design of POJO Server] - Re: vfs issue?

by pete.muir＠jboss.org

I can see this too. Another problem: org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/Users/pmuir/workspace/jbossas/build/output/jboss-5.0.0.Beta3/server/default/deploy/jboss-seam-numberguess.ear/jboss-seam-numberguess.war | at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:175) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:906) | at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) | at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498) | at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131) | at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:408) | at org.jboss.Main.boot(Main.java:208) | at org.jboss.Main$1.run(Main.java:534) | at java.lang.Thread.run(Thread.java:613) | Caused by: java.lang.NoClassDefFoundError: com/sun/facelets/compiler/Compiler | at java.lang.Class.getDeclaredFields0(Native Method) | at java.lang.Class.privateGetDeclaredFields(Class.java:2232) | at java.lang.Class.getDeclaredFields(Class.java:1715) | at org.jboss.metadata.annotation.creator.AbstractComponentProcessor.processClass(AbstractComponentProcessor.java:258) | at org.jboss.metadata.annotation.creator.AbstractComponentProcessor.processClass(AbstractComponentProcessor.java:208) | at org.jboss.metadata.annotation.creator.AbstractComponentProcessor.process(AbstractComponentProcessor.java:149) | at org.jboss.metadata.annotation.creator.web.WebComponentProcessor.process(WebComponentProcessor.java:60) | at org.jboss.metadata.annotation.creator.web.WebComponentProcessor.process(WebComponentProcessor.java:42) | at org.jboss.metadata.annotation.creator.web.Web25MetaDataCreator.create(Web25MetaDataCreator.java:68) | at org.jboss.deployment.AnnotationMetaDataDeployer.processJBossWebMetaData(AnnotationMetaDataDeployer.java:190) | at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:149) | at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:78) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169) | ... 18 more | 21:44:02,695 INFO [TomcatDeployment] deploy, ctxPath=/invoker, vfsUrl=http-invoker.sar/invoker.war this occurs on the standard build for the numberguess example, obviously including facelets solves this, but facelets isn't needed for this example View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109570#4109570 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109570

17 years

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: JBoss Remoting SVN conversion is today!

by david.lloyd＠jboss.com

I set the mime-type of all the keystore files to application/octet-stream, so hopefully they won't get mangled... does this fix the problem? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109569#4109569 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109569

17 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: ConcurrentModificationException / Classloading / Deploym

by scott.stark＠jboss.org

New class loaders for the package can be added while someone is looking up a class. This will need to be changed to a copy on write type of logic. I have made that change. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109567#4109567 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109567

17 years

1
0
0 / 0

[Design of EJB 3.0] - DefaultJndiBindingPolicy and ReferenceMetaDataResolverDeploy

by scott.stark＠jboss.org

Currently there is no knowledge of the JndiBindingPolicy annotation or DefaultJndiBindingPolicy interface in the metadata. The ReferenceMetaDataResolverDeployer expects that by the time it runs, the JBossEnterpriseBeanMetaData resolved for a ejb-ref/ejb-local-ref can be used to determine the mappeName for the referring EJBLocalReferenceMetaData/EJBReferenceMetaData. This is not the case if the proxy factory is looking to a DefaultJndiBindingPolicy for the name if it was not explicitly set. These need to be brought together if the post ReferenceMetaDataResolverDeployer state is that all references have been resolved and the values determined. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109565#4109565 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109565

17 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums December 2007