You can't really remove "extra structure". Most of the things that are present in a stock Jetspeed are there for a reason.
You might be able to remove some things (like directories and maybe even some jars) by commenting out services in the Jetspeed and Turbine properties files. Experiment with services by turning them on and off in JetspeedProperties and Turbine properties. A lot of services have configurations options defined for them that point to particular directory under WEB-INF for example. If you will not use services like: jcm, ocs or any of the publishing/rss related once might as well get rid of the directories and services that support them. Be careful with "properties merge" function. Some services are used by some other services without documenting that, so you might end up turning off something trivial like "Portlet Stats" service and get "horrible exception" or NPE during runtime. Dmitry -----Original Message----- From: Brian Rowe [mailto:[EMAIL PROTECTED] Sent: Thursday, February 19, 2004 3:33 PM To: Jetspeed Users List Subject: jetspeed deployment best practices Hello, After reading the bluesunrise tutorial series and the various jetspeed documentation, it seems that Jetspeed is the most mature of the open source portals. I am willing to 'take the plunge' and develop some custom components, etc. but am a bit unsure as to what the best practices are for developing with Jetspeed. At this point, I'm mostly interested in how to structure the webapp directories and determine which files are necessary. I only found one thread discussing this matter (Subject: Trying to split Jetspeed and project code, From: Stijn de Witt, Date: 6 Feb. 2004). Unfortunately, there wasn't much discussion about the actual structure used. Is de Witt's approach a good one, or are there some other mature Jetspeed developers that have a tried and proven methodology? I am inclined to use the structure of the bluesunrise tutorials, but there is so much extra structure to support the tutorials, that I am uncertain what is required and what isn't. I know as much that the jetspeed classes can be dropped in to the WEB-INF/lib, but not sure about what other files are necessary. Thanks, Brian -- ===== Brian Rowe (President, Chief Architect) Cenozoa Corporation 3 East 28th Street, 9th Floor, New York 10016 646 536 3066 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
