[Design the new POJO MicroContainer] - Re: Work on 187, 188, 218, .bsh, StructureDeployer
by alesj
"alesj" wrote :
| What I would like to do, is to test that a single deploy|undeploy and (add|remove)+process don't corrupt each other in multithread requests.
| Another test would include a shutdown thread, from where on all other non-shutdown (deploy|undeploy) threads should fail.
| The question is how to gather required information, meaning that a thread was legally allowed to go (or not go) past the locks that we've put?
|
Done.
The first test - DeployerSingleDeploymentTestCase.testMultiThreads - is more a proof of concept through design, unleashing multiple threads just additionally confirms assumptions that deploy/undeploy and (add|remove)+process don't interfere with each other. :-)
The second one - DeployerSingleDeploymentTestCase.testMultiThreadsAndShutdown - is better. :-)
I'm checking if certain DeployerClient method invocation got past the read lock, as such not being valid to fail due to shutdown. All others that didn't get past the read lock must fail.
Perhaps only the way how I'm checking if thread got past the lock is a bit too impl detail - intercepting Deployment.getName method invocation.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106680#4106680
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106680
18 years, 4 months
[Design the new POJO MicroContainer] - Re: Getting content of XML element
by kabir.khan@jboss.com
"adrian(a)jboss.org" wrote :
| Why do you want to do this? This is usually horrible.
| Is this the old XmlLoadable stuff?
|
It is to support the ClassMetaData stuff, e.g. I need to be able to translate the following -aop.xml style stuff
| <metadata tag="SomeTag" class="org.jboss.test.aop.bean.POJOConstructorTest">
| <constructor expr="POJO()">
| <data>ctor</data>
| </constructor>
| <method expr="int *(..)">
| <data>method1</data>
| </method>
| <method expr="void *()">
| <data>method2</data>
| </method>
| </metadata>
|
into
| <bean name="ClassMetaData" class="org.jboss.aop.microcontainer.beans2.ClassMetaData">
| <property name="manager"><inject bean="AspectManager"/></property>
| <property name="tag">SomeTag</property>
| <property name="className">org.jboss.test.microcontainer.beans2.POJO</property>
| <property name="element">
| <![CDATA[
| <metadata>
| <constructor expr="POJO()">
| <data>ctor</data>
| </constructor>
| <method expr="int *(..)">
| <data>method1</data>
| </method>
| <method expr="void *()">
| <data>method2</data>
| </method>
| </metadata>
| ]]>
| </property>
| </bean>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106651#4106651
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106651
18 years, 4 months
[Design of POJO Server] - Re: Annotation to metadata status
by scott.stark@jboss.org
"wolfc" wrote : Bugrit, I forgot to commit the MyStateless21Bean fix.
|
| MyStatefulBean is not according to spec. It declares an EJB 2.1 remote home with an EBJ 3 remote business interface, but no EJB 2.1 remote interface. (EJB 3 4.6.1 bullet 2 & 3) So unless we're doing a negative test, this should be cleaned up.
|
Ok, I see. This requires validation of the @Remote target class. Is this something we need to be adding to the processor?
"wolfc" wrote :
| I've added the ability to load a sub-package to AnnotationEjb3UnitTestCase.
| I can move this to the common test package and allow for the following:
| @ScanPackage("org.jboss.test.metadata.ejb3.annotation.multiview")
| | public void testMultiview() {
| | Collection<Class<?>> classes = PackageScanner.loadClasses();
| | ...
| | }
| Looks good.
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106629#4106629
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106629
18 years, 4 months