|
||||||||||
| PREV NEXT | FRAMES NO FRAMES | |||||||||
| Packages that use MatchMode | |
|---|---|
| net.sourceforge.openutils.mgnlcriteria.jcr.query.criterion | |
| Uses of MatchMode in net.sourceforge.openutils.mgnlcriteria.jcr.query.criterion |
|---|
| Fields in net.sourceforge.openutils.mgnlcriteria.jcr.query.criterion declared as MatchMode | |
|---|---|
static MatchMode |
MatchMode.ANYWHERE
Match the pattern anywhere in the string |
static MatchMode |
MatchMode.END
Match the end of the string to the pattern |
static MatchMode |
MatchMode.START
Match the start of the string to the pattern |
| Methods in net.sourceforge.openutils.mgnlcriteria.jcr.query.criterion with parameters of type MatchMode | |
|---|---|
static JCRFunctionExpression |
Restrictions.like(String nodeName,
Object value,
MatchMode matchMode)
Apply a "like" constraint to the named node Be warned when using jcr:like function, as it can be very slow. The following account of why it is so, was taken from users@jackrabbit.apache.org mailing list Question: My xpath is '//*[jcr:like(@propertyName, '%somevalue%')]' and it takes minutes to complete. |
| Constructors in net.sourceforge.openutils.mgnlcriteria.jcr.query.criterion with parameters of type MatchMode | |
|---|---|
LikeExpression(String propertyName,
Object value,
String function,
MatchMode matchMode)
|
|
|
||||||||||
| PREV NEXT | FRAMES NO FRAMES | |||||||||