Apr 21st, 2005, 08:02 AM
Modules 0.1 - SWF, Hivemind and Tapestry
Since there is a Module 0.1 released, stating:
"The HiveMind and Commons Validator support classes are considered to be stable and ready for use in production."
Does this mean we ca now configure Tapestry as a bunch of Spring Beans?
So, we could easily write a Page implementation supporting WebFlows?
Jonas Van Poucke
Apr 21st, 2005, 08:41 AM
This doesn't answer your question, but anyway: SWF-Tapestry integration has already been talked about, but so far hasn't been implemented yet.
Apr 21st, 2005, 08:45 AM
Hmm, thanks for your response Erwin. Do you have any pointer on the integration (forum or somewhere else)? I might give it a try...
Originally Posted by ev9d9
Apr 21st, 2005, 09:00 AM
The SpringModules HiveMind support allows for HiveMind services to be accessed like Spring beans not the other way around. As I understand it, HiveMind already has support for accessing Spring beans as if they were HiveMind services so this might do want you want.
Apr 21st, 2005, 09:01 AM
That would be excellent!
SWF itself is protocol (Servlet, Portlet, JSF, Tapestry, ...) independent to make it easy to integrate with other systems. I suggest you take a look at the Servlet integration as an example, on which you can probably build (http://www.springframework.org/docs/...e-summary.html). Basically you have to do the following:
* Create an ExternalEvent (http://www.springframework.org/docs/...rnalEvent.html) subclass that captures all required information coming into the webflow system from the client system, so probably a TapestryEvent with appropriate properties usefull in a Tapestry environment.
* Create a FlowExecutionManager (http://www.springframework.org/docs/...onManager.html) that manages flow execution from the client system, so probably a TapestryFlowExecutionManager.
* A Tapestry integration component that can drive the flow execution from inside Tapestry (e.g. it is the client of the TapestryFlowExecutionManager). As an example, take a look at the FlowAction (http://www.springframework.org/docs/...lowAction.html) that drives web flow execution from inside Struts.
I don't know anything about Tapestry, so you might need to do other stuff, but this is the basic overview.
Apr 21st, 2005, 09:05 AM
Heel hartelijk bedankt, ik zal zien wat ik kan doen!(*)
(*) Thank you very much, I'll give it a try
Apr 25th, 2005, 01:21 PM
I'm also very interested into the Tapestry integration...
Originally Posted by jvpoucke
It seems to me that the flow could be integrated only with new components:
* ExternalEvent: if I understand that well, it receives info from the client (I assume for instance info from hidden fields), then that could be implemented in a subclass of a hidden component which would store and read/use the info
* FlowExecutionManager: would plug into the same previous component that stores info in hidden field or url
* TapestryFlowExecutionManager: I think this one could be plugged into several @Form components and be a listener.
So what about subclassing the @Form component into a @SWFForm?
An obscure point is how to integrate the tapestry valid components and custom errors into the workflow?