Announcement Announcement Module
Collapse
No announcement yet.
Description attribute/element and portlet support Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Description attribute/element and portlet support

    Hi,

    I have to questions about Spring WebFlow:

    1. Would it be possible for you to add a "description" attribute or sub element to the "webflow" element? We are building a rather large application on SWF and we would like to be able to create a "catalog" with descriptions of the implemented flows. This could be implemented as an ant task which builds javadoc like docs.

    2. We want to deploy our flows as portlets and would like to test this as soon as possible. When will the portlet support be released with SWF? Is there already something in CVS that we can test?

    Thanks in advance

    /Kax

  • #2
    1) All elements in the SWF XML support 'properties' to describe them. At the Java code level they are AnnotatedObject's (http://static.springframework.org/sp...tedObject.html).

    So in the XML definition you could have:

    Code:
    <webflow id="myFlow" start-state="someState">
       <property name="description" value="My First Flow"/>
       ...
    </webflow>
    You're ofcourse free to select the property names you want.

    2) Portlet support is making it's return ASAP, as soon as Spring 1.3 RC1 is available a new SWF release will be made that reintroduces Portlet support. Hopefully this will be later this month!

    Erwin

    Comment


    • #3
      This feature appears not to support lists in the following way:

      Code:
      <property name="applicationTransactionParticipants">
         <list>
            <value>myFirstSubflow</value>
            <value>myThirdSubflow</value>
         </list>
      </property>
      Is this accurate? Is there another less obvious way that I could simulate this capability?

      Comment


      • #4
        The properties are basic String properties by default. So either you'll have to parse them yourself from a string representation, or you can use the type attribute with a custom Convertor:
        Code:
        <property name="foo" type="java.util.ArrayList">
           <value>bar0, bar1</value>
        </property>
        You then have to register a String->ArrayList convertor with the ConversionService.

        Erwin

        Comment

        Working...
        X