nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

cssdk API usage for callouts

nagendra

Is it advisable/possible to use cssdk API in Templating callouts? If so how to do this (any example)? Is that only cgi callouts are supported not java based callouts?

env: Teamsite 6.7.1/solaris

Find more posts tagged with

Comments

Sailesh

Is it advisable/possible to use cssdk API in Templating callouts? If so how to do this (any example)? Is that only cgi callouts are supported not java based callouts?

env: Teamsite 6.7.1/solaris

What is your requirement and what exactly you want to use?

nagendra

CSSDK API has serveral methods which are required even in general callout scripts (ex: set/getProperties of CSUser, set/getExtendedAttributes of CSFile etc). I do not see any standard API(otherthan DCRNode etc) with in Perl for Teamsite functionalities other than CLTs.

Sailesh

CSSDK API has serveral methods which are required even in general callout scripts (ex: set/getProperties of CSUser, set/getExtendedAttributes of CSFile etc). I do not see any standard API(otherthan DCRNode etc) with in Perl for Teamsite functionalities other than CLTs.

Why not use CLT's provide to achieve the same results, you can call the CLT's in your CGI file.

iw_store

Why not use CLT's provide to achieve the same results, you can call the CLT's in your CGI file.

I feel poster is talking about :
http://support.interwoven.com/library/manuals/cs/html/cs.210_jar/index.html, not the one you mentioned.

nagendra

We can use CLTs to implement, but cssdk methods provides objects (ex: CSFile.getFileRevision(java.lang.String revisionString) returns CSFile) and to implement Object oriented coding we need to place wrappers on CLTs.

It would be great if we can able to use already object oriented cssdk API instead of writing wrappers on CLTs.

nagendra

Can someone answer my original post?

jkm

Nagendra,

I believe you can use java based callouts in templates for example to call a jsp based cross branch browser on click of a button...Is this something similar you are looking at or something different ??

Thanks
-Rocky

nagendra

we are currently inprocess of implementing a new project and I was asked to create common API which can be used across different scripts used in callouts/external tasks. During this phase I felt that I am recreating most of CSSDK API methods in perl.

jkm

I am not completely sure about your common API and what is this API doing?

You mentioned earlier you want to use the CSSDK instead of cgi callout. Does this hold good still?

This will be good if you provide the context of your actual requirements over here to get better understanding.

nagendra

Lets take this following simple requirement:
we need to get all extended attributes on a dcr and display it in a calllout popup.

To acheive above I can think of following ways:
I
a) provide a callout button in DCT form
b) onCallout call a cgi script which uses 'iw-home/bin/iwexattr' CLT
c) call a callback method to display this info.

II
a) provide a callout button in DCT form
b) onCallout call a JAVA servlet / JSP which uses CSSDK API
c) call a callback method to display this info.

What I would like to know is that whether 2nd approach is a advisable one to implement?

Why 2nd approach:
CSSDK API is already a wrapper on top of CLTs, object oriented and java based.

jkm

ohh dark clouds are gone now Nagendra and i can see what you are looking at

I dont see anything wrong if you are using CSSDK but I personally would like to use cgi callouts because it is quick to implement, no need to recompile the web app etc to see the results...and this depends upon your confort level and your skill set

Technically nothing is stopping you to use any of them

Bjorn

What I would like to know is that whether 2nd approach is a advisable one to implement?

Advisable schmisable. I don't know if it is advisable, but we've been doing it for almost 2 years and it's great. If you want to do something like iterate through 1000 files and set TeamSite EAs on all of them, doing it by calling a servlet that uses the CSSDK is noticeably faster and easier on your resources than using Perl/CGI and clunking through the overhead of qx's, backticks or systems calls to the CLTs. The CLTs are great for using on the command line or for quick and dirty scripts, but for production use, I'm not sure the CSSDK can be beat.

Bjorn

preview.pdf