Raphael,
I noticed that you updated the turbine.jar.
Ingo recently zipped up the turbine source into /lib/src/turbine.zip when he
checked in turbine.jar.
I was hoping that we would continue to provide the current source for
turbine with the latest jar if its not too much trouble?
Thanks for updating the Hypersonic SQL database with the latest Turbine
schema.
Its been broken for the last week or so.
Did you have trouble getting the turbine-hypersonic.sql script to run?
I noticed that you didn't check it in. I had problems with the 'default -1'
on the TURBINE_SCHEDULED_JOB table and had to remove the 'default'
constraints. (Im not sure how SQL-2 compliant hypersonic is, but regardless
Im really beginning to like it.) It now seems obvious to me that
jetspeed.script was used to create the database for the WAR distribution.
To point out another point that may or may not be obvious, it appears that
the 'jetspeed-system' directory will no longer be used. Now the default
hypersonic database, cache and logs are all placed under the webapp/WEB-INF
directory.
-- David
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> [EMAIL PROTECTED]
> Sent: Monday, December 11, 2000 7:00 AM
> To: JetSpeed
> Subject: Re: WAR support
>
>
>
>
> ingo schuster wrote:
> >
> > 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?
>
> No. The "webapp" is bith the application and document root. WEB-INF is the
> special folder in webapps which is *not* accessible from server
> and therefore
> mainly for storing private items of the webapp.
>
> > 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?
> >
>
> OK the directory structure is currently
>
> webapp/ root for the documents web application
> index.jsp simple redirector so that http://dddd/jetspeed/ works
> images/ images directory
> jcm/ all jcm portlets files and images
> rss/ all local rss documents
> search/ images and files for the "search" portlet
> WEB-INF/ private configuration directory
> conf/ conf directory where TR.p and JR.p are located
> lib/ jar libraries. This is automatically in the classpath of
> a Servlet 2.2 runner like Tomcat
> log/ the log directory
> cache/ the cache directory for external resources
> tmp/ a tmp dir used by the feed daemon
> templates/ the templates used for the jetspeed screens
> jsp/ jsp templates
> vm/ velocity templates
> wm/ webmacro templates
> psml/ the PSML config files
> xsl/ the internal stylesheets used by Jetspeed
>
> As you can see WEB-INF contains only configuration or internal use
> file, not publicly accessible ones.
>
> And no, jetspeed-config.jcfg or any PSML or XSL files do not currently
> need to be accessible by HTTP because we use the servlet runner
> getResource() to reach them and thus go directly through file: or
> classpath: URLs.
>
> What server are you using for testing Jetspeed, Tomcat or WebSphere ?
>
> --
> 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]
