In the 2.0 release the jboss.jcml file is a dump of the servers loaded configuration.
You
need to put mbean configurations in the jboss.conf. This:
> <!-- Add your custom MBeans here -->
>
> <mbean code="org.jboss.zoap.HttpServer" name="zoap:server=HTTP">
> </mbean>
is only valid for the current jboss cvs release which write the server configuration
to a jboss-auto.jcml
file. The corresponding jboss.conf entry for the above should be this:
<MLET CODE = "org.jboss.zoap.HttpServer" ARCHIVE="zoap.jar" CODEBASE="../../lib/ext/">
</MLET>
I don't know if the current zoap cvs release is compatible with the jboss 2.0 final so
post back
with any additional problems.
----- Original Message -----
From: "Jeffrey Wescott" <[EMAIL PROTECTED]>
To: "jBoss" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, January 11, 2001 2:22 PM
Subject: Re: AW: AW: [jBoss-User] Using ZOAP?
<sigh> I'm very frustrated. I don't quite understand why the lines are
"automatically" removed for me. I add those two lines right before the
container factory and then they are deleted when the server starts up.
It seems that jboss.jcml is written by the server. I'm using the
embedded Tomcat / Jboss distribution 2.0 FINAL.
Nothing appears in the log file about zoap at all, except that it was
adding zoap.jar to the classpath.
I'm about to give up ...
++Jeff
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
