February 2008 - jboss-dev-forums - Jboss List Archives

[Design of POJO Server] - Re: FIELD granularity web session replication tests

by kabir.khan＠jboss.com

The JBossWebMetaData.classLoading file (of type ClassLoadingMetaData) always seems to be null. This also seems to be the only place for the information I would be interested in. Is this a bug? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126289#4126289 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126289

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: FIELD granularity web session replication tests

by scott.stark＠jboss.org

How was this working before with the UnifiedLoaderRepository based class loader? There should be the same relationship between UnifiedClassLoaders and BaseClassLoaders in the new model in terms of peers and parents. The AspectDeployer should be loaded by a BaseClassLoader that is a peer of the BaseClassLoader which loads the jboss-metadata.jar. Don't really care how its fixed for beta4, but let's be clear on how aspects are being handled in terms of class loading. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126288#4126288 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126288

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: FIELD granularity web session replication tests

by kabir.khan＠jboss.com

I basically need access to the JBossWebMetaData attachment from the AspectDeployer. I can work around that though and do it via a bean that is deployed at the correct classloader level View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126280#4126280 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126280

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: extra jars needed when deploying a Seam app into JBAS5 b

by scott.stark＠jboss.org

I'm looking at it. Needs a new metadata release. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126276#4126276 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126276

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: FIELD granularity web session replication tests

by scott.stark＠jboss.org

No, needing metadata and javaee jars in /lib really is not valid for the core bootstrap. I'm not understanding why changing the class loader has changed where these jars need to be. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126275#4126275 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126275

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: extra jars needed when deploying a Seam app into JBAS5 b

by charles.crouch＠jboss.com

I've put this in the Beta4 bucket and marked it for Scott to make sure this gets triaged ASAP. Dimitris/Scott, any comments? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126274#4126274 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126274

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: FIELD granularity web session replication tests

by kabir.khan＠jboss.com

Moving jboss-metadata.jar and jboss-javaee.jar to jboss-5.0.0.Beta4/lib from jboss-5.0.0.Beta4/server/xxx/lib, and adding them to the bootstrap-beans.xml BootstrapClassLoader works. Leaving jboss-javaee.jar gives the error shown. Please let me know if having jboss-javaee.jar in the bootstrap is also fine? | 17:10:57,921 ERROR [AbstractKernelController] Error installing to Start: name=WarDeployer state=Create | java.lang.NoClassDefFoundError: javax/persistence/PersistenceContextType | at java.lang.Class.getDeclaredMethods0(Native Method) | at java.lang.Class.privateGetDeclaredMethods(Class.java:2395) | at java.lang.Class.getDeclaredMethods(Class.java:1763) | at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.getDeclaredMethods(IntrospectionTypeInfoFactoryImpl.java:479) | at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.getMethods(IntrospectionTypeInfoFactoryImpl.java:188) | at org.jboss.reflect.plugins.ClassInfoImpl.getDeclaredMethods(ClassInfoImpl.java:394) | at org.jboss.beans.info.plugins.AbstractBeanInfoFactory.getMethods(AbstractBeanInfoFactory.java:203) | at org.jboss.beans.info.plugins.AbstractBeanInfoFactory.getBeanInfo(AbstractBeanInfoFactory.java:136) | at org.jboss.config.plugins.AbstractConfiguration.getBeanInfo(AbstractConfiguration.java:83) | at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateType(JBossXBNoSchemaBuilder.java:767) | at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:695) | at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:683) | at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateTypeBinding(JBossXBNoSchemaBuilder.java:462) | at org.jboss.xb.builder.JBossXBNoSchemaBuilder.resolveTypeBinding(JBossXBNoSchemaBuilder.java:421) | at org.jboss.xb.builder.JBossXBNoSchemaBuilder.bindProperty(JBossXBNoSchemaBuilder.java:1715) | at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateType(JBossXBNoSchemaBuilder.java:1054) | at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:695) | at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:683) | at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateTypeBinding(JBossXBNoSchemaBuilder.java:462) | at org.jboss.xb.builder.JBossXBNoSchemaBuilder.resolveTypeBinding(JBossXBNoSchemaBuilder.java:421) | at org.jboss.xb.builder.JBossXBNoSchemaBuilder.createElementBinding(JBossXBNoSchemaBuilder.java:300) | at org.jboss.xb.builder.JBossXBNoSchemaBuilder.createRootElementBinding(JBossXBNoSchemaBuilder.java:280) | at org.jboss.xb.builder.JBossXBNoSchemaBuilder.createRootElements(JBossXBNoSchemaBuilder.java:260) | at org.jboss.xb.builder.JBossXBNoSchemaBuilder.build(JBossXBNoSchemaBuilder.java:184) | at org.jboss.xb.builder.JBossXBBuilder.build(JBossXBBuilder.java:102) | at org.jboss.web.tomcat.service.deployers.TomcatDeployer.start(TomcatDeployer.java:401) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:56) | at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:110) | at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:214) | at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:45) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:108) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:69) | at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:135) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:46) | at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) | at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) | at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) | 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.install(AbstractController.java:574) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:398) | at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:69) | at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:42) | at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:65) | 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:874) | 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:239) | 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:595) | Moving jboss-javaee to the root lib directory and adding it to the BootstrapClassLoader fixes this problem. Please let me know if this is acceptable or not View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126273#4126273 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126273

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: FIELD granularity web session replication tests

by kabir.khan＠jboss.com

Ah yes, I had muddled my facts slightly View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126263#4126263 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126263

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: FIELD granularity web session replication tests

by scott.stark＠jboss.org

Adding jboss-metadata.jar to the bootstrap-beans.xml BootstrapClassLoader config won't be a problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126260#4126260 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126260

18 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: RM Sender/Receiver as High Available (HA) Components

by richard.opalka＠jboss.com

Second identified problem is HA WS-RM in combination with WS-Security. HA WS-RM must reside on top of transport layer (this results from WS-RM specification). Current WS-Security and WS-RM un/marshalling processings reside in JAX-RPC/JAX-WS handlers. In order to support HA WS-RM plus WS-Security joint combinations (as required by e.g. Microsoft Web Services Interop Plug Fest Scenarios) it is necessary to move both WS-RM and WS-Security one layer lower in the processing chain i.e. implement it in transport un/marshallers because of the following two requirements: WS-Security processing must be the last/first thing in client and endpoint outgoing/incoming processing chain. HA WS-RM must reside on top of transport layer View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126251#4126251 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126251

18 years, 2 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 February 2008