Hello Dmitry, On Thursday 19 February 2004 03:53 pm, Dmitry Sklyut wrote: > You can't really remove "extra structure". Most of the things that are > present in a stock Jetspeed are there for a reason. >
So then is it best to install jetspeed and then have a separate project to deploy on top of the jetspeed installation? This is probably the simplest technique, but I'm not particularly happy about using a multi-stage build process. I would rather have an encapsulated jar that I can drop into my project that has no outside dependencies. I read that there is an option to override properties, which seems to help out a lot -- but the main question is how susceptible will I be to upgrades in the jetspeed source if I follow this method? > 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. Are you talking about the technique at http://jakarta.apache.org/jetspeed/site/override_props.html for overriding properties? 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]
