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 140602 - JAXB Binding library project and editor not finding package red underline hint
Summary: JAXB Binding library project and editor not finding package red underline hint
Status: RESOLVED WORKSFORME
Alias: None
Product: xml
Classification: Unclassified
Component: JAXB (show other bugs)
Version: 6.x
Hardware: Sun Solaris
: P3 blocker (vote)
Assignee: _ gmpatil
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-17 18:47 UTC by teodoro
Modified: 2009-10-22 22:47 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
XML schema file used (1.13 KB, text/xml)
2008-09-23 20:08 UTC, _ gmpatil
Details

Note You need to log in before you can comment on or make changes to this bug.
Description teodoro 2008-07-17 18:47:42 UTC
I'm using a Java project to create a library that is generated from JAXB Bindings (classes from xml schemas)
Another project uses the Java library. 
Everything works fine on Netbeans 6.0.

Although on Netbeans 6.1, it compiles right with no errors but on the editor screen the Java project classes that uses
the library classes keeps showing red underline messages and exclamation that package wasn't found. It also doesn't find
the package on code complete. 

Any idea where the problem is ?
Comment 1 _ gmpatil 2008-07-17 21:09:58 UTC
Yes. It is regression.
Issue 114164.
Comment 2 _ gmpatil 2008-07-24 00:25:16 UTC

*** This issue has been marked as a duplicate of 114164 ***
Comment 3 teodoro 2008-09-02 16:27:51 UTC
I'm trying it with 6.5 Beta and it hasn't been fixed.
Although I noticed that if I use classes from generated XML schema on the same project that has the jaxb folder it works. 

The problem is when I try to use the class on another project that imports it.

the steps to reproduce are:

1. create a simple java project to host the schemas.
2. add a jaxb binding
3. imports schemas and generate java classes. ( In my case they are a large number of classes, huge, > 2500 ) 
4. create another java project.
5. go to properties and import the first project.
6. try to use the ObjectFactory and you'll see that it shows the red underline and it doesn't compile too.

This scenario used to work on 6.0

I can't post the schemas here because they belong to a third party.


Product Version: NetBeans IDE 6.5 Beta (Build 200808111757)
Java: 1.5.0_06; Java HotSpot(TM) Client VM 1.5.0_06-b05
System: SunOS version 5.10 running on x86; ISO8859-1; en_US (nb)
Comment 4 _ gmpatil 2008-09-23 20:08:44 UTC
Created attachment 70358 [details]
XML schema file used
Comment 5 _ gmpatil 2008-09-23 20:11:57 UTC
Could simulate with latest trunk build.

Product Version: NetBeans IDE Dev (Build 20080923152338)
Java: 1.5.0_13; Java HotSpot(TM) Client VM 1.5.0_13-b05
System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb)
Userdir: C:\tmp\nb65_0923

Tried below test cases.
- Java SE project importing another Java SE project.
- Web Application project importing Java SE project.
- EJB project importing Java SE project.
- EJB project importing another EJB project.

teodoro, 
Change related to this was checked-in around Aug 05 to trunk, NB 6.5 beta build (20080811) might have missed the change.
Could you try latest 6.5 dev build? let us know if you still get the issue.

Attached the schema file used to verify.


 
Comment 6 teodoro 2008-09-26 16:28:48 UTC
I tried with the latest v6.5 daily development build and it is fixed.
Thanks. 
Comment 7 teodoro 2009-10-22 20:07:37 UTC
I'm having it with 6.7.1 version again. It seems a regression.
Comment 8 teodoro 2009-10-22 20:27:22 UTC
It went away after some minutes. It looks like a performance issue.
Comment 9 _ gmpatil 2009-10-22 22:46:29 UTC
Closing this issue, based on latest feedback. 
teodoro, If you think it is still issue but related performance or slow updation of classpath, you might want to file a
separate issue with respective NB project type. 
Comment 10 _ gmpatil 2009-10-22 22:47:19 UTC
Closing based on last user response.