Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Analyze Spring Context Files #14

Closed
10 tasks
schauder opened this issue Jan 21, 2013 · 1 comment
Closed
10 tasks

Analyze Spring Context Files #14

schauder opened this issue Jan 21, 2013 · 1 comment
Labels

Comments

@schauder
Copy link
Collaborator

Dependencies in a Spring Context files should be included in the dependency analysis.

Tasks

  • Spring beans should appear as Nodes in diagrams, similar to classes
  • Spring beans should be contained inside nodes representing the context files similar how packages contain classes
  • Spring beans should have a dependency to the class they are implemented by
  • Spring beans should have a dependency to other beans referenced as setter injection parameter
  • Spring beans should have a dependency to other beans referenced as constructor injection parameter
  • Spring beans with the same name or id from different files should be rendered as separate nodes
  • If a Spring bean is dependend on a bean that is not unique a dependency should be considered to all beans with the same name or id
  • add an configuration option to disable Spring context file analysis as a command line parameter
  • add an configuration option to disable Spring context file analysis in the configuration file
  • all Spring context files should get considered that are in directories, subdirectories or jar files of the 'classpath'
@schauder
Copy link
Collaborator Author

Sorry, won't happen. If anybody wants their spring file analyzed I see three options:

  • switch to java configuration
  • make a pull request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant