JetSpeed SPI portability

[mo...@accenture.com]

Hi,

       I'd like to ask this question again hoping to find an answer. 

 

I am trying to understand if code written to JetSpeed SPI to create
services( like Websphere portal ) is portable. Should I assume that only
JSR 168 API code is portable ? What about JetSpeed SPI ?

 

Thanks,

Mohan

 



This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information.  If you have received it in error, please notify the sender immediately and delete the original.  Any other use of the email by you is prohibited.

Re: JetSpeed SPI portability

[Ate Douma <at...@douma.nu>]

mohan.radhakrishnan@accenture.com wrote:
> Hi,
> 
>        I’d like to ask this question again hoping to find an answer.
You're barking up the wrong tree, why didn't you ask on the Jetspeed user list?

> 
>  
> 
> I am trying to understand if code written to JetSpeed SPI to create 
> services( like Websphere portal ) is portable. Should I assume that only 
> JSR 168 API code is portable ? What about JetSpeed SPI ?
As you probably already understand, the jetspeed-api is primarily intended to be used with the jetspeed portal.
But, as jetspeed is build up as a fully Springframework managed set of collaborating components, you might be able to
isolate some components and be able to use them standalone or even integrated within a different portal engine.
Jetspeed-1.6 Fusion is a nice example of that: although Jetspeed-1 has a completely different architecture and Jetspeed-2
doesn't share a single line of code with Jetspeed-1, Jetspeed-1.6 Fusion uses Jetspeed-2 embedded so it now too can run
JSR-168 compliant portlets.

> 
>  
> 
> Thanks,
> 
> Mohan
> 
>  
> 
> This message is for the designated recipient only and may contain 
> privileged, proprietary, or otherwise private information. If you have 
> received it in error, please notify the sender immediately and delete 
> the original. Any other use of the email by you is prohibited.
>