I tried to install WebRaptor (public version) but unfortunately it didn't work (I saw the same error message in the dev-list but no answer to fix it...) and I got no error message into tomcat or jahia logs...
Long time, no test... but I know that Codeva did some slightly changes recently. However I still do not have the .diffs. Perhaps try to contact them directly to get more info.
Anyway, I don't have time, so I'm trying to figure out if it may help me ? May I use that portlet in order to import static html pages into Jahia ? If yes, does WebRaptor import content and images into Jahia or does it only make some external links to the remote web site ? Of course, I guess that I will have to rebuild all the links at least...
The WebRaptor is a web clipping technology. It does not "import" content. It just dynamically clips a external fragment of HTML displayed on another web site into the Jahia portal. Something similar to a web service if you want but directly on http without going through a SOAP API. More similar to an iFrame. So it is fine in order to integrate the CNN news within your portal or to integrate another webapp you developed with another language and you do not want to rebuild it in Java, but perhaps not to export/import content.
Cheers, /SC
Thank you, Olivier.
> First of all let's say that we never implemented such a > solution on our > side. This should just be a possible way of doing it. > However, given the > many criteria in order to apply it (cf. below), most of our customers > finally preferred manually migrating their content (and by > the way, taking > the time to delete or clean outdated content, modify or restructe the > navigation, enter new metadata or categories, etc...). So > they kept their > old HTML pages on a front-end Apache server while moving > their migrated > content section by section once converted to Jahia. Meanwhile > they made > some static cross-references to the ols static content within > their new > sites... This is certainly the most easy way to migrate lot > of content. > > Then if we come back to the suggested solution, you will have > to make a > script which: > 1) crawl and capture your existing sitemap (which page is > linked to which one) > 2) remove the existing navigation, header, footer,... This > may already be a > tough step especially if you have not used generic templates > to make your > site... Then what is a menu, what is just a list of > cross-links to other > pages, how to automatically remove it, etc... > 3) Parse and clean the result with some tools such as Tidy > 4) Upload all the binary files and images on the Jahia webDAV > server and > rewrite all the url to point to the Jahia DAV server > 5) Make a script in Jahia to a) create a new page according > to the sitemap > defined in 1 and b) import the cleaned HTML fragment (cf. 3) > in a Jahia big > text (e.g. the central column). > > But all this process is only possible if all your HTML pages > are quite > generic enough in order to be able to remove all what needs > to be removed > and to easily find the existng navigation path within. If you > have lots of > different "templates" with links pointing to other pages a > bit everywhere > directly hardcoded in the text and so on... this will become > quite a mess > to automate it. > > Finally this will never import 100% of your content. There > will be a lot of > exceptions to treat manually. So you will have to really > evaluate the cost > of developing and testing all this automated migration + > reviewing the > exceptions + then finally remigrating your content a bit > later to some > other more structured templates versus keeping it in HTML for > a while and > directly manually migrating section by section of your sites (or to > outsource such a task in some more affordable off-shore countries) by > beginning by the most urgent ones... > > Good chance! > St�phane
