Third-party component sets often require that an application be configured
specially, e.g. through the specification of a servlet filter or initialization
parameters. During rendering, the components may also perform checks of their
context to ensure that it was configured correctly. Since the design-time "mock"
servlet environment in Visual Web Pack does not model this data, the components
cannot currently be used.
Two enhancements are needed. First, in the design-time API. There should be
methods for getting editable configuration file objects, or individual methods
for getting/setting things like init parameters, filter definitions, etc., so
that the design-time support for comp libs can inject configuration information
Second, the Rave design-time servlet container should register settings found in
the project's web.xml file. It should also listen for changes to the file, and
update itself accordingly. We should probably also extend this to the
faces-config file, or at least certain parts (supported locales, for example).
This need to be dealt post NetBeans 6.0 release.