I was wondering why we need a web interface for this. Maybe I'm wrong, but I think you normally run this export just once, the syntax is easy (two simple parameters), and it has to be executed by the JSPWiki administrator. Also you should not run an export while you have update activity on the wiki pages, makes sense to stop JSPWiki and run the exporter as a batch utility.
Right ? Harry 2009/1/26 Janne Jalkanen <[email protected]> > > The Exporter class is fairly straightforward, but be aware of a caveat - > you can't pipe the output to a JSP because our JSPFilter creates an > in-memory copy of the content. For 700 MB of repository, this would be > deadly ;-). You will need to develop a servlet (or figure out a way to > bypass the JSPFilter). > > /Janne > > > On Jan 26, 2009, at 11:39 , Olaf K. wrote: > > Thanks for you fast reponse. >> After I renamed the apache-package everthings works. >> >> Next weekend I will look at the Exporter-Class and make a Export.jsp >> proposal. >> >> Regards >> Olaf >> >> -------- Original-Nachricht -------- >> >>> Datum: Mon, 26 Jan 2009 09:59:44 +0200 >>> Von: Janne Jalkanen <[email protected]> >>> An: [email protected] >>> Betreff: Re: Question about developing JSPWiki V.3 >>> >> >> >>> A cool way to help would be to create an UI for the exporter! The >>> user experience could be something like "go to admin/Export.jsp >>> (admins only), click on Export, and the browser automatically starts >>> a download of the XML file (preferably gzipped, as it might be fairly >>> big)." >>> >>> Also, the export/import format requires a bit more thinking, since it >>> does not yet export version histories. I'm still debating with >>> myself whether the JCR versioning should be used or not (since I am >>> not sure whether you can import a set of Version nodes.) Any ideas >>> around that would be most welcome. >>> >>> /Janne >>> >>> On Jan 26, 2009, at 08:45 , Harry Metske wrote: >>> >>> Olaf, >>>> >>>> first, much appreciated ! >>>> >>>> There is an Exporter class in the 2.8 branch that exports your >>>> wikipages to >>>> an JSR-170 xml file. >>>> It should be possible to import that, but I have not played with it >>>> yet. >>>> >>>> The NoClassDefFoundError is a result of a bug in the Jasper JSP >>>> compiler, it >>>> is all described in https://issues.apache.org/jira/browse/JSPWIKI-465. >>>> >>>> regards, >>>> Harry >>>> >>>> 2009/1/25 Olaf K. <[email protected]> >>>> >>>> Hi Developers! >>>>> I would like to support you developing the new JSPWiki Version 3. >>>>> So I checked out the trunk, build the application and after I >>>>> copied a >>>>> default 'priha.properties' to the classes-folder >>>>> the Tomcat start without errors. >>>>> >>>>> But in the browser I received an empty main-page, a left-menu and the >>>>> searchbox. >>>>> Everthing looks fine. >>>>> How can I import my old Pages (VersionFileProvider) to the new JCR? >>>>> Should I create a migration-task in Jira and write some code to do >>>>> this? >>>>> Or is there a spec for this task (e.g. GUI definition, Button in >>>>> Install.jsp, ...) >>>>> >>>>> And why show the tomcat console a >>>>> java.lang.NoClassDefFoundError: org/apache/jspwiki/api/WikiPage >>>>> ... >>>>> com.ecyrd.jspwiki.tags.IncludeTag.doEndTag(IncludeTag.java:84) >>>>> ... >>>>> when editing/viewing a page. >>>>> It looks like the WikiActionBeanContext is not correct filled. >>>>> getPage >>>>> delivers null. hmmm..... >>>>> >>>>> Regards >>>>> Olaf >>>>> -- >>>>> NUR NOCH BIS 31.01.! GMX FreeDSL - Telefonanschluss + DSL >>>>> für nur 16,37 EURO/mtl.!* http://dsl.gmx.de/? >>>>> ac=OM.AD.PD003K11308T4569a >>>>> >>>>> >> -- >> NUR NOCH BIS 31.01.! GMX FreeDSL - Telefonanschluss + DSL >> für nur 16,37 EURO/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a >> > >
