The javascript runtime errors are being encountered

RESOLVED INCOMPLETE

Status

Rhino
Compiler
RESOLVED INCOMPLETE
10 years ago
10 years ago

People

(Reporter: ravi, Unassigned)

Tracking

Details

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; GIS IE 6.0 Build 20060616; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727)
Build Identifier: Rhino V.1.5  R3

hi whenever i am using the following script ,
// get the job info parsed
var temp = new String(APPL._user1);
var temp3 = temp.split('^');
APPL.job = temp3[0];
APPL.run_date = temp3[1];
var cycle = temp3[2];
APPL.orgCycle = cycle;


I get the following errors

org.mozilla.javascript.EvaluatorException: Property 0 not found.
	        at org.mozilla.javascript.DefaultErrorReporter.runtimeError(Unknown
	Source)
	        at org.mozilla.javascript.Context.reportRuntimeError(Unknown Source)
	        at org.mozilla.javascript.Context.reportRuntimeError(Unknown Source)
	        at org.mozilla.javascript.Context.reportRuntimeError1(Unknown Source)


Reproducible: Always

Steps to Reproduce:
1.define a script with split()fucntion in it
2.
3.

Comment 1

10 years ago
Not security-sensitive.
Group: security
(Reporter)

Comment 2

10 years ago
hi,
I wanted to know whether this problem is a known bug,if so can you please let me know the way out.(apart from upgrading). or else only upgrading is the only way...
(Reporter)

Comment 3

10 years ago
But what i am looking for is whether this bug is still pertaining in Rhino 1.5v
R3 or not.
I cannot upgrade,but wanted to confirm whether this type of Evaluator
exceptions are present with this release or not.
(Reporter)

Comment 4

10 years ago
hi any updates on this issue?
Please let me know the details since it is effecting my performance a bit.

Comment 5

10 years ago
There is not enough information for me to reproduce the problem. Split appears working fine for me:

js> var x = "ababa".split("b");
js> x[0]
a
js> x = "ababa".split("q");
ababa
js> x[0]
ababa
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.