August 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-421) Support parsing of CREATE/ALTER/DROP VIEW statements for Oracle SQL

by Bojidar Penchev (JIRA)

Support parsing of CREATE/ALTER/DROP VIEW statements for Oracle SQL ------------------------------------------------------------------- Key: DNA-421 URL: https://jira.jboss.org/jira/browse/DNA-421 Project: DNA Issue Type: Sub-task Components: Sequencers, Testing Affects Versions: 0.4 Reporter: Bojidar Penchev Assignee: Bojidar Penchev Fix For: Future Releases Implement additional rules to the ANTLR grammar for Oracle SQL dialect in order to parse CREATE/ALTER/DROP VIEW statements. Implement JUnit tests to test the correctness of parsing. -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (DNA-457) Add JSR-170 Locking Optional Feature

by Brian Carothers (JIRA)

Add JSR-170 Locking Optional Feature ------------------------------------ Key: DNA-457 URL: https://jira.jboss.org/jira/browse/DNA-457 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 locking feature allows users to lock nodes (and, optionally, their descendants) until the session terminates or until they are programatically unlocked. -- 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, 5 months

2
16
0 / 0

[JBoss JIRA] Created: (DNA-323) Create view of artifacts published in repositories

by Johnny Verhaeg (JIRA)

Create view of artifacts published in repositories -------------------------------------------------- Key: DNA-323 URL: https://jira.jboss.org/jira/browse/DNA-323 Project: DNA Issue Type: Sub-task Components: Views Affects Versions: 0.3 Reporter: Johnny Verhaeg Fix For: 0.5 View should allow for multiple repositories, be activated via context menu and menu bar items that reside next to publishing-related actions, and should show mapping to associated workspace items. -- 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, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (DNA-325) Create preference page for working with DNA

by Johnny Verhaeg (JIRA)

Create preference page for working with DNA ------------------------------------------- Key: DNA-325 URL: https://jira.jboss.org/jira/browse/DNA-325 Project: DNA Issue Type: Sub-task Components: Views Affects Versions: 0.3 Reporter: Johnny Verhaeg Fix For: 0.5 Page would include ability to modify decorators, logging levels, etc. -- 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, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (DNA-324) Create publishing-related decorators that can be attached to workspace-related views

by Johnny Verhaeg (JIRA)

Create publishing-related decorators that can be attached to workspace-related views ------------------------------------------------------------------------------------ Key: DNA-324 URL: https://jira.jboss.org/jira/browse/DNA-324 Project: DNA Issue Type: Sub-task Components: Views Affects Versions: 0.3 Reporter: Johnny Verhaeg Fix For: 0.5 We may want to model our approach after SCM repository plug-ins, while making sure we don't conflict with those plug-ins or "over-decorate". -- 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, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (DNA-320) Create connection management view

by Johnny Verhaeg (JIRA)

Create connection management view --------------------------------- Key: DNA-320 URL: https://jira.jboss.org/jira/browse/DNA-320 Project: DNA Issue Type: Sub-task Components: Views Affects Versions: 0.3 Reporter: Johnny Verhaeg Fix For: 0.5 To create and maintain connections to one or more repositories deployed in a container -- 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, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (DNA-322) Create context menu and menu bar items tied to publishing actions

by Johnny Verhaeg (JIRA)

Create context menu and menu bar items tied to publishing actions ----------------------------------------------------------------- Key: DNA-322 URL: https://jira.jboss.org/jira/browse/DNA-322 Project: DNA Issue Type: Sub-task Components: Views Affects Versions: 0.3 Reporter: Johnny Verhaeg Fix For: 0.5 -- 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, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (DNA-505) Svn Repository Source with NPE and other issues while opening connection through Jcr

by Luiz Fernando Teston (JIRA)

Svn Repository Source with NPE and other issues while opening connection through Jcr ------------------------------------------------------------------------------------ Key: DNA-505 URL: https://jira.jboss.org/jira/browse/DNA-505 Project: DNA Issue Type: Bug Components: Connectors Affects Versions: 0.6 Environment: Mac OS X 10.5 - Jvm 1.5 - Maven 2 Reporter: Luiz Fernando Teston Durring a test run to read data from some svn repository using Jcr api from DNA, it throws NullPointerException when trying to read jcr:content for nodes of type folder. This NPEs was really easy to solve. So, I created a patch for this. After this patch, when running the same unit test, it throws a repository source exception saying "svnRepositorySource does not allow same name siblings on nodes: read children of /{http://www.jcp.org/jcr/1.0}content[2] in the ""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace". The stack trace is here also: org.jboss.dna.graph.connector.RepositorySourceException: svnRepositorySource does not allow same name siblings on nodes: read children of /{http://www.jcp.org/jcr/1.0}content[2] in the ""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.checkThePath(SVNRepositoryRequestProcessor.java:1000) at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:151) at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:641) at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:239) at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298) at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219) at org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:176) at org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318) at org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:314) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676) at java.lang.Thread.run(Thread.java:613) -- 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, 7 months

2
16
0 / 0

[JBoss JIRA] Created: (DNA-509) JPA Connector does not close all EntityManager instances that it creates

by Randall Hauch (JIRA)

JPA Connector does not close all EntityManager instances that it creates ------------------------------------------------------------------------ Key: DNA-509 URL: https://jira.jboss.org/jira/browse/DNA-509 Project: DNA Issue Type: Bug Components: Connectors Affects Versions: 0.6 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Blocker Fix For: 0.6 The JPA connector acquires several EntityManager instances, but does not close all of them. This can cause a memory leak in the code, and can cause the JVM to run out of memory. Because the EntityManager is the manager for all of the JPA entity beans (obviously), not closing them will retain objects in memory and prevent them from being garbage collected. There doesn't appear to be an easy way with the current JpaSource and JpaConnection design to properly do this, other than call the JpaSource.close() method. Unfortunately that does not always work, as the current implementation of JpaSource.getConnection() may (if the model is changed) create a new EntityManagerFactory. And even if the JpaConnection did close the EntityManager it's using, the JpaSource's EntityManagerFactory is not guaranteed to be called (even if we adopt a new RepositorySource.close() and require it to be called everywhere). The best way to fix this might be for the JpaSource to not have to maintain all this state (like it currently does), but instead to have an object in-between the JpaSource and JpaConnection that maintains the EntityManagerFactory and creates EntityManagers as needed. The JpaSource can hold onto this, but wouldn't own the instances. This intermediate object can always ensure that all EntityManagers and EntityManagerFactories are closed when no longer needed (e.g., using reference counts and a "last-one-to-leave-turn-the-lights-off" approach). JpaConnection.close() would obvious signal to this object that it no longer needs its EntityManager. JpaSource cannot properly do all this management, because its bean properties can be changed at any time, meaning that even after some connections to one database have been created, the JpaSource can be changed and pointed to a different database. Yes, this isn't good practice, but it technically is possible and thus needs to be addressed. -- 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, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (DNA-508) Workspace move/clone referenceable nodes is failing

by Randall Hauch (JIRA)

Workspace move/clone referenceable nodes is failing --------------------------------------------------- Key: DNA-508 URL: https://jira.jboss.org/jira/browse/DNA-508 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.6 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.6 Two TCK unit test suites ("WorkspaceMoveReferenceableTest" and "WorkspaceCloneReferenceableTest") are not working. These did work before the DNA-466 changes. -- 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, 8 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