[ http://issues.apache.org/jira/browse/JCR-431?page=all ]
Stefan Guggisberg resolved JCR-431:
-----------------------------------
Resolution: Incomplete
where in jackrabbit's code are BLOBFileValue instances reused after they
have been discarded?
what's the exact issue here? are there any jcr api calls that fail?
please provide a simple test case that, using the default configuration,
i.e. DerbyPersistenceManager, demonstrates the issue.
btw: it doesn't help in any way to create multiple jira issues for the same
'problem'...
> BLOBFileValue is reused after its discard ist called
> ----------------------------------------------------
>
> Key: JCR-431
> URL: http://issues.apache.org/jira/browse/JCR-431
> Project: Jackrabbit
> Type: Bug
> Components: core
> Versions: 1.0
> Reporter: Michael Frericks
> Assignee: Stefan Guggisberg
>
> Description:
> BLOBFileValue is reused after its method discard ist called. Discard erases
> the field buffer or the file. At the point of resue this leads to a empty
> property not matching the correct value of the property.
> I observed this bug using the
> org.apache.jackrabbit.core.state.orm.ojb.OJBPersistenceManager.
> Inside its method #load(PropertyId propId) this class calls
> InternalValue create(InputStream value)-> public BLOBFileValue(InputStream in)
> which is the only constructor of BLOBFileValue that sets "temp = true".
> when temp == true then #discard erases the fields buffer or file
> See: http://issues.apache.org/jira/browse/JCR-428
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
