<java-callout> and <cgi-callout>

When creating a <callout> element in my datacapture.cfg I have a class file all ready to go. Thing is, I let my users decide which templating interface to use. The <java-callout> element ONLY works in the java templating client and the <cgi-callout> element ONLY works in the browser based blient. Which is complete ****. It basically means that I have to
create two of every callout script - one in java and the other in perl, to satisfy all users.

But if I do that, it still won't work because the actual element of <java-callout> must be <cgi-callout> or it won't show up at all. Is there any way around this besides restricting my users to one interface or the other?

Thanks.

Whoah TeamSite!
<Charlie/>

Find more posts tagged with

Comments

iwovGraduate

What if you have both the tags -- <java-callout> <cgi-callout> and in your datacapture.cfg ? I believe one of the tags would be ignored depending on the UI used. [I have not tested this]

sbzoom

I think this is working. I still have to test it in the java editor but it seems to be doing the trick. Now I just have to figure out how to write a cgi wrapper script that will run all the java files... Or write everything twice. Smiley Happy

Whoah TeamSite!
<Charlie/>