Which is why the current direction was chosen (and I'm not sure that AutomationRequest has to be short-lived and transient).
Regards, David ____________________________________________________ David Brauneis STSM, Rational Software Delivery Automation Chief Architect email: [email protected] | phone: 720-395-5659 | mobile: 919-656-0874 From: Daniel Berg/Raleigh/IBM@IBMUS To: [email protected], Cc: [email protected], [email protected] Date: 06/29/2012 03:05 PM Subject: Re: [Oslc-Automation] Oslc-Automation Digest, Vol 16, Issue 12 Sent by: [email protected] It is fine if the AutomationRequest has a relationship to the AutomationResult versus the other way around if we want to avoid dangling references. However, we need to have the request parameter values captured and stored with the AutomationResult for audit purposes. Regards, Daniel Berg STSM, Master Inventor IBM Rational, DevOps Lead 1-919-486-0047 | Cell: 1-919-637-8570 oslc-automation-request---06/29/2012 09:02:10 AM---Send Oslc-Automation mailing list submissions to [email protected] From: [email protected] To: [email protected], Date: 06/29/2012 09:02 AM Subject: Oslc-Automation Digest, Vol 16, Issue 12 Sent by: [email protected] Send Oslc-Automation mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://open-services.net/mailman/listinfo/oslc-automation_open-services.net or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Oslc-Automation digest..." Today's Topics: 1. Automation Request and Automation Result relationship (Pramod K Chandoria) ---------------------------------------------------------------------- Message: 1 Date: Fri, 29 Jun 2012 20:53:28 +0530 From: Pramod K Chandoria <[email protected]> To: [email protected] Subject: [Oslc-Automation] Automation Request and Automation Result relationship Message-ID: <ofa9a8d774.2569045d-on65257a2c.0053a6c0-65257a2c.00549...@in.ibm.com> Content-Type: text/plain; charset="us-ascii" Hi All, I am thinking that most often the lifecyle of Automation Request is limited and once automation is complete, can be purged from the system any time. Whereas the lifecycle of AutomationResult is often longer (if not forever). Currently the proposed relationship between AutomationRequest and AutomationResult is from AutomationResult to AutomationRequest. This relationship will become dangling reference very soon once request is deleted. I am thinking rather have reference from Automation Request to Automation Result. As long request is in the system, we can track result from it. Result anyhow have reference to the AutomationPlan and we can always track what was executed to generate it. Any thoughts? -|- Pramod Chandoria Advisory Software Engineer Rational Quality Manager -------------- next part -------------- An HTML attachment was scrubbed... URL: < http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20120629/3962b257/attachment-0001.html > ------------------------------ _______________________________________________ Oslc-Automation mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-automation_open-services.net End of Oslc-Automation Digest, Vol 16, Issue 12 *********************************************** _______________________________________________ Oslc-Automation mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-automation_open-services.net
