Scott, I've seen your posts and I understand your frustration! If I could
give you a straight answer I would, but I just don't know how to solve your
particular problems.
I can give you some pointers as to what I have experienced though. I have
started from scratch about 20 or so times now, and that's probably the most
ever. Getting Jetspeed to work wasn't such a big issue for me, but getting
it to work with a project structure that I liked, that is something entirely
different...
Anyway, when I start over, I do the following (assuming a Win2K machine, but
that shouldn't matter much):
Already installed:
J2EE (I think i'm using 1.4.x something...)
NetBeans
- Install Jakarta Tomcat (I'm using 5.0.18)
- Extract jetspeed-1.4-src.zip to my projects folder
- Move files xalan-2.3.1.jar and xml-apis.jar from jetspeed/lib to
tomcat/common/endorsed
- In NetBeans, Mount->Local Directory->jetspeed/src/java
- In NetBeans, Mount->Local Directory->jetspeed/webapp/WEB-INF/conf
- In NetBeans, Mount->Archive Files->jetspeed/lib/*.jar
- In NetBeans, Mount->Archive Files->tomcat/common/endorsed/*.jar
- In NetBeans, Mount->Local Directory->jetspeed/
- In Netbeans, collapse the jetspeed/ mounted folder
- edit project.properties, change lib.dir from ${lib.repo} to lib
- right-click build.xml ->run target->war (This should build the .war)
- If tomcat is running, stop it
- Manually copy jetspeed.war from jetspeed\target to tomcat\webapps (making
sure any old jetspeed dirs and wars are deleted first)
- Start tomcat
- Point your browser to http://localhost:8080/jetspeed
- Check jetspeed.log in tomcat/webapps/jetspeed/WEB-INF/log for any errors.
If you get this up and running, try switching to mysql...than try adding
persistence with OJB...develop your own stuff...etc.
Hope this might help you!
Oh, before I forget. I have some issues with Tomcat. If I am testing a
jetspeed page, and then rebuild the war, stop tomcat, delete old jetspeed
dir and war, copy new war and restart tomcat, the first time Apache Jakarta
Jetspeed Portal startup will often fail. If I then stop tomcat and restart
it, it does work...So, I'm still looking for a clean build proces. But if I
find it, I will post detailed descriptions!
-Stijn
----- Original Message -----
From: "scott" <[EMAIL PROTECTED]>
To: "Jetspeed Users List" <[EMAIL PROTECTED]>
Sent: Thursday, February 19, 2004 9:42 PM
Subject: Re: jetspeed deployment best practices
> Cudos to you being able to get the tutorial to work. I have been woking
on
> trying to get them to work for 3 days. What is the secret? None of my
> changes take place when I redeploy the app for some reason.
>
> On Thursday 19 February 2004 03:32 pm, Brian Rowe wrote:
> > 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
>
> --
> Scott A. Macri
> Software Engineer/Director
> Macri Solutions, LLC
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
