<rt id="bn8ez"></rt>
<label id="bn8ez"></label>

  • <span id="bn8ez"></span>

    <label id="bn8ez"><meter id="bn8ez"></meter></label>

    The NoteBook of EricKong

      BlogJava :: 首頁 :: 聯(lián)系 :: 聚合  :: 管理
      611 Posts :: 1 Stories :: 190 Comments :: 0 Trackbacks

    Configure an existing J2EE web application to support BlazeDS by performing the following steps:
    1 Add the BlazeDS JAR files and dependent JAR files to the WEB-INF/lib directory.
    2 Edit the BlazeDS configuration files in the WEB-INF/flex directory.
    3 Define MessageBrokerServlet and a session listener in WEB-INF/web.xml.

    RPC service example
    The Remoting Service is one of the RPC services included with BlazeDS. The Remoting Service lets clients access methods of Plain Old Java Objects (POJOs) on the server.In this example, you deploy a Java class, EchoService.java, on the server that echoes back a String passed to it from the client. The following code shows the definition of EchoService.java:

    1 package remoting;
    2 public class EchoService
    3 {
    4     public String echo(String text) {
    5         return "Server says: I received '" + text + "' from you";
    6     }
    7 }
    8 


    The echo() method takes a String argument and returns it with additional text. After compiling EchoService.java,place EchoService.class in the WEB-INF/classes/remoting directory. Notice that the Java class does not have to import or reference any BlazeDS resources.
    Define a destination, and reference one or more channels that transport the data. Configure EchoService.class as a remoting destination by editing the WEB-INF/flex/remoting-config.xml file and adding the following code:

    <destination id="echoServiceDestination" channels="my-amf">
     
    <properties>
      
    <source>remoting.EchoService</source>
     
    </properties>
    </destination>

    The source element references the Java class, and the channels attribute references a channel called my-amf.Define the my-amf channel in WEB-INF/flex/services-config.xml, as the following example shows:

    <channel-definition id="my-amf" class="mx.messaging.channels.AMFChannel">
        
    <endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/amf" class="flex.messaging.endpoints.AMFEndpoint"/>
        
    <properties>
            
    <polling-enabled>false</polling-enabled>
        
    </properties>
    </channel-definition>

    The channel definition specifies that the Flex client uses a non-polling AMFChannel to communicate with the AMFEndpoint on the server.
    Note: If you deploy this application on the samples web application installed with BlazeDS, services-config.xml already contains a definition for the my-amf channel.The Flex client application uses the RemoteObject component to access EchoService. The RemoteObject component uses the destination property to specify the destination. The user clicks the Button control to invoke the remote
    echo() method:

    <?xml version="1.0"?>
    <!-- intro\intro_remoting.mxml -->
    <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" width="100%" height="100%">
    <mx:Script>
    <![CDATA[
     import mx.rpc.events.FaultEvent;
     import mx.rpc.events.ResultEvent;
     // Send the message in response to a Button click.
     private function echo():void {
        var text:String = ti.text;
        remoteObject.echo(text);
     }
     // Handle the recevied message.
     private function resultHandler(event:ResultEvent):void {
         ta.text += "Server responded: "+ event.result + "\n";
     }
     // Handle a message fault.
     private function faultHandler(event:FaultEvent):void {
         ta.text += "Received fault: " + event.fault + "\n";
     }
     
    ]]>
    </mx:Script>
    <mx:RemoteObject id="remoteObject" destination="echoServiceDestination" result="resultHandler(event);" fault="faultHandler(event);"/>
    <mx:Label text="Enter a text for the server to echo"/>
    <mx:TextInput id="ti" text="Hello World!"/>
    <mx:Button label="Send" click="echo();"/>
    <mx:TextArea id="ta" width="100%" height="100%"/>
    </mx:Application>

    Compile the client application into a SWF file by using Flex Builder or the mxmlc compiler, and then deploy it to
    your web application.
     

    posted on 2011-06-29 11:09 Eric_jiang 閱讀(232) 評(píng)論(0)  編輯  收藏 所屬分類: Flex
    主站蜘蛛池模板: 成人片黄网站色大片免费观看cn| 久久久久久精品免费看SSS| 麻豆成人精品国产免费| 久久久青草青青国产亚洲免观| 亚洲福利视频网址| 99re6在线视频精品免费下载| 亚洲国产精品婷婷久久| 久久国产精品免费专区| 亚洲视频2020| 999国内精品永久免费观看| 亚洲AV成人噜噜无码网站| 久久精品免费一区二区喷潮| 亚洲人成色777777老人头| 国产免费拔擦拔擦8x| 人妻免费久久久久久久了| 国产亚洲精品一品区99热| 99精品视频免费在线观看| 在线综合亚洲中文精品| 免费国产成人午夜私人影视| 两个人看的www免费高清| 亚洲ⅴ国产v天堂a无码二区| 蜜臀98精品国产免费观看| 亚洲欧洲日韩国产一区二区三区| 日韩精品免费一区二区三区| 亚洲春黄在线观看| 搡女人真爽免费视频大全| 青青青亚洲精品国产| 在线精品免费视频| 国产成人亚洲精品蜜芽影院| 亚洲中文字幕日产乱码高清app| 国产精品亚洲а∨无码播放麻豆| 亚洲精品无码av天堂| 人妻无码久久一区二区三区免费| 亚洲第一男人天堂| 亚洲综合色在线观看亚洲| 18成禁人视频免费网站| 亚洲A∨精品一区二区三区下载| 在线观看人成视频免费| a级毛片100部免费观看| 亚洲人成在久久综合网站| 亚洲狠狠爱综合影院婷婷|