Valy, the only bug I know of in this area for Beta 2 has to do with AMF 0. If you're not changing the objectEncoding of the underlying NetConnection to ObjectEncoding.AMF0 then it's likely that you either have registered the wrong alias for the type or you simply don't have the class linked in to the SWF, as Matt suggested.
The debug trace output of your AMF response has the typed Object name as org.ifm.model.TlcPhoneNumber but this is not what you've registered as the class alias in the [RemoteClass] metadata…
[RemoteClass(alias="org.ifm.model.PhoneNumber")]
…even though the Java code you pasted below has this as its classname.
Are you returning the wrong type from your Java service at runtime? Note that it can not be an implementation of an interface in order for a server type to be matched to a client type… the client type alias must match the concrete implementation's class name.
Also, rather than relying on rumor of fixes for beta 3, can you please try to add the following in one of your MXML script blocks to see if it fixes the issue Matt describes?
import org.ifm.model.PhoneNumber;
private var dep:PhoneNumber;
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
| Web site design development | Computer software development | Software design and development |
| Macromedia flex | Software development best practice |
YAHOO! GROUPS LINKS
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
