Re: [jboss-dev-forums] [Management Development] - domain.xml work
by Scott Stark
Scott Stark [http://community.jboss.org/people/scott.stark%40jboss.org] replied to the discussion
"domain.xml work"
To view the discussion, visit: http://community.jboss.org/message/535942#535942
--------------------------------------------------------------
It seems to me we are not all on the same page with regard to how the profileservice functions in terms of management edits. I'm sorry if this seems to be going backwards, but I want to be clear on how we are all viewing the domain.xml. There are 3 elements:
1. The metadata that drives the deployers to create runtime components.
2. The profileservice admin view of the metadata as described by the ManagedComponents. This is a possibly indirect mapping that allows the deployer/container specific metadata that carries implementation details from a stable admin view that is compatible across releases. Realize that right now we are far from complete in this being a one to one mapping. Only a fraction of the projects have an admin view that is anywhere near complete. The embedded console uses this admin view implicitly by defining its own mapping of ManagedComponent properties onto its UI elements. The push to define a domain.xml is a centralization of the admin view of the metadata. The intention is that this really is the only supported admin interface. Perhaps I have obscured the issue by mentioning that there could be ManagedComponents not in the domain.xml or even properties not in the domain.xml. What is important is that we are defining a complete admin view of the metadata that is decoupled from the deployer metadata. This is our historic problem which manifested as implementation xml files spread out all over in the server deployments.
3. The profileservice implementation which is manages applying admin edits to the admin (domain) metadata view onto the deployer implementation metadata.
Related to Brian's question he started on another summary thread, the first step is to define a sufficient domain.xml metadata model that we accept as our supported admin interface, and evolve that compatibily for each subsequent release. Realize we already have a limited admin domain model that JON supports that is defined by the rhq-plugin.xml mapping between ManagedComponents and the console's supported admin components. We have to step outside of our project metadata models and deal with both the admin metadata view and implementation view. I don't see a limited domain.xml in AS6.0 as a problem because that is in fact the reality. My notion for a minimal domain.xml is one that encapsulates the current embedded JON rhq-plugin.xml model.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/535942#535942]
Start a new discussion in Management Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
Re: [jboss-dev-forums] [JBoss Tools Development] - How to Make Your JUnit Tests Run Faster in Eclipse
by Denis Golovin
Denis Golovin [http://community.jboss.org/people/dgolovin] commented on the document
"How to Make Your JUnit Tests Run Faster in Eclipse"
To view all comments on this document, visit: http://community.jboss.org/docs/DOC-15108#comment-3085
--------------------------------------------------
JavaModelManager.getIndexManager().disable();
JavaModelManager.getIndexManager().enable();
But be aware that it is not good approach to have indexing disabled TestCase with many test* methods in startUp and enabled in tearDown, because those methods will be exectuted before and after each test method. This will not improve performance because as soon as you enable it, indexing starts and next method will wait until it is finished. It make sense to use disable/enable java indexing as part of TestSetup wrapper implementation, so it is called once for all tests inside suite.
--------------------------------------------------
16 years
[JBoss Tools Development] - How to Make Your JUnit Tests Run Faster in Eclipse
by Denis Golovin
Denis Golovin [http://community.jboss.org/people/dgolovin] created the document:
"How to Make Your JUnit Tests Run Faster in Eclipse"
To view the document, visit: http://community.jboss.org/docs/DOC-15108
--------------------------------------------------------------
TBD: more tips and examples are comming (work is still in progress)
1. Consider mocking for eclipse interfaces rather trying to obtain real one from eclipse
2. Consider using core tests instead of ui tests, which is required to start eclipse workbench
3. If you need test project during test execution try to make it as simpler as it possible:* remove all unused jars and remove all unused classes from jars you need to make java indexing faster
* remove all builders from .project file that doesn't required in your test or disable them during runtime
* disable validation if your tests are not for validation issues
* disable java indexing if you cannot create test project without jars
* disable auto builder if you do not need to test incremental builder functionality
4. Try to reuse test projects between several tests to import it only ones during test execution. Use TestSetup wrapper to achieve this, because setUp and tearDown methods are executed before and after each test* methods in class.
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-15108]
Create a new document in JBoss Tools Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
16 years