I've just set up a WSAD sample project with a basic JSR 168 portlet.

When I try to run it on a test server in WSAD it says "this function is not 
supported for portlet (JSR 168) project" and the server status shows "incomp
atible".

I found this comment in the Portal Infocenter - "The Portlet API provided in
 WebSphere Portal is the first step toward the Portlet API standardization" 
- next to a link to the JSR 168 spec.

Am I right to assume that Websphere Portal 5.0.2 does not support JSR 168 ? 

Martin

[ Post a follow-up to this message ]

Hi Martin

You can deploy JSR168 portlets to WebSphere Portal v5.0.2, providing that
the portal server is running as a stand-alone installation i.e. not via the
Portal Test Environment. JSR168 is currently available as a technology
preview
(http://www-106.ibm.com/developerwor...ads/jsr168.html).
Full support should be available in a future release of the product.

It's also worth noting that, by default, the portlet container for JSR168 is
disabled on WebSphere Portal V5.0.2. The container is enabled by the
following setting in ConfigService.properties in the
wp_root/shared/app/config/services directory: -

portal.enable.jsr168 = true

and then restarting the Portal server.

There's also an eFix available for Portal v5.0.2 at: -

http://www-1.ibm.com/support/docvie...uid=swg24005598

which you should apply (this is also shipped with Portal v5.0.2).

Regards

Dave Hay




"griffett" <griffett.139qxj@mail.webservertalk.com> wrote in message
news:griffett.139qxj@mail.webservertalk.com...
>
> I've just set up a WSAD sample project with a basic JSR 168 portlet.
>
> When I try to run it on a test server in WSAD it says "this function is
> not supported for portlet (JSR 168) project" and the server status
> shows "incompatible".
>
> I found this comment in the Portal Infocenter - "The Portlet API
> provided in WebSphere Portal is the first step toward the Portlet API
> standardization" - next to a link to the JSR 168 spec.
>
> Am I right to assume that Websphere Portal 5.0.2 does not support JSR
> 168 ?
>
> *_Martin_*
>
>
>
> --
> griffett
> ------------------------------------------------------------------------
> Posted via http://www.webservertalk.com
> ------------------------------------------------------------------------
> View this thread: http://www.webservertalk.com/message152616.html
>

[ Post a follow-up to this message ]

Have you seen the Portal Toolkit page?
http://www-306.ibm.com/software/inf...&S_CMP=campaign
The page says "Portal Test environment does not support JSR 168 portlet debu
gging . You must use a remote server to debug your JSR 168 portlet. "

[ Post a follow-up to this message ]

For good comparison of jsr168 and wps502 read:
http://www-106.ibm.com/developerwor...403_hepper.html

[ Post a follow-up to this message ]

Hi All,

I ran into problem when upgrading to Portal toolkit v5.02.
I have installed 

    1. WAS 5.0
    2. WSAD 5.0 and upgrade to 5.0.1
    3. WAS 5 PTF to the WebSphere Test Environment
    4. WAS 5 interim fixes
    5. Portal toolkit 5.0
    6. WebSphere Portal 5.0 for Test Environment

I am wondering whether this "You can deploy JSR168 portlets to WebSphere Por
tal v5.0.2, providing that the portal server is running as a stand-alone ins
tallation i.e. not via the Portal Test Environment" applies to my settings?

Does that mean I am not going to deploy JSR168 portlet even
I upgrade to portal toolkit v5.02?

your help is appreciated
Allen


quote:
Originally posted by Dave Hay 
Hi Martin

You can deploy JSR168 portlets to WebSphere Portal v5.0.2, providing that
the portal server is running as a stand-alone installation i.e. not via the
Portal Test Environment. JSR168 is currently available as a technology
preview
(http://www-106.ibm.com/developerwor...ads/jsr168.html).
Full support should be available in a future release of the product.

It's also worth noting that, by default, the portlet container for JSR168 is
disabled on WebSphere Portal V5.0.2. The container is enabled by the
following setting in ConfigService.properties in the
wp_root/shared/app/config/services directory: -

portal.enable.jsr168 = true

and then restarting the Portal server.

There's also an eFix available for Portal v5.0.2 at: -

http://www-1.ibm.com/support/docvie...uid=swg24005598

which you should apply (this is also shipped with Portal v5.0.2).

Regards

Dave Hay




"griffett" <griffett.139qxj@mail.webservertalk.com> wrote in message
news:griffett.139qxj@mail.webservertalk.com...
>
> I've just set up a WSAD sample project with a basic JSR 168 portlet.
>
> When I try to run it on a test server in WSAD it says "this function is
> not supported for portlet (JSR 168) project" and the server status
> shows "incompatible".
>
> I found this comment in the Portal Infocenter - "The Portlet API
> provided in WebSphere Portal is the first step toward the Portlet API
> standardization" - next to a link to the JSR 168 spec.
>
> Am I right to assume that Websphere Portal 5.0.2 does not support JSR
> 168 ?
>
> *_Martin_*
>
>
>
> --
> griffett
> ------------------------------------------------------------------------
> Posted via http://www.webservertalk.com
> ------------------------------------------------------------------------
> View this thread: http://www.webservertalk.com/message152616.html
> 

[ Post a follow-up to this message ]