chkal/pf-issue-test — Issue #117: SpringBeanNameResolver could be smarter about Spring AOP
Author: chkal
Created: 2012-03-06 07:38:43+00:00
State: open

Originally filed by **gudnabr...@gmail.com** on 2011-08-16T22:45:30

Google Code issue: http://code.google.com/p/prettyfaces/issues/detail?id=119

NOTE: For fastest resolution when reporting an issue, please provide attach
example project or file *with sources* that reproduces the problem.

What steps will reproduce the problem?
1. Define a Spring-managed bean with @Named("foo") and @Scope(value=*, proxyMode=!NONE), with one or more @URLMappings
2. Watch PrettyFaces ask for a @URLBeanName annotation
3. Be stubborn, get mad ;P

What is the expected output? What do you see instead?
In this case, Spring returns both "foo" and "scopedTarget.foo". By calling ScopedProxyUtils.getTargetBeanName(String) against "foo", springBeanNameResolver can be smart enough to discard the scoped proxy, which is not for our type of use anyway.

What version of PrettyFaces are you using? On what server and version,
version of JSF, and other relevant technologies?
3.3.1 trunk

Please provide any additional information below.
I consider this an enhancement rather than a defect, but can't see any way to report the former. Git pull request forthcoming.