[ 
https://issues.apache.org/jira/browse/JCR-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761615#action_12761615
 ] 

Michael Xue commented on JCR-1946:
----------------------------------

sure, Claus.  I applied jcr-2.0-b114.jar and moved over the "javax/jcr/Binary". 
 However, another exception comes up.   "javax.resource.ResourceException: 
Failed to create session: Cannot instantiate persistence manager 
org.apache.jackrabbit.core.persistence.bundle.BundleFsPersistenceManager ".  I 
guess it is another jackrabbit/jcr upgrade issue.  Our current configuration is 
based on jackrabbit release 1.5.   The following is the repository.xml.   Do 
you see anything wrong with the configuration of BundleFsPersistenceManager?   
Thanks, Michael

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE Repository PUBLIC "-//The Apache Software Foundation//DTD Jackrabbit 
1.2//EN"
"http://jackrabbit.apache.org/dtd/repository-1.4.dtd";>
<Repository>
    <FileSystem class="org.apache.jackrabbit.core.fs.local.LocalFileSystem">
        <param name="path" value="/data/repo-home/repository"/>
    </FileSystem>
    <Security appName="Jackrabbit">
        <AccessManager 
class="org.apache.jackrabbit.core.security.SimpleAccessManager" />
        <LoginModule 
class="org.apache.jackrabbit.core.security.SimpleLoginModule">
                <param name="anonymous" value="anonymous"/>
        </LoginModule>
        </Security>
    <Workspaces rootPath="/doc-archives/JCRRepo/workspaces" 
defaultWorkspace="default" />
    <Workspace name="${wsp.name}">
        <FileSystem class="org.apache.jackrabbit.core.fs.local.LocalFileSystem">
                <param name="path" value="${wsp.home}"/>
        </FileSystem>
        <PersistenceManager 
class="org.apache.jackrabbit.core.persistence.bundle.BundleFsPersistenceManager">
                <param name="bundlecacheSize" value="8"/>
                <param name="consistencyCheck" value="false"/>
                <param name="errorHandling" value=""/>
        </PersistenceManager>
        <!-- Dont want a SearchIndex, setup for Indexing -->
    </Workspace>
    <Versioning rootPath="${rep.home}/versions">
        <FileSystem class="org.apache.jackrabbit.core.fs.local.LocalFileSystem">
            <param name="path" value="${rep.home}/versions"/>
        </FileSystem>
        <PersistenceManager 
class="org.apache.jackrabbit.core.state.xml.XMLPersistenceManager" />
    </Versioning>
    <Cluster id="${weblogic.Name}">
        <Journal class="org.apache.jackrabbit.core.journal.FileJournal">
        <param name="revision" 
value="/doc-archives/JCRRepo/cluster-revision/revision.log" />
        <param name="directory" value="/doc-archives/JCRRepo/cluster-journal/" 
/>
        </Journal>
</Cluster>
</Repository>   


> JCAResourceAdapter must implement Serializable
> ----------------------------------------------
>
>                 Key: JCR-1946
>                 URL: https://issues.apache.org/jira/browse/JCR-1946
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jca
>    Affects Versions: 1.5.0
>         Environment: Oracle Weblogic 10.0 on Sun Solaris OS 10
>            Reporter: Michael Xue
>             Fix For: 2.0-alpha12
>
>         Attachments: jackrabbit-jca JNDI entry in a single server.jpg, 
> jackrabbit-jca JNDI entry in cluster server.jpg
>
>
> We are running Weblogic 10.0 servers in cluster environment.   When deploying 
> the rar, we always get this warning from weblogic stdout.log: 
> <Jan 15, 2009 2:42:10 AM PST> <Warning> <Connector> <BEA-190155> <Compliance 
> checking/validation of the resource adapter 
> /home/user/jackrabbit_rar/jackrabbit-jca-1.5.0.rar resulted in the following 
> warnings:  The ra.xml <resourceadapter-class> class 
> 'org.apache.jackrabbit.jca.JCAResourceAdapter' should implement 
> java.io.Serializable but does not.> 
> When trying to do the JNDI lookup the repository, we got the error "No Object 
> found: jackrabbit|null".   The jackrabbit entry in the jndi tree is visible 
> only as a javax.naming.reference and not as the JCARepositoryHandle due to 
> the above warning.  Due to that, we can't deploy jackrabbit-jca in 
> Test/Production environment.  
> I'm no expert in JCA, but feel it is fairly easy to implement Serializable 
> for  JCAResourceAdapter.  Please help us out.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to