Tapestry 5
  1. Tapestry 5
  2. TAP5-393

Tapestry IOC should log the names of any loaded module classes and clearly indicate module classes that could not be loaded

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.0
    • Fix Version/s: 5.1.0.0
    • Component/s: tapestry-ioc
    • Labels:
      None

      Description

      If you screw up the manifest of a module or have other classpath problems, it is impossible to know exactly what modules have been loaded. Logging that (perhaps using the org.apache.tapestry5.ioc.Registry logger) would be a big help.

        Activity

        Hide
        Howard M. Lewis Ship added a comment -

        Logs each loaded class on logger org.apache.tapestry5.ioc.RegistryBuilder at level info.

        Show
        Howard M. Lewis Ship added a comment - Logs each loaded class on logger org.apache.tapestry5.ioc.RegistryBuilder at level info.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development