You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/04/03 00:55:12 UTC
[jira] Closed: (TAP5-602) Contributing to TypeCoercer with service
fails even with @InjectService
[ https://issues.apache.org/jira/browse/TAP5-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-602.
-------------------------------------
Resolution: Fixed
Fix Version/s: 5.1.0.3
I don't really have a test case for this, but from the log, it was clear the problem was a missing @Bulitin in PerThreadServiceLifecycle, which forces the creation of the Alias service right in the middle of instantiating the Alias service.
> Contributing to TypeCoercer with service fails even with @InjectService
> -----------------------------------------------------------------------
>
> Key: TAP5-602
> URL: https://issues.apache.org/jira/browse/TAP5-602
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.1.0.2
> Reporter: Alfie Kirkpatrick
> Assignee: Howard M. Lewis Ship
> Fix For: 5.1.0.3
>
> Attachments: tapestry_log.txt
>
>
> This is somewhat related to TAPESTRY-1558. That JIRA mentions a workaround to avoid self-reference on startup using @InjectService by name rather than standard @Inject. However, between 5.1.0.1 and the 5.1.0.2 snapshot this workaround has stopped working.
> I am having trouble producing a simple test case for this but will attempt to do so and post it here.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.