richfaces 4.1 a4j:push usage problem

[typek_pb]

Hi all,

while trying to use the JMS-free push in richfaces 4.1 I get the following warning:

2012-01-03 13:06:45.734:WARN:oejs.ServletHandler:/yourpresenter/rfRes/org.richfaces.resource.PushResource.jsf

java.lang.IllegalArgumentException

    at org.richfaces.resource.PushResource.encode(PushResource.java:85)

    at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188)

    at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:222)

    at javax.faces.webapp.FacesServlet.service(FacesServlet.java:407)

    at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:547)

    at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1355)

    at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88)

    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)

    at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1326)

    at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:479)

    at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)

    at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:520)

    at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)

    at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:940)

    at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:409)

    at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)

    at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:874)

    at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)

    at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:250)

    at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:149)

    at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110)

    at org.eclipse.jetty.server.Server.handle(Server.java:349)

    at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:441)

    at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:904)

    at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:565)

    at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:217)

    at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:46)

    at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:545)

    at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:43)

    at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:533)

    at java.lang.Thread.run(Thread.java:619)

my relevant jsf page chunk looks like this:

...

<h:form>

     <a4j:push id="statePush" address="statePushTopic" ondataavailable="alert('pushed');" />

</h:form>

...

Moreover I've noticed that no popup window is beeing open.

Any idea how to fix this?

thanks

[lfryc]

Hi Peter,

it seems like integration issue with Spring Web Flow,

as the pushTopic request parameter is not propagated correctly to the PushServlet [1].

Could you please provide us with small sample app (preferably Maven based) reproducing issue?

[1] https://github.com/richfaces/components/blob/4.1.0.20111212-Final/core/ui/src/main/java/org/richfaces/resource/PushResource.java#L85

[typek_pb]

Hi,

I'm not using Spring web flow in my app (as far as I'm aware of it ).

There seems to be similar problem reported elsewhere: https://community.jboss.org/message/645882#645882

Where there is also sample app provided.

In the meantime if possible I'll try to extract only relevant part of my app to provide sample for my setup as well.

Just a sidenote, is it required to use weld to have jms-free push running (as I've seen that it's used in the showcase)?

Peter B.

[healeyb]

I have this problem now and don't use spring web flow, did any progress ever get made resolving this issue?

Thanks,

Brendan.

[lfryc]

Peter,

CDI/Weld is not required to get that running, see documentation:

http://docs.jboss.org/richfaces/latest_4_X/Component_Reference/en-US/html/chap-Component_Reference-Actions.html#sect-Component_Reference-a4jpush-Using_TopicsContext_to_publish_message

You can go deeply and "debug" your app - the problem is that push requests does not have "pushTopic" request parameter setup.

Let's use Chrome Dev Tools or Firebug (F12) to see Resources tab,

following sample is from http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=push&skin=blueSky

you can see request for /rfRes/org.richfaces.resource.PushResource.jsf,

and its Form Data (request parameters) have pushTopic=pushTopicsContext

Could you please check what you are getting in your app?

[healeyb]

Lukas, you're quite right that there is no pushTopic form data, in fact there is no form data at all, despite

a4j:push being in a h:form. I think that the exception is interrupting normal processing, and it's the reason

behind the exception that we need to determine.

[lfryc]

Could you please try solution from following thread?

https://community.jboss.org/message/647015#647015

[healeyb]

Lukas, I'm using glassfish 3.1.1 which supports the servlet 3.0 spec, so I'm not expecting to explicitly declare

the push servlet in web.xml. I have included the following context params:

<context-param>

        <param-name>org.atmosphere.useBlocking</param-name>

        <param-value>true</param-value>

    </context-param>

    <context-param>

        <param-name>org.richfaces.push.handlerMapping</param-name>

        <param-value>/__richfaces_push</param-value>

</context-param>

Then when I run it I don't get an exception which is good, but I'm still not seeing pushTopic in the form data,

and it doesn't work end-to-end, I'm getting no js alert to indicate that any data has been received.

When I load the page containing a4j:push the final request issued as part of the page load is this, which

returns a 404:

GET https://localhost:8181/SportQuest/__richfaces_push?__richfacesPushAsync=1&pushSessionId=312ae100-9fe7-4b4c-bb33-46e42ec6ef5c

If I explicitly declare PushServlet in the web.xml I get an NPE exception in the PushServlet constructor. Phew,

sure is proving tricky this...

[lfryc]

Please refer to Starting with RichFaces Push on Various Servlet Containers .

I would appreciate your feedback there.

[lfryc]

Hey Brendan, AtmosphereServlet does not have to be registered, PushServlet is extending in order to serve push requests.

Could you please file issue for problems with automatic servlet registration on Glassfish?

[typek_pb]

Hey Lukas,

thanks a lot for referred article! You made my day!

Now a4j:push works with my app deployed on jetty 7.5.4.