Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-1002

Have injection check for existing component

    Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Out of Date
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None

      Description

      Right now, if a component is injected from an unbound context variable, it is treated as if it were null. Consequently if a field/setter is misspelled or not renamed when a component is renamed, this results in errors at the time the component is injected or accessed. When components are first set up, there should be a warning logged if there are any injections detected for context variables that were never defined or outjected anywhere.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                pmuir Pete Muir
                Reporter:
                chuckadams Chuck Adams
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: