I have found a work-around for this problem, thought I would share it in case anyone else runs into it.
It does appear to be caused by our proxy server and we could find no way to correctly pass credentials to get around it. I did find that schema validation for the changeset.xsd could be turned off by setting the following system property: drools.schema.validating=false -- View this message in context: http://drools.46999.n3.nabble.com/rules-users-proxy-config-for-change-set-schema-fetch-tp2952812p3683482.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
