On Tue, Mar 2, 2010 at 4:57 PM, Birmingham, Steven
<[email protected]> wrote:
> Thank you for the reply.  I had a second question.  I tried using OCM with 
> annotations and my test class includes a bean annotation.  It resulted in an 
> exception that the bean class could not be inserted because it had no UUID. 
> The JackRabbit 2.0 OCM docs mention that the bean needs to be registered.  Is 
> this still true?  If yes, what is the minimal amount of configuration needed 
> to register the bean.  I looked at the OCM Digester test and it has about 10 
> configuration files defined.

i am not an OCM expert, i successfully managed to stay away so far
from OCM and sorts. why don't you just use the plain old JCR api?;)

if you insist on using OCM, one of our OCM experts (christophe?) might
be able to answer your question.

cheers
stefan


>
> Thanks again,
> Steve
>
> -----Original Message-----
> From: Stefan Guggisberg [mailto:[email protected]]
> Sent: Tuesday, March 02, 2010 8:34 AM
> To: [email protected]
> Subject: Re: ImportXml object size limitation?
>
> hi steven,
>
> the issue you've run into ('Form too large') seems to be a limitation/
> bug of the spi2dav remoting layer.
>
> as a workaround you can try the following:
> - access local repo
> and/or
> - use Workspace.importXml
>
> cheers
> stefan
>
> On 01.03.2010, at 20:49, "Birmingham, Steven"
> <[email protected]> wrote:
>
>> Hello,
>>
>> I am new to JackRabbit and am running some insertions tests using
>> the session.ImportXml capability.  I have it working but get errors
>> on large objects due to an internal form size limit.  Is this
>> configurable?  Is this a good way to persist objects or should I be
>> using OCM?
>>
>> Thanks,
>> Steve
>>
>> Error with Repository
>> javax.jcr.RepositoryException: Form too large350728>200000
>>      at org.apache.jackrabbit.spi2dav.ExceptionConverter.generate
>> (ExceptionConverter.java:113)
>>      at org.apache.jackrabbit.spi2dav.ExceptionConverter.generate
>> (ExceptionConverter.java:49)
>>      at org.apache.jackrabbit.spi2davex.RepositoryServiceImpl
>> $BatchImpl.start(RepositoryServiceImpl.java:457)
>>      at org.apache.jackrabbit.spi2davex.RepositoryServiceImpl
>> $BatchImpl.access$200(RepositoryServiceImpl.java:399)
>>      at org.apache.jackrabbit.spi2davex.RepositoryServiceImpl.submit
>> (RepositoryServiceImpl.java:304)
>>      at org.apache.jackrabbit.jcr2spi.WorkspaceManager
>> $OperationVisitorImpl.execute(WorkspaceManager.java:830)
>>      at org.apache.jackrabbit.jcr2spi.WorkspaceManager
>> $OperationVisitorImpl.access$500(WorkspaceManager.java:797)
>>      at org.apache.jackrabbit.jcr2spi.WorkspaceManager.execute
>> (WorkspaceManager.java:594)
>>      at
>> org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.save
>> (SessionItemStateManager.java:139)
>>      at org.apache.jackrabbit.jcr2spi.ItemImpl.save(ItemImpl.java:246)
>>      at org.apache.jackrabbit.jcr2spi.SessionImpl.save
>> (SessionImpl.java:328)
>>      at com.ist.jcr.jackrabbit.test.SigIntDataCreateTest.<init>
>> (SigIntDataCreateTest.java:104)
>>      at com.ist.jcr.jackrabbit.test.SigIntDataCreateTest.main
>> (SigIntDataCreateTest.java:141)
>> Caused by: org.apache.jackrabbit.webdav.DavException: Form too
>> large350728>200000
>>      at
>> org.apache.jackrabbit.webdav.client.methods.DavMethodBase.getResponseException(
>> DavMethodBase.java:169)
>>      at
>> org.apache.jackrabbit.webdav.client.methods.DavMethodBase.checkSuccess(
>> DavMethodBase.java:181)
>>      at org.apache.jackrabbit.spi2davex.RepositoryServiceImpl
>> $BatchImpl.start(RepositoryServiceImpl.java:453)
>>
>> ________________________________
>> This e-mail and any files transmitted with it may be proprietary and
>> are intended solely for the use of the individual or entity to whom
>> they are addressed. If you have received this e-mail in error please
>> notify the sender.
>> Please note that any views or opinions presented in this e-mail are
>> solely those of the author and do not necessarily represent those of
>> ITT Corporation. The recipient should check this e-mail and any
>> attachments for the presence of viruses. ITT accepts no liability
>> for any damage caused by any virus transmitted by this e-mail.
>

Reply via email to