August 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-62) Sequence JAR files to extract class structure and annotations

by Randall Hauch (JIRA)

Sequence JAR files to extract class structure and annotations ------------------------------------------------------------- Key: DNA-62 URL: http://jira.jboss.com/jira/browse/DNA-62 Project: DNA Issue Type: Feature Request Components: Sequencers Reporter: Randall Hauch Fix For: 0.2 This use case comes from a discussion about starting up the Microcontainer, and the desire to have a single processor of the JAR files to extract into a centralized repository the runtime annotations. Right now the annotations are scanned by each component/service that needs them. This feature would obviate the scanning being done by each component/service. Consider using http://scannotation.sourceforge.net/ for doing the actual scanning. -- 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

2
12
0 / 0

[JBoss JIRA] Created: (DNA-256) Packaging and deployment

by Sergiy Litsenko (JIRA)

Packaging and deployment ------------------------ Key: DNA-256 URL: https://jira.jboss.org/jira/browse/DNA-256 Project: DNA Issue Type: Feature Request Components: Server, Web Application Environment: Java EE 5 certified environment Java SE 5 certified environment Reporter: Sergiy Litsenko Fix For: Future Releases Define flexible packaging and deployment scenarios that satisfy both Embedded/Standalone and Enterprise deployments. Maven plugins can package the project as different deployment artifacts: http://maven.apache.org/plugins/maven-ear-plugin/ JEE Enterprise Archive (EAR) file format http://maven.apache.org/plugins/maven-rar-plugin/ JEE Enterprise JCA Resource adaptor Archive (RAR) file format http://maven.apache.org/plugins/maven-ejb-plugin/ JEE Enterprise Javabean (EJB) file format http://maven.apache.org/plugins/maven-war-plugin/ JEE Enterprise Web Archive (WAR) file format http://maven.apache.org/plugins/maven-assembly-plugin/ Custom packaging http://maven.apache.org/plugins/maven-dependency-plugin/ Custom packaging Examples of deployment scenarios/packaging: http://jackrabbit.apache.org/deployment-models.html Apache Jackrabbit deployment models - including embedded, Shared J2EE Resource, and Repository Server accessble through RMI over JRMP or IIOP or WebDAV. http://docs.jboss.org/seam/2.1.0.GA/reference/en-US/html/configuration.html JBoss Seam framework packaging scenarios: 29.3. Configuring Seam in Java EE 5 29.5. Configuring Seam in Java SE, without JBoss Embedded 29.6. Configuring Seam in Java SE, with JBoss Embedded -- 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

2
2
0 / 0

[JBoss JIRA] Created: (DNA-368) Referenced Nodes Can Be Deleted

by Brian Carothers (JIRA)

Referenced Nodes Can Be Deleted ------------------------------- Key: DNA-368 URL: https://jira.jboss.org/jira/browse/DNA-368 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.3 Reporter: Brian Carothers There is not currently a check in AbstractJcrNode.remove() to see if the node (or any of its child nodes) are targets of references. Per section 7.1.6 of the 1.0.1 specification, this should cause a ReferentialIntegrityException to be thrown. -- 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

2
5
0 / 0

[JBoss JIRA] Created: (DNA-367) AbstractJcrNode.getReferences() Is Incorrect

by Brian Carothers (JIRA)

AbstractJcrNode.getReferences() Is Incorrect -------------------------------------------- Key: DNA-367 URL: https://jira.jboss.org/jira/browse/DNA-367 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.3 Reporter: Brian Carothers AbstractJcrNode.getReferences currently returns all of the reference properties in that node. According to section 6.2.3 of the 1.0.1 specification, it is supposed to return all _other_ nodes that refer to it. -- 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

2
4
0 / 0

[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

1
1
0 / 0

[JBoss JIRA] Created: (DNA-460) NodeTypeManager.unregisterType

by Brian Carothers (JIRA)

NodeTypeManager.unregisterType ------------------------------ Key: DNA-460 URL: https://jira.jboss.org/jira/browse/DNA-460 Project: DNA Issue Type: Feature Request Components: JCR Affects Versions: 0.5 Reporter: Brian Carothers Fix For: 1.0 The JSR-170 specification doesn't require (or really even mention) registering and unregistering custom node types. But since DNA supports registering node types, it seems like its pretty important to support unregistering node types as well. A swapTypes method to atomically port from one set of types to another may also be useful. -- 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

1
6
0 / 0

[JBoss JIRA] Created: (DNA-456) Add JSR-170 Observation Optional Feature

by Brian Carothers (JIRA)

Add JSR-170 Observation Optional Feature ---------------------------------------- Key: DNA-456 URL: https://jira.jboss.org/jira/browse/DNA-456 Project: DNA Issue Type: Feature Request Components: JCR Affects Versions: 0.5 Reporter: Brian Carothers Fix For: 1.0 JSR-170 defines several optional features. The observation feature would provide notification of node and property changes to registered listeners. -- 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

3
9
0 / 0

[JBoss JIRA] Created: (DNA-455) Add Sub-Project to Execute Official TCK

by Brian Carothers (JIRA)

Add Sub-Project to Execute Official TCK --------------------------------------- Key: DNA-455 URL: https://jira.jboss.org/jira/browse/DNA-455 Project: DNA Issue Type: Sub-task Components: JCR Affects Versions: 0.5 Reporter: Brian Carothers Fix For: 0.6 JSR-170 compliance is achieved when all tests in the official TCK are passed. This TCK is distinct from (but related to) the "unofficial" JackRabbit TCK that DNA currently runs each night. In order to achieve full compliance(and make sure that future changes don't break it), an automated means of executing the official TCK (and passing or failing based on the results) should be added. -- 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

2
4
0 / 0

[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

3
9
0 / 0

[JBoss JIRA] Created: (DNA-373) Provide OSGi information in archives (via META-INF/MANIFEST.MF files)

by Randall Hauch (JIRA)

Provide OSGi information in archives (via META-INF/MANIFEST.MF files) --------------------------------------------------------------------- Key: DNA-373 URL: https://jira.jboss.org/jira/browse/DNA-373 Project: DNA Issue Type: Feature Request Components: Development Environment, Documentation Reporter: Randall Hauch Priority: Minor Fix For: Future Releases If the JBoss DNA JAR files each included a META-INF/MANIFEST.MF file, our existing JARs could be used as OSGi bundles within an OSGi class loader environment (for example within Eclipse), while they continue to work outside of an OSGI environment. Another option is to create a single OSGi bundle containing the top-level archives and OSGi bundles for each of our extensions. -- 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

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues August 2009