Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

BlazeDS Data Push - Chat App

Avatar

Level 1
I'm trying to learn how data push works in BlazeDS by using
the following
chat
tutorial
. The tutorial gives you a preconfigured version of
Tomcat and all works well, very nice. So I took the next step and
added the chat code and XML files (services-config.xml,
messaging-config.xml, etc) to my pre-existing Flex project. When I
deployed my web-app to Tomcat 5.5 the chat application doesn't
receive any data from the server, not even an error. Anybody know
what might be the difference between the preconfigured Tomcat where
the chat works and my standard Tomcat 5.5? Any suggestions on how
to debug this, no errors pop up and the tomcat logs are
clean.
2 Replies

Avatar

Level 1
Tomcat is finally giving me an error! However, I don't know
how to fix it. Here is the error:




quote:



[EMST]03/31/2008 10:49:44.938 [WARN] HttpFlexSession has not
been registered as a listener in web.xml for this application so no
events will be dispatched to FlexSessionAttributeListeners or
FlexSessionBindingListeners. To correct this, register
flex.messaging.HttpFlexSession as a listener in web.xml.





However my web.xml file is the same file where it worked in
the pre-configured tomcat server that adobe gave out:




quote:



<?xml version="1.0" encoding="UTF-8"?>



<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD
Web Application 2.3//EN" "
http://java.sun.com/dtd/web-app_2_3.dtd">



<web-app>

<display-name>Chat</display-name>

<description>Chat Application</description>



<context-param>

<param-name>flex.class.path</param-name>


<param-value>/WEB-INF/flex/hotfixes</param-value>

</context-param>



<!-- Http Flex Session attribute and binding listener
support -->

<listener>


<listener-class>flex.messaging.HttpFlexSession</listener-class>

</listener>



<!-- MessageBroker Servlet -->

<servlet>


<servlet-name>MessageBrokerServlet</servlet-name>


<display-name>MessageBrokerServlet</display-name>


<servlet-class>flex.messaging.MessageBrokerServlet</servlet-class>

<init-param>


<param-name>services.configuration.file</param-name>


<param-value>/WEB-INF/flex/services-config.xml</param-value>

</init-param>

<load-on-startup>1</load-on-startup>

</servlet>

<servlet-mapping>


<servlet-name>MessageBrokerServlet</servlet-name>

<url-pattern>/messagebroker/*</url-pattern>

</servlet-mapping>



<login-config>

<auth-method>BASIC</auth-method>

</login-config>

</web-app>





Any suggestions to fix this error would be greatly
appreciated.

Avatar

Level 1
Just thought I'd post this for the sake of completion.
Tomcat/Flex magically decided to start working and I'm 75% sure I
didn't change anything. Maybe my flex app wasn't rebuilding when I
thought it was?