[
https://issues.apache.org/jira/browse/ARIES-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835190#action_12835190
]
Guillaume Nodet commented on ARIES-182:
---------------------------------------
So I propose to:
* move the resolution process from createApplication() to resolve()
* have install() call resolve() if needed
* add a isResolved() method on the AriesApplication and javadoc to explain
that the new application should be obtained from the ApplicationContext in case
the application was not resolved before installation
> The resolution process should be able to be done separatly from the
> AriesApplication creation
> ---------------------------------------------------------------------------------------------
>
> Key: ARIES-182
> URL: https://issues.apache.org/jira/browse/ARIES-182
> Project: Aries
> Issue Type: Improvement
> Reporter: Guillaume Nodet
>
> Several use cases:
> * the user wants to impose constraints without having to resolve the
> application twice
> * the resolution fails but we'd like to understand why and have some
> informations about the application
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
