[Design the new POJO MicroContainer] - Re: Annotation Tests in deployers-vfs
by alesj
"adrian(a)jboss.org" wrote : "alesj" wrote : "adrian(a)jboss.org" wrote : The annotation tests in deployers-vfs are failing for me under eclipse.
| | Do you still get failing tests under eclipse?
|
| Yep. One of them is fixed but the other still fails:
|
|
| | junit.framework.AssertionFailedError: Expected [appc.jar, ejbs.jar, web.jar, services.jar] got [] expected:<4> but was:<0>
| | at junit.framework.Assert.fail(Assert.java:47)
| | at junit.framework.Assert.failNotEquals(Assert.java:277)
| | at junit.framework.Assert.assertEquals(Assert.java:64)
| | at junit.framework.Assert.assertEquals(Assert.java:195)
| | at org.jboss.test.deployers.vfs.structure.AbstractStructureTest.assertChildContexts(AbstractStructureTest.java:79)
| | at org.jboss.test.deployers.vfs.structure.ear.test.EARStructureUnitTestCase.testEARAnnotationScanning(EARStructureUnitTestCase.java:143)
| |
What about now?
I've changed to use string as annotation classname, which means it will be loaded via unit's classloader - which should then definitely match annotation on the test class.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156951#4156951
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156951
16 years, 3 months
[Design of JBossCache] - Re: JBoss Cache Public API
by genman
"manik.surtani(a)jboss.com" wrote : "genman" wrote :
| | The problem with "putAll" (and "put" and "remove") is that they require a storage read for every call. If you can get them to perform okay, then I don't really care.
| |
|
| Why? I agree that such calls should be optimised by the Interceptors not to do a load if the state needed is already in mem (for the return value of a put or remove), but beyond that, why would putAll, etc. do a storage read?
|
I don't see why they do, but they do.
For example, for FileCacheLoader, if erase is "false", which is called by "put(Fqn, Map)", then a read is made:
| @Override
| public void put(Fqn fqn, Map attributes, boolean erase) throws Exception
| {
| lock.acquireLock(fqn, true);
| try
| {
| Map m = erase ? new HashMap() : loadAttributes(fqn);
| if (m == null) m = new HashMap();
| if (attributes != null)
| {
| m.putAll(attributes);
| }
| storeAttributes(fqn, m);
| }
| finally
| {
| lock.releaseLock(fqn);
| }
| }
|
JDBC and all the other cache loaders are similar... I don't see why they should necessarily do a read for this operation.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156881#4156881
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156881
16 years, 3 months