> -----Message d'origine-----
> De: Jarecsni János [mailto:[EMAIL PROTECTED]]
> Date: vendredi 8 février 2002 11:30
> Ŕ: JBoss-List
> Objet: [JBoss-user] Configuring embedded Catalina
>
>
> Hi,
>
> since I have to integrate JBoss with Apache I have to
> configure the embedded
> tomcat service to emit the AJP configuration for Apache. The
> only question
> is HOW? (I know fairly well how to do this with standalone
> catalina). I
> inserted the following in my jboss.jcml
>
> <mbean code="org.jboss.web.catalina.EmbeddedCatalinaServiceSX"
> name="DefaultDomain:service=EmbeddedTomcat">
> <attribute name="Configuration">
> file:/JBoss-2.4.4_Tomcat-4.0.2b/catalina/conf/server.xml
> </attribute>
> </mbean>
>
> It had absolutely no effect. (The server.xml in catalina's
> conf directory
> has the necessary <Listener> tags, which work well if I run
> Catalina stand
> alone.)
the content of "Config" attribute (not configuration) is not an URL but
an XML tree, with a single root element...
as you seems to already know, server.xml is not read in jboss244+catalina
in official jboss244+catalina only connector, connector/factory
and server/service/connector/listener are interpreted...
the rest is ignored without any warning.
so you may be able to do what you want by
<mbean code="org.jboss.web.catalina.EmbeddedCatalinaServiceSX"
name="DefaultDomain:service=EmbeddedTomcat">
<attribute name="Config">
<server>
<service>
<connector ... ajp13 ...>
<listener ........>
</listener>
</connector>
</service>
</server>
</attribute>
</mbean>
note also that the default http conector still exists, since there is
no way in standard jboss244 to remove the implicit connector created
before the Config attribute
I've proposed a patch to extend the kind of supported tags
(engine, hosts, valve, connector/listener instead of
server/service/connector/listener ).
it also gives an option not to creat the implicit connector
and depend fully on the Config attribute and embedded Connector tags.
I can send you source and even the binary catalina-engine.jar
so that you can use it on a binary distrib.
I'll check soon wether I can do what you propose, but I think
it is the case. otherwise I'll add one more function to
my patch.
could you send here the server.xml which you want to imitate,
so I can respond with a valid mbean config, and maybe even test it here...
> I tried this because I saw this is how you'd
> configure Jetty (using
> the <attribute> tag with a file URI pointing to the config
> file for Jetty).
you give me an idea...
to have an indirect < Attribute
name="ConfigFile">../conf/catalina/catalina-service.xml</Attribute>
or < Attribute
name="ConfigUrl">http://config.cluster.corp.com/catalina-service.xml</Attrib
ute>
< Attribute
name="ConfigRessource">org/jboss/catalina/catalina-service.xml</Attribute>>
or otherwise have something like
< Attribute name="Config"><include
file="../conf/catalina/catalina-service.xml"/></Attribute>
< Attribute name="Config"><include
url="http://config.cluster.corp.com/catalina-service.xml"/></Attribute>
< Attribute name="Config"><include
ressource="org/jboss/catalina/catalina-service.xml"/></Attribute>
or maybe through process instruction
or entity ... but I have few knowledge on entity inclusion...
> Hope someone know how to do it :)
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
