Hi Alexis,
We had the same problem. While we haven't found the exact source of the problem
(most likely the sun JAX-WS client implementation) there are several
work-arounds that worked for us: The problem happened when we used a JAX-WS
client generated by NetBeans and executed the client by the
Mike-
Thanks for the help. Changed xacml.enabled to "true" (it was "false") and
restarted Tomcat. I am running this off a Parallels virtual volume on an
external hard drive attached to a MacBook. The Ubuntu volume shares the
MacBook's network connection and can get to the web, etc. When I test
Howard,
To see if you enabled XACML check the following:
FEDORA_HOME/install/install.properties for "xacml.enabled=true"
You need to add your desktop/laptop ip to the XACML file if you are
accessing the web GUI. By default it only allows local host. The
following file needs to be modifie
Dear Gert,
We are looking at a use case for GSearch that requires a remote solr
installation. For the most part GSearch has worked very well for us.
To more easily enable this use case in the future, though, I'd like to
recommend two relatively small changes:
1. don't require a local index
> the dependency on a mock local index
can be avoided by a few code changes in a future release, but it works as it is.
> host their Solr instance(s) remotely from their GSearch instance to still
> benefit from GSearch's search functionality
Well, GSearch's search functionality for the Solr pl