I believe it still works that way, but the issue is more that the
packaged WAR doesn't have a default Recommender, so people are
required to unjar it and then change the web.xml and then repackage it.
-Grant
On Feb 19, 2009, at 6:11 PM, Sean Owen wrote:
Yes you have to say what class to use as the Recommender. This was
done by passing a system property, under Ant, with -D. I am not sure
the part that then builds the right web.xml from that got ported. It
is not a big deal. i can tell people to edit web.xml instead locally.
On Thu, Feb 19, 2009 at 9:29 PM, Grant Ingersoll
<[email protected]> wrote:
I again tried to run the taste-webapp as some kind of sanity
check. If I
use
the one from the distribution it fails and tells me to set the
Recommender
class in the properties file. I do not know whether this is intended
behaviour. But to me it seemed odd that I needed to check out the
sources,
and edit the properties file to make the example webapp run. Maybe
it
would
be better to just provide a default configuration?
I believe you would just have to edit the web.xml and make sure the
Recommender implementation is in the JAR.
--------------------------
Grant Ingersoll
http://www.lucidimagination.com/
Search the Lucene ecosystem (Lucene/Solr/Nutch/Mahout/Tika/Droids)
using Solr/Lucene:
http://www.lucidimagination.com/search
