thanks to danch, when I use Jboss2.1 beta, all of things are OK.
thanks to Ken Jenks.
in addition:
Perhaps it is a silly problem.
I want to know why the file "jboss.conf" and other likewise ***.conf files
use the format of XML? but when I comment this line in jboss.conf like this:
<MLET CODE = "org.jboss.util.ClassPathExtension" ARCHIVE="jboss.jar"
CODEBASE="../../lib/ext/">
<!-- Comment by Sam Liu
<ARG TYPE="java.lang.String" VALUE="../../../jakarta-tomcat-3.2.1/lib/">
-->
<ARG TYPE="java.lang.String" VALUE="../../../tomcat/lib/">
<ARG TYPE="java.lang.String" VALUE="Tomcat">
</MLET>
i found that jboss can not start up tomcat.
that is to say ***.conf do NOT support XML parsering.
when I correct it like this:
<MLET CODE = "org.jboss.util.ClassPathExtension" ARCHIVE="jboss.jar"
CODEBASE="../../lib/ext/">
<!-- ARG TYPE="java.lang.String" VALUE="../../../jakarta-tomcat-3.2.1/lib/" -->
<ARG TYPE="java.lang.String" VALUE="../../../tomcat/lib/">
<ARG TYPE="java.lang.String" VALUE="Tomcat">
</MLET>
it is OK.
So, if all of the files of "***.conf" can be parsered on html or xml format,
perhaps is it better?
------- origional info----------
First, I assume you're running JBoss 2.0? If you're running 2.1/2.2, the
config is a little different.
...........
�,�ǫ����x%��I�,�ǫ�+-��.�ǟ�� ��a���X���(�� ~��zw��X�����b��?��,��
