If you have a suitable entry point into your tiny java library, i.e. a class with a public, no args constructor, then you should be able to use RemoteObject.
To keep things simple, the service name is the fully qualified class name. You must ensure that this service name is in the whitelist for your Flex application (see /WEB-INF/flex/flex-config.xml, specifically the remote-objects section of this file; note that you must restart the web application if you make such changes to this file). By default, RemoteObject uses a simple binary protocol called AMF between the Flash Player and the Flex Server. Your java class should return data in a suitable format to be used as a dataProvider for a tree (such as an XML Document, and, I think ArrayList). --- In [email protected], "brian_r_christian" <[EMAIL PROTECTED]> wrote: > It just occurred to me that my previous post may be unnecessary, in > that the debate.xml file that's causing the trouble right now is > just a stand-in for what we'd ultimately like to do, which is > generate a mx:Tree based on data in a SQL database sitting on our > server. > > It seems like RemoteObject is the way to make this happen, but I > haven't been able to gather from the docs on RemoteObject exactly > what an implementation might look like. We've written a tiny java > library that has methods for pulling data from the SQL database...is > there a way to link up to that? > > Thanks again, > > Brian
