SourceForge.net Logo
Main Overview Wiki Issues Forum Build Fisheye
Issue Details (XML | Word | Printable)

Key: CMP-751
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Shay Banon
Reporter: Daan de Wit
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Compass

component mapping prefix does not work with dynamic meta data

Created: 22/Oct/08 04:32 AM   Updated: 22/Oct/08 09:53 PM
Component/s: Compass::Core
Affects Version/s: 2.1.0 RC
Fix Version/s: 2.1.0 GA


 Description  « Hide
The searchable component mapping prefix does not work with dynamic meta data. Change, for example, the test in annotations.test.component.prefix.deep1 and add the following to Address.java: @SearchableDynamicMetaData(name="dyn1", expression="return data.location", converter="groovy"). Add this assert to the test Deep1PrefixNoUnmarshall.java: assertEquals("firstHome", resource.getValue("first_home_dyn1"));
The test fails with the following message: "expected: <firstHome> but was: <null>"

When printing the resource to stdout, you'll see that it contains four fields named dyn1, containing the four different values.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Shay Banon added a comment - 22/Oct/08 09:53 PM
Thanks, I fixed it. I added the prefix support for SearchableConstant mapping as well, though I am not sure that it should be there. Maybe will later add a flag to disable prefix on constants.