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 91259 - NB generates empty classes that are already available
Summary: NB generates empty classes that are already available
Status: STARTED
Alias: None
Product: javame
Classification: Unclassified
Component: Build System (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Michal Skvor
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-19 08:49 UTC by ieising
Modified: 2007-10-06 11:34 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ieising 2006-12-19 08:49:45 UTC
Hi,

I have 3 projects:
- Mobile Library
- Mobile Application
- Web Application with JSF support

The library is actually used by both the Mobile Application and the Web
Application, thus ensuring I have the same classes at both ends when adding a
webclient to the Mobile Application.

Now when I add a webclient to the Mobile Application, I select a class in the
Web Application that is to be the interface to the web backend and start
generating the code.
Now what I witness is that in my Mobile Application a package is generated with
the same name as the package in the Mobile Library project that contains the
classes that are used by both application projects. In addition, the newly
generated package contains those classes as well, but they are empty. Thus after
the generation of the mobile web client, the Mobile Application project doesn't
compile and I have to delete the generated package and then it all works again.

Iwan
Comment 1 Lukas Hasik 2007-06-11 09:42:10 UTC
reassigning to the right Michal
Comment 2 Michal Skvor 2007-10-06 11:34:25 UTC
Implementing this feature is pretty tricky. The code generator should check all server and client parameter types one by
one including check for parameter and their respective types to see whether they are completely equal on the API level
(code level check does not have sense). Even after this check the generator will not have absolute control whether the
called classes on the client side are correct. Therefore the actual generator is designed to create client classes from
scratch as "data mirror" for the server classes. 

I'm setting this as feature for next versions.