[ http://jira.andromda.org/browse/SPRING-133?page=history ] Peter Friese closed SPRING-133: -------------------------------
> Add a tagged value turn on/off named parameters for each finder individually > ---------------------------------------------------------------------------- > > Key: SPRING-133 > URL: http://jira.andromda.org/browse/SPRING-133 > Project: Spring Cartridge > Type: Improvement > Versions: 3.1 > Reporter: Peter Friese > Assignee: Peter Friese > Fix For: 3.2-RC1 > > Using the namespace property "hibernateQueryUseNamedParameters" it is > possible to let finders use named parameters or unnamed parameters. Due to > the very nature of a namespace setting, this has a globel effect. Sometimes, > it is desirable to let just one finder behave differently. > That's why I suggest we introduce a new tagged value > "@hibernateQueryUseNamedParameters" to be able to configure the usage of > named parameters on a per-finder basis. > I have seen that there are two locations in the metafacades where we'd have > to perform a change: > SprinQueryOperationLogicImpl.handleIsUseNamedParameters() and > HibernateFinderMethodLogicImpl.handleIsUseNamedParameters(). ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
