Home
Content Management (Extended ECM)
API, SDK, REST and Web Services
LiveLink V10 release date and the possibility to call external applications
Application_Services_FUJITSU_(fuji_ware03_-_(delet
Hi,I have been looking for the following information, but have a hard time finding it.Is there a release date for LiveLink V10, can I find some more information about this product and will it be fully Java enabled?Can we call external applications from the new LiveLink version and thus still use the LiveLink interface, but embed some external logic?ThanksBarry
Find more posts tagged with
Comments
eLink User
Message from David Slimmon via eLinkGood morning Barry,Maybe I can fill in a couple blanks here based on what is known as of July12, 2001 (today).For the moment, the Livelink version number for the product that will bereleased in the fall is still technically Livelink 9.1. This may change.But for the time being, we refer to the builds for the fall as "Livelink9.1". The fall release is not fully Java-enabled. A subsequent majorrelease of Livelink is expected to be the Java-enabled build that you arereferring to. The actual release number for that version is not yet knownof course and will depend on what we name the fall release.So it is a little difficult to refer to Livelink 10 right now, at least inan official capacity, since the version number for the late October/November(LinkUp) release has not been announced.Technical details about the functionality available in the fall release willof course become available as we move into a testing mode, with a betaperiod etc. And naturally, much more information and training about ways toextend Livelink will be made available directly at the LinkUp conferenceitself.Regards,Dave Slimmon-----Original Message-----Hi,I have been looking for the following information, but have a hard timefinding it.Is there a release date for LiveLink V10, can I find some more informationabout this product and will it be fully Java enabled?Can we call external applications from the new LiveLink version and thusstill use the LiveLink interface, but embed some external logic?ThanksBarry
Application_Services_FUJITSU_(fuji_ware03_-_(delet
Hello Dave,Thanks for the answer. I found a document at the following location:
https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2098690&objAction=browsewhich
is called "Why not all java" that is pretty negative about java in general. Can you elaborate a bit more on Opentext's point of view considering Java?Best regards,Barry Nauta
eLink User
Message from magnus <<A HREF="mailto:magnus@ids.se">magnus@ids.se> via eLink
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink
Comment from a non OT person: the story you reference is mostly critical to Java run on
the client (read Browser).
What is happening now is that part of the server code goes from Oscript to Java....
The problem with having things running on the client you maybe have experienced with Livelink
Explorer (Active X) and Livelink Desktop .....
Regards
Magnus@ids.se
eLink User
Message from David Slimmon via eLinkHi again Barry,It's a little difficult to say that Open Text has a single "opinion" onJava, as this can mean different things to different people. Java withinthe browser is one thing, and Magnus alluded to this in the discussion.Certainly Java in browser windows has had both some performance andstability concerns over the years and from platform to platform. So, thedocument you referenced on the KC does make some good points, but I thinkmost would agree that there have been some improvements out there in thelast year or so with regard to how newer browsers handle Java and howperformance has improved with network bandwidth, high-speed etc. It isstill by no means perfect. But I think we'd all agree that Java within thebrowser window itself is probably more stable and quicker than it's everbeen - even if it still leaves a bit to be desired sometimes. But that'sjust Java in the browser window...Coding in Java to extend and enhance Livelink is kind of a different issue.Open Text has had to look at how can we better roll-out future versions ofLivelink that are accessible for developers who do not wish to code inOScript. At one time, it seemed like the promise of Java would address someof the concerns that our clients had about the Open Text Scripting languageitself. The complaints, which are certainly not a secret to anyone who'sbeen reading this thread for a while, had to do with the fact that in orderto build custom code to extend and enhance Livelink functionality, you hadto use the Livelink SDK and live your life in OSpaces, etc. Many of ourclients in the development community want to write Livelink-ready code inJava, and other languages incidentally.We are still very interested in getting to a place with Livelink wheredevelopers can work on Livelink projects in a programming language thatsuits them and that meets their needs. Java holds the most promise for thisit seems. But we must also accept that we have a lot of tremendous clients(and employees of course) who have been working in OScript for many, manyyears. Many clients who have been with Open Text from really early dayshave a tremendous extant investment in tailor-made OScript code that theyeither built themselves or had our PS organization build for them.The transition from the OScript world to "something else" is going to be anincredible shift to say the least. For people new to Livelink, it mightpass by unnoticed. But if you've lived with OScript for a long time, itwill be a big adjustment - but one full of promise.I don't know if I've made things more confusing here or whether it makesmore sense to you. Please don't hesitate to write back to the group or towrite to me directly if you'd like to talk more on this.Kind regards,David___________________________________________O P E N T E X T C O R P O R A T I O NDavid Slimmon, M.L.I.S.Supervisor - Customer SupportOttawa, Canada
https://knowledge.opentext.comdslimmon@opentext.comJoin
us in Las Vegas for LiveLinkUp 2001!Open Text User ConferenceBellagio, Las Vegas, NevadaNovember 5-9, 2001www.opentext.com/livelinkup/-----Original Message-----Hello Dave,Thanks for the answer. I found a document at the following location:
https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2098690&objAction=browseWhich
is called "Why not all java" that is pretty negative about java ingeneral. Can you elaborate a bit more on Opentext's point of viewconsidering Java?Best regards,Barry Nauta