You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@openwebbeans.apache.org by Sven Linstaedt <sv...@googlemail.com> on 2009/08/31 11:26:42 UTC

Testing OWB against JSF 2.0 RI ?

Hi,

I suppose OWB should also work with JSF 2.0, even the examples currently use
JSF 1.x. Today I tried to check out some of the new JSF 2 features and run
into various problems (in other words: exceptions). Is there someone already
tried to use this combination of frameworks and give me a hint, if the
web.xml and faces-config.xml setup differs between usage of OWB in JSF 1.x
and JSF 2.0?

br, sven

Re: Testing OWB against JSF 2.0 RI ?

Posted by Gurkan Erdogdu <gu...@yahoo.com>.

Hi Sven;

>>However as I am further determining features and benefits of the duo
OWB + JSF 2.0 RI in webapplications, I can update you about usage of
these both >>together, if you want.

Yeah, it will be fine. Also it is very good idea to run our samples via JSF 2.0. Please also share your experience with our dev@ list.

Thanks a lot;

--Gurkan




________________________________
From: Sven Linstaedt <sv...@googlemail.com>
To: openwebbeans-user@incubator.apache.org
Sent: Monday, August 31, 2009 7:00:05 PM
Subject: Re: Testing OWB against JSF 2.0 RI ?

Actually it turns out, the OWB exceptions were caused by JSF 2.0 RI by dispatching resource request to a full jsf lifecycle, if the FacesServlet is prefix mapped to the application's root. Because the request has no viewstate attached and the URI could not be resolved to a metadata view the viewroot is null, so JSFUtil.isPostBack() fails.

However as I am further determining features and benefits of the duo OWB + JSF 2.0 RI in webapplications, I can update you about usage of these both together, if you want.

br, Sven




javax.faces.FacesException
    at com.sun.faces.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:136)
    at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:115)
    at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:110)
    at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
    at javax.faces.webapp.FacesServlet.service(FacesServlet.java:310)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
    at org.apache.webbeans.jsf.WebBeansJSFFilter.doFilter(WebBeansJSFFilter.java:79)
    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:387)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:326)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:539)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
Caused by: java.lang.NullPointerException
    at org.apache.webbeans.util.JSFUtil.isPostBack(JSFUtil.java:50)
    at org.apache.webbeans.jsf.WebBeansPhaseListener.afterPhase(WebBeansPhaseListener.java:46)
    at com.sun.faces.lifecycle.Phase.handleAfterPhase(Phase.java:179)
    at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:103)
    ... 23 more




2009/8/31 Gurkan Erdogdu <cg...@gmail.com>

Hi Sven;
>
>Last time Matthias Wessendorf from MyFaces Project also tried to use JSF 2.0 with OWB but he was not successful. I do not know what is the problem with JSF 2.0.  I did not try using JSF 2 with OWB.
>
>Could you give an exception stack trace that your application throws?  Which implementation you use RI JSF 2 or MyFaces ?
>
>Thanks;
>
>-- Gurkan
>
>
>2009/8/31 Sven Linstaedt <sv...@googlemail.com>
>
>
>>>Hi,
>>
>>I suppose OWB should also work with JSF 2.0, even the examples currently use JSF 1.x. Today I tried to check out some of the new JSF 2 features and run into various problems (in other words: exceptions). Is there someone already tried to use this combination of frameworks and give me a hint, if the web.xml and faces-config.xml setup differs between usage of OWB in JSF 1.x and JSF 2.0?
>>
>>br, sven
>>
>
>
>-- 
>Gurkan Erdogdu
>http://gurkanerdogdu.blogspot.com
>

Re: Testing OWB against JSF 2.0 RI ?

Posted by Sven Linstaedt <sv...@googlemail.com>.

Actually it turns out, the OWB exceptions were caused by JSF 2.0 RI by
dispatching resource request to a full jsf lifecycle, if the FacesServlet is
prefix mapped to the application's root. Because the request has no
viewstate attached and the URI could not be resolved to a metadata view the
viewroot is null, so JSFUtil.isPostBack() fails.

However as I am further determining features and benefits of the duo OWB +
JSF 2.0 RI in webapplications, I can update you about usage of these both
together, if you want.

br, Sven




javax.faces.FacesException
    at
com.sun.faces.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:136)
    at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:115)
    at
com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:110)
    at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
    at javax.faces.webapp.FacesServlet.service(FacesServlet.java:310)
    at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
    at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
    at
org.apache.webbeans.jsf.WebBeansJSFFilter.doFilter(WebBeansJSFFilter.java:79)
    at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148)
    at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:387)
    at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
    at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
    at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:326)
    at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
    at
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:539)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
    at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
Caused by: java.lang.NullPointerException
    at org.apache.webbeans.util.JSFUtil.isPostBack(JSFUtil.java:50)
    at
org.apache.webbeans.jsf.WebBeansPhaseListener.afterPhase(WebBeansPhaseListener.java:46)
    at com.sun.faces.lifecycle.Phase.handleAfterPhase(Phase.java:179)
    at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:103)
    ... 23 more



2009/8/31 Gurkan Erdogdu <cg...@gmail.com>

> Hi Sven;
>
> Last time Matthias Wessendorf from MyFaces Project also tried to use JSF
> 2.0 with OWB but he was not successful. I do not know what is the problem
> with JSF 2.0.  I did not try using JSF 2 with OWB.
>
> Could you give an exception stack trace that your application throws?
> Which implementation you use RI JSF 2 or MyFaces ?
>
> Thanks;
>
> -- Gurkan
>
> 2009/8/31 Sven Linstaedt <sv...@googlemail.com>
>
>> Hi,
>>
>> I suppose OWB should also work with JSF 2.0, even the examples currently
>> use JSF 1.x. Today I tried to check out some of the new JSF 2 features and
>> run into various problems (in other words: exceptions). Is there someone
>> already tried to use this combination of frameworks and give me a hint, if
>> the web.xml and faces-config.xml setup differs between usage of OWB in JSF
>> 1.x and JSF 2.0?
>>
>> br, sven
>>
>
>
>
> --
> Gurkan Erdogdu
> http://gurkanerdogdu.blogspot.com
>

Re: Testing OWB against JSF 2.0 RI ?

Posted by Gurkan Erdogdu <cg...@gmail.com>.

Hi Sven;

Last time Matthias Wessendorf from MyFaces Project also tried to use JSF 2.0
with OWB but he was not successful. I do not know what is the problem with
JSF 2.0.  I did not try using JSF 2 with OWB.

Could you give an exception stack trace that your application throws?  Which
implementation you use RI JSF 2 or MyFaces ?

Thanks;

-- Gurkan

2009/8/31 Sven Linstaedt <sv...@googlemail.com>

> Hi,
>
> I suppose OWB should also work with JSF 2.0, even the examples currently
> use JSF 1.x. Today I tried to check out some of the new JSF 2 features and
> run into various problems (in other words: exceptions). Is there someone
> already tried to use this combination of frameworks and give me a hint, if
> the web.xml and faces-config.xml setup differs between usage of OWB in JSF
> 1.x and JSF 2.0?
>
> br, sven
>



-- 
Gurkan Erdogdu
http://gurkanerdogdu.blogspot.com