Hi,
Sorry if I'm repeating some a already discussed problem but I haven't
managed to find a similar issue.
I'm using jackrabbit resource adapter deployed in weblogic as a separate
deployment. I've attached the ra.xml and weblogic-ra.xml.
Also my application packaged as a war is deployed in the weblogic app
server.
I obtain the jackrabbit repository with spring and jndi:
<bean id="wl_repository"
class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiName" value="${wl.jcr.repository}" />
<property name="proxyInterface" value="javax.jcr.Repository" />
</bean>
The problem is that when I start the application server the two
applications (the jackrabbit ra and my war) I see that weblogic
successfully deploys the ra first and then tries to deploy the war but
when the
war is being deployed it fails because it doesn't find the jndi name.
Invocation of init method failed; nested exception is
javax.naming.NameNotFoundException: Unable to resolve 'jackrabbitOUT'.
Resolved ''; remaining name 'jackrabbitOUT'.
I might be barking on the wrong tree here, maybe this looks more like a
weblogic issue. But I'm just asking if someone has a similar
configuration in weblogic like a jackrabbit resource adapter and a war
deployed separately and communicating with jndi.
I know that a solution might be to package a ear in which to include the
ra and the war, but is there another approach?
<connector xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd" version="1.5">
<display-name>Jackrabbit JCR Adapter</display-name>
<vendor-name>Apache.org</vendor-name>
<eis-type>JCR Adapter</eis-type>
<resourceadapter-version>1.0</resourceadapter-version>
<resourceadapter>
<resourceadapter-class>org.apache.jackrabbit.jca.JCAResourceAdapter</resourceadapter-class>
<outbound-resourceadapter>
<connection-definition>
<managedconnectionfactory-class>org.apache.jackrabbit.jca.JCAManagedConnectionFactory</managedconnectionfactory-class>
<config-property>
<config-property-name>HomeDir</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>/data/bes/wl_repository</config-property-value>
</config-property>
<config-property>
<config-property-name>ConfigFile</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>/data/bes/wl_repository/repository.xml</config-property-value>
</config-property>
<connectionfactory-interface>javax.jcr.Repository</connectionfactory-interface>
<connectionfactory-impl-class>org.apache.jackrabbit.jca.JCARepositoryHandle</connectionfactory-impl-class>
<connection-interface>javax.jcr.Session</connection-interface>
<connection-impl-class>org.apache.jackrabbit.jca.JCASessionHandle</connection-impl-class>
</connection-definition>
<transaction-support>XATransaction</transaction-support>
<reauthentication-support>false</reauthentication-support>
</outbound-resourceadapter>
</resourceadapter>
</connector><weblogic-connector xmlns="http://www.bea.com/ns/weblogic/90">
<jndi-name>jackrabbitRA</jndi-name>
<enable-access-outside-app>true</enable-access-outside-app>
<enable-global-access-to-classes>true</enable-global-access-to-classes>
<outbound-resource-adapter>
<connection-definition-group>
<connection-factory-interface>javax.jcr.Repository</connection-factory-interface>
<connection-instance>
<jndi-name>jackrabbitOUT</jndi-name>
<connection-properties>
<pool-params>
<initial-capacity>1</initial-capacity>
<max-capacity>200</max-capacity>
<capacity-increment>1</capacity-increment>
<shrinking-enabled>true</shrinking-enabled>
<shrink-frequency-seconds>60</shrink-frequency-seconds>
</pool-params>
<logging>
<log-filename>logs/jcr-ra.log</log-filename>
<logging-enabled>true</logging-enabled>
</logging>
<properties>
<property>
<name>HomeDir</name>
<value>/data/bes/wl_repository</value>
</property>
<property>
<name>ConfigFile</name>
<value>/data/bes/wl_repository/repository.xml</value>
</property>
</properties>
</connection-properties>
</connection-instance>
</connection-definition-group>
</outbound-resource-adapter>
</weblogic-connector>