Details
-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 3.1
-
Fix Version/s: None
-
Component/s: Bridge
-
Labels:None
-
Environment:Weblogic 10.3.5
Windows
Description
Let me put in this way, I am installing liferay from scratch and i have placed the portal-service and portlet Jar in mydomain/lib folder when i restart the server and access my non portlet icefaces application it gives me below mentioned error
WARNING: Unable to find WindowScope for view /general/logins/login.xhtml
Oct 7, 2013 7:58:56 PM org.icefaces.impl.event.WindowAndViewIDSetup$1 encode
SEVERE: Missing window ID attribute. Request map cleared prematurely.
And when i remove those JAR from mydomain/lib folder then the icefaces application runs accordingly. The weblogic entry for icefaces application is
<?xml version="1.0"?>
<wls:weblogic-web-app
xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-web-app"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.4/weblogic-web-app.xsd"
>
<wls:container-descriptor>
<wls:prefer-application-packages>
<wls:package-name>org.apache.xerces.*</wls:package-name>
</wls:prefer-application-packages>
<wls:optimistic-serialization>true</wls:optimistic-serialization>
</wls:container-descriptor>
<wls:library-ref>
<wls:library-name>jsf2.0</wls:library-name>
</wls:library-ref>
<wls:context-root>/CCMWeb</wls:context-root>
</wls:weblogic-web-app>
Regards,
Muhammad Amir Hanif
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Please note that, due to changes made as per ICE-9157, the logging for missing window ID attribute are now only fired as WARNINGS and only when in Development stage. So it could be that it's simply a potentially expected behaviour where the logging has been reduced in severity. You may want to consider upgrading to the latest version of ICEfaces and running your application again.
Thanks for the reply, I have been running the application in production mode and I have also update the version to icefaces 3.3 but still same issue. Your help in this regard will be of great help.
For ICEfaces 3.3, the code in question is as follows:
if (windowID == null) { if (context.isProjectStage(ProjectStage.Development)) { Log.warning("Missing window ID attribute. Request map cleared prematurely."); } return; }
So the latest version of ICEfaces will not log anything unless the ProjectStage is set to Development and it will only log a WARNING, not a SEVERE-level event. As noted in a previous comment, further support for running Liferay under WebLogic requires an enterprise support agreement.
I have been using Community Edition version of Liferay which does not requires any license,can you please specify whetehr it is better way to dedicate application server/domain to run only Liferay Portal. What I think is that icefaces lifecycle is effected by the portal lifecycle due to which non portlet icefaces application are not working when liferay deployed on weblogic.
You could try running Liferay on Tomcat (you can download pre-bundled versions from Liferay directly) and see if you run into the same problem.
This is likely a Liferay/WebLogic specific configuration issue and would need to be dealt with under a commercial support agreement.