• Post Reply Bookmark Topic Watch Topic
  • New Topic

jndiname not found  RSS feed

 
ajju Saharan
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
dear all
I have use the petstore application on jboss. when i go to deploy this it shows Exception that attribute JndiName not found,
and other exception is attribute 'ManagedConnectionFactoryName' not found.
i'm sending u the code of xml file in that error is genrating.
<?xml version="1.0" encoding="UTF-8" ?>
- <!-- =====================================================================
-->
- <!--
-->
- <!-- JBoss Server Configuration
-->
- <!--
-->
- <!-- =====================================================================
-->
- <server>
- <!-- ====================================================================
-->
- <!-- ConnectionManager setup for local informix dbs
-->
- <!-- Thanks to Larry Sanderson (larrys@mrstock.com)
-->
- <!-- Build jmx-api (build/build.sh all) and view for config documentation
-->
- <!-- ====================================================================
-->
- <mbean code="org.jboss.resource.connectionmanager.LocalTxConnectionManager" name="jboss.jca:service=LocalTxCM,name=EstoreDataSource">
- <!--
Include a login module configuration named InformixDbRealm.
Update your login-conf.xml, here is an example for a
ConfiguredIdentityLoginModule:
<application-policy name = "InformixDbRealm">
<authentication>
<login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required">
<module-option name = "principal">yourprincipal</module-option>
<module-option name = "userName">yourusername</module-option>
<module-option name = "password">yourpassword</module-option>
<module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=InformixDS</module-option>
</login-module>
</authentication>
</application-policy>
NOTE: the application-policy name attribute must match SecurityDomainJndiName, and the
module-option name = "managedConnectionFactoryName"
must match the object name of the ConnectionManager you are configuring here.

-->
- <!-- uncomment out this line if you are using the Informix DbRealm above
-->
<attribute name="SecurityDomainJndiName">CloudscapeDbRealm</attribute>
- <depends optional-attribute-name="ManagedConnectionFactoryName">
- <!-- embedded mbean
-->
- <mbean code="org.jboss.resource.connectionmanager.RARDeployment" name="jboss.jca:service=LocalTxDS,name=EstoreDataSource">
<attribute name="JndiName">EstoreDB</attribute>
- <attribute name="ManagedConnectionFactoryProperties">
- <properties>
<config-property name="ConnectionURL" type="java.lang.String">jdbc:rmi://localhost:1098/jdbc:cloudscape:EstoreDB;create=true</config-property>
<config-property name="DriverClass" type="java.lang.String">COM.cloudscape.core.RmiJdbcDriver</config-property>
- <!-- set these only if you want only default logins, not through JAAS
-->
<config-property name="UserName" type="java.lang.String">estoreuser</config-property>
<config-property name="Password" type="java.lang.String">estore</config-property>
</properties>
</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=EstoreDataSource">
<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)
-->
<attribute name="Criteria">ByContainer</attribute>
</mbean>
</depends>
<depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager</depends>
<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>
- <mbean code="org.jboss.resource.connectionmanager.LocalTxConnectionManager" name="jboss.jca:service=LocalTxCM,name=InventoryDataSource">
- <!-- uncomment out this line if you are using the Informix DbRealm above
-->
<attribute name="SecurityDomainJndiName">CloudscapeDbRealmInventory</attribute>
- <depends optional-attribute-name="ManagedConnectionFactoryName">
- <!-- embedded mbean
-->
- <mbean code="org.jboss.resource.connectionmanager.RARDeployment" name="jboss.jca:service=LocalTxDS,name=InventoryDataSource">
<attribute name="JndiName">InventoryDB</attribute>
- <attribute name="ManagedConnectionFactoryProperties">
- <properties>
<config-property name="ConnectionURL" type="java.lang.String">jdbc:rmi://localhost:1098/jdbc:cloudscape:EstoreDB;create=true</config-property>
<config-property name="DriverClass" type="java.lang.String">COM.cloudscape.core.RmiJdbcDriver</config-property>
- <!-- set these only if you want only default logins, not through JAAS
-->
<config-property name="UserName" type="java.lang.String">estoreuser</config-property>
<config-property name="Password" type="java.lang.String">estore</config-property>
</properties>
</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=InventoryDataSource">
<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)
-->
<attribute name="Criteria">ByContainer</attribute>
</mbean>
</depends>
<depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager</depends>
<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>
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!