cornercorner
FeaturesPluginsDocs & SupportCommunityPartners

Bug 175979 - Can't create a mobile client for Web application
: Can't create a mobile client for Web application
Status: VERIFIED FIXED
: mobility
Web Services
: 6.8
: All All
: P1 with 1 vote (vote)
: 6.8
Assigned To:
:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2009-11-03 17:17 by
Modified: 2009-11-19 06:42 (History)
Issue Type: DEFECT
:


Attachments
screenshot (61.90 KB, image/png)
2009-11-03 17:17, Andrei Chistiakov
Details
sample projects (45.32 KB, application/x-compressed)
2009-11-03 17:18, Andrei Chistiakov
Details
patch (3.06 KB, text/plain)
2009-11-18 07:24, t_h
Details


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2009-11-03 17:17:18
Product Version: NetBeans IDE Dev (Build 200911030222)
Java: 1.6.0_16; Java HotSpot(TM) Client VM 14.2-b01
System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb)

To reproduce:
- open the attached projects
- select MobileApplication1 and invoke New->Java ME Client For Web Application
- press Next
- check any method

There are two issues:

- Next and Finish buttons remain disabled even if a method is checked
- attempt to check more than one method in the tree fails. Only one method can
be checked

See attached screenshot
------- Comment #1 From 2009-11-03 17:17:48 -------
Created an attachment (id=90459) [details]
screenshot
------- Comment #2 From 2009-11-03 17:18:23 -------
Created an attachment (id=90460) [details]
sample projects
------- Comment #3 From 2009-11-04 09:08:09 -------
Marku, I think this is an optimization issue which was rounding around for a
while.
------- Comment #4 From 2009-11-04 09:10:15 -------
Sorry the comment was for #175960 :)
------- Comment #5 From 2009-11-11 04:15:29 -------
It does not work in 6.7.1 as well. I am trying to find the root cause
------- Comment #6 From 2009-11-14 14:51:19 -------
It seems the events are not for some reasons propagated back to model. This can
be by some change in BeanTreeView or so, I was not able to find the root cause
yet
------- Comment #7 From 2009-11-16 07:14:55 -------
This seems to be connected with lazy nodes .. I need some help
------- Comment #8 From 2009-11-16 07:32:20 -------
what kind of help you need ?
------- Comment #9 From 2009-11-16 09:15:21 -------
I am currently not able to drill down what is the root of the issue? Any hint?
------- Comment #10 From 2009-11-17 00:24:50 -------
This is IDE Log when i`m trying to create Mobile Client for Web App

INFO [org.netbeans.api.java.source.ElementHandle]: Cannot resolve:
ElementHandle[kind=CLASS; sigs=webservice.feedback.wallet.package-info ]


java.lang.Exception: Stack trace
        at java.lang.Thread.dumpStack(Thread.java:1206)
        at
org.netbeans.api.java.classpath.ClassPath.getClassPath(ClassPath.java:546)
        at
org.netbeans.api.java.source.ClasspathInfo.create(ClasspathInfo.java:263)
        at
org.netbeans.api.java.source.ClasspathInfo.create(ClasspathInfo.java:274)
        at
org.netbeans.modules.mobility.end2end.multiview.ServicesPanel.updateTree(ServicesPanel.java:243)
        at
org.netbeans.modules.mobility.end2end.multiview.ServicesPanel.access$000(ServicesPanel.java:92)
        at
org.netbeans.modules.mobility.end2end.multiview.ServicesPanel$1.run(ServicesPanel.java:104)
        at
org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:577)
        at
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1030)

where webservice.feedback.wallet - namespace for Web Service Reference in my
Web Application. I guess the INFO block throwed exception.
------- Comment #11 From 2009-11-18 07:09:36 -------
Probably broken by #4e49c36ab2a7, specifically by changes in
MethodCheckedNodeRenderer.getTreeCellRendererComponent(). I guess it should use
'this' and return this and not to create new MethodCheckedNodeRenderer on every
call.
------- Comment #12 From 2009-11-18 07:24:58 -------
Created an attachment (id=91256) [details]
patch
------- Comment #13 From 2009-11-18 07:45:26 -------
>Probably broken by #4e49c36ab2a7, specifically by changes in
>MethodCheckedNodeRenderer.getTreeCellRendererComponent(). I guess it should use
>'this' and return this and not to create new MethodCheckedNodeRenderer on every
>call.

I think this is true.
My change #4e49c36ab2a7 has introduced this issue.
It was inaccurate at least. ( Methods addItemListener(), ... requires delegates
).

BUT your fix is just rollback of fix #4e49c36ab2a7.
As result Issue #162018 appears again.
------- Comment #14 From 2009-11-18 08:05:53 -------
1) Your assumption for fix #162018:

"OK, I have found the problem actually .
Renderer has used the same component for each cell.
But component for each cell should be different."

is wrong. The fix was wrong and inefficient.

2) I did not see #162018 in samples from #175979 after fix. If it appears again
the issue #162018 should be reopened and re-evaluated.
------- Comment #15 From 2009-11-18 09:55:53 -------
Rollback 4e49c36ab2a7, CS e0718f5760fc see
https://netbeans.org/bugzilla/show_bug.cgi?id=162018 for more details
------- Comment #16 From 2009-11-19 06:42:00 -------
Verified with NetBeans IDE Dev (Build 200911190201)