December 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-580) Rebrand project to new name

by Randall Hauch (JIRA)

Rebrand project to new name --------------------------- Key: DNA-580 URL: https://jira.jboss.org/jira/browse/DNA-580 Project: DNA Issue Type: Task Affects Versions: 0.7 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Blocker Fix For: 1.0 The project will be rebranded, so we need to change the package names and all references to "JBoss DNA" in the code and documentation. -- 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
10
0 / 0

[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-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-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-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-613) XPath order-by clause is not working

by Randall Hauch (JIRA)

XPath order-by clause is not working ------------------------------------ Key: DNA-613 URL: https://jira.jboss.org/jira/browse/DNA-613 Project: DNA Issue Type: Bug Components: JCR, Query Affects Versions: 0.7 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Blocker Fix For: 0.7 The JCR extension to XPath that adds support for 'order by' is not working. -- 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, 4 months

1
5
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, 4 months

1
6
0 / 0

[JBoss JIRA] Created: (DNA-591) NullPointerException in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded()

by Barry LaFond (JIRA)

NullPointerException in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded() ----------------------------------------------------------------------------- Key: DNA-591 URL: https://jira.jboss.org/jira/browse/DNA-591 Project: DNA Issue Type: Bug Affects Versions: 0.7 Reporter: Barry LaFond Attachments: test_cnd.cnd Using the attached CND file, the repository set-up fails with an NPE when attempting to resolve node types. (ala config.repository(xxxxxx).addNodeTypes('test_cnd.cnd') java.lang.NullPointerException at org.jboss.dna.jcr.JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded(JcrNodeDefinition.java:113) at org.jboss.dna.jcr.JcrNodeDefinition.getRequiredPrimaryTypes(JcrNodeDefinition.java:161) at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1938) at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1861) at org.jboss.dna.jcr.RepositoryNodeTypeManager.registerNodeTypes(RepositoryNodeTypeManager.java:1513) at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:246) at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:161) My original DDL seqencer cnd is much more complex, but by paring it down to the following, the error still occured. //------------------------------------------------------------------------------ // N A M E S P A C E S //------------------------------------------------------------------------------ <jcr='http://www.jcp.org/jcr/1.0'> <nt='http://www.jcp.org/jcr/nt/1.0'> <mix='http://www.jcp.org/jcr/mix/1.0'> <ddl='http://jboss.org/dna/ddl/1.0'> [ddl:statement] mixin abstract - ddl:expression (string) mandatory + * (ddl:ddlProblem) = ddl:ddlProblem multiple [ddl:schemaDefinition] > ddl:statement mixin - ddl:defaultCharacterSetName (STRING) + * (ddl:ddlStatement) = ddl:ddlStatement multiple [ddl:ddlProblem] mixin - ddl:problemLevel (LONG) mandatory - ddl:message (STRING) mandatory The [ddl:schemaDefinition] mixin is the ONLY mixin that both extends a mixin and allows children of the same mixin type (i.e. [ddl:statement]) however the NPE is occuring when attempting to find the primary node type for [ddl:ddlProblem] Note that the NPE does not occur when the [ddl:schemaDefinition] type is removed. -- 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, 4 months

3
11
0 / 0

[JBoss JIRA] Created: (DNA-610) Allow JPA Connector to be generic (not require hibernate)

by John Ament (JIRA)

Allow JPA Connector to be generic (not require hibernate) --------------------------------------------------------- Key: DNA-610 URL: https://jira.jboss.org/jira/browse/DNA-610 Project: DNA Issue Type: Feature Request Components: Connectors Affects Versions: 0.6 Reporter: John Ament Priority: Minor Allowing the use of any JPA provider (not just hibernate) would make it easier to use the JPA connector on other app servers - e.g. glassfish, weblogic, etc. There is no direct dependency on hibernate's features in the jpa connector, other than using their Ejb3Configurator. It looks like the config settings could be done in such a way that the persistence.xml could be provided by the bundling application. Design of it should probably be discussed a bit more thoroughly, and hopefully come up with a way that it can be automatically bootstrapped by the container, instead of the way configuration is done now. I'm willing to provide the implementation of this if you'd like. -- 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, 4 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues December 2009