Java Reference
In-Depth Information
</channels>
<properties>
<scope>application</scope>
<source>com.appirio.Gateway</source>
</properties>
</destination>
</service>
</services>
<channels>
<channel-definition id="my-graniteamf"
class="mx.messaging.channels.AMFChannel">
<endpoint
uri="/graniteamf/amf"
class="flex.messaging.endpoints.AMFEndpoint"/>
</channel-definition>
</channels>
</services-config>
For Flex remoting to work correctly you need to pass some arguments to the compiler,
telling it where to find the services file that defines your remoting destination. Your
remoting destination points to a class called Gateway that you will create shortly. Right-
click the project name in the left panel and select Properties ¾ Flex Compiler. Replace
your compiler arguments with the following:
-locale en_US -services ../war/WEB-INF/flex/services-config.xml
Since you are using GraniteDS, you have to provide the runtime configuration
for the container. Create a new folder called “granite” under /WEB-INF/ and paste
the granite-config.xml file from graniteds/examples/graniteds_pojo/resources/
WEB-INF/granite/ into it.
In this example you'll be using the Java Persistence API (JPA) as the persistence
protocol. Since App Engine utilizes JDO by default, you'll need to create the
configuration file for JPA manually. Create the persistence.xml file with the code
from Listing 4-17 in the /src/META-INF/ directory.
Listing 4-17. JPA persistence.xml file
<?xml version="1.0" encoding="UTF-8" ?>
<persistence xmlns=" http://java.sun.com/xml/ns/persistence"
xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation=" http://java.sun.com/xml/ns/persistence
 
Search WWH ::




Custom Search