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.
Summary: | The web modules in a web freeform project should map to the underlying Java freeform compilation units | ||
---|---|---|---|
Product: | javaee | Reporter: | Andrei Badea <abadea> |
Component: | Web Freeform | Assignee: | issues@javaee <issues> |
Status: | NEW --- | ||
Severity: | blocker | CC: | pjiricka |
Priority: | P2 | ||
Version: | 4.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 66807, 89477 |
Description
Andrei Badea
2005-04-05 14:30:41 UTC
*** Issue 56904 has been marked as a duplicate of this issue. *** Reassigning according to our discussion. The problem originally described in this issue was fixed. The classpath element is not entirely unnecessary. Its contents is used to compute the return value of the EjbJar module (or WebModule in the web freeform). However, the correctness of this approach should still be investigated. The web and EJB natures build on the Java nature, which has the concept of compilation units. Compilation units can be disjunct and each one can have its own classpath. However, the classpath element in the web and EJB natures seem to ignore this and allow going across compilation unit boundaries. Instead of this, a simple 1:N mapping of an EjbJar or WebModule to a set of compilation units could be simpler and make more sense. The EJB freeform project has been dropped from NetBeans 6.0. Still applies to the web freeform. moving opened issues from TM <= 6.1 to TM=Dev |