[
https://issues.apache.org/jira/browse/TAP5-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791287#action_12791287
]
Peter Rietzler commented on TAP5-955:
-------------------------------------
I absolutely agree with you. The standard behavior should not change - I
thought of something like this:
@Contribute(to = "service-name", optional = true)
public static void arbitraryContributeMethodName(....)
or
@Optional
public static void contributeServiceName(...)
> Optional service contributions
> ------------------------------
>
> Key: TAP5-955
> URL: https://issues.apache.org/jira/browse/TAP5-955
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-ioc
> Reporter: Peter Rietzler
>
> Currently the registry wil not start if a module makes contributions to a
> service which does not exist (e.g. because the module with the service is not
> loaded). This makes problems with applications, that allow installations with
> a subset of all modules started. A module should be able to contribute to an
> extension point only if it is available. In case the service does not exist,
> the contribution should be ignored.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
