← Back to branch summary

~donal-k-fellows/taverna-server/2.4.1i-maintenance

« back to all changes in this revision

Viewing changes to server-webapp/src/main/webapp/WEB-INF/beans.xml

  • Committer: Donal Fellows
  • Date: 2015-06-23 10:32:45 UTC
  • Revision ID: git-v1:75f33c4befcbf47d6d1068e585e7e73202a207e5
Workaround problems with interactions when running Taverna Server inside
Docker inside a VM.
The networking configuration in that situation is non-trivial, and
beyond what it is practical to auto-detect. This means that at least it
is possible to fix the problem by just adjusting a properties file,
instead of having to edit the bean configuration file directly.

Show diffs side-by-side

added added

removed removed

Lines of Context:
server-webapp/src/main/webapp/WEB-INF/beans.xml
499
499
                class="org.taverna.server.master.identity.WorkflowInternalAuthProvider">
500
500
                <property name="dao" ref="worker.runDAO" />
501
501
                <property name="cacheBound" value="${default.runlimit}" />
 
502
                <property name="additionalAuthorizedAddresses" value="${taverna.interaction.trusted_ip_addresses}" />
502
503
        </bean>
503
504
        <bean id="velocity" class="org.apache.velocity.app.VelocityEngine"
504
505
                init-method="init" lazy-init="false">