"adrian(a)jboss.org" wrote :
| Stages (1) and (2) are optional if they already exist
|
| 1) Create a MutableMetaData for this scope
| 2) Create a kernel (or maybe just a kernel controller) for this scope and add it to
| the MutableMetaData, the kernel's parent would come from any kernel in the
| parent's scope or the default kernel if there is no such thing
| 3) Deploy the bean(s) into that scoped kernel
|
Where to plug-in these stages?
Since I need to know bean annotations before I deploy bean into the controller (BeanMetaDataDeployer, AbstractKernelDeployer), but currently they are realized in DescribeAction.
Or should I do my own scope-annotation lookup just before I do the deployment into controller?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4014936#4014936
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4014936
Hi Julien,
We are comparing apple and oranges here. :-)
The regular portal 2.6 testsuite is run against three AS version while DB is running with only 4.0.4.GA but seven different DB configs..
For example: there are 7 different DB config so we have (7*14=98) tests for DB and (14*3=42) tests for regular case. All tests in regular case are run three times while in DB case only DB tests are run against multiple times. I looked into other modules and they seem to fit this logic as well. It's hard to debug if there is no bug. :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4014806#4014806
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4014806