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; } } }

java callout wrapper

heidiiwov

Has anybody got a cgi wrapper to wrap around Java callouts so that they can be used in the future which is here today (FormAPI and 6.X). My client has numerous java callouts and telling them to just re-write everything in CGI is not an answer. Any suggestions any answers? Anybody else dealing with this problem?

Find more posts tagged with

Comments

Migrateduser

> just re-write everything...is not an answer

Get used to it. Backwards compatability has never been a concern of Interwoven's - they can sell more consulting if everything changes with every release.

Migrateduser

I'm afraid there is no easy answer to this. There are a couple of issues that should be pointed out:

1. Java callouts, like FormAPI scripts, are executed on the client side. CGI callouts, on the other hand, are run on the server side.
2. Java callouts are implemented as Java classes. FormAPI scripts utilize the JavaScript and the JavaScript engine of the client browser to run. Although it might be conceptually possible to bridge the two technologies (to my knowledge, it doesn't exist?), they are for the most part incompatible.

Having said this, there are two options I know of:
1. Rewrite the callout as a formapi script and have the callout button listen to the "onCallout" event.
2. Rewrite the callout as a CGI that (eventually) emits JavaScript to alter the form if necessary.

Out of curiosity, how many callouts are we talking about?

--Daniel

Migrateduser

In case people are not familiar with the Java callout feature, this is part of the Java templating UI, which IWOV announced an EOL (end of life) plan for over a year ago.

All customers were notified of the plan, and at that time were told that the Java templating UI would not be supported in TS6.

Customer who are interested in moving to new interfaces were encouraged to contact Interwoven Support for assistance. This is still the case.

Regards,

lissa

heidiiwov

Hi Daniel,

Thre are an abundant amount of callouts in the codebase. More than I have bothered to count.

heidiiwov

we contacted them and were tod, just go and re-write in CGI. Not a nice suggestion if you want to keep your customer.

Adam Stoller

You have a choice - keep using the antiquated version of the product you've been using, or finally pay heed to the warnings which were made for probably over a year now that the interface you were using is being discontinued and re-write your customizations to work with the other interface.

I admit, it's not nice when a feature is discontinued, but to be fair - Interwoven *did* provide *very ample* warning about this - and the fact that nobody in your organization seemed to pay attention to it is not really Interwoven's fault.

You *might* be able to write a CGI wrapper for the Java callout (not really sure, I don't do much Java coding) - but otherwise you're left with the two choices I mentioned above: (1) stick with Java callouts using an old, unsupported version of the product; (2) accept the fact that functionality was removed and re-code the callouts as CGIs rather than Java programs so that you can upgrade to the latest version of the product.

Were the callouts doing anything so exceptional that make it incredibly difficult to convert the code? CGI code can be tricky at times, but usually it's far less than "rocket-science".

(PS: You might get more assistance in the conversion process if you post this in the Templating forum, rather than this forum)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com