Details

    • Type: Feature Request
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 1.1.9.Final
    • Fix Version/s: 2.0.3.Final
    • Component/s: None
    • Labels:
      None

      Description

      I'm currently working at migrating a fairly big project (100+ services split in 16 different projects). Until now an home grown solution was used to manually "inject" the requested service like "ServiceHelper.getService(MyService.class)".

      The problem with this approach is that no circular dependency is ever checked (which is bad).

      Anyways, when circular dependencies are found and DeploymentException is thrown by Weld, it would be very nice to prettify the exception and print the dependency tree to pin point more easily the circular dependency problem (which in big project can be fairly difficult to point out).

      There's probably some string utilities in the Hibernate project that could help to perform this task ? I'm thinking about the entity debugging that is showing the entity mapping as a tree.

      Hope this is possible,

      Big thanks !

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                luksa Marko Luksa
                Reporter:
                matlach Mathieu Lachance
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: