Dear Ron,
thanks for the "interesting question"... I do hope no one got offended by my
comments anyway :)
As I said, I used J1 for a couple of European project and I finally was
quite acquainted with its setup etc.
I was able to setup a new portal in a few hours... great... then obviously
nobody wanted to use it anymore (don't ask me why...)
The problem I see with J2 (I have followed the mailing list for years now)
is that, whereas you had many posts for J1 related to "how can I
customize/add a portlet here & there etc.", for J2 (I beg your pardon if I
am exaggerating) the largest part of posts are related to very, very
technical issues as setups/configuration etc.
Alsot the documentation online has a total different flavour.
It is true there should be a webmaster + a database administrator + a system
administrator + a project manager for every project, but very often you have
a dummy guy(webmaster + database administrator + system administrator +
project manager) who is unfortunately in charge of "getting it/setting it
up/customize it/evaluate it/report".
As for your points:
What would you consider to be the maximum number of things that you could
install to evaluate it?
It would be amazing for those who at least have a bit of know how on Tomcat
to get just a plug'n'play .war to deploy and play with.
The release I got installed a bare new Tomcat on my pc... maybe it would be
nice to be simpler in organizing releases (I am NOT a pure IT guy - and
proud to say good IT guys are great but sometimes so tricky...).
Maven, Ant... great tools indeed but... wow... how many weeks do I have to
set the portal up?!
How many steps in the process is acceptable?
The stargin issue is - good & clear instructions.
Good programmers I met never spent a minute in commeting their code...
ouch...
How much damage to existing setups is acceptable?
Well, it depends... some love to reinstall OS twice a day, my PM has
Windows2000 on 256Mb RAM...
How close to a production system does the evaluation have to be? Could the
database and servlet container be demo quality?
Well, I think it should give a flavour of what you can do...
I certainly like to get software that comes with a Windows installer that
only asks 1 question "Do you want to over ride my choice of xxx under your
Program Files directory?"
Me too... but I am sure there can be a good compromise.
The fact that the resulting demo would not be anything useful in the long
term may not be an issue to an evaluator.
I think it could be a disposable installation somehow - install it, play,
configure a bit - then if you really like it, you can spend more time on
that.
Another point - please pay attention to online demos - are they still broken
links? yes, they are....
Running portals/sites using J2 would be great to have a look at - it helped
a lot to see what others did with J1 when I was learning I to use it.
Sorry for being that long - I do hope I did not force you to waste your time
guys.
Hope it helps, hold on!
Stefano
P.S. Said that, I can not help too much (unless providing organisation
consult) as I spend my evenings ironing (my wife is pregnant ;)
----- Original Message -----
From: "Ron Wheeler" <[email protected]>
To: "Jetspeed Users List" <[email protected]>
Sent: Monday, May 11, 2009 6:14 PM
Subject: Re: Jetspeed2 Installation
You have raised an interesting question.
What would you consider to be the maximum number of things that you could
install to evaluate it?
How many steps in the process is acceptable?
How much damage to existing setups is acceptable?
How close to a production system does the evaluation have to be? Could the
database and servlet container be demo quality?
I certainly like to get software that comes with a Windows installer that
only asks 1 question "Do you want to over ride my choice of xxx under your
Program Files directory?"
The fact that the resulting demo would not be anything useful in the long
term may not be an issue to an evaluator.
Ron
Stefano Bianchi wrote:
This is exactly the point! Great you got it.
I did not mean to be critic, but I am sure you can understand someone who
can not start installing maven/ant etc. to evaluate it.
An incremental approach for documentation would be definitively great.
Good luck,
S
----- Original Message ----- From: "Ron Wheeler"
<[email protected]>
To: "Jetspeed Users List" <[email protected]>
Sent: Friday, May 08, 2009 5:27 PM
Subject: Re: Jetspeed2 Installation
The user community is trying to fix up the documentation but we are very
early into the process.
There is a wiki where we are trying to get an outline of what we all
would have liked to have when we started.
http://wiki.apache.org/portals/Jetspeed2
It is an old unused wiki and I have started to clean out some of the old
stuff.
I have asked Hippo(Jetspeed developers) to update the roadmap on the
wiki.
If you have some suggestions about what you think we should create,
please let the group know.
I have some ideas about how the documentation should be organized to
allow different types of users to get the information that they need.
A person who is trying to run jetspeed "out of the box" with no
customization(evaluator for example) needs different information than a
developer who needs to modify the way that users login which is
different from the info required by someone who is going to build custom
portlets
I would like some discussion about this approach to see if we can build
a modular documentation set that will give us as much of a custom view
of the documentation as possible while minimizing the number of
overlapping documents.
We also need some high level documentation that can help evaluators to
understand what they are getting with Jetspeed, the underlying
architecture and when this the right way to go.
Ron
Stefano Bianchi wrote:
Hi all,
fine to hear you made it (at least start it), as I tried unsuccesfully
to do the same... no way to make it work on MySQL backend.
I used J1.X for several projects, but the time I am spending to
evaluate J2 is definitively too high...
My sincere congratulations to the developer team, nevertheless consider
it might be hard for "dummy" interested parties to start using J2.
My two cents, just a comment.
Be well,
Stefano
----- Original Message ----- From: "rache" <[email protected]>
To: <[email protected]>
Sent: Friday, May 08, 2009 10:55 AM
Subject: Jetspeed2 Installation
Hi,
I'm new to portals and I was able to install Jetspeed2 using the demo
installer jar.
I used Oracle XE as the database. The portal was fine except for some
portlets that are not working.
I have a couple of questions though.
I wanted to create my own portal following the JetExpress tutorial.
However, even if I use a different database for the 2nd portal i get
an
exception
on my container name not being unique; jetspeed - actionvalve bean
can't be
created due to this.
Even if I changed the name in the mvn command to use jetexpress, I
wonder
why its throwing this.
So I just installed a fresh Tomcat instance and used mysql as the 2nd
database.
Custom portal was deployed but I can't login using any of the
credentials
that comes along.
Its sayign that the DefaultLoginModule class can not be found.
I checked the tomcat lib folder and it has the security jar.
Any help will be greatly appreciated.
Thanks,
Rache
--
View this message in context:
http://www.nabble.com/Jetspeed2-Installation-tp23442409p23442409.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
