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 85385 - Persistence Javadoc not available for J2SE project
Summary: Persistence Javadoc not available for J2SE project
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: Persistence (show other bugs)
Version: 5.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: Dongmei Cao
URL:
Keywords:
: 101228 109257 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-09-20 22:11 UTC by Petr Jiricka
Modified: 2009-11-02 11:15 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2006-09-20 22:11:34 UTC
Build 20060920, WinXP, JDK 6 build 97.

1. Start the IDE with a clean userdir
2. Register Sun Appserver (so that the sample database is available)
3. Create a new Java SE project
4. Create Entity Classes from Database (including Persistence Unit)
5. Open the generated entity in the editor
6. Go to the import of a persistence class and press Ctrl+Space:
import javax.persistence.Enti|ty

=> Code completion is shown, but the Javadoc window says that the Javadoc is not
found.

The truth is that in the Library Manager, no Javadoc is registered for Toplink
Essentials. The workaround is to register the Javadoc (file
$IDE_HOME/enterprise3/docs/javaee5-doc-api.zip) in the library manager manually.
Comment 1 Erno Mononen 2007-03-23 11:10:24 UTC
Fixed in trunk.

Checking in toplink_lib.xml;
/cvs/j2ee/toplinklib/src/org/netbeans/modules/j2ee/toplinklib/
toplink_lib.xml,v  <--  toplink_lib.xml
new revision: 1.3; previous revision: 1.2
done
Comment 2 Petr Jiricka 2007-03-23 11:16:11 UTC
Although, will not there be an issue when the enterprise cluster is not
installed?  This in practice can happen, see the installable components document:
http://wiki.netbeans.org/wiki/view/NB6InstallableComponents

I think the correct solution would be to split the Java EE javadoc into two
parts (JPA and the rest) and put the JPA part in the IDE cluster. I am not sure
though whether we can do this legally.

I think I would leave this open as a P4, what do you think?
Comment 3 Erno Mononen 2007-03-23 11:41:18 UTC
Yes, I see that could be a problem. If we can't split the javaee5 javadoc, what 
about including it in the ide cluster? Although clearly it wouldn't be ideal, 
especially since the zip is that large.
Comment 4 martin_adamek 2007-06-22 10:06:43 UTC
*** Issue 101228 has been marked as a duplicate of this issue. ***
Comment 5 Erno Mononen 2007-07-25 13:45:26 UTC
*** Issue 109257 has been marked as a duplicate of this issue. ***
Comment 6 Erno Mononen 2007-07-25 13:46:27 UTC
Raising to P3 since there are two duplicates already.
Comment 7 Dongmei Cao 2008-09-17 19:56:51 UTC
will not be fixed in 6.5. Set the target the future
Comment 8 Dongmei Cao 2008-11-19 00:23:02 UTC
This depends on if the persistence Javadoc will be separated out or not
Comment 9 Quality Engineering 2009-11-02 11:15:51 UTC
NetBeans.org Migration: changing resolution from LATER to WONTFIX