Alan,
Just to complement...
I'm used VO (AMFPHP approach) with a lot of method with no
problem. These VOs have the same face as above.
On Mon, Nov 10, 2008 at 9:39 PM, Alan [EMAIL PROTECTED] wrote:
On my last AMFPHP project my PHP and Flex VOs were:
package com.mydomain
{
[Bindable]
Hi, all;
I have some VO's that I've created to work with AMFPHP. When I call
the service, I'm getting an array of untyped objects. Another
developer on the project believes that the reason for the problem is
that the objects extend EventDispatcher and because they have
additional methods on
Might be completly irrelevant (have not used AMFPHP) but are you using
Remote class Metas?
example:
package beans
{
[RemoteClass(alias=net.w2w.semantic.annotation.beans.SemanticTags)]
[Bindable]
public class SemanticTags
{
public var type:String ;
public var
Is it creating a problem for you? It shouldn't. From what I remember
you don't even really need VOs with AMFPHP.
Are you getting those warning that say something like unable to bind
to property 'X '. Unfortunately, no one really knows what's going on
with AMFPHP :) Wade said he's
If you are getting an array of untyped objects, that means that your class
mapping is not set up properly. As already mentioned, make sure that you
have the $_explicitType variable set in your php VOs, and the RemoteClass
metadata included in your AS classes. This might help:
On my last AMFPHP project my PHP and Flex VOs were:
package com.mydomain
{
[Bindable]
[RemoteClass(alias=UserVO)]
public class UserVO
{
public var id :int;
public var username :String;
6 matches
Mail list logo
