[JBoss JIRA] Created: (DNA-159) Federate/cache content from a remote JCR (and DNA) repository
by Randall Hauch (JIRA)
Federate/cache content from a remote JCR (and DNA) repository
-------------------------------------------------------------
Key: DNA-159
URL: http://jira.jboss.com/jira/browse/DNA-159
Project: DNA
Issue Type: Feature Request
Components: Connectors
Reporter: Randall Hauch
Priority: Minor
Fix For: Future Releases
The primary use case for this feature is to allow an application to have a local DNA repository that is configured to be a local, cached copy of a single remote JCR repository. So, rather than having multiple sources, this use case would have a single source (using a connector to a remote JCR repository), and it would be configured to probably have a cache policy with a relatively short TTL. (Of course the TTL could be extended if the connector could listen to the remote repository to receive events, which would be propagated up to the local "federated" repository and would cause those particular changed instances to be purged from the cache.
Ideally this could be made to be very lightweight and very easy to configure, maybe even using just an in-memory "integrated repository" (aka, cache).
This use case is far superior to an implementation that uses remote calls for every operation.
--
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
14 years, 3 months
[JBoss JIRA] Created: (DNA-102) setProperty method in SequencerOutput interface should enforce limitations on property value types
by Greg Haber (JIRA)
setProperty method in SequencerOutput interface should enforce limitations on property value types
--------------------------------------------------------------------------------------------------
Key: DNA-102
URL: http://jira.jboss.com/jira/browse/DNA-102
Project: DNA
Issue Type: Bug
Components: API
Affects Versions: 0.1, 0.2
Reporter: Greg Haber
Priority: Minor
The setProperty method of the SequencerOutput method, as it currently exists, accepts arbitrary single Objects or arrays of Objects as property values via its use of "Object..." in the method signature. In DNA-77, it was suggested that the current method definition should be replaced with multiple type-specific methods, but it was decided to not do this, and instead recommend use of ValueFactory to create the values used in this method.
The problem with this is that, by leaving the interface as is and having use of ValueFactory be optional, it is easy for users to set properties to value types that are not currently supported (meaning that they will see a run-time error somewhere else in the code in these cases, rather than a compile-time or run-time error at the actual point where the issue was introduced (their misuse of setProperty).
One possible way to enforce this in the interface is to define the interface as throwing some sort of exception if the value is not an instance of an allowed class. Another solution would be a more substantial revision of the interface to mandate use of ValueFactory to create property values.
--
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
14 years, 11 months