In Mirth 1.5 and previous versions I could indicate the classpath in the launcher.xml file.
<launcher>
<classpath base=".">
<lib path="mirth-server.jar" />
<lib path="lib/" />
<lib path="lib/jetty" />
<lib path="lib/mule" />
<lib path="lib/custom" />
<lib path="lib/custom/xxx" />
</classpath>
</launcher>
In Mirth 1.6 I have modified the shell-launcher.xml to indicate the classpath and it does not find my classes. Should I indicate it in other file? Or this is the correct way?
<launcher>
<classpath base=".">
<lib path="mirth-server.jar" />
<lib path="mirth-client-core.jar" />
<lib path="conf/" />
<lib path="lib/" />
<lib path="lib/jetty" />
<lib path="lib/mule" />
<lib path="lib/custom" />
<lib path="lib/custom/xxx" />
<lib path="extensions/connectors" />
</classpath>
</launcher>
Post edited by: apalmero, at: 08/29/2007 09:06
<launcher>
<classpath base=".">
<lib path="mirth-server.jar" />
<lib path="lib/" />
<lib path="lib/jetty" />
<lib path="lib/mule" />
<lib path="lib/custom" />
<lib path="lib/custom/xxx" />
</classpath>
</launcher>
In Mirth 1.6 I have modified the shell-launcher.xml to indicate the classpath and it does not find my classes. Should I indicate it in other file? Or this is the correct way?
<launcher>
<classpath base=".">
<lib path="mirth-server.jar" />
<lib path="mirth-client-core.jar" />
<lib path="conf/" />
<lib path="lib/" />
<lib path="lib/jetty" />
<lib path="lib/mule" />
<lib path="lib/custom" />
<lib path="lib/custom/xxx" />
<lib path="extensions/connectors" />
</classpath>
</launcher>
Post edited by: apalmero, at: 08/29/2007 09:06