Tapestry 5
  1. Tapestry 5
  2. TAP5-602

Contributing to TypeCoercer with service fails even with @InjectService

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.2
    • Fix Version/s: 5.1.0.3
    • Component/s: tapestry-ioc
    • Labels:
      None

      Description

      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.

      1. tapestry_log.txt
        354 kB
        Alfie Kirkpatrick

        Activity

        Howard M. Lewis Ship made changes -
        Status In Progress [ 3 ] Closed [ 6 ]
        Fix Version/s 5.1.0.3 [ 12313782 ]
        Resolution Fixed [ 1 ]
        Howard M. Lewis Ship made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Howard M. Lewis Ship made changes -
        Assignee Howard M. Lewis Ship [ hlship ]
        Alfie Kirkpatrick made changes -
        Field Original Value New Value
        Attachment tapestry_log.txt [ 12403790 ]
        Alfie Kirkpatrick created issue -

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Alfie Kirkpatrick
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development