make context:exclude-filter expression supports placeholder like context:component-scan base-package [SPR-10424]

[spring-projects-issues]

Yanming Zhou opened SPR-10424 and commented

<context:component-scan base-package="${APP_BASE_PACKAGE}">
<context:exclude-filter type="regex" expression="${APP_EXCLUDE_PACKAGE:}"/>
</context:component-scan>

same to context:include-filter

---

Reference URL: https://jira.springsource.org/browse/SPR-4351

Issue Links:

• Placeholders in context:component-scan's base-package attribute [SPR-4351] #9030 Placeholders in context:component-scan's base-package attribute
• please let context:component-scan base-package eval placeholder then split by comma [SPR-10425] #15058 please let context:component-scan base-package eval placeholder then split by comma
• Consistent Environment access in XML bean definition parsing code [SPR-12248] #16862 Consistent Environment access in XML bean definition parsing code

[spring-projects-issues]

Yanming Zhou commented

ping

[spring-projects-issues]

Juergen Hoeller commented

Finally addressed for 4.1.1! Please give the upcoming 4.1.1 snapshot a try and let me know whether it works for you...

Juergen

[spring-projects-issues]

Yanming Zhou commented

It works fine with version "4.1.1.BUILD-20140924.233856-34", thanks !

[spring-projects-issues]

Yanming Zhou commented

Should exclude-filter and include-filter supports comma seperation? so we can use one placeholder to rule them all.

[spring-projects-issues]

Juergen Hoeller commented

I'm afraid this is significantly harder since filter expressions can have many formats, with a comma - or any other character - not necessarily being a good separator. I'd rather leave this as-is, just supporting the auto-splitting for base package specifications (along the lines of many other places where we support comma-separated class and package names).

Juergen