YES! One success leads to another. Thanks, this got the remoting working - definately different than with OpenAMF. Shortly after, we got a successful remote RTMP connection to one of our Red5 servers using RTMPClient!
Thank you very much for your help. Bill Joachim Bauch wrote: > Hi Bill, > > Sales Department schrieb: >> Thanks. I've got the connection working now. >> I have another problem. I feel like an idiot, but I have not found >> anything in the lists to help. Here's what I'm getting now: >> >> [WARN] 16293 btpool1-13:( >> org.red5.server.service.ServiceInvoker.invoke ) Service not found: >> com.interalab.somefolder.SomeClass >> >> So, I have a connection, but Red5 doesn't recognize it. The class is >> in the right place on the app scope I'm in. When I added the servlet >> definition to the web.xml like you do with OpenAMF, Red5 complains >> that my class isn't a servlet - which it isn't of course. > > you shouldn't pass the classname as service name in your remoting call, > but register the class as service for your app. > > So instead of calling "com.interalab.somefolder.SomeClass.someMethod" > you call "someService.someMethod" and add the following to your > red5-web.xml: > > <bean id="someService.service" > class="com.interalab.somefolder.SomeClass" > singleton="true" /> > > Hope that helps, > Joachim > > ------------------------------------------------------------------------ > > _______________________________________________ > Red5 mailing list > [email protected] > http://osflash.org/mailman/listinfo/red5_osflash.org > _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
