Yes, Sir, i can provide some instructions on how to do this - meaning download and install the nightly build for jetspeed.
i am not suggesting that you do it - i am just gonna tell you how you can proceed. if you have put time and energy into understanding Jetspeed from the release version as i have - throw away all of your knowledge - spit it out like waste. the whole thing has changed. you won't be able to find things. the files are not where you expect them to be. new tags have appeared and ya can't find their definitions - tell me where screenJsp is defined. it used to be ecsscreen defined in ... /templates/tld/template.tld - don't expect screenJsp to be defined there. jetspeed.jcfg is gone. no rhyme, no reason, no explanation - just gone. search far and wide through piles and piles of files - this is called progress. this is a painful experience. after you have "upgraded" (that sure is the wrong word), the site becomes painfully slow - sometimes you wonder if it will ever return - if you get tired of waiting, minimize the browser, and restore it - this was faster for me. the site has bloomed, but is it better? try to make heads and tails of it. go to http://jakarta.apache.org/builds/jakarta-jetspeed/nightly/2001-12-03/ there are two jetspeed zip files - one for windows platforms, on efor Unix platforms. select the one right for you. place the downloaded file in a directory of your choice on Windows, i put it right at C:\ on Unix, i put it at /usr/tools unzip the file on Windows extract, on Unix use GNU tar to untar the resultant directory is jakarta-jetspeed follow the directions in the Install file (these are good useful directions, the builds scripts are great) after installing and viewing the installation with your browser - return to the land of pain when you attempt to produce your first class using PortletHowTo things go south in a hurry - the classpaths are a nightmare. the jetspeed jar is not where you would have expected it - .../WEB-INF/lib with all of the rest of the jars. also, the Turbine jar would not work for me - had to point to another version elsewhere. the documentation was not included in the download - thus not in the WAR file - this is meaningful to me because i am developing on an isolated Intranet - otherwise you would just point your browser at the Jetspeed site on the Internet and view the documentation. i didn't have this advantage at my developement site, therefore, the pain was increased. you will observe that life is a set of checks and balances. when the pain outweighs the advantages, we cease and go elsewhere - what other choice does one have? i believe the issue of portals (information perspective) and view ports (GUI layouts and decorations) had become too interwoven and too interspersed that the true meanings of the terms can no longer be discerned. the nighlty build is further separated from interaction with Cocoon then the release build - this is a tremendous setback for me. ---------- From: Geoff Hollingworth (EUS)[SMTP:[EMAIL PROTECTED]] Reply To: Jetspeed Users List Sent: Monday, December 03, 2001 9:30 PM To: Jetspeed Users List Subject: RE: .../WEB-INF/classes Can anybody direct me to instructions on how to do this? regards /geoff "I suggest you upgrade to jetspeed version 1.3a2-dev from the nightly build. Most of the discussions are related to 1.3a2-dev." -----Original Message----- From: Ray Martin [mailto:[EMAIL PROTECTED]] Sent: Monday, December 03, 2001 4:15 PM To: 'Jetspeed Users List' Subject: RE: .../WEB-INF/classes Sir, i have done searches through some of the mail lists. i was not able to surface an answer to my predicament. if anyone can help me, i would appreciate it. my customer is looking at me like i am a dumb ass (and they are probably right - i just didn't want to prove it so early in the project) i persuaded them that the project should leverage off of the tremendous thought and energy by using some of the tools located at the Apache web site instead of using PERL and CGI. now because of my dilema, they are pointing at me and going "Yeah, right..." i am using jdk1.3 - i had previously backed away from jdk1.4 - my brother was having trouble with jdk1.4 and Cocoon2. thanx, Ray ---------- From: [EMAIL PROTECTED][SMTP:[EMAIL PROTECTED]] Reply To: Jetspeed Users List Sent: Friday, November 30, 2001 5:04 PM To: Jetspeed Users List Subject: Re: .../WEB-INF/classes I suggest you upgrade to jetspeed version 1.3a2-dev from the nightly build. Most of the discussions are related to 1.3a2-dev. I believe their is a JDK problem with a unix, although I do not know the version of the JDK or which Unix. The resolution was to use a previous version of the JDK. Suggest you search the jetspeed user and developer mailing lists, http://www.mail-archive.com Paul Spencer Jetspeed Users List <[EMAIL PROTECTED]>,"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > using two different machines - one running Windows 2000, the other Solaris 2.8. i do the "how to write a porlet" discussion. i place the HelloWorldPortlet in WEB-INF/classes and register the portlet with jetspeed-config.jcfg. the portlet does its thing on the Windows box - says hello and appears in the customizer. the Solaris 2.8 machine - nothing - no hello, no HelloWorldPortlet in the customizer. i may be screwing up here - this could well be a Tomcat issue and i am asking my question in the wrong forum - or worse yet a Unix problem - then i'm really gonna be embarassed. not to cross forums, but just for a little more information - Turbine and Cocoon2 stand up on the Windows box, but neither stand up on the Unix box (this is what makes me believe that my problem is not a Jetspeed issue). i am running catalina on both platforms passing in 'run' on the command line but no '-security'. -- To unsubscribe, e-mail: For additional commands, e-mail: -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
