This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 35245 - "ALERT: No such method" in Midlets
Summary: "ALERT: No such method" in Midlets
Status: VERIFIED INVALID
Alias: None
Product: javame
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P1 blocker (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-02 17:51 UTC by nhoggard
Modified: 2006-06-23 17:26 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description nhoggard 2003-08-02 17:51:30 UTC 
"Alert: No such method" runtime error calling an abstract 
method in a midlet. Happens only in midlets recompiled with 
Netbeans and the new MIDP modules. These midlets have 
always compiled and run fine in Sun Forte Mobile Edition. 
The runtime error occurs in all emulators I have - Motorola 
iDEN, Nokia Series 60, Sun emulator.

Here are the details:

- A subclass calls a method in the the superclass which in 
turn calls one of its own abstract methods which is 
implemented in the subclass. Result: "ALERT: No such 
method" and app terminates. (The abstract method is defined
in an interface which the superclass "implements", although 
the abstract methods from the interface are only actually 
implemented in the subclass.)

Switching off the obfuscator has no effect. 

Netbeans 3.5 build 200306022350
Java 1.4.1_03
VM Java hotspot client vm 1.4.1_03-b02
"java home": c:\j2sdk1.4.1_03\jre
Comment 1 _ ttran 2003-08-05 15:04:26 UTC 
you filed a bug against the wrong component.  This is not a bug in NB
core, but in the MIDP module I think.  Please refile the bug against it.
Comment 2 nhoggard 2003-08-20 22:10:45 UTC 
The "Component" menu does not allow me to refile this bug 
under MIDP. Please tell me what to file it under.
Comment 3 _ ttran 2003-08-21 08:01:02 UTC 
where did you get the MIDP modules from?  

Please keep this bug closed, because it's indeed invalid in its
current form.
Comment 4 nhoggard 2003-08-21 11:03:47 UTC 
The MIDP modules are from Netbeans "J2MEWTK 1.0.4 Windows"

I don't agree that this issue should be 
classified "resolved invalid".
Comment 5 _ ttran 2003-08-21 12:47:26 UTC 
I am not saying that the bug is invalid per se.  It's invalid only
because you file it against NetBeans.  You should file the bug against
"J2MEWTK 1.0.4 Windows"  I have no idea what it is and where you got
it from.  It's not a NetBeans module and not "core"

Cc Martin Ryzl who perhaps can help.
Comment 6 Martin Ryzl 2003-08-21 14:08:35 UTC 
so far the best way is to report such problems through nbusers mailing
list or directly to me: martin.ryzl@sun.com. J2ME modules were
designed for Sun ONE Studio ME and released through NetBeans Update
Center because Sun ONE Studio CE was replaced by NetBeans. At the
moment J2ME modules are not part of NetBeans project. 

Regarding the problem, I need name of the method that is called and
what SDK was used for compilation - I mean what emulator was default
when the application was being compiled.
Comment 7 Marian Mirilovic 2003-09-02 18:44:52 UTC 
verifying
Comment 8 Lukas Hasik 2006-06-23 17:26:28 UTC 
this is old issue - 3.5, 3.6