Issue Details (XML | Word | Printable)

Key: ICE-4394
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Ted Goddard
Votes: 2
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
ICEfaces

Google App Engine support

Created: 22/Apr/09 11:35 AM   Updated: 07/Jan/10 12:07 PM
Component/s: Framework
Affects Version/s: 1.8
Fix Version/s: 1.8.1

Environment: ICEfaces, Google App Engine

ICEsoft Forum Reference: http://www.icefaces.org/JForum/posts/list/12361.page


 Description  « Hide

It is desirable to have ICEfaces applications run on the Google App Engine.


 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Ted Goddard added a comment - 22/Apr/09 11:52 AM

Core changes to support the Google App Engine fall into two categories:
 
  1. Threads cannot be spawned (this affects MonitorRunner, SessionMonitor, and MessageServiceClient)
  2. InetAddress is not available (this affects ICEfaces ID generation)

Ted Goddard added a comment - 22/Apr/09 12:37 PM
Changes for auctionMonitor included the following:

Synchronous mode:

     <context-param>
         <param-name>com.icesoft.faces.synchronousUpdate</param-name>
        <param-value>true</param-value>
     </context-param>

Do not run the item update in parallel:

// Thread t = new Thread(
// new AuctionMonitorItemDetailer(this, searchItemBeans));
// t.start();
            (new AuctionMonitorItemDetailer(this, searchItemBeans)).run();

Comment-out RenderManager in faces-config.xml (not relevant for synchronous mode and the app engine objects to the managed-property injection).

Ted Goddard added a comment - 27/Apr/09 11:47 AM

Google App Engine fixes for synchronous mode applications have been checked in. Please create individual JIRA entries for any specific issues.