[JBoss JIRA] (SRAMP-161) S-RAMP Client: obey endpoints found in /servicedocument
by Kurt Stam (JIRA)
[ https://issues.jboss.org/browse/SRAMP-161?page=com.atlassian.jira.plugin.... ]
Kurt Stam updated SRAMP-161:
----------------------------
Fix Version/s: 0.3.1 - jBPM - bugfix 1
(was: 0.3.0 - JBPM6 Integration)
> S-RAMP Client: obey endpoints found in /servicedocument
> -------------------------------------------------------
>
> Key: SRAMP-161
> URL: https://issues.jboss.org/browse/SRAMP-161
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: S-RAMP API
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Priority: Minor
> Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> Currently we use the non-normative URL formats suggested in the S-RAMP Atom Binding document as presumptive endpoints for the various artifact types. Instead, the Atom API Java client should obey the endpoints it finds in the /servicedocument. This means it will *always* query that service document.
--
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
11 years, 7 months
[JBoss JIRA] (SRAMP-161) S-RAMP Client: obey endpoints found in /servicedocument
by Kurt Stam (JIRA)
[ https://issues.jboss.org/browse/SRAMP-161?page=com.atlassian.jira.plugin.... ]
Kurt Stam updated SRAMP-161:
----------------------------
Issue Type: Bug (was: Feature Request)
> S-RAMP Client: obey endpoints found in /servicedocument
> -------------------------------------------------------
>
> Key: SRAMP-161
> URL: https://issues.jboss.org/browse/SRAMP-161
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: S-RAMP API
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Priority: Minor
> Fix For: 0.3.0 - JBPM6 Integration
>
>
> Currently we use the non-normative URL formats suggested in the S-RAMP Atom Binding document as presumptive endpoints for the various artifact types. Instead, the Atom API Java client should obey the endpoints it finds in the /servicedocument. This means it will *always* query that service document.
--
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
11 years, 7 months
[JBoss JIRA] (SRAMP-188) Auditing: handle phase2 commits for artifact creates
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-188?page=com.atlassian.jira.plugin.... ]
Eric Wittmann resolved SRAMP-188.
---------------------------------
Resolution: Won't Fix
I have decided to re-implement auditing without using the jcr observer pattern. This decision deprecates this task.
> Auditing: handle phase2 commits for artifact creates
> ----------------------------------------------------
>
> Key: SRAMP-188
> URL: https://issues.jboss.org/browse/SRAMP-188
> Project: S-RAMP
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Core
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.3.0 - JBPM6 Integration
>
>
> When artifacts are added to the s-ramp repository the JCR nodes are written in two phases. In the case of non-derived artifacts, the second phase will updated the JCR node with any meta-data added to it by the Deriver.
> In the case of derived artifacts, the second phase will update the JCR node with most of the primary artifact meta-data.
> In both cases, the audit handler should update the appropriate audit entry JCR node with information recorded during the second phase commit. It should not create a new audit entry.
--
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
11 years, 7 months
[JBoss JIRA] (SRAMP-187) Auditing: properly audit classifiers
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-187?page=com.atlassian.jira.plugin.... ]
Eric Wittmann resolved SRAMP-187.
---------------------------------
Resolution: Done
I have decided to re-implement auditing without using the jcr observer pattern. This decision deprecates this task.
> Auditing: properly audit classifiers
> ------------------------------------
>
> Key: SRAMP-187
> URL: https://issues.jboss.org/browse/SRAMP-187
> Project: S-RAMP
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Core
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Priority: Critical
> Fix For: 0.3.0 - JBPM6 Integration
>
>
> The auditing implementation currently doesn't properly handle classifiers (because it's a multi-value property in JCR). The impl should be enhanced to handle classifiers in an appropriate way.
--
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
11 years, 7 months
[JBoss JIRA] (SRAMP-188) Auditing: handle phase2 commits for artifact creates
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-188?page=com.atlassian.jira.plugin.... ]
Eric Wittmann closed SRAMP-188.
-------------------------------
> Auditing: handle phase2 commits for artifact creates
> ----------------------------------------------------
>
> Key: SRAMP-188
> URL: https://issues.jboss.org/browse/SRAMP-188
> Project: S-RAMP
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Core
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.3.0 - JBPM6 Integration
>
>
> When artifacts are added to the s-ramp repository the JCR nodes are written in two phases. In the case of non-derived artifacts, the second phase will updated the JCR node with any meta-data added to it by the Deriver.
> In the case of derived artifacts, the second phase will update the JCR node with most of the primary artifact meta-data.
> In both cases, the audit handler should update the appropriate audit entry JCR node with information recorded during the second phase commit. It should not create a new audit entry.
--
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
11 years, 7 months