JS Error, Permission denied.

Because it's a Javascript error, it's complaining about your Javascript code, not Perl. What are you attempting to do in Javascript (particularly on line 5)?

i just track down the code
the error come from getScriptFrame();
any idea on this ?


 // Get handle to the FormAPI/userscript frame.
 api = parent.getScriptFrame();
 api.isExist = $isExist;

I think the error is actually occuring on the next line:

api.isExist = $isExist;

as I recall, isExist is a function and if this is the case, you can't assign a value to it. Rather, you could do the following:

alert(api.isExist)

instead of your second line of code and you would presumably see "true" in an alert window.

Try commenting out the line in question and see if you get the same error.

I try to comment
//api.isExist = $isExist;
and still got the error.

The error is from
api = parent.getScriptFrame();

and I try to do
alert(api); which is error too.

if i try to do
alert(parent);
which i can return
[object]

That seems strange -- what happens when you comment the troublesome line, i.e. "api = parent.getScriptFrame();" and instead put:

alert(parent.location);

, since we know that parent is a valid object. What I'm suggesting is that perhaps the callout window isn't referencing the parent properly, although "api = parent.getScriptFrame();" is the standard way to define the api window from a callout.

I try to comment
//api.isExist = $isExist;
and still got the error.

The error is from
api = parent.getScriptFrame();

and I try to do
alert(api); which is error too.

if i try to do
alert(parent);
which i can return
[object]

What is the location of your JS code ?

If it is DCT - open a support case with IW, it should work as it is.

However, the fragment "api.isExist = $isExist;" (commented out or not) hints that your code
is generated by some Perl CGI. If so, then a) your syntax should probably be api = opener.parent.getScriptFrame(); and
b) you have a bug somewhere else that left $isExist unevaluated

If so, then a) your syntax should probably be api = opener.parent.getScriptFrame();

I respectfully disagree. This is the same way I always start my callouts when I need to communicate back to the DCT. However, I agree that $isExist should be investigated and it might be better to have single quotes around this value but since it still bugs out when this line is commented, we can rule that out as the immediate problem.

...we can rule that out as the immediate problem.

Absolutely - I never said otherwise, it's commented out after all.

However, it would certainly help to know code location.
If it is a cgi the first question to ask is "Is it in the same domain as DCR ?"
If the answer is No, then almost any attempt of opener access will give a security violation error.
If the answer is Yes, I would try to go via opener and see if anything changes...

Very good point -- and he should be using the wrapper to call this, also. I've had very similar problems when I wasn't referencing a callout with the wrapper. I wonder if this is his problem.

I have external js file locaates in
$iw-home\httpd\iw\javascript

in my DCT


function init() {
IWEventRegistry.addItemHandler("/Name", "onItemChange", chkFile);
}

in external js function


function chkFile( item ){
 setValidName( item );
 var parameters = new Object();
 parameters.vpath = parent.datacapture.getDCRVPath();
IWDatacapture.callServer("http://jupiter.humber.org/iw-bin/isFileExist.ipl", parameters);
}

In Windows this will always give you security violation.

So...
When you open up your Datacapture Form, is it Domain ".humber.org" ?
If no, you would have to redesign, there is no way you can modify opener fields from the location with different Domain.

If yes, your life is easier. Much...
create cgi counterpart for isFileExist by copying cgi wrapper with "isFileExist.cgi" name and call it "...iw-bin/isFileExist.cgi"

Dave, it seems you were right on...

I *think* his DCT / TeamSite box would need to be jupiter.humber.org, specifically -- not just *.humber.org. This is a guess but I know your non-use of the wrapper is a problem, maybe not the only one though.

I *think* his DCT / TeamSite box would need to be jupiter.humber.org, specifically -- not just *.humber.org. This is a guess but I know your non-use of the wrapper is a problem, maybe not the only one though.

If memory serves, Microsoft cross-domain Security model has been tightened around Summer 2002.

It was my understanding back then that the domain (leading dot including) is sufficient to allow interpage
modifications, eg "www.yahoo.com" is allowed to modify "finance.yahoo.com". In the syntax above, "jupiter" is the first
resource and not a part of Domain.

I might be wrong though, never really tried it with that granularity.

DCT, external JS, and server callout script - isFileExist.ipl
are sitting in the same machine which is jupiter.humber.org

isFileExist.ipl is cgi script,
how about cgi wrapper?
how should I do create cgi wrapper, any reference can point to?

Thanks.

The wrapper is already there for you, in httpd/iw-bin. I recommend taking out the fully qualified URL in your callout tag but reference the cgi wrapper in the following way:

[size=2]url="/iw-bin/iw_cgi_wrapper.cgi/dct_calendar.ipl"

I'm pulling this one because I actually used it recently in another post here and it was still on my clipboard. Anyway, my script is called dct_calendar.ipl so you would replace that with the name of your script. FYI, you can also send additional arguments to your callout by using a path suffix after your script name. For instance, my calendar script will also allow the user to select the time of day but this is not always wanted. If I say [size=2]/iw-bin/iw_cgi_wrapper.cgi/dct_calendar.ipl/1, for instance, I'm instructing the script to display the hour and minute drop downs. It's pretty handy -- you can have query string type stuff after that last "/" and you could also have multiple "/"'s, but that's how you would include the wrapper.[/size][/size]

Dave, I would appreciate your help Smiley Happy

It is working fine after I took out the server name.

Thanks,

Wait, you mean that you're not using the wrapper and it still works??

DCT, external JS, and server callout script - isFileExist.ipl
are sitting in the same machine which is jupiter.humber.org

isFileExist.ipl is cgi script,
how about cgi wrapper?
how should I do create cgi wrapper, any reference can point to?

Thanks.

Alternatively you can copy existing "show_env.cgi" as isFileExist.cgi (just rename a copy)
and call url="/iw-bin/isFileExist.cgi "

Working Coding:


function chkFile( item ){
 setValidName( item );
 var parameters = new Object();
 parameters.vpath = parent.datacapture.getDCRVPath();
 IWDatacapture.callServer("/iw-bin/isFileExist.ipl", parameters);
}

I removed http://jupiter.humber.org
IWDatacapture.callServer("http://jupiter.humber.org/iw-bin/isFileExist.ipl", parameters);

Well, I'm happy that it's working for you now but honestly, I'm a little surprised that it is. If you have any more problems with this, I would consider using the wrapper. Actually, I would seriously consider using the wrapper, anyway.

IWDatacapture.callServer("/iw-bin/iw_cgi_wrapper.cgi/isFileExist.ipl", parameters);

I changed into calling wrapper, its working fine too.

am I still using "IWDatacapture.callServer" to call wrapper?

Thanks, you just quelled my obsessive-compulsive tendencies for now :-) yes, you still use callServer when using the wrapper.

TeamsiteUser

I too am facing the similar problem(but i am not using callserver from user script instead i am using window.open to open up my JSP window which is not in same doamin and my javascript code is giving me security viaolation issue when i try to use a opener.((my formapi method)) to write back my data to DCT
What should be done in this case?