I would recommend putting libs into WEB-INF/libs, because that puts them
into the classpath automatically (per Servlet 2.2 spec), instead of the user
having to modify the classpath externally. Servlet classes (ones that are
not jarred) should go into WEB-INF/classes. Also no need to modify the
classpath. This is the recommended way on J2EE-conformant platforms (which
nowadays are commonplace ;-)).
Also per servlet spec, the content of WEB-INF must not be served to the
public, therefore it cannot contain html files or the like.
----- Original Message -----
From: "ingo schuster" <[EMAIL PROTECTED]>
To: "JetSpeed" <[EMAIL PROTECTED]>
Sent: Monday, December 11, 2000 1:41 PM
Subject: Re: WAR support
At 11:22 2000-12-11, [EMAIL PROTECTED] wrote:
>I've just committed in the CVS an initial webapp support for jetspeed based
>on my Turbine resources patches.
>
>Their are some known issues yet with the WAR but it builds OK and I should
>be able to iron out all the small details tonight.
>
>In the webapp directory, I tried to reorganize the user documents I
>welcome any comments, suggestions, etc on the document structure.
Raphael,
Can you explain the directory structure in more detail?
Am I right that "webapp" is the application root and "WEB-INF" is meant to
be the document root?
How can it then be that the images are not below the document root?
What I'd really like to have is a directory structure that separates
content (in the docroot) from configuration and application data (below the
webapp but not below the docroot). I'd propose a structure like follows
(that's quite similar to what I use at the moment):
webapp
|- WEB-INF
|- lib
|- portlets
|- servlets
|- config
|- log
|- cache
|- doc_root
|- images
|- static
|- dynamic
|- stylesheets
|- ...
|- templates
| |- jsp
| | |- layouts, navigations,screens
| |- wm
| |- layouts, navigations,screens
|- psml
|- portlet_resources
|- portlet1
|- portlet2
|- portlet3
"WEB-INF" contains only web.xml
"lib" contains the portal jars: jetspeed.jar, turbine.jar,
xerces.jar,...
"portlets" holds jars of portlets
"servlets" may contain additional servlets, but is empty (or not
present at all) in the standard installation
"config" contains all our config (properties) files - (the webapps
configuration shouldn't really be exposed in the docroot!)
"cache","log" are application folders
"lib", "portlets","servlets" would be in the classpath.
Below "doc_root" (or whatever you name it) the HTTP accessible files are
stored:
"images", "stylesheets", etc. - content
"templates" - our templates
"psml" - the psml files (if stored in the filesystem and
not in a DB,LDAP,...)
"portlet_resources" - portlet specific resources such as
images, stylesheets, sample data,....
I know that there are some problems to realize this structure (e.g.
jetspeed-config.jcfg needs to be below the doc_root at the moment), but as
I said, that the kind of structure makes sense to me (and so it's probably
worth some effort to achive it).
What do you think? Raphael, could you perhaps list and explain your
directory structure as well?
ingo.
>--
>Rapha�l Luta - [EMAIL PROTECTED]
>
>
>--
>--------------------------------------------------------------
>Please read the FAQ! <http://java.apache.org/faq/>
>To subscribe: [EMAIL PROTECTED]
>To unsubscribe: [EMAIL PROTECTED]
>Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
>Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
