Here it is in attachement.
> -----Message d'origine-----
> De : [EMAIL PROTECTED]
> [mailto:tapestry-developer-admin@;lists.sourceforge.net]De la part de
> marc harster
> Envoye : dimanche, 27 octobre 2002 00:11
> A : [EMAIL PROTECTED]
> Objet : [Tapestry-developer] McKoi DB on JBoss3.0.3
>
>
> When I try to use mckoi service in JBoss 3.0.3 I get
> the complain reported below.
>
> Does anybody achieved to use mckoi in jb3.0.3?
> The strange thing is that Mckoi service shows started
> in the jmx console, the error seems to be related with
> the flag CONFIGURED but in short I have no clue .
> Thanks.
>
>
>
> 00:04:04,593 ERROR [URLDeploymentScanner]
> MBeanException: Exception in MBean operation
> 'checkIncompleteDeployments()'
> Cause: Incomplete Deployment listing:
> Packages waiting for a deployer:
> <none>
> Incompletely deployed packages:
> <none>
> MBeans waiting for classes:
> <none>
> MBeans waiting for other MBeans:
> [ObjectName: jboss.jca:service=LocalTxCM,name=McKoiDB
> state: CONFIGURED
> I Depend On: jboss:service=McKoiDB
> jboss.jca:service=LocalTxDS,name=McKoiDB
> jboss.jca:service=LocalTxPool,name=McKoiDB
> jboss.jca:service=CachedConnectionManager
> jboss.security:name=JaasSecurityManager
> jboss.jca:service=RARDeployer
>
> Depends On Me: ]
>
> __________________________________________________
> Do you Yahoo!?
> Y! Web Hosting - Let the expert host your web site
> http://webhosting.yahoo.com/
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ApacheCon, November 18-21 in
> Las Vegas (supported by COMDEX), the only Apache event to be
> fully supported by the ASF. http://www.apachecon.com
> _______________________________________________
> Tapestry-developer mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/tapestry-developer
>
<?xml version="1.0" encoding="UTF-8"?>
<!-- $Id: mckoi-service.xml,v 1.3 2002/06/17 21:00:48 hship Exp $ -->
<!-- ===================================================================== -->
<!-- -->
<!-- McKoi Database 0.92 configuration -->
<!-- -->
<!-- ===================================================================== -->
<!-- This is basically a cut-and-paste of the Solid example service, modified
for McKoi DB. The McKoi MBeans reside in
net.sf.tapestry.contrib-x-x-x.jar. -->
<server>
<mbean code="net.sf.tapestry.contrib.mckoi.McKoiDB" name="jboss:service=McKoiDB">
<attribute name="RootPath">../server/tapestry/db</attribute>
<attribute name="ConfigPath">../server/tapestry/db/vlib.conf</attribute>
</mbean>
<mbean
code="org.jboss.resource.connectionmanager.LocalTxConnectionManager"
name="jboss.jca:service=LocalTxCM,name=McKoiDB">
<depends>jboss:service=McKoiDB</depends>
<depends optional-attribute-name="ManagedConnectionFactoryName">
<!--embedded mbean-->
<mbean
code="org.jboss.resource.connectionmanager.RARDeployment"
name="jboss.jca:service=LocalTxDS,name=McKoiDB">
<attribute name="JndiName">McKoiDB</attribute>
<!--NOTE: Solid wants the username/password in the URL, it will
ignore the specific arguments.-->
<attribute name="ManagedConnectionFactoryProperties">
<properties>
<config-property name="ConnectionURL" type="java.lang.String">jdbc:mckoi://localhost/</config-property>
<config-property name="DriverClass" type="java.lang.String">com.mckoi.JDBCDriver</config-property>
<config-property name="UserName" type="java.lang.String">admin</config-property>
<config-property name="Password" type="java.lang.String">secret</config-property>
</properties>
<!--These properties are ignored by the Solid driver.
<config-property name="UserName" type="java.lang.String"></config-property>
<config-property name="Password" type="java.lang.String"></config-property>
-->
</attribute>
<!--hack-->
<depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper</depends>
</mbean>
</depends>
<depends optional-attribute-name="ManagedConnectionPool">
<!--embedded mbean-->
<mbean code="org.jboss.resource.connectionmanager.JBossManagedConnectionPool"
name="jboss.jca:service=LocalTxPool,name=McKoiDB">
<attribute name="MinSize">0</attribute>
<attribute name="MaxSize">50</attribute>
<attribute name="BlockingTimeoutMillis">5000</attribute>
<attribute name="IdleTimeoutMinutes">15</attribute>
<!--criteria indicates if Subject (from security domain) or app supplied
parameters (such as from getConnection(user, pw)) are used to distinguish
connections in the pool. Choices are
ByContainerAndApplication (use both),
ByContainer (use Subject),
ByApplication (use app supplied params only),
ByNothing (all connections are equivalent, usually if adapter supports
reauthentication)-->
<!-- Since at present only a single user specified in the URL is supported,
ByNothing is mosst appropriate. If a URL construction scheme is implemented,
this could be one of the other values -->
<attribute name="Criteria">ByNothing</attribute>
</mbean>
</depends>
<depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager</depends>
<!-- Since the username/password needs to be in the url, there is no way at
present for a generic wrapper to supply user/pw to the driver. A custom
wrapper could be used to consruct the url dynamically from a base and the
user/pw. In case someone does that, I'm leaving the container-managed-security
attribute in. -->
<!-- <attribute name="SecurityDomainJndiName">SolidDbRealm</attribute>-->
<depends optional-attribute-name="JaasSecurityManagerService">jboss.security:service=JaasSecurityManager</depends>
<attribute name="TransactionManager">java:/TransactionManager</attribute>
<!--make the rar deploy! hack till better deployment-->
<depends>jboss.jca:service=RARDeployer</depends>
</mbean>
</server>
