![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
06/Jun/14 11:11 PM
|
|
Description:
|
Various places in Jenkins we have to look up StaplerRequest.getAncestor to find the parent Project/Build/etc that an object in question is built for.
Similar pattern exists during XStream deserialization, as one often wants to know the context in which an object is deserialized.
There's a room for generalizing this to create a protocol-agnostic contextual ancestor retrieval mechanism.
(Jesse wanted a separate but related ability to register callbacks to XStream that gets fired at the end of the deserialization when all objects in the graph are fully ready, which allows a far more sophisticated readResolve()) to be written.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Kohsuke Kawaguchi
|
|
|
|
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
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
