Hi,
>> -How to handle revisions - Can we have methods to read those tags too. > one > >> for WikiPageRevision and other for AttachmentRevision. > > Maybe something like: > > beginWikiPage() > beginWikiPageRevision() > beginObject(type) > onProperty() > endObject() > beginObject() > onProperty() > endObject() > beginClass() > onProperty() > endClass() > beginAttachment() > onAttachmentRevision() > endAttachment() > endWikiPage() > beginWikiPageRevision() > beginObject(type) > onProperty() > endObject() > beginObject() > onProperty() > endObject() > onAttachmentRevision() (since i think you can't have several > attachement revision for the same wiki page revision) > endWikiPage() > endWikiPage() > +1 for something like this. Now I don't think that other wiki formats (mediawiki, confluence) will normally fire events like beginObject() / endObject() but it's important to have the full span of XWiki's capabilities embodied into this API. Because then we can, 1) Use this generic importer even when importing xwiki xml exports, 2) We'll be able to map different concepts of other wiki exports into xwiki concepts. An example is mapping [category] links of mediawiki into xwiki tags. Thanks. - Asiri > basically you can look at XWiki xml ecport format and map something > similar for events I think (not the exact same thing the export format > need improvements). > > >> > >> > >>> I think you should start working on a revised proposal with this > >>> information > >>> taken into account. In the mean time other developers will comment on > this > >>> proposal if they have further suggestions. > >>> > >>> - Asiri > >>> > >>> > >>> > > > >>> > > > >>> > >> *** [NICE TO HAVE] List<Class<?>> getParameters(): the list of > >>> > >> parameters type to provide to the importer, that way you can > generate > >>> > >> a UI based on it since parameters totally depends on the importer, > you > >>> > >> could have an importer able to import the wiki from an URL for > example > >>> > >> using REST/XMLRPC... for the same reason List<InputStream> is not > >>> > >> generic enough IMO. You can look at MacroDescriptor for > inspiration, > >>> > >> we could make it more generic as a list of parameters instead of a > >>> > >> list of macro parameters to use it in wiki importer, > authenticators, > >>> > >> etc. I see this tool as a generic way to get wiki content from any > >>> > >> kind of external source, we could even use it to copy a XWiki wiki > >>> > >> without having to do an export/import by hand for example. > >>> > >> > >>> > > > >>> > > +1 > >>> > > > >>> > > This will make it possible to define different types of importers > with > >>> > > different requirements (rather than restricting them to > >>> > List<InputStream>) > >>> > > > >>> > > Thanks. > >>> > > > >>> > > - Asiri > >>> > > _______________________________________________ > >>> > > devs mailing list > >>> > > [email protected] > >>> > > http://lists.xwiki.org/mailman/listinfo/devs > >>> > > > >>> > > >>> > > >>> > > >>> > -- > >>> > Thomas Mortagne > >>> > _______________________________________________ > >>> > devs mailing list > >>> > [email protected] > >>> > http://lists.xwiki.org/mailman/listinfo/devs > >>> > > >>> _______________________________________________ > >>> devs mailing list > >>> [email protected] > >>> http://lists.xwiki.org/mailman/listinfo/devs > >>> > >> > >> > >> > >> -- > >> Best Regards, > >> Arun Reddy > >> _______________________________________________ > >> devs mailing list > >> [email protected] > >> http://lists.xwiki.org/mailman/listinfo/devs > >> > > > > > > > > -- > > Thomas Mortagne > > > > > > -- > Thomas Mortagne > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
