Wouter de Vaal wrote:
Could you clarify the difference between the two?I'm looking for a way to have a complete collection structure being
exported with keeping meta-data on XML documents and binaries in tact
and which
I can import again afterwards. Is there functionality for this (as far
as I can see, xindice -export doesn't support this)?
Do you mean "inline metadata" or "external metadata facilities"? You can export external metadata using "-export" command, it is stored under system collection.
For details on external meta data, see:
xml-xindice\java\src\org\apache\xindice\client\xmldb\services\MetaService.java
xml-xindice\java\src\org\apache\xindice\core\meta\MetaData.java
And config.xml:
- use-metadata:
- When set to 'on', enables external metadata facilities
- for this database instance.
And also see guide-developer.xml, it describes external meta data.
For details on internal meta data, see:
xml-xindice\java\src\org\apache\xindice\core\meta\inline
xml-xindice\java\tests\src\org\apache\xindice\integration\client\resources\BinaryResourceTest.java
Internal meta data used to store some information beside the data, such as xml/binary flag and creation/modification dates. External meta data is accessible programmatically and can be used in applications.
this?Does this need to be written? If so, any suggestions how I should do
For external metadata, I guess the only thing needed is improvement in documentation on import/export. For inline metadata, it should be possible to modify export command to store it in separate file beside resource files. Send patches to the dev list for discussion and applying to CVS.
I can find the export command, but I can't see how it supports metadata, could you give me some pointers where to look?
This exports meta data for test collection:
bin\xindice export -c /db/meta/Metas/test -f output-dir
Vadim
I've looked in CVS at org.apache.xindice.tools.command.ImportTree/ExportTree, but didn't see anything of the kind..
If needed, I'm certainly willing to do my bit.
Regards, Wouter
