December 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-578) JPA Connector Simple Model Does Not Support "supportsUpdates" Property

by Brian Carothers (JIRA)

JPA Connector Simple Model Does Not Support "supportsUpdates" Property ---------------------------------------------------------------------- Key: DNA-578 URL: https://jira.jboss.org/jira/browse/DNA-578 Project: DNA Issue Type: Feature Request Components: Connectors Affects Versions: 0.6 Reporter: Brian Carothers Priority: Optional Fix For: Future Releases The JPA Basic Model supported a read-only mode by setting the "supportsUpdates" property to false on the JpaSource. This feature was unintentionally omitted from the Simple Model. This could be added to the MapRequestProcessor and MapRepository classes pretty easily (which would enable it for the Simple Model, the JBoss Cache repository, Infinispan repository, and the InMemoryRepository (where it would be worse than useless). However, I'm struggling to see where this would be used, especially since the database for the JPA connector is not intended to be shared. If anyone needs to set up a master-clone configuration for DNA where the master DNA server has read-write access to the database and the clone has read-only access, we could add this pretty quickly. -- 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

16 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (DNA-105) Sequence metadata from delimited text files

by Greg Haber (JIRA)

Sequence metadata from delimited text files ------------------------------------------- Key: DNA-105 URL: http://jira.jboss.com/jira/browse/DNA-105 Project: DNA Issue Type: Feature Request Components: Sequencers Reporter: Greg Haber Priority: Minor It is a somewhat common practice for delimited text files such as comma-separated (CSV) or tab delimited files to contain a list of column names in the first line of the file. A sequencer to capture this metadata could be useful,and should be straightforward to implement. -- 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

16 years, 4 months

3
8
0 / 0

[JBoss JIRA] Created: (DNA-601) POM Version of HSQLDB No Longer Exists in Maven Repository

by Brian Carothers (JIRA)

POM Version of HSQLDB No Longer Exists in Maven Repository ---------------------------------------------------------- Key: DNA-601 URL: https://jira.jboss.org/jira/browse/DNA-601 Project: DNA Issue Type: Bug Affects Versions: 0.6 Reporter: Brian Carothers Assignee: Brian Carothers Priority: Blocker The HSQLDB version 1.8.0.7 no longer exists in the project Maven repository. Current versions that we can choose from are 1.7.2, 1.8.0.2, 1.8.0.8-brew, 1.8.0.8patch01-brew, and 1.8.0.8patch02-brew. -- 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

16 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (DNA-600) mvn eclipse:clean eclipse:eclipse doesn't work on dna-connector-store-jpa

by Serge Emmanuel Pagop (JIRA)

mvn eclipse:clean eclipse:eclipse doesn't work on dna-connector-store-jpa ------------------------------------------------------------------------- Key: DNA-600 URL: https://jira.jboss.org/jira/browse/DNA-600 Project: DNA Issue Type: Bug Components: Development Environment Affects Versions: 0.7, 1.0, 1.1, Future Releases Environment: MAC OS X 10.6.2, java version "1.6.0_17", Apache Maven 2.2.0 Reporter: Serge Emmanuel Pagop Assignee: Serge Emmanuel Pagop Priority: Critical Fix For: 0.7 During building the DNA modules with mvn clean install eclipse:clean eclipse:eclipse I got this error: ------ Start Error Trace [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Request to merge when 'filtering' is not identical. Original=resource src/test/resources: output=target/test-classes, include=[*|**/*], exclude=[database.properties|**/*.java], test=true, filtering=false, merging with=resource src/test/resources: output=target/test-classes, include=[database.properties], exclude=[**/*.java], test=true, filtering=true at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Request to merge when 'filtering' is not identical. Original=resource src/test/resources: output=target/test-classes, include=[*|**/*], exclude=[database.properties|**/*.java], test=true, filtering=false, merging with=resource src/test/resources: output=target/test-classes, include=[database.properties], exclude=[**/*.java], test=true, filtering=true ------ End Error Trace Because this is a bug in the maven eclipse plugin version 2.7, this link "http://stackoverflow.com/questions/1397903/setting-project-for-eclipse-us..." gives more information about -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-593) File system connector documentation is missing the 'updatesAllowed' property

by Randall Hauch (JIRA)

File system connector documentation is missing the 'updatesAllowed' property ---------------------------------------------------------------------------- Key: DNA-593 URL: https://jira.jboss.org/jira/browse/DNA-593 Project: DNA Issue Type: Bug Components: Connectors, Documentation Affects Versions: 0.6 Reporter: Randall Hauch Assignee: Brian Carothers Priority: Critical Fix For: 0.7 The Reference Guide chapter on the File System connector (http://docs.jboss.org/jbossdna/0.6/manuals/reference/html/file-system-con...) is missing the 'updatesAllowed' property. Marking as 'critical' just so it gets done. -- 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

16 years, 4 months

2
4
0 / 0

[JBoss JIRA] Resolved: (DNA-37) Federate schema information from relational sources

by Brian Carothers (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-37?page=com.atlassian.jira.plugin.... ] Brian Carothers resolved DNA-37. -------------------------------- Fix Version/s: 0.7 (was: 1.1) Resolution: Done Committed patch to complete integration with JCR layer. At this point, the connector functions like any other read-only connector, so I am going to mark this defect as resolved. If any new feature requests or bugs come up, they can be opened and addressed separately. > Federate schema information from relational sources > --------------------------------------------------- > > Key: DNA-37 > URL: https://jira.jboss.org/jira/browse/DNA-37 > Project: DNA > Issue Type: Feature Request > Components: Connectors > Reporter: Randall Hauch > Assignee: Brian Carothers > Priority: Minor > Fix For: 0.7 > > Attachments: DNA-37_deletes_and_project_pom.patch, DNA-37_graph_changes.patch, DNA-37_jcr_works.patch, DNA-37_jdbc_meta_connector.patch, DNA-37_mysql_postgresql.patch, DNA-37_other_databases.patch > > > Create a connector for the federation engine that contributes and exposes the database schema information for a relational database (via JDBC) into the federated repository. This would make it possible to have a repository provide information about the databases in an organization. One choice would be whether to import (and copy) the schema structure, or to provide access to it in real time. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (DNA-37) Federate schema information from relational sources

by Brian Carothers (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-37?page=com.atlassian.jira.plugin.... ] Brian Carothers updated DNA-37: ------------------------------- Attachment: DNA-37_jcr_works.patch Attached patch that adds custom node types, a JCR integration test for the connector, a provision to the integration test framework to allow for the importing of a custom node types file, and a minor fix to getProperties(). > Federate schema information from relational sources > --------------------------------------------------- > > Key: DNA-37 > URL: https://jira.jboss.org/jira/browse/DNA-37 > Project: DNA > Issue Type: Feature Request > Components: Connectors > Reporter: Randall Hauch > Assignee: Brian Carothers > Priority: Minor > Fix For: 1.1 > > Attachments: DNA-37_deletes_and_project_pom.patch, DNA-37_graph_changes.patch, DNA-37_jcr_works.patch, DNA-37_jdbc_meta_connector.patch, DNA-37_mysql_postgresql.patch, DNA-37_other_databases.patch > > > Create a connector for the federation engine that contributes and exposes the database schema information for a relational database (via JDBC) into the federated repository. This would make it possible to have a repository provide information about the databases in an organization. One choice would be whether to import (and copy) the schema structure, or to provide access to it in real time. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (DNA-37) Federate schema information from relational sources

by Brian Carothers (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-37?page=com.atlassian.jira.plugin.... ] Brian Carothers updated DNA-37: ------------------------------- Attachment: DNA-37_other_databases.patch Attached patch that adds DDL and code corrections for other databases (Oracle 10g/11g, MS SQL 2008, IBM DB2 v9, Sybase ASE 15). > Federate schema information from relational sources > --------------------------------------------------- > > Key: DNA-37 > URL: https://jira.jboss.org/jira/browse/DNA-37 > Project: DNA > Issue Type: Feature Request > Components: Connectors > Reporter: Randall Hauch > Assignee: Brian Carothers > Priority: Minor > Fix For: 1.1 > > Attachments: DNA-37_deletes_and_project_pom.patch, DNA-37_graph_changes.patch, DNA-37_jdbc_meta_connector.patch, DNA-37_mysql_postgresql.patch, DNA-37_other_databases.patch > > > Create a connector for the federation engine that contributes and exposes the database schema information for a relational database (via JDBC) into the federated repository. This would make it possible to have a repository provide information about the databases in an organization. One choice would be whether to import (and copy) the schema structure, or to provide access to it in real time. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (DNA-596) Relax security by default to be more accessible to new users

by Jason Dobies (JIRA)

Relax security by default to be more accessible to new users ------------------------------------------------------------ Key: DNA-596 URL: https://jira.jboss.org/jira/browse/DNA-596 Project: DNA Issue Type: Feature Request Components: Documentation, Examples Affects Versions: 0.6 Reporter: Jason Dobies While doing a quick prototype/proof of concept using DNA for the first time, I ran into two issues: - I wasn't able to simply login using Repository.login(). I had to configure and use JAAS. - I wasn't able to write files to a FileSystemSource, getting an error similar to "source does not support update" The latter was fixed by adding the configuration property "updatesAllowed" and setting it to true. After some discussion in the chat room with bcar and rhauch, it sounds like everyone is on board making the initial user experience easier (avoiding the above two issues). A potential side JIRA to this would be to add documentation on hardening DNA for a production deployment, which would mention things such as disabling anonymous login and file writing (assuming that's desired). On a personal note: the docs do a really good job of laying out the other steps I needed to take with regard to creating the configuration, engine, repository, and session. Once I got JAAS configured the code I had written to interact with DNA worked fine. -- 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

16 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (DNA-594) The JDBC Metadata Connector documentation in Reference Guide is missing

by Randall Hauch (JIRA)

The JDBC Metadata Connector documentation in Reference Guide is missing ----------------------------------------------------------------------- Key: DNA-594 URL: https://jira.jboss.org/jira/browse/DNA-594 Project: DNA Issue Type: Bug Components: Connectors, Documentation Affects Versions: 0.6 Reporter: Randall Hauch Assignee: Brian Carothers Priority: Critical Fix For: 0.7 The Reference Guide lists in the TOC the chapter on the JDBC Metadata Connector and has a link for it, but the chapter doesn't exist. Since 0.7 won't have include the connector, we should remove it from the TOC, and add it back in when we have something. -- 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

16 years, 4 months

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues December 2009