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]
