Announcement Announcement Module
Collapse
No announcement yet.
2.0 M4 to 2.0.0.RC1 Upgrade Steps Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • 2.0 M4 to 2.0.0.RC1 Upgrade Steps

    For those of you running M4, there are a few configuration changes you will likely need to make when upgrading to 2.0.0.RC1. Thanks to Peter for initially compiling this list for the benefit of our community. I've taken the list, added to it, and stuck this thread.

    M4 to 2.0.0.RC1 Configuration Changes
    --------------------------------------------

    The ResourceServlet has moved from Spring Faces to Spring Javascript (spring-js), as it is reusable outside of a JSF environment:

    Code:
    M4:
    org.springframework.faces.ui.resource.ResourceServlet
    
    RC1:
    org.springframework.js.resource.ResourceServlet
    The faces-config namespace has changed to just 'faces', in-line with Spring schema naming conventions:

    Code:
    M4:
    xmlns:faces="http://www.springframework.org/schema/faces-config"
    http://www.springframework.org/schema/faces-config
    http://www.springframework.org/schema/faces-config/spring-faces-config-2.0.xsd
    
    RC1:
    xmlns:faces="http://www.springframework.org/schema/faces"
    http://www.springframework.org/schema/faces
    http://www.springframework.org/schema/faces/spring-faces-2.0.xsd
    The Spring MVC FlowController has moved to the mvc.servlet package, since there is also now mvc.portlet support:

    Code:
    M4:           
    org.springframework.webflow.mvc.FlowController
    
    RC1:
    org.springframework.webflow.mvc.servlet.FlowController
    You will see this error if defining flow <var>'s that use the 'scope' attribute:

    Code:
    org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'scope' is not allowed to appear in element 'var'.
    The <flow> <var> element no longer has a 'scope' attribute. Flow instance variables should be flow scoped, so the attribute is unnecessary. For those using a value of 'conversation' before, first evaluate if you need conversation scope instead of flow scope; if so, set the conversation scoped variable using an on-start action instead.

    You will see this error if you are not running Spring Framework 2.5.3:

    Code:
    org.springframework.web.util.NestedServletException: Handler processing failed; nested exception is java.lang.NoSuchMethodError: org.springframework.util.xml.DomUtils.getChildElementsByTagName(Lorg/w3c/dom/Element;[Ljava/lang/String;)Ljava/util/List;
    Web Flow 2.0.0.RC1 requires Spring 2.5.3.
    Last edited by Keith Donald; Apr 14th, 2008, 07:53 AM.

  • #2
    a couple more things

    Code:
    m4:
    org.springframework.webflow.mvc.MvcViewFactoryCreator
    
    Rc1
    org.springframework.webflow.mvc.view.MvcViewFactoryCreator


    Code:
    m4:
    <bean id="flowController" class="org.springframework.webflow.mvc.servlet.FlowController">
    		<constructor-arg ref="flowExecutor" />
    		<property name="flowRequestUrlHandler">
    			<bean class="org.springframework.webflow.context.servlet.ParameterBasedFlowUrlHandler"/>
    		</property>
    
    	</bean>
    	
    
    rc1
    <bean id="flowController" class="org.springframework.webflow.mvc.servlet.FlowController">
    		<constructor-arg ref="flowExecutor" />
    		<property name="flowUrlHandler">
    			<bean class="org.springframework.webflow.context.servlet.WebFlow1FlowUrlHandler"/>
    		</property>
    	</bean>
    note the change in the property name. In the reference doc it is the new class file but the old property name

    Comment


    • #3
      When using facelets don't forget to add the following in your web.xml:

      Code:
      <context-param> 
          <param-name>facelets.RESOURCE_RESOLVER</param-name>  
          <param-value>org.edoframework.faces.ClasspathResourceResolver</param-value> 
        </context-param>
      Kind regards
      Jan

      Comment


      • #4
        Originally posted by secutus View Post
        When using facelets don't forget to add the following in your web.xml:

        Code:
        <context-param> 
            <param-name>facelets.RESOURCE_RESOLVER</param-name>  
            <param-value>org.edoframework.faces.ClasspathResourceResolver</param-value> 
          </context-param>
        What is this for? The sample application doesn't require it. Which jar do you need for the dependency.

        Comment


        • #5
          yes,why this is required?

          Comment


          • #6
            Hello,

            My previous post on this thread was done at the wrong place and at the wrong time. Sorry for that.
            Still the class mentioned in my post allows our framework to search for facelets template in the classpath.

            Kind regards
            Jan

            Comment

            Working...
            X