Often your Red5 project may need some external variable to be passed into Red5 application as a part of your configuration data, such that its not hard coded into the red5 application and you can change it as and when needed. For example : A database name, a configuration file path etc etc
Here we will demonstrate two ways to pass configuration data into Red5 application.
- Though red5-web.xml directly
- Through red5.properties routed via red5.xml
Passing parameters through red5-web.xml
This is the first method used to pass configuration data into your red5 application. In this example we will pass variable into the main application class.
import org.red5.server.Scope;
import org.red5.server.adapter.ApplicationAdapter;
import org.red5.server.api.IConnection;
import org.red5.server.api.IScope;
import org.red5.server.api.service.ServiceUtils;
public class Application extends ApplicationAdapter {
public String database = "mydb.sqlite";
/** {@inheritDoc} */
@Override
public boolean appStart(IScope scope) {
return true;
}
@Override
public boolean connect(IConnection conn, IScope scope, Object[] params) {
return true;
}
@Override
public void disconnect(IConnection conn, IScope scope) {
super.disconnect(conn, scope);
}
public void setDatabase(String dbname)
{
database = dbname;
}
}
Note the last function: setDatabase this is the public setter function which will set the value of the variable database. Now the second part of this process is sending value to this function from outside Red5. For that we will be usingt the Red5 bean configuration file – red5-web.xml
So now we will edit the red5-web.xml file at the application’s bean handler definition and add the the variable property to it.
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">
<beans>
<!--
Defines a properties file for dereferencing variables
-->
<bean id="placeholderConfig" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
<property name="location" value="/WEB-INF/red5-web.properties" />
</bean>
<!--
Defines the web context
-->
<bean id="web.context" class="org.red5.server.Context"
autowire="byType" />
<!--
Defines the web scopes
-->
<bean id="web.scope" class="org.red5.server.WebScope"
init-method="register">
<property name="server" ref="red5.server" />
<property name="parent" ref="global.scope" />
<property name="context" ref="web.context" />
<property name="handler" ref="web.handler" />
<property name="contextPath" value="${webapp.contextPath}" />
<property name="virtualHosts" value="${webapp.virtualHosts}" />
</bean>
<!--
Defines the web handler which acts as an applications endpoint
-->
<bean id="web.handler" class="org.red5.core.Application" singleton="true">
<property name="database" value="mydb.sqlite"/>
</bean>
</beans>
Note the application bean definition to see how the database property is passed into the application bean handler to the public setter function
<property name="database" value="mydb.sqlite"/>
</bean>
At this stage it is important to note of the setter function is named:
public function setDatabase, like in the following format
setVariablename. The variable name is camel-cased along with the word”set”