June 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-463) Federation connector incorrectly expects identification properties on all source nodes

by Randall Hauch (JIRA)

Federation connector incorrectly expects identification properties on all source nodes -------------------------------------------------------------------------------------- Key: DNA-463 URL: https://jira.jboss.org/jira/browse/DNA-463 Project: DNA Issue Type: Bug Affects Versions: 0.5 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Blocker Fix For: 0.6 The JoinProcessor always expects identification properties on all nodes coming from sources. Since some connectors do not have identification properties, this causes a NullPointerException when accumulating the identification properties: java.lang.NullPointerException at org.jboss.dna.graph.connector.federation.JoinRequestProcessor.process(JoinRequestProcessor.java:272) at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:235) at org.jboss.dna.graph.connector.federation.JoinRequestProcessor.process(JoinRequestProcessor.java:164) at org.jboss.dna.graph.connector.federation.FederatedRepositoryConnection.execute(FederatedRepositoryConnection.java:220) at org.jboss.dna.graph.connector.RepositoryConnectionPool$ConnectionWrapper.execute(RepositoryConnectionPool.java:991) at org.jboss.dna.graph.Graph.execute(Graph.java:243) at org.jboss.dna.graph.Graph$5.process(Graph.java:186) at org.jboss.dna.graph.request.RequestBuilder.readNode(RequestBuilder.java:139) at org.jboss.dna.graph.Graph.getNodeAt(Graph.java:1843) at org.jboss.dna.graph.Graph.getNodeAt(Graph.java:1853) The problem is this snippet: // Accumulate the identification properties ... for (Property propertyInSource : readFromSource.getActualLocationOfNode().getIdProperties()) { ... } since the JavaDoc for getIdProperties() says that it should return null if there are no properties. This code should be wrapped with a check to see if the Location has identification properties. -- 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, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (DNA-461) new item in source doesn't appear in federated source projection

by Luiz Fernando Teston (JIRA)

new item in source doesn't appear in federated source projection ----------------------------------------------------------------- Key: DNA-461 URL: https://jira.jboss.org/jira/browse/DNA-461 Project: DNA Issue Type: Bug Components: Connectors, Examples, Federation Affects Versions: 0.5 Environment: Mac OS 10.5.7 with JVM 1.6 and maven 2.1 Reporter: Luiz Fernando Teston I'm not sure if it is a bug or an error in my configuration or environment. I just follow the examples without getting the CNDs and also without importing the example data. When I create some new item using the graph api this item is created in a correct way on the repository source that I'm using (example: cars) but it doesn't appears on the projection on federated source (example: vehicles/cars). I created this test case that should be used on doc/examples/repository project. I also did this same test using the JAAS configuration. package org.jboss.example.dna.repository; import static org.hamcrest.core.Is.is; import static org.hamcrest.core.IsNull.notNullValue; import static org.junit.Assert.assertThat; import java.net.URL; import org.jboss.dna.graph.Graph; import org.jboss.dna.jcr.JcrConfiguration; import org.jboss.dna.jcr.JcrEngine; import org.junit.Test; public class FederationOnDifferentSourcesTest { @Test public void shouldHaveProjectionInsideFederatedSource() throws Exception { JcrConfiguration configuration = new JcrConfiguration(); URL configUrl = Thread.currentThread().getContextClassLoader() .getResource("configRepository.xml"); assertThat(configUrl, is(notNullValue())); configuration.loadFrom(configUrl); JcrEngine engine = configuration.build(); engine.start(); Graph vehiclesGraph = engine.getGraph("Vechicles"); assertThat(vehiclesGraph.getNodeAt("/Cars"), is(notNullValue())); } @Test public void shouldCreateItemOnSourceRepositoryAndShowTheSameItemOnFederatedSource() throws Exception { JcrConfiguration configuration = new JcrConfiguration(); URL configUrl = Thread.currentThread().getContextClassLoader() .getResource("configRepository.xml"); assertThat(configUrl, is(notNullValue())); configuration.loadFrom(configUrl); JcrEngine engine = configuration.build(); engine.start(); Graph carsGraph = engine.getGraph("Cars"); carsGraph.create("/Honda"); assertThat(carsGraph.getNodeAt("/Honda"), is(notNullValue())); Graph vehiclesGraph = engine.getGraph("Vehicles"); assertThat(vehiclesGraph.getNodeAt("/Cars/Honda"), is(notNullValue())); } } -- 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, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (DNA-453) Implement Workspace.copy(String, String, String, boolean)

by Brian Carothers (JIRA)

Implement Workspace.copy(String, String, String, boolean) --------------------------------------------------------- Key: DNA-453 URL: https://jira.jboss.org/jira/browse/DNA-453 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.5 Reporter: Brian Carothers DNA currently supports the same-workspace version of the workspace copy method. It also must support the cross-workspace copy method for L2 compliance. -- 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, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (DNA-459) Mandatory Child Nodes Can Be Removed

by Brian Carothers (JIRA)

Mandatory Child Nodes Can Be Removed ------------------------------------ Key: DNA-459 URL: https://jira.jboss.org/jira/browse/DNA-459 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.5 Reporter: Brian Carothers Fix For: 0.6 The JCR implementation will not allow a new node that is missing a mandatory child node to be saved. It will, however, allow an existing node to be saved after a mandatory child node is removed and not replaced. This violates the spec and breaks a TCK test case. -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (DNA-458) Create SequencerOutputMap.addProperty Method

by Brian Carothers (JIRA)

Create SequencerOutputMap.addProperty Method -------------------------------------------- Key: DNA-458 URL: https://jira.jboss.org/jira/browse/DNA-458 Project: DNA Issue Type: Feature Request Components: Sequencers Affects Versions: 0.5 Reporter: Brian Carothers Priority: Optional Fix For: 1.0 It would be helpful to either add an addProperty method to SequencerOutputMap or change the semantics of SequencerOutputMap.setProperty to append values instead of overwriting them. This would allow multiple sequencers (e.g., a JAR sequencer, an ESB JAR sequencer, a SOA Governance sequencer) to operate on the same input and write to the same output nodes while adding one or more mixin types per sequencer (i.e., JAR sequencer adds java:jar mixin type, SOA-G sequencer adds jboss:artifact mixin type, no conflicts). There are, of course, other ways to solve this 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (DNA-446) Screenshots of example applications need to be updated in the Getting Started document

by Randall Hauch (JIRA)

Screenshots of example applications need to be updated in the Getting Started document -------------------------------------------------------------------------------------- Key: DNA-446 URL: https://jira.jboss.org/jira/browse/DNA-446 Project: DNA Issue Type: Task Components: Documentation Affects Versions: 0.4 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.5 The screenshots in the Getting Started document showing the running examples need to be updated. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-449) Federation connector does not find it's configuration when imported using the JcrConfiguration

by Randall Hauch (JIRA)

Federation connector does not find it's configuration when imported using the JcrConfiguration ---------------------------------------------------------------------------------------------- Key: DNA-449 URL: https://jira.jboss.org/jira/browse/DNA-449 Project: DNA Issue Type: Bug Components: API, Connectors Affects Versions: 0.4 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Blocker Fix For: 0.5 When a configuration file is imported using the JcrConfiguration (or DnaConfiguration), the Federation Connector doesn't find the connector's workspace definitions. I believe this is because the configuration files are imported with slightly modified paths. This problem prevents the federation connector from being used, and thus is a bigger problem. Fixing this should be pretty straightforward and is low risk, and simply involves supplying the correct path to the source configuration element when the RepositorySource's are initialized by the RepositoryLibrary, then changing the FederatedRepositorySource to use this new path. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-447) Make REST PUT Method Support add/removeMixin Like POST Method

by Brian Carothers (JIRA)

Make REST PUT Method Support add/removeMixin Like POST Method ------------------------------------------------------------- Key: DNA-447 URL: https://jira.jboss.org/jira/browse/DNA-447 Project: DNA Issue Type: Bug Components: JCR, Server Affects Versions: 0.4 Reporter: Brian Carothers Assignee: Brian Carothers Priority: Minor Fix For: 1.0 The REST POST method automatically translates the jcr:mixinTypes property (if set on the request) into a series of addMixin calls. The PUT method should compare the jcr:mixinTypes property (if present) to the existing mixin types for the node and attempt to add or remove mixin types as needed. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-443) Java sequencer is not saving content correctly

by Randall Hauch (JIRA)

Java sequencer is not saving content correctly ---------------------------------------------- Key: DNA-443 URL: https://jira.jboss.org/jira/browse/DNA-443 Project: DNA Issue Type: Bug Components: Examples, Sequencers Affects Versions: 0.4 Reporter: Randall Hauch Fix For: 0.6 The Java sequencer doesn't appear to be sequencing the Java source code and saving it correctly. The SequencingClientTest.shouldUploadAndSequenceJavaSourceFile() fails and has been temporarily ignored. -- 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, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (DNA-389) Change Getting Started examples to use the DnaConfiguration and JcrConfiguration components

by Randall Hauch (JIRA)

Change Getting Started examples to use the DnaConfiguration and JcrConfiguration components ------------------------------------------------------------------------------------------- Key: DNA-389 URL: https://jira.jboss.org/jira/browse/DNA-389 Project: DNA Issue Type: Task Components: Documentation, Examples Reporter: Randall Hauch Fix For: 0.5 The DnaConfiguration and JcrConfiguration components were created previously (see DNA-58), but the Getting Started examples and document (and Reference Guide document) need to be changed to use them. -- 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, 11 months

1
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues June 2009