<factories>
<factory id=”spring” class=”blaze.SpringFactory” />
</factories>

The above assumes that you copied the source code to a file called SpringFactory.java in a folder called blaze under your application’s source folder. You can then add destinations to your remoting-config.xml file like the following, to reference your Spring bean services:

<destination id=”loginService”>
<properties>
<factory>spring</factory>
<source>loginManager</source>
</properties>
</destination>

The above will expose a Spring bean with the id of loginManager as a remote object with the name loginService.

Scenario – I’m using Alfresco which has a huge API with a ton of spring beans that I could feasibly expose to BlazeDS. Unfortunately, for those of us that are not Java folks (more on the Flex end), doing so seems to be a daunting task.

I think everyone needs more actual examples on how to expose a theoretical, already-existing bean on a server to remoting. What if you don’t have the actual Java classes for the beans? Do the beans automatically define the data types that are used for communication and BlazeDS can read those descriptors and use them?

I’d love to try out BlazeDS but at the moment, it’s pretty difficult to get going.