[#CMP-234] contract <id> tag must provide a <meta-tag> and <meta-tag> needs a value

Compass

contract <id> tag must provide a <meta-tag> and <meta-tag> needs a value

Created: 26/Jul/06 07:40 AM Updated: 28/Sep/06 04:48 PM

Component/s:

None

Affects Version/s:

None

Fix Version/s:

1.1 M3

Description

« Hide

When making a class-mapping with a <contract>, one must specify store="yes" index="un_tokenized"
<contract alias="myClass">
<id name="id">
<meta-data store="yes" index="un_tokenized">something</meta-data>
</id>
</contract>
Could this be ommited, since store="yes" index="un_tokenized" is always required?

Additionally, the meta-data needs a value (now set to "something", but it may not be empty)

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Shay Banon added a comment - 26/Jul/06 08:47 AM

You don't have to specify meta-data for an id mapping. And if you specify one, it won't necessarily have to be store="yes" index="un_tokenized", you might want to have a tokenized meta-data for it as well. Compass will identify it, and will create an internal meta-data for it in such a case (the same reason why it creates one when there is no meta-data).

[ Permlink | « Hide ]

Shay Banon added a comment - 28/Jul/06 03:00 PM

Any comments about this, or can I close this?

[ Permlink | « Hide ]

Shay Banon added a comment - 03/Aug/06 07:50 AM

Last chance to comment on this one before I close it.

[ Permlink | « Hide ]

Jonas Van Poucke added a comment - 03/Aug/06 09:28 AM

The store and index attribute may be ommitted, but the meta tag must not be empty:
Does not work and throws a NPE
<contract alias="MyClass">
<id name="id">
<meta-data store="yes" index="un_tokenized"></meta-data>
</id>
</contract>

Is ok:
<contract alias="MyClass">
<id name="id">
<meta-data store="yes" index="un_tokenized">justafiller</meta-data>
</id>
</contract>