[
https://issues.apache.org/jira/browse/PLUTO-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neil Griffin updated PLUTO-751:
-------------------------------
Summary: V3AnnotationPortletArtifactValidityTests inject dependent-scoped
strings into @ApplicationScoped beans (was:
V3AnnotationPortletArtifactValidityTests inject dependent-scoped String into
@ApplicationScoped beans)
> V3AnnotationPortletArtifactValidityTests inject dependent-scoped strings into
> @ApplicationScoped beans
> ------------------------------------------------------------------------------------------------------
>
> Key: PLUTO-751
> URL: https://issues.apache.org/jira/browse/PLUTO-751
> Project: Pluto
> Issue Type: Bug
> Components: tck
> Affects Versions: 3.0.0, 3.0.1
> Reporter: Neil Griffin
> Assignee: Neil Griffin
> Priority: Major
> Fix For: 3.0.2
>
>
> Three classes in V3AnnotationPortletArtifactValidityTests inject a
> dependent-scoped {{String}} (the value for which is the portlet name, which
> is associated with the portlet request):
> {code:java}
> @Inject
> @PortletName
> private String portletName;
> {code}
> The fix would be to follow the pattern already found elsewhere in the tests
> by injecting the {{@PortletRequestScoped PortletRequestScopedArtifacts}}
> instance and calling the {{getPortletName()}} method:
> {code:java}
> @Inject
> private PortletRequestScopedArtifacts portletRequestScopedArtifacts;
> ...
> String portletName = portletRequestScopedArtifacts.getPortletName();
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
