Questions about 9.5

ATHANASSIOS_FAMELIARIS

Hello all!We are trying to get OpenText to send us bulder 9.5 for more than a month now with no luck. And I can't get their support to answer my questions. So if anyone can answer any of the following questions, I would greatley appreciate it! Thanks in advance!1) Can one create entire modules writing entirely in Java, using no oScript? 2) If so, how are these modules packaged? Using the traditional .oll file, or some Java type format (like JAR) 3) Can weblingo and jsp tags be combined in the same page? If so, how? 4) How can we reuse functionality from oScript using Java (see Orphan today)? 5) Can we use Java inside an existing oScript module? 6) How can one edit the code in Java modules? Does it have to be done through the builder or can we use any java development environment? 7) If this can be done outside the builder, (a) how do changes in those modules affect Livelink without restarting? (b) Is it still a requirement that the developer has to sit on the same machine as the Livelink server? 8) If Java modules are not packaged in .oll files, how are they deployed onto Livelink? 9) What Java libraries does Livelink 9.5 provide to give access to Livelink features though Java code? For example, can one use the DAPI though Java? 10) Using the libraries from question 9 would someone have to write code similar to LAPI, or are they more similar to oScript? (i.e. are these libraries just a version of LAPI, or are they made to make Java development similar to oScript developement?) 11) What kind of debugging is there for modules written in Java? 12) Will internationalization be handled in the same way as oScript modules? (i.e. using property files) 13) Is there any documentation that we can download before we get LLBuilder 9.5?

DCX_Technical_(dcx_tech_-_(deleted))

Dear Stavroula:I'll try to answer your questions as well as I possibly can. I'm really new to the Java environment myself so I may even have the wrong answers, but here goes:1) Can one create entire modules writing entirely in Java, using no oScript?You still need to "bind" your module into the Livelink environment by means of oscript. It seems to need that to know the Java module exists. I haven't done this myself yet, but it sounds easy enough. I'm also not sure whether one needs to create the object actions and functions in oscript - it seems that's how it was done for the My Home module example. I suspect that it should be possible to do everything (except for the binding) in Java.2) If so, how are these modules packaged? Using the traditional .oll file, or some Java type format (like JAR)WAR format and .oll3) Can weblingo and jsp tags be combined in the same page? If so, how?I don't think so.4) How can we reuse functionality from oScript using Java (see Orphan today)?Not as far as I know.5) Can we use Java inside an existing oScript module?It looks like you might be able to mix-and-match wherever a clean break exists. E.g. the object action is registered in oscript but it references a URL that is executed in Java.6) How can one edit the code in Java modules? Does it have to be done through the builder or can we use any java development environment?Nope. Grab Eclipse 3.x (www.eclipse.org) stable and install. You'll also need the RMI plugin from http://www.genady.net/rmi/.You then set up Builder, Tomcat (if that's what you're using) and eclipse to talk to each other so that you can run in live debug mode. It's a pretty complicated and tricky setup if you ask me, but the end-result seems quite promising. The systems all talk to each other via RMI. Once the code is ready for deployment, it needs to go through an extra packaging step so that it can be installed on a non-development path on e.g. a production server.Personally, I've also set up Subversion with subclipse and JavaSVN so that I can check in/out my code under revision control. So many benefits when working in a more generally used development environment !7) If this can be done outside the builder, (a) how do changes in those modules affect Livelink without restarting? (b) Is it still a requirement that the developer has to sit on the same machine as the Livelink server?a) Don't know yet for sure - it seems that you should be able to recompile & run in Eclipse without requiring a restart anywhereb) I think in theory one could probably get the systems to talk across machines (because the debug bindings are done via RMI), but it wouldn't be my preference.I'd rather see developers working on their own machines and publishing against a revision control system.Then testing can be performed separately on some test instance using interim releases of the code.8) If Java modules are not packaged in .oll files, how are they deployed onto Livelink?WAR files. (You may still need an oscript container to refer to your Java module, but that doesn't seem complicated and probably only needs to be set up at the beginning of each custom module project).9) What Java libraries does Livelink 9.5 provide to give access to Livelink features though Java code? For example, can one use the DAPI though Java?I haven't gone through the API in detail (provided in JavaDoc format), but it looks like it is pretty complete.10) Using the libraries from question 9 would someone have to write code similar to LAPI, or are they more similar to oScript? (i.e. are these libraries just a version of LAPI, or are they made to make Java development similar to oScript developement?)It looks like this was written independent of LAPI. Remember, the Java environment is actually an alternative to using llisapi.dll or livelink.exe, and I'd say they've really ported a large portion of the functionality already to Java!11) What kind of debugging is there for modules written in Java?I'm still not too familiar with debugging in Eclipse but it should be pretty good.12) Will internationalization be handled in the same way as oScript modules? (i.e. using property files)Looks like it. This seems to be one of the reasons for the move to property files in the first place.13) Is there any documentation that we can download before we get LLBuilder 9.5?Don't think so, but I wouldn't see any harm in Open Text publishing it here. Even if one has to ask permission to access it.Let's see how much of a fool I've made of myself ;-)Regards,Rolf.