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 32701 - steps of creation of web module should be declarative if possible
Summary: steps of creation of web module should be declarative if possible
Alias: None
Product: javaee
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Windows 3.1/NT
: P3 blocker (vote)
Assignee: Pavel Buzek
Depends on: 23818 32408 34057
  Show dependency tree
Reported: 2003-04-08 10:12 UTC by Pavel Buzek
Modified: 2003-12-11 14:27 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Exception Reporter:

commit log (1.09 KB, text/plain)
2003-08-08 09:43 UTC, Pavel Buzek

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Buzek 2003-04-08 10:12:10 UTC
- point to sources declaratively, see

- create and setup jarackager target declaratively
Comment 1 Pavel Buzek 2003-04-08 10:16:09 UTC
does not have direct impact on user, only a design issue
Comment 2 Pavel Buzek 2003-07-23 15:59:11 UTC
current status:
- it is possible to setup props of web module (build target, etc.) and
execution target settings (these are serialized)
- java compilation unit is being setup in wizard, I am waiting for
32408 to use declarative way but to avoid more serialized data

example is in module web/core
Comment 3 Peter Liu 2003-07-31 21:26:56 UTC
For the execution target and build target settings for the web module,
are they going to remain as serialized data? If so, how do I go about
creating the data in the first place and how do I serialize them? 
Comment 4 Pavel Buzek 2003-08-08 09:43:20 UTC
Created attachment 11249 [details]
commit log
Comment 5 Pavel Buzek 2003-08-08 10:00:30 UTC
I moved the following parts of setup from wizard into project template:

- java compilation unit, 
- document base, 
- output folders for b. targets, 
- default build target

The remaining parts that are still done programatically in wizard are:
- jarpackager content (I plan to fix this)
- web module version, creation of web.xml and sample files (this will
probably remain in wizard since we let the user to choose the version
of spec and the rest depends on it. It is possible though to put this
into a template if you do not require customization)

The template still contains serialized data for primitive values. We
will be able to replace them with text values when 34057 gets fixed.

The only way to create those serialized data (AFAIK) is to copy/paste
from an existing project file. This is only a temporary solution.

Docs for web project template will be added soon.
Comment 6 Pavel Buzek 2003-08-08 10:45:35 UTC
documentation for web module project updated
Comment 7 Pavel Buzek 2003-09-02 14:46:52 UTC
Implementation of classpath content for library will enable
declarative setup of Servlet API library. It will also make project
transferable to another system since it will replace the absolute URL
pointing to servlet api jar file with a symbolic library name.
Comment 8 Pavel Buzek 2003-12-10 05:28:58 UTC
closing obsolete issues related to prj40_prototype