September 2008 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-217) Connector SPI should have protocol for cancelling operations

by Randall Hauch (JIRA)

Connector SPI should have protocol for cancelling operations ------------------------------------------------------------ Key: DNA-217 URL: https://jira.jboss.org/jira/browse/DNA-217 Project: DNA Issue Type: Task Components: Connectors, SPI Affects Versions: 0.2 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.2 The Connector SPI needs a specific way for calls to the connector to be canceled. Currently, most of the methods throw InterruptedException, which is a painful (and confusing) way to handle it. This exception should be removed while the use of ProgressMonitor be added. Additionally, we may want to consider modifying the ProgressMonitor framework so that it's possible for it to threat Thread.interrupt() as a cancellation (whereby it would use that, in addition to the internal flag, to determine whether the monitor is canceled. This may require an additional method whereby the code checking "isCanceled()" acknowledges that it is canceling what it's doing (so that the ProgressMonitor can call Thread.interrupted() to clear the interrupted state). -- 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

15 years, 5 months

1
4
0 / 0

[JBoss JIRA] Created: (DNA-181) Consolidate security, messages, and progress within the ExecutionContext and make framework consistent in its use and passing of this context

by Johnny Verhaeg (JIRA)

Consolidate security, messages, and progress within the ExecutionContext and make framework consistent in its use and passing of this context --------------------------------------------------------------------------------------------------------------------------------------------- Key: DNA-181 URL: https://jira.jboss.org/jira/browse/DNA-181 Project: DNA Issue Type: Feature Request Components: API, SPI Affects Versions: 0.1 Reporter: Johnny Verhaeg Fix For: 0.2 We are already passing around an ExecutionContext to various parts of the DNA framework, and in some places a progress monitor that in turn contains problems encountered (as of DNA-75). We're now looking into security information that also needs to be passed around during login and execution, and it's now evident that a better way to handle all of these information types would be to consolidate all of it within the execution context and make it the common "token" that is consistently passed between all framework components, including the SPI. Messages, progress, security, etc., should always be dealt with in relation to a particular context, and contexts may be hierarchical in nature. For example, the messages, problems, and progress for a particular operation should be recorded in a manner that ties them to that operation's execution within whatever context it occurred, which will have been initiated as part of a broader context, that being either a higher-level or composite operation or, at the very least, within the context of the client's session. Recording information in this manner should make it easier to audit, debug, providing complex logging facilities, etc. "Problems" should be treated more generically as simply "Messages", allowing the framework much for flexibility to handle context-specific information, such as messages specific to an operation or executed command. The entire logging framework can then work off of these messages rather than leaving it to SPI implementors to determine when something should be logged, added as a problem/message, or both. The framework contains only a few other types of information, none of which should be dangerous to pass around, and any of which can be further protected if necessary via context wrappers that may, for instance, return immutable versions of that information. -- 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

15 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (DNA-84) Use quotes consistently in I18n localization property files

by Randall Hauch (JIRA)

Use quotes consistently in I18n localization property files ----------------------------------------------------------- Key: DNA-84 URL: http://jira.jboss.com/jira/browse/DNA-84 Project: DNA Issue Type: Task Reporter: Randall Hauch Assigned To: Randall Hauch Priority: Minor Fix For: 0.2 We appear to be using single quotes and double quotes in our localization messages. Single quotes are used by MessageFormat (which we're not using), but we should use double quotes to be more consistent. -- 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

15 years, 6 months

1
3
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

15 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

15 years, 6 months

1
4
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

15 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

15 years, 6 months

3
9
0 / 0

[JBoss JIRA] Created: (DNA-104) Sequence Powerpoint files

by Randall Hauch (JIRA)

Sequence Powerpoint files ------------------------- Key: DNA-104 URL: http://jira.jboss.com/jira/browse/DNA-104 Project: DNA Issue Type: Feature Request Components: Sequencers Reporter: Randall Hauch Fix For: Future Releases Create a sequencer that extracts the content from Excel spreadsheets. Consider using Apache POI (http://poi.apache.org/index.html) to access the Excel files. -- 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

15 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (DNA-215) Graph API for working with repository content

by Randall Hauch (JIRA)

Graph API for working with repository content --------------------------------------------- Key: DNA-215 URL: https://jira.jboss.org/jira/browse/DNA-215 Project: DNA Issue Type: Feature Request Components: API, Connectors Affects Versions: 0.2 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.3 Attachments: dna-spi.patch We need to make it easier to work with the content provided by the connectors. The command framework is okay, but it is entirely oriented towards the connector, not the user of the connector. Instead, we need an API that hides the command system (as much as possible) and that provides an easy way to work with the content. -- 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

15 years, 6 months

1
6
0 / 0

[JBoss JIRA] Created: (DNA-213) Review the graph SPI commands to better handle node identification (e.g., when getting children)

by Randall Hauch (JIRA)

Review the graph SPI commands to better handle node identification (e.g., when getting children) ------------------------------------------------------------------------------------------------ Key: DNA-213 URL: https://jira.jboss.org/jira/browse/DNA-213 Project: DNA Issue Type: Task Components: SPI Affects Versions: 0.2 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.2 The graph commands in the SPI were an initial attempt to identify the set of functionality that the connectors should support. One problem with the current design is that it's not really feasible or possible to track with each child the identification properties for the child. For example, when getting the children of a node, it's not mandatory (nor that clear) that identification properties be recorded for each child as well. It's very important to provide a way for all nodes (including children) to be fully identified. -- 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

15 years, 6 months

1
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues September 2008