Jeff,
Yup. for WebService calls, that's the right thing to do. However, for
HTTPService calls, the machinery doesn't use the SchemaRegistry.
The earlier suggestion of taking a look at the code generated by the
FlexBuilder 3 WebService "wizard" was a good one - although the sheer
volume of code generated has convinced me that this is a disgustingly
tedious problem to attack.
For the moment, I've shifted away from Schema and am simply assuming
the type of the objects coming over the wire and hardcoding that into
my Flex app. Works for a small project with relatively simply XML data
feeds and low rates of change.
I'd still love to see a more generalized non-WebService (SOAP)
solution at some stage. I'd even be happy to use WSDL to define the
HTTP / REST endpoint...although I note that WSDL 2.0 + REST semantics
seem largely unexplored territory.
Yet another alternative I *have* seen used out there in AS3 space, of
moving to JSON over the wire, takes me away from my goal of using XML.
Regards,
Brett.
--- In flexcoders@yahoogroups.com, [EMAIL PROTECTED] wrote:
>
> On Thu, Mar 20, 2008 at 03:55:28AM -0000, Brett Adam wrote:
>
> > Has anyone done any work in this area? Is there some blindingly
simple solution that I just
> > can't see?
>
>
> On WebService calls, I use
>
> SchemaTypeRegistry.getInstance().registerClass(new
QName("http://www.foo.com/foo-common","FacilityType";),FacilityType)
>
> where the first param to QName is the schema's targetNamespace and
the second param is the name of the type. RegisterClass's second
parameter is the
> AS class name. In my case, FacilityType contains properties that
are other classes, so I have to make sure everything in the tree is
registered
> prior to invoking the web service.
>
>
> Jeff
>
