You are viewing a plain text version of this content. The canonical link for it is here.
Posted to taglibs-dev@jakarta.apache.org by bu...@apache.org on 2004/08/13 12:39:41 UTC
DO NOT REPLY [Bug 30647] New: -
JSTL examples application does not follow the Blueprints structure
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30647>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30647
JSTL examples application does not follow the Blueprints structure
Summary: JSTL examples application does not follow the Blueprints
structure
Product: Taglibs
Version: nightly
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: Standard Taglib
AssignedTo: taglibs-dev@jakarta.apache.org
ReportedBy: petr.jiricka@netbeans.com
The source structure of the JSTL examples application contains directories conf,
src and web, where conf contains web.xml and jslt-examples.tld.
According to the J2EE Blueprints recommendation at
http://java.sun.com/blueprints/code/projectconventions.html, these files should
be placed in web/WEB-INF. See the paragraph about web/WEB-INF in this document:
"Contains the web.xml deployment descriptor and static configuration files such
as faces-config.xml. May also include vendor-specific runtime deployment
descriptors, such as sun-web.xml. Generally, this directory contains files that
are copied rather than changed during a build. Dynamic configuration files
should be placed in the conf/ directory."
Not following the Blueprints recommendation will cause problems when trying to
use the examples in an IDE, as most IDEs assume the Blueprints structure.
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org