Modular bundling of Flows and XHTML [SWF-1565]

[spring-operator]

Dhrubo opened SWF-1565* and commented

This has been reported in many forums and possibly issues. We all love to make modular applications. For example - we would love to pack - XHTML + Flows + other resouces (css, images) , controllers, services, repository code in different jars for ease of management, sharing , development etc. However it is not possible to do the same with SWF 2.3.1. Even if we can pack flows in jar, the view facelets would never be available as context classpath resource is required error. It would be great if SWF team helps us to sort out this problem. So that we can do modular development and deployment of applications with SWF which is such a wonderful framework

---

Affects: 2.3.1

Issue Links:

• The view path cannot be resolved if the flow is located in the classpath. [SWF-1319] #509 The view path cannot be resolved if the flow is located in the classpath.
  ("duplicates")
• Cannot load flows and views from classpath correctly in SWF 2.2.1 and JSF 2 [SWF-1425] #613 Cannot load flows and views from classpath correctly in SWF 2.2.1 and JSF 2
  ("duplicates")

[spring-operator]

Rossen Stoyanchev commented

We'll take a look. To be more specific, resources such as css and images can be loaded from the classpath. The issue is about flow definitions and XHTML pages.

[spring-operator]

Dhrubo commented

Thanks. Yes I know css, images can be loaded from the classpath. Problem is with flow definionts and XHTML pages. If we configure to load flows from classpath. It works fine flows are loaded. But the related views or xhtml files for that flow is never loaded and it fails with context classpath resource is required exception. I tried overriding with a bean post processor by changing the file resource to context classpath resource but then it fails while rendering. I am using PF 3.X, MOJARRA 2.1.10 on Tomcat 7.x running on Ubuntu 10 and JDK 1.6
Hope this helps

[spring-operator]

Phil Webb commented

Hi Dhrubo,

If you are using Maven, one option that you might want to consider, until this issue is addressed, is using war-overlays [1]. I have used this technique in the past to help split an application into logical modules. Obviously this is not ideal, but it may work as a stop-gap for you.

[1] http://maven.apache.org/plugins/maven-war-plugin/overlays.html