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

[Design of JCA on JBoss] - Re: Tests failing in JBoss Head

by weston.price＠jboss.com

Probably differently. I will take care of it. For the XAWrapper stuff, JBoss4 should be the authority not 5. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091085#4091085 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091085

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - New KernelBus lookup failure

by alesj

I'm having problems locating runtime component via new KernelBus lookup. The lookup goes over KernelRegistry, which eventually delegates things to registered KernelRegistryPlugins. Currenty there are three KernelRegistryPlugins: BasicKernelRegistryFactory, AbstractKernelController, JNDIKernelRegistryPlugin. OK, we can forget about the last one - JNDI. But the thing is that neither of the first two is able to find simple 'name=DefaultDS,service=ManagedConnectionPool' service. Looking at the AbstractKernelController makes it clear, since this service is not a POJO supplier. But one would expect to find it in the first registry. What's the idea/algorithm what goes into BasicKernelRegistryFactory and is not present as installed ControllerContext in Controller and vice versa? Since I get 188 entries in BasicKernelRegistryFactory and 359 Installed contexts in Controller. And BasicKernelRegistryFactory doesn't return service, where Controller.getInstalledContext returns the service context. I'm running AS5 profileservice configuration. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091075#4091075 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091075

18 years, 2 months

1
0
0 / 0

[Design of JBossCache] - Re: Eviction and buddy backup regions

by bstansberry＠jboss.com

Correct. CacheImpl.gravitateData() uses findNode() to look for the data; doesn't go through the interceptors. If the call is to go through the interceptors, and auto-gravitation is turned on, there needs to be a mechanism to suppress gravitation for the call. We have the Option to force gravitation, but not the opposite. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091073#4091073 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091073

18 years, 2 months

1
0
0 / 0

[Design of JCA on JBoss] - Tests failing in JBoss Head

by adrian＠jboss.org

Some of the jca tests are failing in JBoss Head. All the tests pass in JBoss4 (some of them I recently copied from JBoss4 to JBoss5 so I know they are the same). I fixed some of them by the change in the other post to fix the deployment metadata. I think some of the tests are failing just because they need more time so there maybe a regression in performance somewhere? I have my doubts looking at some of the code whether JBoss5 is up-to-date compared with the changes that have been done in JBoss4. I know JBoss5 has some features that are not in JBoss4 and some of it might be implemented differently so it is difficult to just do a straight diff. e.g. a diff of TxConnectionManager shows | 381a419 | > | 384d421 | < xaResource = JcaXAResourceWrapperFactory.getResourceWrapper(mc.getXAResource(), isSameRMOverrideValue); | 385a423,436 | > if(wrapXAResource) | > { | > log.trace("Generating XAResourceWrapper for TxConnectionManager" + this); | > xaResource = new XAResourceWrapper(isSameRMOverrideValue, padXid, mc.getXAResource()); | > | > } | > | > else | > { | > log.trace("Not wrapping XAResource."); | > xaResource = mc.getXAResource(); | > | > } | > | 429a481 | Is this something not ported or just something implemented differently? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091022#4091022 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091022

18 years, 2 months

1
0
0 / 0

[Design of JCA on JBoss] - New DataSource deployment metadata

by adrian＠jboss.org

I've brought the datasource deployment metadata up-to-date with the JBoss5 MCFs. I think we still need to support the old ha-*-datasource xml for backwards compatiblity don't we? We should be able to support this by just doing something like? | @XmlType(name="ha-xa-datasource") | @XmlAccessorType(XmlAccessType.FIELD) | @ManagementObject(componentType=@ManagementComponent(type="DataSource",subtype="XA")) | public class HAXADataSourceDeploymentMetaData extends XADataSourceDeploymentMetaData | { | } | and then adding the dummy classes to the ManagedConnectionFactoryDeploymentGroup? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091019#4091019 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091019

18 years, 2 months

1
0
0 / 0

[Design of JBossCache] - Re: JBCACHE-1154 - Introduce ability to mark nodes as reside

by manik.surtani＠jboss.com

I don't think this has anything to do with tx scoping. This is more a configuration thing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090978#4090978 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090978

18 years, 2 months

1
0
0 / 0

[Design of JBossCache] - Re: Eviction and buddy backup regions

by manik.surtani＠jboss.com

anonymous wrote : | Unfortunately, there's another major problem with eviction and buddy replication. If a node is only available via a cache loader, data gravitation fails. | You mean if the node has been evicted in memory on the buddy, but lives on in the buddy's cache loader, the DG call doesn't force the buddy to load from cache loader? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090964#4090964 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090964

18 years, 2 months

1
0
0 / 0

[Design of the JBoss EJB Container] - Re: NPE in HomeHandleImplIIOP

by adrian＠jboss.org

I've fixed the serialization, but I've not closed the issue until Bill confirms it resolves the problem he was seeing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090945#4090945 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090945

18 years, 2 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: ClassLoading Module usage

by kabir.khan＠jboss.com

When generating classes, the way it currently works in JBossClassPool.toClass() is that 1) The class file is written to the "dynamic" url, so that it is available both for the classloader and for the ClassPool itself 2) The loader blacklists are cleared 3) The class is loaded through the classloader The classpool itself should be able to cache the class, so I think the main question is how this will work at classloader level. I will try without this and see what happens. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090940#4090940 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090940

18 years, 2 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: ClassLoading Module usage

by adrian＠jboss.org

For what purpose? You can't change the new classloader in an ad hoc fashion like you could the old one. That would be very dangerous for security reasons. When I wrote the new classloader I deliberately left those methods out that look dangerous. The new classloader runs off the VFS files that each [sub]deployment specifies in the getClassPath(). So if you want to add a URL (VFS file) you should do it before the classloader is constructed by modifying the ClassPath of the deployment in question. See org.jboss.deployers.vfs.deployer.plugins.classloader VFSClassLoaderPolicy and VFSTopLevelClassLoaderSystemDeployer View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090936#4090936 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090936

18 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums October 2007