[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-499) Wrap system access, context class loader access, and reflection with doPrivileged
by Randall Hauch (JIRA)
Wrap system access, context class loader access, and reflection with doPrivileged
---------------------------------------------------------------------------------
Key: DNA-499
URL: https://jira.jboss.org/jira/browse/DNA-499
Project: DNA
Issue Type: Bug
Components: API, Common, Connectors, Examples, Federation, Graph, JCR, Maven Classloader, Sequencers
Affects Versions: 0.5
Reporter: Randall Hauch
Fix For: 0.6
Several activities should make use of the Java SecurityManager to ensure the caller has the appropriate privileges to perform the activity. These activities should be wrapped in a block such as the following:
String lineSeparator = java.security.AccessController.doPrivileged(
new java.security.PrivilegedAction<String>() {
public String run() {
return System.getProperty("line.separator");
}
}
);
obviously with the correct generic type for whatever is being returned from the run. (Nice and concise, huh? Ugh.)
We need to go through all of the (non-test) code and add this checking (if it is not already there) when the following types of activities are performed:
- System.getProperty
- System.setProperty
- Thread.currentThread().getContextClassLoader()
- All code executed via reflection
--
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
14 years, 3 months