On 8/6/10 10:15 AM, Kiran Ayyagari wrote:
IMO, this is barely acceptable for API 0.2, but has to be fixed for 0.3.
There is no reason to extract to disk when all the ldifs are available in a
jar, as it's just a matter of loading them in memory.
It should be a 2 hours work to get the code read the jar and load the schema
in memory...
it is already possible to do this using JarLdifSchemaLoader , but note
that this will always
contain the bundled default schemas only. A user can only add custom
schema if the
schema directory is present on disk.
Ah, so we are golden.
Is there a place where this is documented (even roughly) ?
I think we have some users facing this issue.
Btw, I don't really care if users can't extend the schema when they
can't write on disk. But we can discuss about allowing this too.
Thanks Kiran.
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
