[ https://issues.jboss.org/browse/SRAMP-137?page=com.atlassian.jira.plugin.... ]
Eric Wittmann resolved SRAMP-137.
---------------------------------
Resolution: Done
> Add getArtifactMetaData(ArtifactSummary) to the client api
> ----------------------------------------------------------
>
> Key: SRAMP-137
> URL: https://issues.jboss.org/browse/SRAMP-137
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Priority: Minor
> Fix For: 0.3.0 - JBPM6 Integration
>
>
> Makes it easier for users to access the full meta-data for a given result set item.
> Consider alternatives such as:
> summary.fetchArtifact() -> BaseArtifactType
--
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
[ https://issues.jboss.org/browse/SRAMP-137?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-137:
--------------------------------
Git Pull Request: https://github.com/Governance/s-ramp/pull/265
> Add getArtifactMetaData(ArtifactSummary) to the client api
> ----------------------------------------------------------
>
> Key: SRAMP-137
> URL: https://issues.jboss.org/browse/SRAMP-137
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Priority: Minor
> Fix For: 0.3.0 - JBPM6 Integration
>
>
> Makes it easier for users to access the full meta-data for a given result set item.
> Consider alternatives such as:
> summary.fetchArtifact() -> BaseArtifactType
--
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
[ https://issues.jboss.org/browse/SRAMP-137?page=com.atlassian.jira.plugin.... ]
Work on SRAMP-137 started by Eric Wittmann.
> Add getArtifactMetaData(ArtifactSummary) to the client api
> ----------------------------------------------------------
>
> Key: SRAMP-137
> URL: https://issues.jboss.org/browse/SRAMP-137
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Priority: Minor
> Fix For: 0.3.0 - JBPM6 Integration
>
>
> Makes it easier for users to access the full meta-data for a given result set item.
> Consider alternatives such as:
> summary.fetchArtifact() -> BaseArtifactType
--
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
[ https://issues.jboss.org/browse/SRAMP-165?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-165:
--------------------------------
Git Pull Request: https://github.com/Governance/s-ramp/pull/264
> Implement negation (not() function) for S-RAMP queries
> ------------------------------------------------------
>
> Key: SRAMP-165
> URL: https://issues.jboss.org/browse/SRAMP-165
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Core
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Priority: Critical
> Fix For: 0.3.0 - JBPM6 Integration
>
>
> We added support for negation in s-ramp queries to the spec recently. Need to implement that function.
--
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
[ https://issues.jboss.org/browse/SRAMP-165?page=com.atlassian.jira.plugin.... ]
Eric Wittmann resolved SRAMP-165.
---------------------------------
Resolution: Done
> Implement negation (not() function) for S-RAMP queries
> ------------------------------------------------------
>
> Key: SRAMP-165
> URL: https://issues.jboss.org/browse/SRAMP-165
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Core
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Priority: Critical
> Fix For: 0.3.0 - JBPM6 Integration
>
>
> We added support for negation in s-ramp queries to the spec recently. Need to implement that function.
--
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
[ https://issues.jboss.org/browse/SRAMP-165?page=com.atlassian.jira.plugin.... ]
Eric Wittmann closed SRAMP-165.
-------------------------------
> Implement negation (not() function) for S-RAMP queries
> ------------------------------------------------------
>
> Key: SRAMP-165
> URL: https://issues.jboss.org/browse/SRAMP-165
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Core
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Priority: Critical
> Fix For: 0.3.0 - JBPM6 Integration
>
>
> We added support for negation in s-ramp queries to the spec recently. Need to implement that function.
--
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
[ https://issues.jboss.org/browse/SRAMP-165?page=com.atlassian.jira.plugin.... ]
Work on SRAMP-165 started by Eric Wittmann.
> Implement negation (not() function) for S-RAMP queries
> ------------------------------------------------------
>
> Key: SRAMP-165
> URL: https://issues.jboss.org/browse/SRAMP-165
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Core
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Priority: Critical
> Fix For: 0.3.0 - JBPM6 Integration
>
>
> We added support for negation in s-ramp queries to the spec recently. Need to implement that function.
--
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
[ https://issues.jboss.org/browse/SRAMPUI-69?page=com.atlassian.jira.plugin... ]
Eric Wittmann closed SRAMPUI-69.
--------------------------------
> Add breadcrumb control to all Pages
> -----------------------------------
>
> Key: SRAMPUI-69
> URL: https://issues.jboss.org/browse/SRAMPUI-69
> Project: S-RAMP UI
> Issue Type: Feature Request
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
>
> Once we have a Dashboard and the common Overlord top nav bar, we also need to have a breadcrumb widget on all the browser pages.
> e.g.
> S-RAMP / Artifacts / OrderService.wsdl
> That might be the breadcrumb for the ArtifactDetails page for a WSDL artifact named OrderService.wsdl.
--
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
[ https://issues.jboss.org/browse/SRAMPUI-69?page=com.atlassian.jira.plugin... ]
Eric Wittmann resolved SRAMPUI-69.
----------------------------------
Resolution: Done
This has been implemented in the latest UI impl.
> Add breadcrumb control to all Pages
> -----------------------------------
>
> Key: SRAMPUI-69
> URL: https://issues.jboss.org/browse/SRAMPUI-69
> Project: S-RAMP UI
> Issue Type: Feature Request
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
>
> Once we have a Dashboard and the common Overlord top nav bar, we also need to have a breadcrumb widget on all the browser pages.
> e.g.
> S-RAMP / Artifacts / OrderService.wsdl
> That might be the breadcrumb for the ArtifactDetails page for a WSDL artifact named OrderService.wsdl.
--
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
[ https://issues.jboss.org/browse/SRAMPUI-34?page=com.atlassian.jira.plugin... ]
Eric Wittmann updated SRAMPUI-34:
---------------------------------
Priority: Minor (was: Major)
> Leverage GWT code-splitting
> ---------------------------
>
> Key: SRAMPUI-34
> URL: https://issues.jboss.org/browse/SRAMPUI-34
> Project: S-RAMP UI
> Issue Type: Task
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Priority: Minor
> Fix For: Future (Unscheduled)
>
>
> Determine the best way to apply code-splitting to the project so that the UI can scale out reasonably well.
--
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