mp4parser dependency MappedByteBuffer about mp4parser HOT 13 CLOSED

never thought of that - I am not even sure where this class actually used since 
a do not use it directly. But as it seems the app-engine does not allow any 
java.nio Buffers. That's a problem for me since I use these all over the place.
I would need to create a new level of abstraction ... Not sure if I can do this 
this weekend but I'll try. My GF is on a business trip - got some time to spare

Introducing the interface was easy. Now there is still the getSegment method 
returning a ByteBuffer. Let's see...

java.nio.ByteBuffer is in the whitelist of Google AppEngine
I don't clearly understand your last comment

Ooops. I didn't read the list too carefully. 
I like the interface without ByteBuffer better, anyhow. The change was not that 
big.

Two days ago, I've done successful test with mp4parser in a Java application.
Today, I've done a new try with Google App Engine and I get the message
===========================================
java.lang.NoClassDefFoundError: java.nio.MappedByteBuffer is a restricted 
class. Please see the Google  App Engine developer's guide for more details.
    at com.google.appengine.tools.development.agent.runtime.Runtime.reject(Runtime.java:51)
    at com.coremedia.iso.IsoBufferWrapperImpl.<init>(IsoBufferWrapperImpl.java:75)
.......
===========================================
line 75 is:

buffers.add(raf.getChannel().map(FileChannel.MapMode.READ_ONLY, i, filelength - 
i).slice());

Is there an implicit usage of MappedByteBuffer?

The MappedByteBuffer is always used if you map a file into the memory. Perhaps 
you could try to read the file into a bytebuffer by yourself and then put that 
into the IsoBufferWrapper. That should not use a MappedByteBuffer!

OK
It's a bit tricky, but I will try it and send a report
Thank you for the reply

It's trash, but it do the work for the test. Now, I'm confident that the 
library can work in Google App Engine.
I will search how I have to do it properly to be compatible with future version 
of your code (something like surcharge of IsoBufferWrapperImpl class and better 
attention to large files). Any advice is welcome.
Thank's for your help. 

Other point:
I think you have a problem in HandlerBox.java if the name returned by getName() 
is a string with length=1 and the only char is the byte 0 (which occurs); then 
you produce a malformed string with a 0 in the middle
Possibly the same problem occurs in DataEntryUrnBox.java in the getName method

I added a FileChannelIsoBufferWrapperImpl based on RandomAccessFile. Just check 
out the trunk. This should work on AppEngine.

Fine
It works

is it ok to close the issue?

closing. seems to be resolved

Renamed FileChannelIsoBufferWrapperImpl to 
RandomAccessFileIsoBufferWrapperImpl. The old name was misleading!