Supposing a ParameterExpression is defined and then subsequently not used in a query, for example due to an application setting, when the user attempts to set this parameter using Query::setParameter a nullpointer exception is thrown.

This is due to CriteriaQueryTypeQueryAdapter::explicitParameterInfoMap not having a key for the parameter, as it was never used in the query to begin with.

Either this should throw an explicit runtime exception, if this behavior is indeed meant to be disallowed or silently do nothing, as the parameter is not in the query to begin with.

Apologies if this has been fixed in a newer version.