Java Reference
In-Depth Information
<filter>
<filter-name>AMFMessageFilter</filter-name>
<filter-class>org.granite.messaging.webapp.AMFMessageFilter</filter-
class>
</filter>
<filter-mapping>
<filter-name>AMFMessageFilter</filter-name>
<url-pattern>/graniteamf/*</url-pattern>
</filter-mapping>
<!-- processes AMF requests -->
<servlet>
<servlet-name>AMFMessageServlet</servlet-name>
<servlet-
class>org.granite.messaging.webapp.AMFMessageServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>AMFMessageServlet</servlet-name>
<url-pattern>/graniteamf/*</url-pattern>
</servlet-mapping>
GraniteDS communicates with the servlet container through a remoting destination,
which exposes a Java class to your Flex application so that it can invoke methods
remotely. In Listing 4-16, the destination ID is a logical name that your Flex application
uses to refer to the remote class. This eliminates the need to hard-code a reference to the
fully qualified Java class name. This logical name is mapped to the Java class as part of
the destination configuration in services-config.xml. Create a new folder under
/WEB-
INF/
called “flex” and create the services-config.xml file with the code in Listing 4-16.
Listing 4-16. The services-config file for your remoting destination
<?xml version="1.0" encoding="UTF-8"?>
<services-config>
<services>
<service
id="granite-service"
class="flex.messaging.services.RemotingService"
messageTypes="flex.messaging.messages.RemotingMessage">
<destination id="Gateway">
<channels>
<channel ref="my-graniteamf"/>
