You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by Stefan Hepper <st...@hursley.ibm.com> on 2003/11/11 21:22:02 UTC
Re: some discussion about pluto from other forum
Yes, I think that is true, as I think you can only claim compliance for
products. And if you integrate a component (pluto) that is certified you
still need to re-test the product to be able to claim JSR 168
compliance. In case of the JSR 168 tests that somehow makes sense, as
the tests also rely on a portal driving the container, which was one of
the reasons (besides having something to play around) to create the
portalImpl. If you now only take the pluto container and replace the
portalImpl you need to show that your portal implementation does not
break anything.
Stefan
jeffrey z. lee wrote:
> Hi everyone,
>
> I read discussion slightly about pluto from
> http://www.theserverside.com/home/thread.jsp?thread_id=22209
>
> ###
>
> Note that Jetspeed 1.4 DOES NOT use pluto as its portlet container.
> This will only be the case for Jetspeed2.
> So actually if you want a portal that uses a portlet container that is a
> JSR 168 Open Source implementation (still need to get the TCK from Sun
> to claim compliance) look at ... ok you already know where to look after
> my article on TSS.
> ###
> do you think " still need to get the TCK from Sun to claim compliance"
> is right ?
>
> jeffrey z. lee
> jeffreyzlee@hotmail.com
>
> ------------------------------------------------------------------------
> Protect your PC - Click here <http://g.msn.com/8HMBENCA/2755??PS=> for
> McAfee.com VirusScan Online