[ https://issues.jboss.org/browse/RTGOV-256?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-256.
------------------------------
Resolution: Done
> Headers not reported for switchyard events
> ------------------------------------------
>
> Key: RTGOV-256
> URL: https://issues.jboss.org/browse/RTGOV-256
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.1.0.Final
>
>
--
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
Gary Brown created RTGOV-256:
--------------------------------
Summary: Headers not reported for switchyard events
Key: RTGOV-256
URL: https://issues.jboss.org/browse/RTGOV-256
Project: RTGov (Run Time Governance)
Issue Type: Bug
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.1.0.Final
--
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/RTGOV-255?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on RTGOV-255:
-----------------------------------------------
Gary Brown <gbrown(a)redhat.com> changed the Status of [bug 998829|https://bugzilla.redhat.com/show_bug.cgi?id=998829] from NEW to MODIFIED
> Remove default type from the context, so json serialized form has it listed explicitly
> --------------------------------------------------------------------------------------
>
> Key: RTGOV-255
> URL: https://issues.jboss.org/browse/RTGOV-255
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.1.0.Final
>
>
--
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/RTGOV-255?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on RTGOV-255:
-----------------------------------------------
Gary Brown <gbrown(a)redhat.com> made a comment on [bug 998829|https://bugzilla.redhat.com/show_bug.cgi?id=998829]
Wasn't a bug as such - the Conversation type was the default value, and json serialization has been configured not to include values that are the same as the default, to ensure it is the most concise representation.
However for clarity, it is probably better that the context type is explicit, so have removed the default type from the Context object.
> Remove default type from the context, so json serialized form has it listed explicitly
> --------------------------------------------------------------------------------------
>
> Key: RTGOV-255
> URL: https://issues.jboss.org/browse/RTGOV-255
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.1.0.Final
>
>
--
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/RTGOV-255?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated RTGOV-255:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=998829
> Remove default type from the context, so json serialized form has it listed explicitly
> --------------------------------------------------------------------------------------
>
> Key: RTGOV-255
> URL: https://issues.jboss.org/browse/RTGOV-255
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.1.0.Final
>
>
--
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/RTGOV-255?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-255.
------------------------------
Resolution: Done
> Remove default type from the context, so json serialized form has it listed explicitly
> --------------------------------------------------------------------------------------
>
> Key: RTGOV-255
> URL: https://issues.jboss.org/browse/RTGOV-255
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.1.0.Final
>
>
--
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
Gary Brown created RTGOV-255:
--------------------------------
Summary: Remove default type from the context, so json serialized form has it listed explicitly
Key: RTGOV-255
URL: https://issues.jboss.org/browse/RTGOV-255
Project: RTGov (Run Time Governance)
Issue Type: Task
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.1.0.Final
--
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-226?page=com.atlassian.jira.plugin.... ]
Eric Wittmann resolved SRAMP-226.
---------------------------------
Resolution: Done
> Wagon doesn't refresh artifact meta-data prior to pushing changes to server
> ---------------------------------------------------------------------------
>
> Key: SRAMP-226
> URL: https://issues.jboss.org/browse/SRAMP-226
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 0.3.0 - JBPM6 Integration
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> The s-ramp wagon uploads artifacts and then modifies them with additional meta-data (e.g. sha1 hash). When it does the latter it does not re-fetch the meta-data from the server. So any changes made there (e.g. by dtgov) get overwritten. The wagon should re-fetch prior to making any meta-data changes and pushing them.
--
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-226?page=com.atlassian.jira.plugin.... ]
Eric Wittmann closed SRAMP-226.
-------------------------------
> Wagon doesn't refresh artifact meta-data prior to pushing changes to server
> ---------------------------------------------------------------------------
>
> Key: SRAMP-226
> URL: https://issues.jboss.org/browse/SRAMP-226
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 0.3.0 - JBPM6 Integration
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> The s-ramp wagon uploads artifacts and then modifies them with additional meta-data (e.g. sha1 hash). When it does the latter it does not re-fetch the meta-data from the server. So any changes made there (e.g. by dtgov) get overwritten. The wagon should re-fetch prior to making any meta-data changes and pushing them.
--
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