[ http://jira.jboss.com/jira/browse/DNA-58?page=all ] Stefano Maestri reassigned DNA-58: ---------------------------------- Assignee: Stefano Maestri -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-58: ----------------------------- Fix Version/s: 0.3 (was: 0.2) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.... ] Randall Hauch reassigned DNA-58: -------------------------------- Assignee: Randall Hauch (was: Stefano Maestri) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.... ] Brian Carothers updated DNA-58: ------------------------------- Attachment: DNA-58_component_properties.patch DNA-58_component_properties.patch extends existing ComponentConfig class to optionally contain a mapping of property names to values and modifies ComponentLibrary to dynamically set these properties on the component with these values after instantiation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.... ] Randall Hauch updated DNA-58: ----------------------------- Comment: was deleted -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.... ] Randall Hauch commented on DNA-58: ---------------------------------- Applied the first patch ("DNA-58_component_properties.patch") and a small part of the second ("DNA-58_builder_engine.patch"), which enhanced ComponentConfig to allow properties that are set reflectively on the components when they are instantiated. Subclasses of ComponentConfig were also modified, as were the test cases. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.... ] Randall Hauch commented on DNA-58: ---------------------------------- Refactored the DnaConfiguration to make use of the graph repository for storing the configuration. When used, the DnaConfiguration instance persists all the information to this graph, where it can be read and used. A "save()" method was added to allow the code using the DnaConfiguration instance to control when the content is updated. (This also simplified the unit testing, since it's very easy to check the graph content after the DnaConfiguration methods are used.) The DnaEngine was then updated to read the configuration repository content and to instantiate and set up the services. This "configuration repository" defaults to an in-memory repository, but can be set up to use a particular RepositorySource instance (that has already been set up) or to reflectively create an instance given the class name, optional class loader, and various (implementation-specific) Java bean properties. This means that in the simplest case, one can simply create a DnaConfiguration and configure the sequencers, sources, detectors, etc. It also makes it very simple to "read" an XML file with the configuration, since that just uses the XML graph importer. But using a configuration repository shines in the more advanced cases, such as when a process participates in a cluster. Here, the process can create a DnaConfiguration, very easily set it up to use a shared (and remote) configuration repository (that already has the content), and without any other work immediately build the DnaEngine. Using a graph as the configuration repository also means that any changes to the configuration could be monitored via graph events, allowing the DnaEngine to monitor any changes and dynamically alter its services. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.... ] Randall Hauch commented on DNA-58: ---------------------------------- Minor change to allow a subclass to define the SessionFactory used by the SequencingService. The configuration for the JCR engine may need to provide its own SessionFactory implementation (or instance). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.... ] Randall Hauch commented on DNA-58: ---------------------------------- Refactored the DnaConfiguration class to use more interfaces and to move those interfaces (and reusable implementations) into a Configurator class that uses generics. DnaConfiguration instantiates a configurator, but also implements some of the high-level interfaces by delegating them to the wrapped configurator instance. This allows DnaConfiguration to appear to be doing the configurating, but in reality it is the wrapped builder that is doing it. Also, DnaConfiguration (or other components) can choose which "aspects" of configuration it is to expose by inheriting controlling which higher-level interfaces are implemented. Since delegation is used, this works very well. This is a more complicated design, but it is far more extensible and reusable. A JcrConfiguration class was also created that works in the same way as DnaConfiguration, except that it uses a different type parameter (so all the interfaces return JcrConfiguration). It thus gets to reuse all of the Configurator logic. However, JcrConfiguration doesn't implement all of the "aspects", essentially hiding certain services (e.g., sequencers, since they don't yet work with our implementation). This change also made a few minor corrections to the JavaDoc and visibility modifiers on the classes in the 'org.jboss.dna.jcr' package. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira