Please be more specific--what did you try to do? What happened?

ok, there is a class in your file system.
This class has a main method
Try to set the arguments sent to that class on execution
you can't! (the properties browser don't have no argument prop)

There is no such property on the Execution tab? Do you have write access to the
source file (check permission bits)? To the containing directory? Does Build |
Set Arguments work? What OS and JDK are you using please?

There is no execution tab. The class has no "you can execute me" icon either.
no, I don't have the source file.
I can enter stuff under "Build|Set Arguments"

If I create a class with a main method. Delete the source, leave the .class file
The .class file DOES have a "you can execute me" icon.
However there is still no execute tab (is this supposed to happen?)

The other class, when browsing in the tree has no main method.
However in the Forte501 release it does, I presume you have changed your class
parser?

Build 45
JDK1.2.2
W2K

OK, now I see the problem. Sourceless class objects simply fail to provide an
Execution tab in current dev builds. I suspect this has to do with recent cookie
initialization changes, but that's just a guess. Note that there is an
ExecCookie and ArgumentsCookie and everything, just no Execution sheet set.

BTW RefuX--there should be an execute icon iff the class has a main method. I'm
not sure what you mean about there being no Execution tab for classes with
source, though, it works for me.

>BTW RefuX--there should be an execute icon iff the class has a main method.
yhea, for some reason after adding some supporting librarys of the class,
netbeans can now parse class and see its main method (why? don't ask me).
It now does show the execute icon, however still no execute tab (as has been
established)

>I'm not sure what you mean about there being no Execution tab for classes with
>source, though, it works for me.
works for me too. If there is source, works fine.

Well, I can explain why the class node does not show executable icon if it lacks
some library. Since the structure is scanned using reflection package, the JVM
must be able to load the class. So if the class is missing some library it
depends on, it is not only marked as executable, but as erroneous :-\ This will
change when (if) we add _real_ parsing of .class files.

[010130_1] Verified

Resolved for 3.3.x or earlier, no new info since then -> closing.