e mërkurë Nën 01, 2006
e diel Nën 06, 2005
By pavel on Nën 06, 2005
I wish we had something like this for other project types. The code completion only shows classes that are already on classpath and if you want to use a different class you have to know where it is. Of course the trick used here is that the universe of possible libraries is known upfront, it's just the APIs of modules in the target NetBeans platform, so the dialog knows where to look for them. But I would be happy if this worked for the libraries, projects that are currently open and perhaps recently open projects.
Maybe it could even be more integrated into code completion. If the class is not found in completion instead of "No Suggestions" you would have get a "Look for the class in libraries" item... Maybe this is also an answer to Geertjan's comment: "I don't like [...] that you need to manually put the EJB on the web application's classpath."
- Three lessons I learned when working on NetBeans 5.5
- It's Good to See Your Baby Take Off
- Next Step: Generate Simple JSF Application
- Generate entity classes from DB
- Automatic Generation of Database Tables
- Java EE 5 Persistence Demo
- Java EE 5 Persistence
- NetBeans Module Development: Adding Dependencies
- Hello JavaEE 5