[Red5] Remoting: Problems with Tomcat

[Gordon Leland Hempton]

1. I did not rename ROOT.war; Red5 is the default tomcat servlet.

2. The Gateway servlet is defined in web.xml.

3. Tomcat is listening on port 8080 and I have the remote object. When I
perform the same test using the Standalone Red5 server, it listens on port
5080 and I take this into account.

The interesting thing in my opinion is that it works fine for me if I put
the beans inside of defaultRef.xml instead of the *-web.xml files. This kind
of makes sense to me since each *-web file that requires remoting will be
redefining the flexMessaging.service bean.

Does the echo sample app using http work for anyone else when running in war
mode?

Thanks,
Gordon

On Tue, Aug 12, 2008 at 1:37 AM, Mondain <mondain at gmail.com> wrote:

> Couple of questions:
> 1. Did you rename the ROOT.war?
> 2. Is the "gateway" servlet defined in tomcat/webapps/ROOT/WEB-INF/web.xml?
> 3. Is your Tomcat instance listening on port 8080?
>
> Paul
>
> On Mon, Aug 11, 2008 at 6:55 PM, Gordon Leland Hempton <ghempton at gmail.com
> > wrote:
>
>> Anyone have any insight on this? I believe this is a common problem: I
>> have seen several other posts on the echo sample app not working under
>> Tomcat.
>>
>> Thanks,
>> Gordon
>>
>>
>> On Sun, Aug 10, 2008 at 3:30 PM, Gordon Leland Hempton <
>> ghempton at gmail.com> wrote:
>>
>>> I am trying to get remoting to work running red5 in war mode, however
>>> there is some weird behavior I will outline below:
>>>
>>> If I add the service to my webapp-web.xml as follows:
>>>
>>>     <bean id="myRemote" class="MyRemoteObject"
>>>         singleton="true">
>>>     </bean>
>>>
>>>     <bean id="flexMessaging.service"
>>> class="org.red5.server.net.remoting.FlexMessagingService">
>>>         <property name="serviceInvoker" ref="global.serviceInvoker" />
>>>         <property name="endpoints">
>>>             <map>
>>>                 <entry key="myDestination">
>>>                     <ref bean="myRemote" />
>>>                 </entry>
>>>             </map>
>>>         </property>
>>>     </bean>
>>>
>>> Then I set the endpoint in mxml to http://localhost:8080/gateway, it
>>> complains that the flexMessaging service cannot be found. Note, that this
>>> same error message happens when I run the echo sample application.
>>>
>>> However, I can make everything work by adding the above xml fragment to
>>> the defaultContext.xml file instead of webapp-web.xml, however this seems
>>> like a hack and will only allow a single web application to use remoting.
>>>
>>> Does anyone know what is going on here?
>>>
>>> Thanks,
>>> --
>>> Gordon Hempton
>>> http://hempton.com
>>>
>>
>>
>>
>> --
>> Gordon Hempton
>> http://hempton.com
>>
>> _______________________________________________
>> Red5 mailing list
>> Red5 at osflash.org
>> http://osflash.org/mailman/listinfo/red5_osflash.org
>>
>>
>
>
> --
> http://gregoire.org/
> http://osflash.org/red5
>
> _______________________________________________
> Red5 mailing list
> Red5 at osflash.org
> http://osflash.org/mailman/listinfo/red5_osflash.org
>
>


-- 
Gordon Hempton
http://hempton.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://osflash.org/pipermail/red5_osflash.org/attachments/20080812/c5778b3a/attachment.html