Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.8.2-EE-GA, 1.8.2a
-
Fix Version/s: 1.8.2-EE-GA_P01, 1.8.3
-
Component/s: Framework
-
Labels:None
-
Environment:WebLogic Portal Spring Web Flow
-
Assignee Priority:P1
Description
We have code that detects whether Spring Web Flow (SWF) is present and, if it is, uses a different LifecycleExecutor. However our detection code only looks to see if SWF is loadable from the classpath. Not if it's actually configured to be used.
It appears that on WebLogic Portal, SWF is loadable whether or not it's being used which causes it to attempt to use certain code paths in the ICEfaces framework. We need to make our SWF detection more sophisticated to deal with this as I wasn't able to tell how to remove SWF as a loadable library. Even if that is possible, it may cause other parts of WebLogic Portal to be inoperable.
It appears that on WebLogic Portal, SWF is loadable whether or not it's being used which causes it to attempt to use certain code paths in the ICEfaces framework. We need to make our SWF detection more sophisticated to deal with this as I wasn't able to tell how to remove SWF as a loadable library. Even if that is possible, it may cause other parts of WebLogic Portal to be inoperable.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Code has been committed that enhances our Spring detection code. Now we not only check to see that Spring Web Flow is available on the classpath, but we also check to see that our custom servlet (SpringWebFlowInstantiationServlet) has been initialized - which implies that SWF is purposefully being used.