To be honest, I am not a big fan of the '/@corename' syntax ; I feel the '?core=corename' syntax carries less surprise and may be extended more easily (Stu's comment in solr-350). I've uploaded a small patch to solr-350 (solr-350.patch) so the core as a request parameter works again (& passes the core as a request attribute after it has been resolved).
hossman wrote: > > > I notice this in the MultiCore wiki... > >>> To access the admin pages for each core visit: >>> http://localhost:8983/solr/admin/?core=core0 >>> http://localhost:8983/solr/admin/?core=core1 > > ...trying this out using the example multicore setup didn't seem to work > (the admin screen said core0 even for the second URL) -- but in general > i'm curious if there's a specific desire for the admin pages to work with > URLs like this (the core name as a URL param) instead of the having the > core in the path like for the rest of the URLs? > > Sure the admin pages are (mostly) JSPs, but before the Dispatcher forwards > the request/response up the chain, it could pull the core name out of the > path and include it as a request attribute right? > > > > > -Hoss > > > -- View this message in context: http://www.nabble.com/multicore-and-admin-pages--tp14268867p14275004.html Sent from the Solr - Dev mailing list archive at Nabble.com.
