If your application is so important to be considered career-ending,
you should give David a consulting contract to get him to help get you
started.
We were in the same situation with a project that had company-ending
potential with unreasonable timelines.
We contracted with David to get us started and we were able to meet the
timelines.
It was not very expensive and well worth the dollars, specially at the
beginning.
You can find products that are very easy to start with such as Liferay.
Some friends used that for a portal to support the administrative
functions of an on-line gambling site.
Went up fast but as soon as they started to need sophisticated
functionality, the portal development became very difficult and they
fought the system for the rest of its lifespan.
Short term happiness can sometimes be had, if you don't mind long term pain.
Jetspeed documentation is very difficult to use. It is designed to
document the range of functionality that is available.
It is not atypical for open source projects where the technical writers
are way too involved in the process and spend way too much time with
people of above-average intelligence who have the same backgrounds. They
assume that the rest of use must be that smart and have time to get
familiar with the inner workings of the tool.
In reality, we usually have our talents in other areas and only want to
know enough about the portal platform to get an application going.
But you can buy the expertise for a few dollars and you can get just as
much as you need to get you started.
Ron
On 20/07/2010 7:10 PM, David Sean Taylor wrote:
On Fri, Jul 16, 2010 at 2:00 PM, edingogh<[email protected]> wrote:
Woonsan:
That is the documentation I was talking about. The doc which is out-of-date
and innaccurate and incomplete.
Could you please provide examples to substantiate your claims of
"inaccurate" and "out-of-date" and "incomplete"?
Building the source is as easy as "svn checkout" and "mvn install".
The deployment options become a bit more involved, since there are
database properties required
But don't worry--I've wasted enough time with Jetspeed. I've come accross
many other devs who have discovered the same thing about Jetspeed 2's
documentation "issue" as they call it.
IMO, the documentation is pretty thorough for an open source project,
and btw I like Hunter S's books.. maybe thats the problem :-)
I have no more time to waste on it. I dread doing this, but I am going to
have to implement my own portal container from scratch to hit the deadline.
I can sense trying to use Jetspeed's documentation would be a career-ender.
Have you tried Pluto? Perhaps you can build your new portal based on
the Pluto portlet container, instead of writing an entire container
from scratch. There are also other open source portals: Gatein,
Liferay that you might want to check out. Just trying to help and be
friendly out here in open source
---------------------------------------------------------------------
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]
