October 2008 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-242) Change the XML importer code to no longer use XmlSequencer

by Randall Hauch (JIRA)

Change the XML importer code to no longer use XmlSequencer ---------------------------------------------------------- Key: DNA-242 URL: https://jira.jboss.org/jira/browse/DNA-242 Project: DNA Issue Type: Task Affects Versions: 0.2 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Critical Fix For: 0.3 The XML import capability is currently reusing the XmlSequencer for it's implementation. The XmlSequencer behavior, however, doesn't really generate the graph content that is compatible with "importing JCR graph content". For example, it includes in the generated content all of the DTD entities, comments, etc. So, we should really move most of this functionality into an XML importer class that is relatively configurable in what it's behavior is. (For example, retain DTD content, retain XML comments, replace entity references with values, etc.) Then, this should be used for the Graph importer, and it can be used by the XmlSequencer. Because the XmlSequencer doesn't really work for how it's used, JPAV and I agree that it is critical to fix in 0.3. -- 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

17 years, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (DNA-245) Add methods to Name, Path.Segment, and Path to allow using custom delimiters

by Randall Hauch (JIRA)

Add methods to Name, Path.Segment, and Path to allow using custom delimiters ---------------------------------------------------------------------------- Key: DNA-245 URL: https://jira.jboss.org/jira/browse/DNA-245 Project: DNA Issue Type: Task Components: Graph Affects Versions: 0.2 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Minor Fix For: 0.3 The current "getString(...)" methods provide a way to encode all of the characters in the Name, Path.Segment, and/or Path, except for the delimiters. Add another form of getString(...) that takes a second TextEncoder that would be used to encode any of the delimiters. -- 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

17 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-186) Remove ProgressMonitor from StreamSequencer.sequence signature

by Johnny Verhaeg (JIRA)

Remove ProgressMonitor from StreamSequencer.sequence signature -------------------------------------------------------------- Key: DNA-186 URL: https://jira.jboss.org/jira/browse/DNA-186 Project: DNA Issue Type: Sub-task Reporter: Johnny Verhaeg -- 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

17 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (DNA-230) Enhance NamespaceRegistry with additional functionality

by Randall Hauch (JIRA)

Enhance NamespaceRegistry with additional functionality ------------------------------------------------------- Key: DNA-230 URL: https://jira.jboss.org/jira/browse/DNA-230 Project: DNA Issue Type: Feature Request Components: API, SPI Affects Versions: 0.2 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Minor Fix For: 0.3 NamespaceRegistry has no ability to obtain a consistent snapshot of the prefix/URI pairs, which is important for a thread-safe and concurrent namespace registry. Also, may want an alternative registry that takes a register behavior enum specifying what to do when registering a namespace if that namespace or prefix is already used. Options include: 1) replace, 2) use automatically generated prefix, 3) fail -- 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

17 years, 6 months

1
4
0 / 0

[JBoss JIRA] Updated: (DNA-34) Federate content stored on file system

by Johnny Verhaeg (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-34?page=com.atlassian.jira.plugin.... ] Johnny Verhaeg updated DNA-34: ------------------------------ Fix Version/s: 0.4 (was: 0.3) Pushing to 0.4 > Federate content stored on file system > -------------------------------------- > > Key: DNA-34 > URL: https://jira.jboss.org/jira/browse/DNA-34 > Project: DNA > Issue Type: Feature Request > Components: Connectors > Reporter: Randall Hauch > Assignee: Stefano Maestri > Fix For: 0.4 > > > Create a connector for the federation engine that contributes and exposes content stored on the file system (in one or more directories) into the federated repository. This connector would dynamically create the "nt:file" and "nt:folder" nodes to mirror the contents of the file system. -- 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Commented: (DNA-55) REST-based API for remote access and usage

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-55?page=com.atlassian.jira.plugin.... ] Randall Hauch commented on DNA-55: ---------------------------------- Another interesting article on REST APIs that summarizes Roy's post (but that adds a number of other useful links): http://www.infoq.com/news/2008/10/rest-api > REST-based API for remote access and usage > ------------------------------------------ > > Key: DNA-55 > URL: https://jira.jboss.org/jira/browse/DNA-55 > Project: DNA > Issue Type: Feature Request > Components: Server, Web Application > Reporter: Randall Hauch > Priority: Minor > Fix For: Future Releases > > > Create a DNA server that uses a REST-based API, allowing client applications to access and use the repository using HTTP for protocol/transport. > AtomPub is also very interesting (as it is RESTful) for a message structure, but it doesn't currently support hierarchical data. And although one could build a repository to be flatter (or at least exposed though collections; see how Bento does it: http://www.filemaker.com/bento/), it may be difficult to have no way of interacting with the hierarchical data. Bento and iTunes both show how powerful user-defined collections (and "smart collections") can be, so maybe adopting a collection-only approach would work (at least for remote access). -- 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Commented: (DNA-55) REST-based API for remote access and usage

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-55?page=com.atlassian.jira.plugin.... ] Randall Hauch commented on DNA-55: ---------------------------------- One of the things we want to develop for JBoss DNA is an ability to interface and interact with the repository using a RESTful API. We should consider RESTeasy - no way do we want to implement our own RESTful library. But there's more to a RESTful API than just picking an enabling library. Perhaps the biggest task is actually designing the RESTful API. This includes among other things the design of the URIs (e.g., what the URIs look like, how they map to the "resources" that exist in a repository, and how they different verbs map to actions on these resources), the representations of the resources and the choice of media types used by those representations (e.g., HTML, XML, JSON,etc.), and ensuring that the appropriate actions are mapped to the underlying resources. For future reference, here are some interesting links: - Recent post by Roy Fielding on what a REST API actually needs to be like: http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven - Roy's definition of "hypertext", which is more general than what most people probably assume: http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven#com... - Interpretation of Roy's REST API post (above): http://www.25hoursaday.com/weblog/2008/10/24/RESTAPIDesignInventMediaType... - Apache Sling: http://incubator.apache.org/sling > REST-based API for remote access and usage > ------------------------------------------ > > Key: DNA-55 > URL: https://jira.jboss.org/jira/browse/DNA-55 > Project: DNA > Issue Type: Feature Request > Components: Server, Web Application > Reporter: Randall Hauch > Priority: Minor > Fix For: Future Releases > > > Create a DNA server that uses a REST-based API, allowing client applications to access and use the repository using HTTP for protocol/transport. > AtomPub is also very interesting (as it is RESTful) for a message structure, but it doesn't currently support hierarchical data. And although one could build a repository to be flatter (or at least exposed though collections; see how Bento does it: http://www.filemaker.com/bento/), it may be difficult to have no way of interacting with the hierarchical data. Bento and iTunes both show how powerful user-defined collections (and "smart collections") can be, so maybe adopting a collection-only approach would work (at least for remote access). -- 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (DNA-185) Modify SequencerContext to extend ExecutionContext

by Johnny Verhaeg (JIRA)

Modify SequencerContext to extend ExecutionContext -------------------------------------------------- Key: DNA-185 URL: https://jira.jboss.org/jira/browse/DNA-185 Project: DNA Issue Type: Sub-task Reporter: Johnny Verhaeg -- 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

17 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (DNA-232) situation with the running examples application

by Serge Emmanuel Pagop (JIRA)

situation with the running examples application ----------------------------------------------- Key: DNA-232 URL: https://jira.jboss.org/jira/browse/DNA-232 Project: DNA Issue Type: Bug Components: Examples Affects Versions: Future Releases Environment: Test on Mac OS X Reporter: Serge Emmanuel Pagop Assignee: Serge Emmanuel Pagop Fix For: Future Releases first I uploaded the MySource.java in repository and then with s) I searched the metadata without problem and secondly I uploaded the two media sample1.mp3 and caution.png, after that I searched the repository and this time I only get the extracted metadata of the two media, but not for java source. for only searching java from repository works fine but once I upload caution.png and sample1.mp3 and then calls the menu s), only metadata for media are printed out -- 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

17 years, 6 months

3
9
0 / 0

[JBoss JIRA] Created: (DNA-234) create a sub maven module project for jbpm jPDL sequencer

by Serge Emmanuel Pagop (JIRA)

create a sub maven module project for jbpm jPDL sequencer --------------------------------------------------------- Key: DNA-234 URL: https://jira.jboss.org/jira/browse/DNA-234 Project: DNA Issue Type: Sub-task Components: Sequencers Affects Versions: Future Releases Reporter: Serge Emmanuel Pagop Fix For: Future Releases -- 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

17 years, 6 months

2
8
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues October 2008