Prototype method, local variable issue

when i write prototype method and declare a variable inside the prototype method. this is fine but as sonn as i declare another variable with the same name i get an error. conflict with "variable" namespace internal.
i've contact other users and they claim they don't get this same issue. so i ask you guys for help. i'm using flash CS3, i have flash player 10 installed but cs3 only supports up to 9 so i have 9 selected. and i'm using AS3. this is some code you can use to test to see if you get this issue:
var testArray:Array = [];
Array.prototype.testOne = function(){
var intTest:int = 1;
this.push(intTest);
Array.prototype.testTwo = function(){
var intTest:int = 2;
this.push(intTest);
testOne();
testTwo();
trace(testArray);

it works? how annoying, all i get is an error saying conflict with intTest namespace internal.
i'm aware im declaring the same variable twice. if it were using a normal function and not a prototype one, then it works fine. but as soon as i use a prototype function bang i get this error.
how do i get that error stack thing you asked for?

Similar Messages

Approval task SP09: Evaluation of approvalid failed with Exception: while trying to invoke the method java.lang.String.length() of an object loaded from local variable 'aValue'

Hi everyone,
I just installed SP09 and i was testing the solution. And I found a problem with the approvals tasks.
I configured a simple ROLE approval task for validate add event. And when the runtime executes the task, the dispatcher log shows a error:
ERROR: Evaluation of approvalid failed with Exception: while trying to invoke the method java.lang.String.length() of an object loaded from local variable 'aValue'
And the notifications configured on approval task does not start either.
The approval goes to the ToDO tab of the approver, but when approved, also the ROLE stays in "Pending" State.
I downgraded the Runtime components to SP08 to test, and the approvals tasks works correctly.
Has anyone passed trough this situation in SP09?
I think there is an issue with the runtime components delivered with this initial package of SP09.
Suggestions?

Hi Kelvin,2016081
The issue is caused by a program error in the Dispatcher component. A fix will be provided in Identity Management SP9 Patch 2 for the Runtime component. I expect the patch will be delivered within a week or two.
For more info about the issue and the patch please refer to SAPNote 2016081.
@Michael Penn - I might be able to assist if you provide the ticket number
Cheers,
Kristiyan
IdM Development

Reference to a local variable object returned by a method is alive?

I have an instance method getEmployee().
This method forms a local variable, Employee and returns it.
public Employee getEmployee()
Employee e = new Employee();
e.setSNo(sNo+=);
e.setMailBox();
return e;
There's another instance method in the same class that calls getEmployee() in this manner:-
Employee newEmployee = getEmployee();
newEmployee.printDetails();
I want to know whether the employee returned by getEmployee() is still alive when we are doing newEmployee.printDetails().
I am confused because in C, the lifetime of a local variable is limited only to the life time of the function. Once the function finishes, the local variable is considered garbage.
How does it work in case of Java?

No, It rarely has any use but can be used to unload things (from a cache for example). However I have never needed to do this. All I know is that finallizers can only be relied on to clear up memory. How or why you would do this is another question.
The GC runs when memory is low (not any other resource). It calls finalizers when it clears up objects. Therefore the only thing you can reliably release in a finalizer is memory. Other resources can become depleted without heap being depleated so you can't use finalizers to relialy clean up non-memory resources.
Anyway.
some more info on escape analysis
a compile time escape analysis
http://www.excelsior-usa.com/pdf/StackAlloc.pdf
This can handle some finalizers
This does not handle finalizers (marks them all as GLOBAL_ESCAPE
http://delivery.acm.org/10.1145/330000/320386/p1-choi.pdf?key1=320386&key2=0718563811&coll=Portal&dl=ACM&CFID=15151515&CFTOKEN=6184618
bit more recent and about runtime optimization (finalizers not handled)
http://ssw.jku.at/Research/Papers/Ko05/Ko05.pdf
I don't think that not handling finalizers is too much of a problem. Most objects that will benifit from stackability are small objects anyway (especially the built in wrapper types). Most objects that have custom finalizers tend to be pretty complicated.
matfud

While trying to invoke the method java.lang.String.length() of an object loaded from local variable 'payload'

Hi,
Our PI is getting data from WebSphere MQ and pushing to SAP. So our sender CC is JMS and receiver is Proxy. Our PI version is 7.31.
Our connectivity between the MQ is success but getting the following error while trying to read the payload.
Text: TxManagerFilter received an error:
[EXCEPTION]
java.lang.NullPointerException: while trying to invoke the method java.lang.String.length() of an object loaded from local variable 'payload'
       at com.sap.aii.adapter.jms.core.channel.filter.ConvertJmsMessageToBinaryFilter.filter(ConvertJmsMessageToBinaryFilter.java:73)
       at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:204)
       at com.sap.aii.adapter.jms.core.channel.filter.InboundDuplicateCheckFilter.filter(InboundDuplicateCheckFilter.java:348)
       at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:204)
I have searched SDN but couldn't fix it. Please provide your suggestion.
With Regards
Amarnath M

Hi Amarnath,
Where exactly you are getting this error?
If you are getting at JMS Sender communication channel, try to stop and start the JMS communication channel and see the status, also use XPI Inspector to get the exact error log.
for reference follow below blogs:
Michal's PI tips: ActiveMQ - JMS - topics with SAP PI 7.3
Michal's PI tips: XPI inspector - help OSS and yourself
XPI Inspector

Memory (RAM) model in Flex or ActionScript for local variables in a method

I have a method in AS3 to handle certain event generated from some Components in <mx:Repeater>. Two different Components can fire the same event
at the same time so the same method must handle the two events together. My question is if the two calls on the same event handler method will step on each other. The event handler method only uses the local variables.
In Java, the local variables of a method for the two callers are in two different memory (RAM) addresses. So they will not step on each other. Not sure about
Flex/ActionScript.

Actionscript runs in a single thread. One of the events will get fully
processed before the other.

Inner class inside a method - how does it access method's local variable?

hello All:
I've learnt that, an inner class, if defined inside a method, it can access the method's local variables, only when they are defined as "final".
Anyone can help explain the rationale behind it?
Thanks a lot!
Sway

fathomBoat wrote:
In java, everything is about pass-by-reference.
Wrong! Nothing in Java is ever pass-by-reference.
Java uses pass-by-value everywhere.
It makes sense to me if the reason of enforcing a variable to be "final" is to prevent it being messed up.No, the reason is that a copy is made and if the variable weren't final then it could change later on and the developer could be confused because his inner class didn't "see" that change.
The variable being final prevents that scenario.
However, if a copy of the variable is made inside the inner class, i dont see how possible it could affect variables outside of class?Such a copy is made, but the language designers wanted to hide that fact from the developer. By forcing all accessed variables to be declared final the developer has no way to realize that he's actually working on a copy.

Why method local inner class can use final variable rather than....

Hi all
Just a quick question.
Why method-local inner class can access final variable defined in method only?
I know the reason why it can not access instance variable in method.
Just can not figure out why??
any reply would be appreciated.
Steven

Local classes can most definitely reference instance variables. The reason they cannot reference non final local variables is because the local class instance can remain in memory after the method returns. When the method returns the local variables go out of scope, so a copy of them is needed. If the variables weren't final then the copy of the variable in the method could change, while the copy in the local class didn't, so they'd be out of synch.

Inaccessible with local variable(non-final) via method local inner class

Hi All,
Usually local variables, including automatic final variable live on the stack and objects & instanace variables live on the heap.The contracts for using the method local inner class should allow merely method final variable, not non-final stack variable.
Can anyone please clarify me ,behind the scene what is actual fact why method inner class should not access the stack(method) variable and only allow final variable?
Is anything correlated with the stack and heap aspects?
Thanks,
Stalin.G

[email protected] wrote:
...behind the scene what is actual fact why method inner class should not access the stack(method) variable and only allow final variable?...explained by dcminter and Jardium in [an older thread|http://forums.sun.com/thread.jspa?messageID=10694240#10694240|http://forums.sun.com/thread.jspa?messageID=10694240#10694240]:
...Final variables are copied into inner classes - that's why they have to be declared final; to avoid the developer making an incorrect assumption that the local variable can be modified and have the change reflected in the copy.
When a local class uses a local variable, it doesn't actually use the variable. Instead, it takes a copy of the value which is contained in the variable at the moment the class is instantiated. It's like passing the variable to a constructor of the class, except that you do not actually declare any such constructor in your code.
To avoid messy execution flows to be present in a Java method, the Java language authors thought it was better to allow a single value to be present in such a variable throughout all its life. Thus, the variable has to be declared final.
...HTH

Issue with local variable in forms personalization

Hi All,
I did the following things at last it is give me syntax error, please help me on this.
Rules section:
seq Description Level Enabled
1 Populate Number Function y
Conditions:
T.E : When new item instance
T.O : REQ_LINES.REQUISIOTN_NUMBER
Condition::REQ_LINES.BLANKET_PO_NUM_DSP IS NOT NULL AND
:REQ_LINES.SELECT_LINE='Y'
Processing mode: Not in enter query mode
Actions:
seq: Type: Desc: Langauge: Enabled
1: property: local variable :Y
Object Type: Local Varibale
Target Object: XXNUM
property : Value
Text: = TO_CHAR(${item.req_lines.blanket_po_num_dsp.value})
Rules section:
seq Description Level Enabled
1 Default Number Function y
Conditions:
T.E : When block instance
T.O : New_DOCUMENT
Condition:
Processing mode: Not in enter query mode
Actions:
seq: Type: Desc: Langauge: Enabled
1: property: use of local variable :Y
Object Type:ITEM
Target Object:NEW_DOCUMENT.DOCUMENT_NUMBER
property : Value
*Text: = SELECT TO_CHAR (${var.XXNUM.value}) from dual*
The line which i bold shows me an syntax error, please check the syntax and if it is wrong please correct it.
Thanks and Regards
Zaheer
Edited by: zaheer on Feb 10, 2010 11:25 PM
Edited by: zaheer on Feb 10, 2010 11:25 PM

Hi Zaheer,
Try using this:
Actions:
seq: Type: Desc: Langauge: Enabled
1: property: use of local variable :Y
Object Type:ITEM
Target Object:NEW_DOCUMENT.DOCUMENT_NUMBER
property : Value
Text: = ${var.XXNUM.value}
PS: You might get a message while validating, but you can ignore that.
Regards,
Sujoy

How to use local variables declared in b/t the methods in other views

Hi
i need to use the value of the local variables declared in b/w the views in one other view,as i have manipulated the value based on some condition & want to use it in 1 more view for my req.,but that variable is not global one just for once i need to use it,and i can't again write the whole for its conditions,as its there in initialization view,which if coded again,can hit the functionality there,so is it possible to use the value of such local variables thereafter or not,if yes pls let me know,or i need to declare the global variable for this.

hi,
1.Declare an Attribute in Component controller.
2. Pass the value to this Attribute in View V1.
using :
wd_comp_controller->Att = 'Saurav'.
3. Now in view2 , you can access this Attribute using:
data lv type string.
lv = wd_comp_controller->Att .
Here Att is my attribute of type string declared in component controller.

Debugger issue - local variable table missing

I have compiled my sources using IBM's jikes compiler with the -g option (for debugging purposes). I am using Sun's JRE 1.2.2. and JPDA 1.0.
When I run the debugger using JPDA and try to set a watch for local variables I get an error saying that the local variable table is missing. And it asks me to compile the source with the debug option (which I've already done but with the jikes compiler)
Any ideas what is going wrong here?
Thanks,
Rahul.

How about using javac?

How can I put the contents of an array into a set of write local variable clusters?

I have a set of controls that a user fills in. The controls are clustered by rows, then combined into a 1D array, then written to a file. When I read the file, I want to feed the array back into the clusters with write local variables. Is there a simple way to handle the numerous local variable clusters so I can stuff the array back into them?
Is there a better way to handle the whole issue of storing and recovering the information?
The rows are steps in a procedure, and each row (cluster) contains numerical as well as string controls.

There are many ways of doing this
You may convert all your data to strings and save as an ascii file (you have to pay attention to the file format, so you can read it properly.
Or you can use the configuration vi's, it may work in your case.
or you may use an invoke node to get all controls of the vi's, save it, then read it, without worrying about any format. I have attached a vi that uses this method.
Attachments:
Temp.vi ‏52 KB

Final attributes and local variables - performance ??

Hi all,
I and a colleague have done some performance testing regarding the use of final attributes and final local variables, e.g.
with final:
public class MyClass {
private final int i;
public final void myMethod() {
    final int j = 5;
    // do something with i and j
}vs. non-final:
public class MyClass {
private int i;
public final void myMethod() {
    int j = 5;
    // do something with i and j
}I couldn't find any speed differences in a small test program, but my colleague did so in his application. Who is right ??
Still, I will have do some formal testing next week and I will post the results.
I'd prefer the version using final anyway because I find it better readable, but the issue I am having is whether I'll spend 2-3 days going through the program making everything final or not.

I made some tests with final arguments to a method: I could not find any difference between final and non-final arguments. code is posted below
import java.io.*;
import java.net.*;
import java.rmi.*;
import java.util.*;
import javax.ejb.*;
import javax.naming.*;
import javax.rmi.PortableRemoteObject;
import junit.framework.*;
import junit.extensions.*;
public final class FinalVariablesTest extends TestCase /* from junit */ {
     * Constructors
    public FinalVariablesTest(String name) {
        super(name);
     * helper methods/classes
    protected void setUp() throws Exception {
        super.setUp();
    protected void tearDown() throws Exception {
        super.tearDown();
     * Test Suite
    public static void main(String[] args) {
     junit.textui.TestRunner.run(suite());
    public static Test suite() {
        return new TestSuite(FinalVariablesTest.class);
     * Test Cases
    /** tests the effect of passing an (final or non-final) int parameter
     to a method which uses the variable in a for loop.
     <p>
     Linux System:
     cat /proc/cpuinfo
     processor       : 0
     vendor_id       : GenuineIntel
     cpu family      : 6
     model           : 8
     model name      : Pentium III (Coppermine)
     stepping        : 1
     cpu MHz         : 501.146
     cache size      : 256 KB
     fdiv_bug        : no
     hlt_bug         : no
     sep_bug         : no
     f00f_bug        : no
     coma_bug        : no
     fpu             : yes
     fpu_exception   : yes
     cpuid level     : 2
     wp              : yes
     flags           : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr xmm
     bogomips        : 999.42
     </pre>
     <p>
     Results:
     <pre>
     java version "1.4.0"
     Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
     Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)
     final     non-final
     498     500
     491     494
     491     493
     491     494
     534     494
     492     494
     491     494
     492     493
     491     494
     495     494
     4966     4944 (Totals)
     </pre>
    public final void testIntParametersToForLoop() {
     final int RUNS = 10;
     final int INNER = 1000000;
     final int OUTER = 10;
     System.out.println("-----------------------");
     System.out.println("testIntParametersToForLoop");
     for(int i=0; i<RUNS; i++) {
         outerFinalIntParametersToForLoop(INNER, OUTER);
         outerNonFinalIntParametersToForLoop(INNER, OUTER);
    private final void outerFinalIntParametersToForLoop(final int INNER,
                                   final int OUTER) {
     // with final var in for loop
     long start0 = System.currentTimeMillis();
     for(int i=0; i<OUTER; i++) {
         innerFinalIntParametersToForLoop(INNER * i);
     long end0 = System.currentTimeMillis();
     System.out.println("      final:       " +
                  ( end0 - start0 ) + " milliseconds");
    private final void outerNonFinalIntParametersToForLoop(final int INNER,
                                      final int OUTER) {
     // with non-final var in for loop
     long start1 = System.currentTimeMillis();
     for(int i=0; i<OUTER; i++) {
         innerNonFinalIntParametersToForLoop(INNER * i);
     long end1 = System.currentTimeMillis();
     System.out.println(" non final: " +
                  ( end1 - start1 ) + "       milliseconds");
    private final void innerFinalIntParametersToForLoop(final int INNER) {
     for(int i=0; i<INNER; i++) {
         int testVar = i * INNER;
    private final void innerNonFinalIntParametersToForLoop(int loops) {
     for(int i=0; i<loops; i++) {
         int testVar = i * loops;

A null object loaded from local variable 'o' in XSLT mapping

Hi experts,
We are facing an issue in XSLT mapping for one of the inbound scenario.
While executing the source message at mapping level, it is failing with the error text - "javax.xml.transform.TransformerException: com.sap.engine.lib.xsl.xpath.XPathException: Error parsing query -> java.lang.NullPointerException: while trying to invoke the method java.lang.Object.toString() of a null object loaded from local variable 'o'
Kindly help us on this issue!
FYI - We are facing this issue in PO 7.4 version.
Best Regards,
Uday.

HI Hareesh,
Thanks for your inputs...
We are migrating the interface from PI7.1 to PI 7.4 at this one we are getting the error as mentioned the earlier. we are uanle to run it in the mapping level as well.
Why are we getting the error?As this is working in PI7.1 version
Please help us on this.

RE: local variable cross-talk?

Jeff
A global can be considered as a variable to the entire code, where lots of
different vi's can operate it. Locals only have any meaning within their
own vi, or instances of their own vi.
If anything writes to a particular global, whether in reenterent vi's or
not, it's available everywhere in the code.
What you were asking was about locals though. If a vi is non-renentrant
(i.e. as they come out of the box) then the values in the locals are vi
specific, no matter where the vi is, where it was last used, it retains the
data from it's last operation. If it is re-entrant, then the values in the
locals for each occurance of the vi are its own for EACH instance, i.e. just
like different locals in different vi's, it doesn't matter where else the vi
is used, the data held is that from the last operation of that specific
instance.
Simple way to demonstrate this. Make a vi that has one numeric control,
then code in +1 and get it to write to a local variable for that control.
Throw in an indicator to wire out the result of what is written to the local
for the control.
Then take this vi, put it in a for loop, then put another copy in the for
loop as well. Wire the indicators to the side of the for loop and create
indicator arrays for them. Get the loop to run 6 times say. Now try
running this with the vi in the for loop non-reentrant and then reenterrant.
One way the arrays will contain either all the odd no.s 1,3,5,7,9,11 and
then the other array 2,4,6,8,10,12 (don't know which array will be which,
depends which executes first in the for loop of this example). The other
way they will both be 1,2,3,4,5,6. In the first example, the same vi has
run 12 times, i.e. one copy of the vi which retains its info and is called
in many places and therefore only has one set of values, and the other with
two re-enterant copies where they have their information specific to that
instance of them i.e. effectively they are different vi's. Both ways are
useful, depends what you want.
If you're looking for a use for non-reenterant vi's then consider this:-
For instance. Supposing you get many things to try to write to a global
array of numbers, and you have two vi's one "A" writes to the first element
in the array and the other "B" writes to the second element. Because in LV
you have to read a global first and then write to it to perform a change,
these independant vi's "A" and "B" (be they re-enterant versions of the same
vi, or different vi's), can be performing the tasks simultaneously in the
code. I.e. "A" reads, "B" reads, "A" writes, and "B" writes over the top
with a modified version of what it read, and "A"'s changes are lost. This
is what's known as a "race condition" as "A" hadn't finished and "B" needed
to know what "A" was going to write before "B" performed "A" read. Try it,
hours of fun if you code this kind of thing in inadvertantly!
If the same vi is used, and is not re enterant, it can only run in one
instance at a time, hence two read / write operations cannot be performed
together, problem solved. Unless that gives you timing issues of course,
waiting for one to finish, to write the other......but that's another whole
can of worms.
cheers
Tim Price
This e-mail, its content and any files transmitted with it are intended
solely for the addressee(s) and are confidential and may be legally
privileged. Access by any other party is unauthorised without the express
prior written permission of the sender. If you have received this e-mail in
error you may not copy, disclose to any third party or use the contents,
attachments or information in any way.
-----Original Message-----
From: [email protected]
[mailto:[email protected]]On Behalf Of Jeffrey W Percival
Sent: 29 November 2001 21:12
To: [email protected]
Subject: Re: local variable cross-talk?
Another useful reply! What a great news group this is.
One last thing I wanted to ask about, though, is global vs. local. I see
you talk about globals, but in fact the variables in my subVI's were locals.
I can easily understand the behavior I observed accompanying the use of
global variables, But I guess the use of the word "local" stumped me.
Should I interpret "local" in LabVIEW's sense to mean "local to all
instances of this VI"? And global to mean "visible to all instances of this
VI as well as other VI's"?
-Jeff
Tim Price wrote:
This facility is actually very useful, for instances where you want to
encapsulate some code so that it can only run in one place at a time,
i.e.
global arrays that are written to in more than one place. This method
can
eradicate race conditions completely for example when used like this.
There
are multiple other uses as well.
However, using a vi as a module of code, to run in more than one
instance at
a time simultaneously, re-entrant is the way to go. Just make sure you
debug it first!!!
Remember though, just because a vi may be re-eneterant, doesn't mean
that
everything inside is; sub-vi's, Globals etc. The classic one I've seen
is
where people think that a re-enterant vi is talking to it's own copy of
any
Globals used within it, i.e. counters etc., where in actual fact of
course,
they are all using the same Globals.
Worth playing with a few examples to get familiar with it.
Tim Price
Jeffrey W Percival, Senior Scientist and Associate Director
Space Astronomy Laboratory, University of Wisconsin - Madison
1150 University Ave, Madison, WI 53706 USA
608-262-8686 (fax 608-263-0361) [email protected]
http://www.sal.wisc.edu/~jwp

Tim Price wrote:
Tim, thanks very much. I'll try the experiment you suggest.
Thanks for taking the time.
-Jeff
Jeffrey W Percival, Senior Scientist and Associate Director
Space Astronomy Laboratory, University of Wisconsin - Madison
1150 University Ave, Madison, WI 53706 USA
608-262-8686 (fax 608-263-0361) [email protected] http://www.sal.wisc.edu/~jwp

Prototype method, local variable issue

Similar Messages

Maybe you are looking for