[JBoss JIRA] (SRAMP-227) Allow derivers to define and use custom node types
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-227?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-227:
--------------------------------
Fix Version/s: 0.6.0 - Future
> Allow derivers to define and use custom node types
> --------------------------------------------------
>
> Key: SRAMP-227
> URL: https://issues.jboss.org/browse/SRAMP-227
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Randall Hauch
> Assignee: Kurt Stam
> Fix For: 0.6.0 - Future
>
>
> Presently, any content produced by a deriver is stored in the JCR repository with S-RAMP-defined node types, and it is not possible for a deriver to use custom or domain-specific node types or mixins.
> This enhancement would allow derivers to define such domain-specific node types and/or mixins, and to produce content that uses these node types. This would allow directly querying the underlying JCR repository using JCR-SQL (which is based very much on using specific node types and mixins).
> Granted, it may be very difficult to abstract the JCR-ness of the custom node types, especially during content creation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (SRAMP-267) Migrate gwt/bootstrap widgets to overlord-commons
by Kurt Stam (JIRA)
[ https://issues.jboss.org/browse/SRAMP-267?page=com.atlassian.jira.plugin.... ]
Kurt Stam updated SRAMP-267:
----------------------------
Fix Version/s: 0.4.0 - Tomcat Support
> Migrate gwt/bootstrap widgets to overlord-commons
> -------------------------------------------------
>
> Key: SRAMP-267
> URL: https://issues.jboss.org/browse/SRAMP-267
> Project: S-RAMP
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Gary Brown
> Assignee: Kurt Stam
> Fix For: 0.4.0 - Tomcat Support
>
>
> Some of the common bootstrap/gwt related widgets have been moved to overlord-commons, to be shared across overlord projects. This issue is to:
> 1) Move any remaining widgets that are still only in sramp repo
> 2) Migrate sramp (and possibly dtgov) across to use the overload-commons version of the widgets, and remove the sramp copy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (SRAMP-170) Atom feeds do not work very well in exisiting clients
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-170?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-170:
--------------------------------
Fix Version/s: 0.5.0 - API Management
(was: 0.4.0 - Tomcat Support)
> Atom feeds do not work very well in exisiting clients
> -----------------------------------------------------
>
> Key: SRAMP-170
> URL: https://issues.jboss.org/browse/SRAMP-170
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Atom Binding
> Affects Versions: 0.1.1 - Workflow Demo
> Reporter: Kurt Stam
> Assignee: Kurt Stam
> Priority: Minor
> Fix For: 0.5.0 - API Management
>
> Attachments: Screen Shot 2013-03-10 at 12.08.22 PM.png
>
>
> When using exiting atom clients our feed don't work very well. I think one should be able to follow links down into an entry for example, but the link is not populated. We should investigate why this is.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months