It's great to hear you back Shane. Looking forward to see more of your great work :)
i think im getting a cold, i feel like crap!
could you give my thread a gander.... it causes me much unrest..... its about variable passing between task nodes.
Sorry to hear you were sick and good that you are well again!
I heard you were building infrastructure which makes use of named conversation. I am using the names of conversations very heavily in my own application and it works out very well....during the refactoring of my own code, I had some ideas about the infrastructure service which Seam could provide. Please have a look at these two threads if you have time:
In the first thread there were new annotations I imagine which could be used in automatic entity view generation.....
If you are interested I can post more code in my entity beans and conversation beans. (I know jBPM actually does very similar, if not the same thing as using names of conversation, but the UseCaseStack approach is much lighter, good enough for most non-process-intensive web app and it's never too bad to have less library dependencies....)
Could you help to shed some light on how Home and EntityHome classes are intended to be used and extended?
They are central to a seamgen'd application, yet have much "magic" which needs to be understood once the generated application starts to evolve. My specific question related to the wire() and getDefinedInstance() functions, but general information on the basic purpose of various groups of functions inherited into seamgen'd Home classes would be very helpful.