From bridges-user-returnshelley94@example.net Thu Sep 13 11:11:01 2007
Return-Path: <bridges-user-returnshelley94@example.net>
Delivered-To: shelley94@example.net
Received: (qmail 20299 invoked from network); 13 Sep 2007 11:11:00 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155)
  by minotaur.apache.org with SMTP; 13 Sep 2007 11:11:00 -0000
Received: (qmail 78620 invoked by uid 500); 13 Sep 2007 11:10:53 -0000
Delivered-To: shelley94@example.net
Received: (qmail 78541 invoked by uid 500); 13 Sep 2007 11:10:53 -0000
Mailing-List: contact shelley94@example.net; run by ezmlm
Precedence: bulk
List-Help: <mailto:shelley94@example.net>
List-Unsubscribe: <mailto:shelley94@example.net>
List-Post: <mailto:shelley94@example.net>
List-Id: <bridges-user.portals.apache.org>
Reply-To: shelley94@example.net
Delivered-To: mailing list shelley94@example.net
Received: (qmail 78530 invoked by uid 99); 13 Sep 2007 11:10:53 -0000
Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Sep 2007 04:10:53 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of shelley94@example.net designates 83.161.120.155 as permitted sender)
Received: from [83.161.120.155] (HELO nf-out-0910.google.com) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Sep 2007 11:10:50 +0000
Received: by nf-out-0910.google.com with SMTP id e27so443431nfd
        for <shelley94@example.net>; Thu, 13 Sep 2007 04:10:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=beta;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        bh=KfLo6dsVeM6N+7+LODt+deFbQGEHkT/hF/4abU6hWzY=;
        b=PVo6KtEJUIVe6FXAwL+eVzacxLW05ja2oRkTUC1b4GDk/71iah7dZbgQ1wvFaJO9IgnsaQ1SDdrQW5nkx0H31HQObB+eUELlnPyEXt6YL3TrV0nf64ZuBEzyZeRyWLMPSB5dANSwGEW5TKeAekyF6XMN8gYKSjfJzU2nAMaWgXM=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=qV362gzQ1AqhXEJILchDAMnPy/QvRZTui3FdImDW/aPP7YsG6xHx0PLA905jcpeYynXQhOQIlVZcYYZHfaIefKVhJjyA+BR1jd0YNOfFQ3R/hds18Gd1nFelp25BJ5fsJYcVgN7bY6uDRMywyMYxTEn9MdtYGgwYVUz9j2onn88=
Received: by 83.161.120.155 with SMTP id u15mr462014fga.1189681827656;
        Thu, 13 Sep 2007 04:10:27 -0700 (PDT)
Received: by 83.161.120.155 with HTTP; Thu, 13 Sep 2007 04:10:27 -0700 (PDT)
Message-ID: <shelley94@example.net>
Date: Thu, 13 Sep 2007 13:10:27 +0200
From: "Karl Krukow" <shelley94@example.net>
To: shelley94@example.net
Subject: Portlet Bridge and AJAX
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Checked: Checked by ClamAV on apache.org

Hello,

I am having problems with implementing an portlet AJAX solution using
JSF and JSF Apache portlet bridge.

Specifically I am trying to implement an AJAX enabled JSF page using
the technique referenced in

http://java.sun.com/javaee/javaserverfaces/ajax/tutorial.jsp

Specifically I'm registering a PhaseListener to handle the AJAX requests.

This would work as in the tutorial in a non-portal context. However,
I'm having problems in my portal (WebSphere Portal v6.0) using the
org.apache.portals.bridges.jsf.FacesPortlet.

The problem is the following:

Client makes an XMLHttpRequest to the faces servlet
(javax.faces.webapp.FacesServlet) which eventually triggers my
PhaseListener. I guess this is already where something is wrong: The
FacesServlet throws an exception upon this request

[Faces Servlet]: java.lang.IllegalArgumentException: Only
PortletContext supported.

(Stacktrace below).

It seems that the SessionMap can only use a PortletRequest in its
constructs, which is apparently not what it is getting. So I guess
using the FacesServlet is wrong.

So which servlet should I use to route the AJAX through the faces
lifecycle in a portlet context?

Hope someone can help ;-)

Cheers,
- Karl

--- Techs ----
WebSphere Portal v6.0
Java1.4
MyFaces 1.1.5
Apache Portal Bridge: portals-bridges-common-1.0.3, portals-bridges-jsf.1.0.3


--- stacktrace for FacesServlet-----

[Faces Servlet]: java.lang.IllegalArgumentException: Only
PortletContext supported.
at org.apache.portals.bridges.jsf.SessionMap.<init>(SessionMap.java:56)
	at org.apache.portals.bridges.jsf.ServletExternalContextImpl.getSessionMap(ServletExternalContextImpl.java:230)
	at org.apache.myfaces.portlet.PortletUtil.isPortletRequest(PortletUtil.java:64)
	at org.apache.myfaces.lifecycle.RestoreViewExecutor.deriveViewId(RestoreViewExecutor.java:107)
	at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:57)
	at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:95)
	at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:70)
	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:139)

---------------------------------------------------------------------
To unsubscribe, e-mail: shelley94@example.net
For additional commands, e-mail: shelley94@example.net


From bridges-user-returnshelley94@example.net Thu Sep 13 11:19:24 2007
Return-Path: <bridges-user-returnshelley94@example.net>
Delivered-To: shelley94@example.net
Received: (qmail 21287 invoked from network); 13 Sep 2007 11:19:24 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155)
  by minotaur.apache.org with SMTP; 13 Sep 2007 11:19:24 -0000
Received: (qmail 84119 invoked by uid 500); 13 Sep 2007 11:19:17 -0000
Delivered-To: shelley94@example.net
Received: (qmail 84092 invoked by uid 500); 13 Sep 2007 11:19:17 -0000
Mailing-List: contact shelley94@example.net; run by ezmlm
Precedence: bulk
List-Help: <mailto:shelley94@example.net>
List-Unsubscribe: <mailto:shelley94@example.net>
List-Post: <mailto:shelley94@example.net>
List-Id: <bridges-user.portals.apache.org>
Reply-To: shelley94@example.net
Delivered-To: mailing list shelley94@example.net
Received: (qmail 84081 invoked by uid 99); 13 Sep 2007 11:19:17 -0000
Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Sep 2007 04:19:17 -0700
X-ASF-Spam-Status: No, hits=2.0 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: local policy)
Received: from [83.161.120.155] (HELO out.rilinfo.net) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Sep 2007 11:20:53 +0000
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq4HACq36Ebc4Vq5/2dsb2JhbACCPTY
Received: from unknown (HELO mailkol.wdc.in) ([83.161.120.155])
  by out.rilinfo.net with ESMTP; 13 Sep 2007 11:15:58 +0000
To: shelley94@example.net
Subject: Struts Bridge in Oracle Portal
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006
Message-ID: <shelley94@example.net>
From: Samir Sahu <shelley94@example.net>
Date: Thu, 13 Sep 2007 16:48:13 +0530
X-MIMETrack: Serialize by Router on mail/kol/wdc(Release 7.0.1FP1|April 17, 2006) at 09/13/2007
 04:48:16 PM,
	Serialize complete at 09/13/2007 04:48:16 PM
Content-Type: multipart/alternative; boundary="=_alternative 003E172F65257355_="
X-Virus-Checked: Checked by ClamAV on apache.org

--=_alternative 003E172F65257355_=
Content-Type: text/plain; charset="US-ASCII"

Hello Friends,

I am trying to use Apache Struts Bridge to create a JSR168 Struts Portlet 
in the Oracle Portal Server 10.

The problem is that Oracle Portal Server doesnot provide with a 
implementation class for the ServletContextProvider interface of the 
Apache Struts Bridge API.

Please help me, if this can be solved by any means. I need to use JSR 
compliant portlet only.


Samir Sahu
---------------------------------------------------------
Software Developer (Applications Services Group)
Web Development Company Limited
Website: - http://www.wdc.in
---------------------------------------------------------
--=_alternative 003E172F65257355_=--

From bridges-user-returnshelley94@example.net Thu Sep 13 17:54:46 2007
Return-Path: <bridges-user-returnshelley94@example.net>
Delivered-To: shelley94@example.net
Received: (qmail 50864 invoked from network); 13 Sep 2007 17:54:46 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155)
  by minotaur.apache.org with SMTP; 13 Sep 2007 17:54:46 -0000
Received: (qmail 80930 invoked by uid 500); 13 Sep 2007 17:54:39 -0000
Delivered-To: shelley94@example.net
Received: (qmail 80874 invoked by uid 500); 13 Sep 2007 17:54:39 -0000
Mailing-List: contact shelley94@example.net; run by ezmlm
Precedence: bulk
List-Help: <mailto:shelley94@example.net>
List-Unsubscribe: <mailto:shelley94@example.net>
List-Post: <mailto:shelley94@example.net>
List-Id: <bridges-user.portals.apache.org>
Reply-To: shelley94@example.net
Delivered-To: mailing list shelley94@example.net
Received: (qmail 80863 invoked by uid 99); 13 Sep 2007 17:54:39 -0000
Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Sep 2007 10:54:39 -0700
X-ASF-Spam-Status: No, hits=2.0 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of shelley94@example.net designates 83.161.120.155 as permitted sender)
Received: from [83.161.120.155] (HELO el-out-1112.google.com) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Sep 2007 17:54:37 +0000
Received: by el-out-1112.google.com with SMTP id z25so143214ele
        for <shelley94@example.net>; Thu, 13 Sep 2007 10:54:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=beta;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        bh=e/atseHih94EvnOBXGwctBBrw7YzdLzkwFfF7eQ978Y=;
        b=qsBOQxsg4zNQz5v4Ax52NZ4jHHjSven8WMmwIL65VCnu0vHVSOSe6pzuxYSib1VnrjjVtXl7+draHmwOqrls4w0NwykRCVMw3w8zEOzrrJCigK2hkE/XUUiFwM3nx1fYkaHMeMoTuXjew5usoNSqH/FIRE/QEKh2JJ1uHZtVNG8=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=e9AEf4qpT4JJBmT5lHXrUCJ0h99iGDyl6cbsxF7mQfp80pdDx1g0gYagbpZQugf+pOOv6QE5cpN7zgn+qYtma35Abfx0wxZGbfjyvKf+LorCiRRZPPG6mDrzejdVA1w2BR89G6YUZADd8v0sRy9EYp1EjKDedD1mvgDFyeVmOyE=
Received: by 83.161.120.155 with SMTP id e18mr169912wfd.1189706055865;
        Thu, 13 Sep 2007 10:54:15 -0700 (PDT)
Received: by 83.161.120.155 with HTTP; Thu, 13 Sep 2007 10:54:10 -0700 (PDT)
Message-ID: <shelley94@example.net>
Date: Thu, 13 Sep 2007 19:54:10 +0200
From: "Alonso Dominguez" <shelley94@example.net>
To: shelley94@example.net
Subject: Re: Portlet Bridge and AJAX
In-Reply-To: <shelley94@example.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_3082_6129976.1189706050856"
References: <shelley94@example.net>
X-Virus-Checked: Checked by ClamAV on apache.org

------=_Part_3082_6129976.1189706050856
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Karl, you may read this:

http://developers.sun.com/portalserver/reference/techart/ajax-portlets.html

2007/9/13, Karl Krukow <shelley94@example.net>:
>
> Hello,
>
> I am having problems with implementing an portlet AJAX solution using
> JSF and JSF Apache portlet bridge.
>
> Specifically I am trying to implement an AJAX enabled JSF page using
> the technique referenced in
>
> http://java.sun.com/javaee/javaserverfaces/ajax/tutorial.jsp
>
> Specifically I'm registering a PhaseListener to handle the AJAX requests.
>
> This would work as in the tutorial in a non-portal context. However,
> I'm having problems in my portal (WebSphere Portal v6.0) using the
> org.apache.portals.bridges.jsf.FacesPortlet.
>
> The problem is the following:
>
> Client makes an XMLHttpRequest to the faces servlet
> (javax.faces.webapp.FacesServlet) which eventually triggers my
> PhaseListener. I guess this is already where something is wrong: The
> FacesServlet throws an exception upon this request
>
> [Faces Servlet]: java.lang.IllegalArgumentException: Only
> PortletContext supported.
>
> (Stacktrace below).
>
> It seems that the SessionMap can only use a PortletRequest in its
> constructs, which is apparently not what it is getting. So I guess
> using the FacesServlet is wrong.
>
> So which servlet should I use to route the AJAX through the faces
> lifecycle in a portlet context?
>
> Hope someone can help ;-)
>
> Cheers,
> - Karl
>
> --- Techs ----
> WebSphere Portal v6.0
> Java1.4
> MyFaces 1.1.5
> Apache Portal Bridge: portals-bridges-common-1.0.3,
> portals-bridges-jsf.1.0.3
>
>
> --- stacktrace for FacesServlet-----
>
> [Faces Servlet]: java.lang.IllegalArgumentException: Only
> PortletContext supported.
> at org.apache.portals.bridges.jsf.SessionMap.<init>(SessionMap.java:56)
>         at
> org.apache.portals.bridges.jsf.ServletExternalContextImpl.getSessionMap(
> ServletExternalContextImpl.java:230)
>         at org.apache.myfaces.portlet.PortletUtil.isPortletRequest(
> PortletUtil.java:64)
>         at org.apache.myfaces.lifecycle.RestoreViewExecutor.deriveViewId(
> RestoreViewExecutor.java:107)
>         at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(
> RestoreViewExecutor.java:57)
>         at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(
> LifecycleImpl.java:95)
>         at org.apache.myfaces.lifecycle.LifecycleImpl.execute(
> LifecycleImpl.java:70)
>         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:139)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: shelley94@example.net
> For additional commands, e-mail: shelley94@example.net
>
>

------=_Part_3082_6129976.1189706050856--

From bridges-user-returnshelley94@example.net Fri Sep 14 04:51:05 2007
Return-Path: <bridges-user-returnshelley94@example.net>
Delivered-To: shelley94@example.net
Received: (qmail 57482 invoked from network); 14 Sep 2007 04:51:05 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155)
  by minotaur.apache.org with SMTP; 14 Sep 2007 04:51:05 -0000
Received: (qmail 24543 invoked by uid 500); 14 Sep 2007 04:50:58 -0000
Delivered-To: shelley94@example.net
Received: (qmail 24523 invoked by uid 500); 14 Sep 2007 04:50:58 -0000
Mailing-List: contact shelley94@example.net; run by ezmlm
Precedence: bulk
List-Help: <mailto:shelley94@example.net>
List-Unsubscribe: <mailto:shelley94@example.net>
List-Post: <mailto:shelley94@example.net>
List-Id: <bridges-user.portals.apache.org>
Reply-To: shelley94@example.net
Delivered-To: mailing list shelley94@example.net
Received: (qmail 24512 invoked by uid 99); 14 Sep 2007 04:50:57 -0000
Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Sep 2007 21:50:57 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of shelley94@example.net designates 83.161.120.155 as permitted sender)
Received: from [83.161.120.155] (HELO mu-out-0910.google.com) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Sep 2007 04:50:56 +0000
Received: by mu-out-0910.google.com with SMTP id i2so896889mue
        for <shelley94@example.net>; Thu, 13 Sep 2007 21:50:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=beta;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        bh=BsFLhht6SN13g6uimxg5unNR9uwf1ElhopJJe5H81gU=;
        b=QE0qqGuGRX9FkDGpR2cnFZURSX5JGfcFohfHC0hCre3X0A+bUStCG9JWhCs5pAmX9xgdXH3GBrGqaYyOIAuBXWJCitYNwMgM5Fel0a1tleo8MK/Sv2+WcRmokgtM9KvcBYXQSB5R/5jGn6NfIa+5fU1MMmY2IWYe4B3il1sdzm0=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=onWogSqGYxRSwhgCQN8+JvFy8ETCgi3HGTarxJd+H449BWbsIV/+bN66Cds90/2pacUITy56CvaO86K4DO0RMkfZiLJESm4n4P7wPus+H9Az5bhzYAaoL1g3wHw/gREnj10q95axsGV1tHliEbjRRDOEOPRVHIaw17xbx9Uoy7E=
Received: by 83.161.120.155 with SMTP id 2mr1109743fgd.1189745432590;
        Thu, 13 Sep 2007 21:50:32 -0700 (PDT)
Received: by 83.161.120.155 with HTTP; Thu, 13 Sep 2007 21:50:32 -0700 (PDT)
Message-ID: <shelley94@example.net>
Date: Fri, 14 Sep 2007 06:50:32 +0200
From: "Karl Krukow" <shelley94@example.net>
To: shelley94@example.net
Subject: Re: Portlet Bridge and AJAX
In-Reply-To: <shelley94@example.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <shelley94@example.net>
	 <shelley94@example.net>
X-Virus-Checked: Checked by ClamAV on apache.org

Thanks for the pointer Alonso; in fact, I have already read the paper.
Unfortunately, it doesn't help with my problem: I want the AJAX
handler to be a JSF PhaseListener and not a servlet. Why? Because then
the AJAX handler can access the FacesContext and update faces UI
components, apply validators etc., ie take advantage of the JSF
framework. With an AJAX -> Servlet I can't access FacesContext so I
would be by-passing faces altogether.

Since I wrote the original post, I noticed there is a JIRA issue:

http://issues.apache.org/jira/browse/PB-73

Does anyone know

a) if that Jira would solve my problem?

b) when would the issue be solved? (I noticed the JIRA had a patch with it).

Cheers,
- Karl

On 9/13/07, Alonso Dominguez <shelley94@example.net> wrote:
> Hi Karl, you may read this:
>
> http://developers.sun.com/portalserver/reference/techart/ajax-portlets.html
>
> 2007/9/13, Karl Krukow <shelley94@example.net>:
> >
> > Hello,
> >
> > I am having problems with implementing an portlet AJAX solution using
> > JSF and JSF Apache portlet bridge.
> >
> > Specifically I am trying to implement an AJAX enabled JSF page using
> > the technique referenced in
> >
> > http://java.sun.com/javaee/javaserverfaces/ajax/tutorial.jsp
> >
> > Specifically I'm registering a PhaseListener to handle the AJAX requests.
> >
> > This would work as in the tutorial in a non-portal context. However,
> > I'm having problems in my portal (WebSphere Portal v6.0) using the
> > org.apache.portals.bridges.jsf.FacesPortlet.
> >
> > The problem is the following:
> >
> > Client makes an XMLHttpRequest to the faces servlet
> > (javax.faces.webapp.FacesServlet) which eventually triggers my
> > PhaseListener. I guess this is already where something is wrong: The
> > FacesServlet throws an exception upon this request
> >
> > [Faces Servlet]: java.lang.IllegalArgumentException: Only
> > PortletContext supported.
> >
> > (Stacktrace below).
> >
> > It seems that the SessionMap can only use a PortletRequest in its
> > constructs, which is apparently not what it is getting. So I guess
> > using the FacesServlet is wrong.
> >
> > So which servlet should I use to route the AJAX through the faces
> > lifecycle in a portlet context?
> >
> > Hope someone can help ;-)
> >
> > Cheers,
> > - Karl
> >
> > --- Techs ----
> > WebSphere Portal v6.0
> > Java1.4
> > MyFaces 1.1.5
> > Apache Portal Bridge: portals-bridges-common-1.0.3,
> > portals-bridges-jsf.1.0.3
> >
> >
> > --- stacktrace for FacesServlet-----
> >
> > [Faces Servlet]: java.lang.IllegalArgumentException: Only
> > PortletContext supported.
> > at org.apache.portals.bridges.jsf.SessionMap.<init>(SessionMap.java:56)
> >         at
> > org.apache.portals.bridges.jsf.ServletExternalContextImpl.getSessionMap(
> > ServletExternalContextImpl.java:230)
> >         at org.apache.myfaces.portlet.PortletUtil.isPortletRequest(
> > PortletUtil.java:64)
> >         at org.apache.myfaces.lifecycle.RestoreViewExecutor.deriveViewId(
> > RestoreViewExecutor.java:107)
> >         at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(
> > RestoreViewExecutor.java:57)
> >         at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(
> > LifecycleImpl.java:95)
> >         at org.apache.myfaces.lifecycle.LifecycleImpl.execute(
> > LifecycleImpl.java:70)
> >         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:139)
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: shelley94@example.net
> > For additional commands, e-mail: shelley94@example.net
> >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: shelley94@example.net
For additional commands, e-mail: shelley94@example.net


From bridges-user-returnshelley94@example.net Fri Sep 14 10:31:14 2007
Return-Path: <bridges-user-returnshelley94@example.net>
Delivered-To: shelley94@example.net
Received: (qmail 63066 invoked from network); 14 Sep 2007 10:31:14 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155)
  by minotaur.apache.org with SMTP; 14 Sep 2007 10:31:14 -0000
Received: (qmail 94017 invoked by uid 500); 14 Sep 2007 10:31:07 -0000
Delivered-To: shelley94@example.net
Received: (qmail 93997 invoked by uid 500); 14 Sep 2007 10:31:07 -0000
Mailing-List: contact shelley94@example.net; run by ezmlm
Precedence: bulk
List-Help: <mailto:shelley94@example.net>
List-Unsubscribe: <mailto:shelley94@example.net>
List-Post: <mailto:shelley94@example.net>
List-Id: <bridges-user.portals.apache.org>
Reply-To: shelley94@example.net
Delivered-To: mailing list shelley94@example.net
Received: (qmail 93986 invoked by uid 99); 14 Sep 2007 10:31:07 -0000
Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Sep 2007 03:31:07 -0700
X-ASF-Spam-Status: No, hits=2.0 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of shelley94@example.net designates 83.161.120.155 as permitted sender)
Received: from [83.161.120.155] (HELO rv-out-0910.google.com) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Sep 2007 10:31:02 +0000
Received: by rv-out-0910.google.com with SMTP id k20so568403rvb
        for <shelley94@example.net>; Fri, 14 Sep 2007 03:30:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=beta;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        bh=hE5MXUGNYDWqgZSGtwaKRY0KJCKncGfkiaf5C6QfQTY=;
        b=lzcq+dbx+xghPIW8+QLpstyDe8giXmUNzXzbaFCy5q8ocQPCRFvJfldg3aHyIO0qUrc/qCv8jJ2QgXt8ELGhDfKgp4GaO4wQ4bPPbwh6BvzlesUJBe6l2CiJulO3stkP9J2Rl9fAt2cXz1HE4X/8WXBm7jg3RmytrbbzXEKGKvo=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=qe1lf4wmXaYadKqnDt/dbqSvggxNLz/+xyMcN4mK6ocsDCZ5v08cZjeMI/z08mOJRDbRKmFoKJoJbm0aisdk9yCrjlUw47292l+kwXIMo8kP9skbo4brIlGTfBNt+8a1o64XwvchO9NRnkU4bgGXYeyquKJlLT55ieNHQqtElRM=
Received: by 83.161.120.155 with SMTP id n1mr1636287wak.1189765841747;
        Fri, 14 Sep 2007 03:30:41 -0700 (PDT)
Received: by 83.161.120.155 with HTTP; Fri, 14 Sep 2007 03:30:41 -0700 (PDT)
Message-ID: <shelley94@example.net>
Date: Fri, 14 Sep 2007 12:30:41 +0200
From: "Alonso Dominguez" <shelley94@example.net>
To: shelley94@example.net
Subject: Re: Portlet Bridge and AJAX
In-Reply-To: <shelley94@example.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_3116_20879049.1189765841690"
References: <shelley94@example.net>
	 <shelley94@example.net>
	 <shelley94@example.net>
X-Virus-Checked: Checked by ClamAV on apache.org

------=_Part_3116_20879049.1189765841690
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Thanks for pointing me to that issue. It seems that the reason for your
problem is specified at that issue on point 3:

3) the SessionMap/RequestParameterMap etc. will only work if behind a
portlet. In some cases, the JSF-app might run both behind a portlet and a
servlet

I don't know much about Apache JSF Portlet Bridge but I think that bridge
doesn't implements correctly the JSR-301 (JSF Portlet Bridge Spec). You can
try other JSF Portlet Bridge impls, i.e.: Jsf 4 Portlets (
jsf4portlets.sf.net), jsfportletbridge (http://jsfportletbridge.dev.java.net).

I'm currently working on implementing the JSR-301 at those projects, work is
not finished yet but you can do a checkout againts its source repositories.

Regards,
Alonso

2007/9/14, Karl Krukow <shelley94@example.net>:
>
> Thanks for the pointer Alonso; in fact, I have already read the paper.
> Unfortunately, it doesn't help with my problem: I want the AJAX
> handler to be a JSF PhaseListener and not a servlet. Why? Because then
> the AJAX handler can access the FacesContext and update faces UI
> components, apply validators etc., ie take advantage of the JSF
> framework. With an AJAX -> Servlet I can't access FacesContext so I
> would be by-passing faces altogether.
>
> Since I wrote the original post, I noticed there is a JIRA issue:
>
> http://issues.apache.org/jira/browse/PB-73
>
> Does anyone know
>
> a) if that Jira would solve my problem?
>
> b) when would the issue be solved? (I noticed the JIRA had a patch with
> it).
>
> Cheers,
> - Karl
>
> On 9/13/07, Alonso Dominguez <shelley94@example.net> wrote:
> > Hi Karl, you may read this:
> >
> >
> http://developers.sun.com/portalserver/reference/techart/ajax-portlets.html
> >
> > 2007/9/13, Karl Krukow <shelley94@example.net>:
> > >
> > > Hello,
> > >
> > > I am having problems with implementing an portlet AJAX solution using
> > > JSF and JSF Apache portlet bridge.
> > >
> > > Specifically I am trying to implement an AJAX enabled JSF page using
> > > the technique referenced in
> > >
> > > http://java.sun.com/javaee/javaserverfaces/ajax/tutorial.jsp
> > >
> > > Specifically I'm registering a PhaseListener to handle the AJAX
> requests.
> > >
> > > This would work as in the tutorial in a non-portal context. However,
> > > I'm having problems in my portal (WebSphere Portal v6.0) using the
> > > org.apache.portals.bridges.jsf.FacesPortlet.
> > >
> > > The problem is the following:
> > >
> > > Client makes an XMLHttpRequest to the faces servlet
> > > (javax.faces.webapp.FacesServlet) which eventually triggers my
> > > PhaseListener. I guess this is already where something is wrong: The
> > > FacesServlet throws an exception upon this request
> > >
> > > [Faces Servlet]: java.lang.IllegalArgumentException: Only
> > > PortletContext supported.
> > >
> > > (Stacktrace below).
> > >
> > > It seems that the SessionMap can only use a PortletRequest in its
> > > constructs, which is apparently not what it is getting. So I guess
> > > using the FacesServlet is wrong.
> > >
> > > So which servlet should I use to route the AJAX through the faces
> > > lifecycle in a portlet context?
> > >
> > > Hope someone can help ;-)
> > >
> > > Cheers,
> > > - Karl
> > >
> > > --- Techs ----
> > > WebSphere Portal v6.0
> > > Java1.4
> > > MyFaces 1.1.5
> > > Apache Portal Bridge: portals-bridges-common-1.0.3,
> > > portals-bridges-jsf.1.0.3
> > >
> > >
> > > --- stacktrace for FacesServlet-----
> > >
> > > [Faces Servlet]: java.lang.IllegalArgumentException: Only
> > > PortletContext supported.
> > > at org.apache.portals.bridges.jsf.SessionMap.<init>(SessionMap.java
> :56)
> > >         at
> > >
> org.apache.portals.bridges.jsf.ServletExternalContextImpl.getSessionMap(
> > > ServletExternalContextImpl.java:230)
> > >         at org.apache.myfaces.portlet.PortletUtil.isPortletRequest(
> > > PortletUtil.java:64)
> > >         at
> org.apache.myfaces.lifecycle.RestoreViewExecutor.deriveViewId(
> > > RestoreViewExecutor.java:107)
> > >         at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(
> > > RestoreViewExecutor.java:57)
> > >         at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(
> > > LifecycleImpl.java:95)
> > >         at org.apache.myfaces.lifecycle.LifecycleImpl.execute(
> > > LifecycleImpl.java:70)
> > >         at javax.faces.webapp.FacesServlet.service(FacesServlet.java
> :139)
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: shelley94@example.net
> > > For additional commands, e-mail: shelley94@example.net
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: shelley94@example.net
> For additional commands, e-mail: shelley94@example.net
>
>

------=_Part_3116_20879049.1189765841690--

From bridges-user-returnshelley94@example.net Fri Sep 14 13:37:51 2007
Return-Path: <bridges-user-returnshelley94@example.net>
Delivered-To: shelley94@example.net
Received: (qmail 45448 invoked from network); 14 Sep 2007 13:37:51 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155)
  by minotaur.apache.org with SMTP; 14 Sep 2007 13:37:51 -0000
Received: (qmail 8774 invoked by uid 500); 14 Sep 2007 13:37:44 -0000
Delivered-To: shelley94@example.net
Received: (qmail 8759 invoked by uid 500); 14 Sep 2007 13:37:44 -0000
Mailing-List: contact shelley94@example.net; run by ezmlm
Precedence: bulk
List-Help: <mailto:shelley94@example.net>
List-Unsubscribe: <mailto:shelley94@example.net>
List-Post: <mailto:shelley94@example.net>
List-Id: <bridges-user.portals.apache.org>
Reply-To: shelley94@example.net
Delivered-To: mailing list shelley94@example.net
Received: (qmail 8748 invoked by uid 99); 14 Sep 2007 13:37:44 -0000
Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Sep 2007 06:37:44 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: local policy)
Received: from [83.161.120.155] (HELO mail80.jndata.dk) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Sep 2007 13:39:23 +0000
Received: by mail80.jndata.dk; Fri, 14 Sep 2007 15:37:18 +0200
Received: by sjn00077.jndata.local; Fri, 14 Sep 2007 15:37:18 +0200
Received: by mail81.jndata.dk; Fri, 14 Sep 2007 15:37:18 +0200
Received: from DA1633.JBMAIN00.CORP.JYSKEBANK.NET ([83.161.120.155]) by da1444.JBMAIN00.CORP.JYSKEBANK.NET with Microsoft SMTPSVC+1-341-443-6631);
	 Fri, 14 Sep 2007 15:37:18 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: SV: Portlet Bridge and AJAX
Date: Fri, 14 Sep 2007 15:37:18 +0200
Message-ID: <shelley94@example.net>
In-Reply-To: <shelley94@example.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Portlet Bridge and AJAX
Thread-Index: Acf2umhol0sJuT/FTyKs8YULyxQruwAGev/g
From: "Karl Krukow" <shelley94@example.net>
To: <shelley94@example.net>
X-OriginalArrivalTime: 14 Sep 2007 13:37:18.0296 (UTC) FILETIME=[5E8A2580:01C7F6D4]
X-Virus-Checked: Checked by ClamAV on apache.org

Thanks for the references, I will check them out.


Cheers,
- Karl=20

-----Oprindelig meddelelse-----
Fra: Alonso Dominguez [mailto:shelley94@example.net]=20
Sendt: 14. september 2007 12:31
Til: shelley94@example.net
Emne: Re: Portlet Bridge and AJAX

Thanks for pointing me to that issue. It seems that the reason for your
problem is specified at that issue on point 3:

3) the SessionMap/RequestParameterMap etc. will only work if behind a
portlet. In some cases, the JSF-app might run both behind a portlet and
a servlet

I don't know much about Apache JSF Portlet Bridge but I think that
bridge doesn't implements correctly the JSR-301 (JSF Portlet Bridge
Spec). You can try other JSF Portlet Bridge impls, i.e.: Jsf 4 Portlets
( jsf4portlets.sf.net), jsfportletbridge
(http://jsfportletbridge.dev.java.net).

I'm currently working on implementing the JSR-301 at those projects,
work is not finished yet but you can do a checkout againts its source
repositories.

Regards,
Alonso

2007/9/14, Karl Krukow <shelley94@example.net>:
>
> Thanks for the pointer Alonso; in fact, I have already read the paper.
> Unfortunately, it doesn't help with my problem: I want the AJAX=20
> handler to be a JSF PhaseListener and not a servlet. Why? Because then

> the AJAX handler can access the FacesContext and update faces UI=20
> components, apply validators etc., ie take advantage of the JSF=20
> framework. With an AJAX -> Servlet I can't access FacesContext so I=20
> would be by-passing faces altogether.
>
> Since I wrote the original post, I noticed there is a JIRA issue:
>
> http://issues.apache.org/jira/browse/PB-73
>
> Does anyone know
>
> a) if that Jira would solve my problem?
>
> b) when would the issue be solved? (I noticed the JIRA had a patch=20
> with it).
>
> Cheers,
> - Karl
>
> On 9/13/07, Alonso Dominguez <shelley94@example.net> wrote:
> > Hi Karl, you may read this:
> >
> >
> http://developers.sun.com/portalserver/reference/techart/ajax-portlets
> .html
> >
> > 2007/9/13, Karl Krukow <shelley94@example.net>:
> > >
> > > Hello,
> > >
> > > I am having problems with implementing an portlet AJAX solution=20
> > > using JSF and JSF Apache portlet bridge.
> > >
> > > Specifically I am trying to implement an AJAX enabled JSF page=20
> > > using the technique referenced in
> > >
> > > http://java.sun.com/javaee/javaserverfaces/ajax/tutorial.jsp
> > >
> > > Specifically I'm registering a PhaseListener to handle the AJAX
> requests.
> > >
> > > This would work as in the tutorial in a non-portal context.=20
> > > However, I'm having problems in my portal (WebSphere Portal v6.0)=20
> > > using the org.apache.portals.bridges.jsf.FacesPortlet.
> > >
> > > The problem is the following:
> > >
> > > Client makes an XMLHttpRequest to the faces servlet
> > > (javax.faces.webapp.FacesServlet) which eventually triggers my=20
> > > PhaseListener. I guess this is already where something is wrong:=20
> > > The FacesServlet throws an exception upon this request
> > >
> > > [Faces Servlet]: java.lang.IllegalArgumentException: Only=20
> > > PortletContext supported.
> > >
> > > (Stacktrace below).
> > >
> > > It seems that the SessionMap can only use a PortletRequest in its=20
> > > constructs, which is apparently not what it is getting. So I guess

> > > using the FacesServlet is wrong.
> > >
> > > So which servlet should I use to route the AJAX through the faces=20
> > > lifecycle in a portlet context?
> > >
> > > Hope someone can help ;-)
> > >
> > > Cheers,
> > > - Karl
> > >
> > > --- Techs ----
> > > WebSphere Portal v6.0
> > > Java1.4
> > > MyFaces 1.1.5
> > > Apache Portal Bridge: portals-bridges-common-1.0.3,
> > > portals-bridges-jsf.1.0.3
> > >
> > >
> > > --- stacktrace for FacesServlet-----
> > >
> > > [Faces Servlet]: java.lang.IllegalArgumentException: Only=20
> > > PortletContext supported.
> > > at=20
> > > org.apache.portals.bridges.jsf.SessionMap.<init>(SessionMap.java
> :56)
> > >         at
> > >
> org.apache.portals.bridges.jsf.ServletExternalContextImpl.getSessionMa
> p(
> > > ServletExternalContextImpl.java:230)
> > >         at=20
> > > org.apache.myfaces.portlet.PortletUtil.isPortletRequest(
> > > PortletUtil.java:64)
> > >         at
> org.apache.myfaces.lifecycle.RestoreViewExecutor.deriveViewId(
> > > RestoreViewExecutor.java:107)
> > >         at=20
> > > org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(
> > > RestoreViewExecutor.java:57)
> > >         at=20
> > > org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(
> > > LifecycleImpl.java:95)
> > >         at org.apache.myfaces.lifecycle.LifecycleImpl.execute(
> > > LifecycleImpl.java:70)
> > >         at=20
> > > javax.faces.webapp.FacesServlet.service(FacesServlet.java
> :139)
> > >
> > > ------------------------------------------------------------------
> > > --- To unsubscribe, e-mail:=20
> > > shelley94@example.net
> > > For additional commands, e-mail:=20
> > > shelley94@example.net
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: shelley94@example.net
> For additional commands, e-mail: shelley94@example.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: shelley94@example.net
For additional commands, e-mail: shelley94@example.net



{'source': 'Apache Software Foundation Public Mail Archives'}