This content has been marked as final.
Show 2 replies
-
1. Re: MBean being registered twice
aidan_b5 Dec 20, 2005 7:05 AM (in response to aidan_b5)Anyone?
jboss-service.xml<?xml version="1.0" encoding="UTF-8"?> <server> <mbean code="com.sms.core.JCR.JCRServiceImpl" name="sms.jcr:service=JCRService" xmbean-dd="meta-inf/jcr-xmbean.xml"> <depends>jboss:service=Naming</depends> </mbean> </server>
jcr-xmbean.xml<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE mbean PUBLIC "-//JBoss//DTD JBOSS XMBEAN 1.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_xmbean_1_2.dtd"> <mbean> <description>JCR MBean service</description> <descriptors> <persistence persistPolicy="OnUpdate" persistPeriod="10" persistLocation="${jboss.server.data.dir}" persistName="JCRService.ser"/> <currencyTimeLimit value="10"/> <state-action-on-update value="keep-running"/> <persistence-manager value="org.jboss.mx.persistence.ObjectStreamPersistenceManager"/> </descriptors> <class>com.sms.core.JCR.JCRServiceImpl</class> <attribute access="read-write" getMethod="getJndiName" setMethod="setJndiName"> <description>JNDI Name</description> <name>jndiName</name> <type>java.lang.String</type> <descriptors> <value value="java:/JCRRepositoryService"/> </descriptors> </attribute> <attribute access="read-write" getMethod="getJCRLocation" setMethod="setJCRLocation"> <description>Location of JCR Repository</description> <name>jCRLocation</name> <type>java.lang.String</type> <descriptors> <value value="c:/temp/rep"/> </descriptors> </attribute> <attribute access="read-write" getMethod="getJCRConfigLocation" setMethod="setJCRConfigLocation"> <description>Location of JCR Repository config file</description> <name>jCRConfLocation</name> <type>java.lang.String</type> <descriptors> <value value="c:/temp/rep/repository.xml"/> </descriptors> </attribute> <operation> <name>start</name> </operation> <operation> <name>stop</name> </operation> </mbean>
-
2. Re: MBean being registered twice
starksm64 Dec 21, 2005 10:43 AM (in response to aidan_b5)There is not sufficient info here to tell what is going on. The lower case meta-inf name is not valid generally, but can be used for your own resources paths. That is the only anomoloy in this info.