Details
-
Type:
Improvement
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.8, 1.8.1
-
Fix Version/s: None
-
Component/s: Documentation
-
Labels:None
-
Environment:ICEfaces 1.8
Description
In the Known Issues section, there is this statement for BEA Weblogic Server 9 & 10:
When deploying an ICEfaces application that uses the ice:inputFile and/or ice:dataExporter components to WebLogic 9 or 10 you must use an exploded directory copied to the domain's autodeploy directory, rather than simply using .war files or using the console. Otherwise, the file-write operations these components depend on will fail (as there is no writeable directory in a .war file).
For ice:inputFile, this is actually only true if a relative uploadDirectory is used (com.icesoft.faces.uploadDirectoryAbsolute = false). Using an absolute uploadDirectory outside the application server's directories should be suggested as a workaround.
When deploying an ICEfaces application that uses the ice:inputFile and/or ice:dataExporter components to WebLogic 9 or 10 you must use an exploded directory copied to the domain's autodeploy directory, rather than simply using .war files or using the console. Otherwise, the file-write operations these components depend on will fail (as there is no writeable directory in a .war file).
For ice:inputFile, this is actually only true if a relative uploadDirectory is used (com.icesoft.faces.uploadDirectoryAbsolute = false). Using an absolute uploadDirectory outside the application server's directories should be suggested as a workaround.