I've added conversation support to the flex integration. The mechanism is compatible with that used in blaze and flamingo examples, but the mechanism on the Seam side is a little different. When I have a more interesting example app I'll post that for reference.
If anyone is interested in testing this before then, let me know and I'll get you something to work with.
What version of Seam will include the flex integration/examples?
The integration is in the 2.2 branch in SVN.
I can help with testing and maybe development of example. Just downloaded 2.2.0GA distro and checked out 2.2.0GA from svn (http://anonsvn.jboss.org/repos/seam/branches/community/Seam22)and flashbuilder 4.0 trial. Thought I'd start from your post at http://relation.to/Bloggers/SeamAndFlex and go from there.
Currently, I am trying to build the jboss-seam-flax.jar and find namespace to include the flex filter via components.xml and follow thru your post.
I was trying to locate an example in the 2.2 branch in svn (http://fisheye.jboss.org/browse/Seam/branches/community/Seam22/examples), but I wasn't able to find any. Am I missing something? Is an example with conversation support available as well?
If there is nothing there, and you just have some random code lying around, could you please post it somewhere? I'd also be interested in testing this out and possibly help in developing a reference example.
even with no examples we managed to make it work. There were some problems in compiling the seam flex library as it seams one of the pom is not defining the repository... but in the end we managed to used it.
Now, we have also tested the conversation support. It looks like it works fine if the flex is calling a method that starts a long running conversation: after that all method calls use that conversation.
However, our use case was different: we needed to have the flex join an already existing conversation, and for that it looks like there is no support yet. So, if anyone is interested in such a thing, we managed to implement our use case by borrowing the SeamRemoteObject flex class (and relatives) from the Flamingo distribution. Using that object we managed to set the conversation id explicitly in the flex code.
We are now cleaning up our example and we'd be happy to share it: what would be the best way for doing that?
The conversation support is compatible with the SeamRemoteObject used by blaze and flamingo. I have my own version that will become a part of the Seam integration, but we'll use the same headers for compatibility.
What was the issue with the pom?
It looks like there was a problem with repository definition in the seam-ui.pom.
When the seam-integrated version of the
Yet, it's not as simple as the GDS.
In GDS, remote object can be treated as the Seam object. The tide framework of GDS does great work.
So I think the official support of Flex should be something like Tide. It's easy for Seam developers indeed.
This seems like a mistake to do, better to get GraniteDS to merge with SEAM Framework.
I don't see much activity in this 2.2 branch (at least for flex) since last October...
Could someone please tell me if this flex-seam integration is going to be available in Seam 3.0? Or something different is being done?
I left this same question here ...