[Design of JCA on JBoss] - Re: DeploymentInfo/Template MCF
by alex.loubyansky@jboss.com
I'd like to clarify how the template is composed for the MCF deployment and what it is supposed to cover.
Is there supposed to be a separate template class for each kind of MCF? i.e. one for DataSource, another for XADataSource, etc?
I thought, there should be one for all. But ran into issues.
Currently, the DsDataSourceTemplateInfo creates a single ManagedObject with name ManagedConnectionFactoryDeploymentGroup and adds various attributes that belong to ManagedConnectionFactoryDeploymentMetaData subclasses to it.
I thought that's wrong. So, in DDSTI I created MO for each subclass of the MCFDMD and the group. But that doesn't work with the current impl of ManagementViewImpl.applyTemplate(). Since, the template contains info for all kinds of MCF deployments while the template created by the client (template instance?) contains e.g. only one kind of MCF. So, applyTemplate will not be able to apply client's template since it's missing all the other MCF deployments.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111684#4111684
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111684
18 years, 4 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: New test structure
by jmesnil
"timfox" wrote : "jmesnil" wrote :
| | There is also the alternative to put the different types of test related to a single "component" under the same tree.
| |
| | e.g. for remoting; all tests related to remoting would be under org.jboss.messaging.test.remoting:
| | - org.jboss.messaging.test.remoting.unit
| | - org.jboss.messaging.test.remoting.integration
| | - org.jboss.messaging.test.remoting.timing
| | - ...
| |
| |
| |
| So, "remoting" in your above example should be "core.remoting" surely? So we mirror the exact package names?
yes. I started doing that when I developed Eclipse applications using their naming conventions: [url=http://wiki.eclipse.org/index.php/Naming_Conventions]
The idea is that a developer most of the time is only interested by a specific piece of code and want to focus on it.
E.g. if I had to add a feature to the new persistence manager and I want to run the tests to make sure I do not break it, I find it simpler to run all tests under org.jboss.messaging.core.pm.test (or something else) than to have to navigate to all the subfolders of unit, fake, integration, etc. to check which ones have tests related to the persistence manager.
Of course, Hudson will still be configured to run all unit tests together, as well as integration tests et al.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111629#4111629
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111629
18 years, 4 months