Kuiper Container/Driver/Testsuite added to sandbox

["David H. DeWolf" <dd...@apache.org>]

All,

As you can probably tell from all of the cvs commit messages, I've added 
the "kuiper" components to the pluto sandbox.  The kuiper container is a 
*possible* starting point for the next generation pluto implementation 
that's been discussed.

Along with the container, I've added a portal driver (it's struts based) 
and testsuite (the testsuite maven project actually just refers to 
pluto-1.0.1 testsuite that's already available).  The container is a 
*PROTOTYPE* of several of the ideas that we've discussed on this mailing 
list (but not all of them) - it is NOT yet fully compliant with the spec 
and should be considered nothing more than a whiteboard for what we 
*could* do.

I've added kuiper to the sandbox in hopes that others will provide their 
ideas, (as well as blood, sweat, and tears) of how kuiper should move 
forward.  I'm interested in all feedback/participation (even if it's 
"what the heck are you thinking!")

To install/test kuiper:

1) cd to the <pluto>/sandbox directory

2) invoke the maven "plugins" goal (prompt> maven plugins) - this will 
install the maven plugins that are necessary to deploy kuiper.  Once you 
have done this step you should never have to do it again.

3) make sure that your maven.tomcat.home property is set in your 
build.properties files (typically I do it in the one in my home 
directory so that it applies to all projects).]

4) invoke the maven "kuiper" goal (prompt> maven kuiper) - this will 
build and deploy to tomcat the kuiper-container, kuiper-driver, 
kuiper-testsuite and all dependencies.

5) start tomcat

6) cross your fingers

7) in a browser go to http://localhost:8080/kuiper (we assume that 
you've got a pretty clean install of tomcat that hasn't been customized 
must.  If you don't, then you probably know how to figure out the url 
you need ;) ).

I hope to put together some more documentation in the near future - 
specifically about integrating with "your" portal so that everyone can 
start to see the api and integration points.

Let me know of any questions and comments,

David

Re: Kuiper Container/Driver/Testsuite added to sandbox

[David Barral <da...@elrincondelprogramador.com>]

>> We're going to use Kuiper because the new approach is simpler and more 
>> straightforward, so the integration seems to be easier and cleaner.
> 
> 
> While I'm extremely glad to hear that you found Kuiper to be easier and 
> cleaner (that was the major purpose for it), I would not recommend that 
> you commit to using it.  Kuiper is nothing more than a prototype of 
> where one developer thinks Pluto should go.  It's really nothing more 
> than a whiteboard discussion put into code for the sake of validating an 
> approach and getting others on board with it. Furthermore, it comes 
> nowhere near implementing the full Portlet specification - we have a lot 
> of work left to get it there.

I see your point. Anyway we have protected ourselves from future 
changes. Our framework uses the container through our own API so both 
versions of Pluto (or any other container) could be plugged without any 
problems (at least that's what we hope xD).

Furthermore our framework is not intended for comercial purposes, it's 
focused on investigation so helping with the development of Pluto and 
suggesting improvements to the Portlet API are part of our goals.

Work is on progress. I'm sure that we'll send you some comments and 
questions soon.

-- 
David Barral
david@elrincondelprogramador.com

Re: Kuiper Container/Driver/Testsuite added to sandbox

["David H. DeWolf" <dd...@apache.org>]

David Barral wrote:

> We're going to use Kuiper because the new approach is simpler and more 
> straightforward, so the integration seems to be easier and cleaner.

While I'm extremely glad to hear that you found Kuiper to be easier and 
cleaner (that was the major purpose for it), I would not recommend that 
you commit to using it.  Kuiper is nothing more than a prototype of 
where one developer thinks Pluto should go.  It's really nothing more 
than a whiteboard discussion put into code for the sake of validating an 
approach and getting others on board with it. Furthermore, it comes 
nowhere near implementing the full Portlet specification - we have a lot 
of work left to get it there.

> Also, we would like to provide a lot of feedback if possible. As our 
> project moves on and code is developed we hope to send you useful comments.
> 

That would be EXCELLENT! All feedback will help us to build a better 
solution.  If this is a direction you'd like to see Pluto go, please 
feel free to support it by submitting patches (code or documentation). I 
can't garuntee that it'll be the commiters first priority to get Kuiper 
patches applied (we've committed to making a 1.0 release our priority - 
something I've slacked of in :( ), but the patches still would be 
appreciated and will help us determine the community's interest in 
switching directions.

David

> Regards,
> 
> David Barral
> david@elrincondelprogramador.com
> 

Re: Kuiper Container/Driver/Testsuite added to sandbox

[David Barral <da...@elrincondelprogramador.com>]

Hi.
We're currently integrating Pluto in our framework (see 
http://www.tic.udc.es/~fbellas/mypersonalizer/index.html currently 
updating the web with the last version).
We're going to use Kuiper because the new approach is simpler and more 
straightforward, so the integration seems to be easier and cleaner.
Also, we would like to provide a lot of feedback if possible. As our 
project moves on and code is developed we hope to send you useful comments.

Regards,

David Barral
david@elrincondelprogramador.com