Thx Ed and Justin,
To have ODWEK replaced by JAVA API and keep the same functionality , what will be the estimated effort on doing this?
My customer is using the ODWEK interface intensively. Does the JAVA API give the same experience? Is someone having a screenshot or something like that?
One more question on something which is confusing me.
I see that the JAVA API is the replacement for ODWEK. But I also read that IBM Content Navigator is the way to go.
So both seem replacements for ODWEK. Do you have an opinion on this?
Thx.
Kind regards
Michel.
Just a word...
ODWEK is a library of many components:
- Old and deprecated CGI (arswww.cgi
- Old and depracted Servlet
- Java API
- Browser Plugins
- Misc other things, mainly docs and samples
That said the Java API is an API and will never 100% replace the CGI part without efforts.
I've done it in the past, because it was cheaper for customer to replace the CGI part with a custom made servlet, than to switch to ICN. I needed to replace the arswww.cgi with EXACTLY the same output of arswww.cgi, to not break the existing software that was parsing the existing html output... really quite a work to do...
It took us a 1 or 2 month (we were 2 doing the work). And we could do something like 70-80% of all the functionality of ARSWWW.CGI.
BUT it was a nightmare to handle the browser part. IE is not retrieving files in the same way than Chrome or Firefox... to handle that part it took us a lot of time.
At first we did ONLY the part the customers needed, and didn't implement the whole spectrum of arswww.cgi options. And after that parts were working as the customer expected, then we added progressibely the rest.
As Justin said, it would be much easier to use ICN instead, since a lot of struggle with browser, etc... are done natively with ICN!