September 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-522) CND files that use keywords as names cannot be read in

by Randall Hauch (JIRA)

CND files that use keywords as names cannot be read in ------------------------------------------------------ Key: DNA-522 URL: https://jira.jboss.org/jira/browse/DNA-522 Project: DNA Issue Type: Bug Components: JCR, Sequencers Affects Versions: 0.6 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.7 The CND parser fails to load CND files that use keywords as unquoted names. Apparently this is a 'feature' of ANTLR, since the generated lexer always returns keyword tokens whenever a token appears in the file (regardless of the position). -- 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

1
2
0 / 0

[JBoss JIRA] Created: (DNA-517) Update Reference Guide and Getting Started Document for New and Modified Features

by Brian Carothers (JIRA)

Update Reference Guide and Getting Started Document for New and Modified Features --------------------------------------------------------------------------------- Key: DNA-517 URL: https://jira.jboss.org/jira/browse/DNA-517 Project: DNA Issue Type: Bug Components: Documentation Affects Versions: 0.5 Reporter: Brian Carothers We need to review the documentation and make sure that it is still accurate. -- 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

2
3
0 / 0

[JBoss JIRA] Created: (DNA-520) DNA w/ JPA/Oracle - bad create table DNA_OPTIONS

by John Ament (JIRA)

DNA w/ JPA/Oracle - bad create table DNA_OPTIONS ------------------------------------------------- Key: DNA-520 URL: https://jira.jboss.org/jira/browse/DNA-520 Project: DNA Issue Type: Bug Environment: Oracle 10g JBoss AS 5.1 JDK6 Reporter: John Ament The create table generated for DNA_OPTIONS is create table DNA_OPTIONS (NAME varchar2(512 char) not null unique, VALUE varchar2(512 char) not null, primary key (NAME)) However, to work correctly in Oracle, it should be: create table DNA_OPTIONS (NAME varchar2(512 char) not null, VALUE varchar2(512 char) not null, primary key (NAME)) which means we have to remove the unique=true attribute from dna options entity. There may be another entity like this as well, will double check. -- 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

2
4
0 / 0

[JBoss JIRA] Created: (DNA-515) JPA connector reports error when inserting default (and blank) namespace URI into Oracle database

by Randall Hauch (JIRA)

JPA connector reports error when inserting default (and blank) namespace URI into Oracle database ------------------------------------------------------------------------------------------------- Key: DNA-515 URL: https://jira.jboss.org/jira/browse/DNA-515 Project: DNA Issue Type: Bug Components: Connectors Affects Versions: 0.6 Reporter: Randall Hauch Priority: Blocker Fix For: 0.6 The user meetoblivion reported on the forums [1] that he was getting an error when he called session.getRootNode().addNode("somepage") and session.getRootNode().addNode("somepage","nt:unstructured"); The full stack trace is listed on the forum thread, but the relevant part is here: 2009-09-08 10:45:10,059 WARN [org.hibernate.util.JDBCExceptionReporter] (pool-159-thread-2) SQL Error: 1400, SQLState: 23000 2009-09-08 10:45:10,108 ERROR [org.hibernate.util.JDBCExceptionReporter] (pool-159-thread-2) ORA-01400: cannot insert NULL into ("JCRPUBLIC"."DNA_NAMESPACES"."URI") 2009-09-08 10:45:10,108 WARN [org.hibernate.util.JDBCExceptionReporter] (pool-159-thread-2) SQL Error: 1400, SQLState: 23000 2009-09-08 10:45:10,108 ERROR [org.hibernate.util.JDBCExceptionReporter] (pool-159-thread-2) ORA-01400: cannot insert NULL into ("JCRPUBLIC"."DNA_NAMESPACES"."URI") Oracle doesn't like empty VARCHAR values, and attempts instead to insert a NULL value rather than the empty VARCHAR value. This is currently a problem, because the DNA_NAMESPACES.URI column is not nullable. [1] http://www.jboss.org/index.html?module=bb&op=viewtopic&t=160723 -- 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

2
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, 8 months

2
16
0 / 0

[JBoss JIRA] Created: (DNA-516) Reference Guide example that defines node types programmatically has several typos

by Randall Hauch (JIRA)

Reference Guide example that defines node types programmatically has several typos ---------------------------------------------------------------------------------- Key: DNA-516 URL: https://jira.jboss.org/jira/browse/DNA-516 Project: DNA Issue Type: Bug Components: Documentation, Examples Affects Versions: 0.5 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.6 The example in Reference Guide that shows how to programmatically define node types (http://jboss.org/file-access/default/members/dna/freezone/docs/0.5/manual...) has several typos: 1) Change NodeTypeManager on line 2 to JcrNodeTypeManager 2) Change [code]childNode.setRequiredPrimaryTypeNames(...)[/code] to [code]childNode.setRequiredPrimaryTypes(...)[/code] 3) Add a boolean argument in the method call in the last line. Also, the text in this section could be more clear about the in which package the DNA-specific interfaces exist. -- 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

2
5
0 / 0

[JBoss JIRA] Created: (DNA-513) REST server does not correctly encode binary values

by Randall Hauch (JIRA)

REST server does not correctly encode binary values --------------------------------------------------- Key: DNA-513 URL: https://jira.jboss.org/jira/browse/DNA-513 Project: DNA Issue Type: Bug Components: Web Application Affects Versions: 0.5 Reporter: Randall Hauch Assignee: Brian Carothers Fix For: 0.6 The REST server (or rather web application) does not properly encode binary values in the JSON results, and instead is embedding the toString() version of the byte[]. The binary values should instead be encoded in Base64, and the REST client should be able to then read (or upload) binary values using this approach. (If the binary value is already a Base64-encoded representation, then the JSON content will just be a Base64-encoded representation of the value that happens to be Base64-encoded. Shouldn't be a problem.) -- 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

2
8
0 / 0

[JBoss JIRA] Created: (DNA-510) The JPA RepositorySource should provide way to specify the 'hibernate.hbm2ddl.auto' property

by Randall Hauch (JIRA)

The JPA RepositorySource should provide way to specify the 'hibernate.hbm2ddl.auto' property -------------------------------------------------------------------------------------------- Key: DNA-510 URL: https://jira.jboss.org/jira/browse/DNA-510 Project: DNA Issue Type: Bug Components: Connectors Affects Versions: 0.5 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.6 The 'hibernate.hbm2ddl.auto' property defines Hibernate's behavior for interacting/changing the database schema. Typically in production the database schema should already exist and should not be changed, while for development users may want to have Hibernate dynamically create the schema. Therefore, one value is not sufficient, and the JpaSource class should allow setting this value. (It may be worthwhile to add the ability to set arbitrary properties on the JpaSource, and then modify the DnaConfiguration and DnaEngine code to look for JavaBean methods for the properties, and if there are none to look for and use a "setProperty(String,String)" method on the RepositorySource. This would make it possible to always add any Hibernate property to the JpaSource configuration.) -- 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
5
0 / 0

[JBoss JIRA] Created: (DNA-512) Add simple example (or integration test) that shows all of the code required to use JCR with a JDBC database

by Randall Hauch (JIRA)

Add simple example (or integration test) that shows all of the code required to use JCR with a JDBC database ------------------------------------------------------------------------------------------------------------ Key: DNA-512 URL: https://jira.jboss.org/jira/browse/DNA-512 Project: DNA Issue Type: Task Components: Documentation, Examples, JCR, Testing Affects Versions: 0.5 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Minor Fix For: 0.6 We don't have an integration test that shows how to set up a JCR repository instance to use a JDBC database. -- 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
2
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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues September 2009