You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2005/11/16 23:52:47 UTC

DO NOT REPLY [Bug 37539] New: - [collections] Error in deserialization of full BoundedFifoBuffer

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37539>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=37539

           Summary: [collections] Error in deserialization of full
                    BoundedFifoBuffer
           Product: Commons
           Version: 3.1
          Platform: All
               URL: http://jakarta.apache.org/commons/collections/api-
                    release/org/apache/commons/collections/buffer/BoundedFif
                    oBuffer.html
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: P2
         Component: Collections
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: apachebugz@tkuhn.de
                CC: apachebugz@tkuhn.de


If a BoundedFifoBuffer is serialized and then deserialized the value of the end
attribute is set to the max size of the Buffer which is a fault and causes an
ArrayIndexOutOfBoundException during add(object). In this case the value of end
must be set to 0 in the deserialization.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org

Re: memory:// protocol implementation

Posted by Mario Ivankovits <ma...@ops.co.at>.

Mark Proctor wrote:
> Anyone know of a memory:// protocol implementation for URLs? I'm 
> guessing it will need implementations for MemoryURLStreamHandler, 
> MemoryURLStreamHandlerFactory, MemoryURLConnect and should be able to 
> work with URLClassLoaders - would have thought this would be in 
> commons io.
The next version of commons-vfs will have a ramfs://
As always in VFS it is able to use it through URLs and in classloaders.

---
Mario


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org

memory:// protocol implementation

Posted by Mark Proctor <li...@markproctor.com>.

Anyone know of a memory:// protocol implementation for URLs? I'm 
guessing it will need implementations for MemoryURLStreamHandler, 
MemoryURLStreamHandlerFactory, MemoryURLConnect and should be able to 
work with URLClassLoaders - would have thought this would be in commons io.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org