[JBoss JIRA] Created: (DNA-302) Make JcrNodeTypeManager not dependent on JcrSession
by Randall Hauch (JIRA)
Make JcrNodeTypeManager not dependent on JcrSession
---------------------------------------------------
Key: DNA-302
URL: https://jira.jboss.org/jira/browse/DNA-302
Project: DNA
Issue Type: Sub-task
Components: API, JCR
Affects Versions: 0.3
Reporter: Randall Hauch
Fix For: 0.4
The JcrNodeTypeManager should not be dependent upon a JcrSession instance. Most of the methods (including those in JcrNodeType, JcrNodeDefinition, and JcrPropertyDefinition) only need an ExecutionContext. JcrNodeDefinition.getDefaultPrimaryType() seems to depend upon the NodeTypeManager to dynamically look up a type (there may be others). This main mean that the JcrNodeTypeManager needs a method to allow adding types from a JcrNodeTypeSource (rather than a JcrNodeTypeSource be passed into the constructor).
--
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, 1 month
[JBoss JIRA] Commented: (DNA-26) Extract EXIF metadata from JPEG files
by Randall Hauch (JIRA)
[ https://jira.jboss.org/jira/browse/DNA-26?page=com.atlassian.jira.plugin.... ]
Randall Hauch commented on DNA-26:
----------------------------------
Note that the current image sequencer (in the "dna-sequencer-images" project) currently extracts the basic image metadata, and does not extract the EXIF metadata.
> Extract EXIF metadata from JPEG files
> -------------------------------------
>
> Key: DNA-26
> URL: https://jira.jboss.org/jira/browse/DNA-26
> Project: DNA
> Issue Type: Feature Request
> Components: Sequencers
> Reporter: Randall Hauch
> Priority: Optional
> Fix For: Future Releases
>
>
> The image sequencer extracts basic metadata from PNG, BMP, JPEG, GIF and other image files. Enhance this sequencer to extract EXIF metadata for JPEG files.
> Drew Noake's metadata extractor (http://www.drewnoakes.com/code/exif/index.html) seems to be a widely used library for extracting EXIF metadata, and has support for a number of cameras. This library does not appear to be in a any of the Maven 2 repositories, and Drew does not specify the Maven coordinates. The package structure is "com.drew.*", but Aduna has it in its Maven 2 repository (http://repository.aduna-software.org/maven2/com/drewnoakes/metadata-extra...) under "com.drewnoakes" (which is Drew's domain).
> The EXIF metadata is organized as tags under directories. See a sample output of EXIF metadata at http://www.drewnoakes.com/code/exif/sampleOutput.html. This could be mapped to JCR by having a child node (of type "exif:directory") named for each directory (e.g., "EXIF"). Should the tags be stored as properties on each directory node (not a great mapping from the tag names to property names, and not really very extensible but probably easier to use), or as child nodes (of type "exit:tag" ?) with properties for the tag name, hex value, and description (value)?
--
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, 1 month
[JBoss JIRA] Created: (DNA-262) JCR-Level 2: Support persistent namespace changes
by Randall Hauch (JIRA)
JCR-Level 2: Support persistent namespace changes
-------------------------------------------------
Key: DNA-262
URL: https://jira.jboss.org/jira/browse/DNA-262
Project: DNA
Issue Type: Feature Request
Affects Versions: 0.3
Reporter: Randall Hauch
Assignee: Randall Hauch
Fix For: 0.4
JCR Level 2 requires support for persisting changes to namespaces in the repository. We can already support that with all of our connectors, since they're all able to store the namespace URIs for the content. In fact, none of them currently store or use the prefixes.
However, one thing DNA still doesn't have is the ability to manage the namespace prefixes in the connectors. This probably will entail having a NamespaceRegistry implementation that can use a connector to populate the namespace registry. This is a little tricky, tho, since the NamespaceRegistry is part of the ExecutionContext, which is passed to the connector's "execute(ExecutionContext,Request)" method. So, while it is ideal that these namespace management methods are just additional requests, the dependency graph may imply that the namespace management methods need to be added to the RepositoryConnector interface.
--
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, 1 month