|
Firstly, I will describe a little about the current implementation of our website in Magnolia. Then I'll describe the problem that I am facing.
We have a website that contains a booking flow. The flow contains a number of pages - search, results, itinerary, payment, confirmation.
At this current moment, the booking flow has been developed as a Blossom Webflow component. This means that the component can be dropped into an area inside a magnolia template.
The problem is this - the business wants to be able to control the booking flow pages from within the author. For example:
The search page is a JSP inside the web application. It is mapped within the webflow view state and resolved by a Spring view resolver. But the business wants to author this page - the business wants to add/remove components to the search page. Also the business want to do the same for other booking flow pages from within the author.
How can we achieve this? Is there a way of defining the pages inside magnolia author and for the Webflow view states to map to them?
We've looked into a couple of potential solutions - the best looking solution involves redirects, e.g.
<view-state id="results" view="externalRedirect:contextRelative:results.html?flowExecutionUrl=#
{flowExecutionUrl}
">
This 'works' (there are a few quirks) up until we start to use the Webflow asynchronous support which should return a fragment from the page. Redirecting won't be compatible with this solution
Do you have a magnolia specific solution (or in fact any solution) to this problem?
Hopefully this describes the problems we're facing - its sometimes difficult to explain more complex problems outside of a conversation so please let me know if any of this is unclear.
Cheers,
Tony
|
