You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Andrew Osborne (JIRA)" <ji...@apache.org> on 2009/12/03 15:59:20 UTC
[jira] Created: (ARIES-68) Custom Component Metadata support
Custom Component Metadata support
---------------------------------
Key: ARIES-68
URL: https://issues.apache.org/jira/browse/ARIES-68
Project: Aries
Issue Type: New Feature
Components: Blueprint
Reporter: Andrew Osborne
This started from a thought related to ARIES-63 of how to improve Passthroughmetadata to allow the object to access blueprint objects via an interface passed to 'getObject'. As more consideration is given to requirements that would be added to Passthroughmetadata, it's restrictions start to feel like a more capable alternative may be required.
Although pass through metadata is interesting, it is also fairly limited, essentially acting like a custom 'singleton' component recipe.
Custom components can get a little more complex, and may wish to act as prototype, or be informed when destruction occurs, or even participate in availability/satisfaction type behaviour (like Reference instances do today).
This feature aims to implement support for custom components through a new custom component metadata & recipe, offering all of the above.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (ARIES-68) Custom Component Metadata support
Posted by "Valentin Mahrwald (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Valentin Mahrwald closed ARIES-68.
----------------------------------
> Custom Component Metadata support
> ---------------------------------
>
> Key: ARIES-68
> URL: https://issues.apache.org/jira/browse/ARIES-68
> Project: Aries
> Issue Type: New Feature
> Components: Blueprint
> Reporter: Andrew Osborne
> Assignee: Valentin Mahrwald
>
> This started from a thought related to ARIES-63 of how to improve Passthroughmetadata to allow the object to access blueprint objects via an interface passed to 'getObject'. As more consideration is given to requirements that would be added to Passthroughmetadata, it's restrictions start to feel like a more capable alternative may be required.
> Although pass through metadata is interesting, it is also fairly limited, essentially acting like a custom 'singleton' component recipe.
> Custom components can get a little more complex, and may wish to act as prototype, or be informed when destruction occurs, or even participate in availability/satisfaction type behaviour (like Reference instances do today).
> This feature aims to implement support for custom components through a new custom component metadata & recipe, offering all of the above.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ARIES-68) Custom Component Metadata support
Posted by "Andrew Osborne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Osborne reassigned ARIES-68:
-----------------------------------
Assignee: Valentin Mahrwald
> Custom Component Metadata support
> ---------------------------------
>
> Key: ARIES-68
> URL: https://issues.apache.org/jira/browse/ARIES-68
> Project: Aries
> Issue Type: New Feature
> Components: Blueprint
> Reporter: Andrew Osborne
> Assignee: Valentin Mahrwald
>
> This started from a thought related to ARIES-63 of how to improve Passthroughmetadata to allow the object to access blueprint objects via an interface passed to 'getObject'. As more consideration is given to requirements that would be added to Passthroughmetadata, it's restrictions start to feel like a more capable alternative may be required.
> Although pass through metadata is interesting, it is also fairly limited, essentially acting like a custom 'singleton' component recipe.
> Custom components can get a little more complex, and may wish to act as prototype, or be informed when destruction occurs, or even participate in availability/satisfaction type behaviour (like Reference instances do today).
> This feature aims to implement support for custom components through a new custom component metadata & recipe, offering all of the above.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ARIES-68) Custom Component Metadata support
Posted by "Valentin Mahrwald (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Valentin Mahrwald resolved ARIES-68.
------------------------------------
Resolution: Fixed
> Custom Component Metadata support
> ---------------------------------
>
> Key: ARIES-68
> URL: https://issues.apache.org/jira/browse/ARIES-68
> Project: Aries
> Issue Type: New Feature
> Components: Blueprint
> Reporter: Andrew Osborne
> Assignee: Valentin Mahrwald
>
> This started from a thought related to ARIES-63 of how to improve Passthroughmetadata to allow the object to access blueprint objects via an interface passed to 'getObject'. As more consideration is given to requirements that would be added to Passthroughmetadata, it's restrictions start to feel like a more capable alternative may be required.
> Although pass through metadata is interesting, it is also fairly limited, essentially acting like a custom 'singleton' component recipe.
> Custom components can get a little more complex, and may wish to act as prototype, or be informed when destruction occurs, or even participate in availability/satisfaction type behaviour (like Reference instances do today).
> This feature aims to implement support for custom components through a new custom component metadata & recipe, offering all of the above.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ARIES-68) Custom Component Metadata support
Posted by "Jeremy Hughes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Hughes updated ARIES-68:
-------------------------------
Fix Version/s: 0.1
> Custom Component Metadata support
> ---------------------------------
>
> Key: ARIES-68
> URL: https://issues.apache.org/jira/browse/ARIES-68
> Project: Aries
> Issue Type: New Feature
> Components: Blueprint
> Reporter: Andrew Osborne
> Assignee: Valentin Mahrwald
> Fix For: 0.1
>
>
> This started from a thought related to ARIES-63 of how to improve Passthroughmetadata to allow the object to access blueprint objects via an interface passed to 'getObject'. As more consideration is given to requirements that would be added to Passthroughmetadata, it's restrictions start to feel like a more capable alternative may be required.
> Although pass through metadata is interesting, it is also fairly limited, essentially acting like a custom 'singleton' component recipe.
> Custom components can get a little more complex, and may wish to act as prototype, or be informed when destruction occurs, or even participate in availability/satisfaction type behaviour (like Reference instances do today).
> This feature aims to implement support for custom components through a new custom component metadata & recipe, offering all of the above.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.