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

Already on GitHub? Sign in to your account

SEC-1164: Spring Security extension does not seem to support security namespace config in Open Graph #1412

spring-issuemaster opened this Issue May 19, 2009 · 6 comments


None yet
1 participant

Willie Wheeler (Migrated from SEC-1164) said:

Please see the Spring forum reference above, and in particular, the message I posted on Mar 29, 2009.

I've installed the Spring IDE Spring Security Extension (2.2.4.RELEASE) and would have expected that this would allow me to use Open Graph to visualize security namespace configurations, such as , , and so forth. (The Spring Batch Extension allows me to visualize the custom Spring Batch namespace just fine.) Not sure if my expectation is wrong or whether I'm just missing something.

Christian Dupuis said:

Spring IDE does not get the required events from Spring Security's namespace parser implementations. You can see that also by looking at the Spring Explorer which in your example only provides on bean.

(see attached screenshot)

Christian Dupuis said:

Luke, I moved that issue from Spring IDE over to Spring Security as the namespace parser implementation fail to register BeanComponentDefinitions that can be captured by Spring IDE.

Luke Taylor said:

Linkking to SEC-1196 as we need to have a single bean registered with knowledge of the providers in order to show them in tooling. Currently a post processor is used to set the providers.

Luke Taylor said:

This should be fixed now. Most of the namespace code has been reworked to remove bean decorators and the use of post-processors for wiring up things like the filter chain, so a realistic portrayal of the final bean configuration can be achieved by the tooling environment.

Willie Wheeler said:

I'm still seeing a blank graph. I'm using

  • Eclipse 3.5 (20090920-1017)
  • Spring IDE Security Extension
  • Spring Security 3.0.0.RC1

Happy to post more information if this is something more than a config issue on my side. :-)

@spring-issuemaster spring-issuemaster added this to the 3.0.0 M2 milestone Feb 5, 2016

This issue depends on #1435
This issue depends on #1444

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment