Janos, Amfphp 1.9 looks for your VO objects in "services\vo" by default. You can change this in the globals.php file.
Michael Ramirez --- In [email protected], "Kun Janos" <[EMAIL PROTECTED]> wrote: > > Hi all. > > I just upgraded amfphp 1.2 to amfphp 1.9 beta 2 and class mapping is > not working any more :( > In one of the messages that Patrick Mineault wrote I read that for > class mapping I should put > [RemoteClass(alias="com.virtualro.shell.vo.LoginVO")] in Flex > LoginVO.as (just like in amfphp 1.2) and > public $_explicitType = "com.virtualro.shell.vo.LoginVO"; //in LoginVO.php > I'm using Charles and I see that the data is sent from flex to amfphp, > but the class mapping doesn't occour. > Using > $msg = ''; > foreach($login as $key => $value){ > $msg .= $key.' -> '.$value.', '; > } > I saw that the data arrives to LoginService.php but using > $login->username gives null :( meaning that data has arrived but class > mapping is not working. > Patrick Mineault also wrote that after setting up LoginVo.php and > LoginVo.as we should read the instructions in advancedsettings.php > The problem is that the file advancedsettings.php doesn't exist in > amfphp 1.9 beta 2, and the methods used in amfphp 1.2 > (setBaseCustomMappingsPath, setCustomIncomingClassMappings and > setCustomOutgoingClassMappings) have been removed from the $gateway. > Can anybody help me? > > Thanks, > Janos >
