Accessing FAM_Space in a Spring Bean

Hi Tom,

Are you using Spring on both the client and the fabric? Specifically, are you using a FabricProxyFactoryBean on the client side to create beans that communicate with the fabric?

Thanks,
Randy

Tom,

In the current 3.9 release the way you will need to obtain a session is through the FAM_Session.createFabricExternalSession(String lockId, String version) static factory method. Unfortunately creating a session this way is complicated and problematic when errors occur so we don't recommend it, but, it should get you going if you're just prototyping. You'll need to populate the lockId with a GUID. The version can just be "1" - its purpose is difficult to explain.

We are currently working on creating a better way of dealing with FAM sessions in the Java api. We'll have a pre-beta build in the next few days so if you'd like to try it out I can send it to you.

Thanks,
Randy

Hi Guerry,

Thanks for the inquiry.

I know that I learn from example, as do many other developers. Unfortunately, given that Appistry is an infrastructure product, its difficult to create a wide enough example set that will cover all of possible uses for the product; however, creating and carrying through a theme a little further, I think, will go a long way to demonstrating how one uses the fabric. i.e. Do all examples for all technologies (which is partially done).

For example:

1) Simple calling of methods - Like hello world, which is already done
2) Calling the fabric API from a deployed bean - Done for a POJO, but not Spring
3) Creating FAM spaces or queues - Done for a POJO, but not Spring
etc.

Given that the Spring Framework is a very popular framework for Java, more Spring-specific examples and/or documentation would be helpful. There are two example sets. Hello world, which is separate from the installed fabric, and the tutorials which get installed. Just a suggestion, but I think it would be easier to consolidate them. Then, for each example and tutorial, do it for each of the technologies.

The API documentation is also lacking in description of the actual uses for the API and the methods.

I think that the Appistry platform is great and serves to solve many of the problems we all face when deploying reliable and scalable solutions. I might recommend that, in order to save developer time, it would be good to see best practices for development environments of choice. i.e. Spring, Java, .Net, etc. Maybe a forun on best practices. But since Appistry built and supports the product, they're in the best position to publish some best practices for implementation.

Any hints on security? I know the topic is broad and maybe not an issue for the fabric, but we're always asked to deal with security, and there really isn't any information on that topic.

I hope this helps.

I'll continue to provide feedback since I think this is an important technology for us to embrace and keep alive.

Tom