Bug 742952 - WFK20_0120: [Committed] [Dev] [P1] RichFaces OpenShift Showcase
Summary: WFK20_0120: [Committed] [Dev] [P1] RichFaces OpenShift Showcase
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: Requirements
Version: 2.0.0.GA
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 2.0.0.GA
Assignee: mark yarborough
QA Contact: Pavol Pitonak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-03 13:02 UTC by mark yarborough
Modified: 2012-06-22 07:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-22 07:22:38 UTC
Type: ---


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RFPL-1455 0 None Resolved Port richfaces-showcase demo to OpenShift 2012-06-18 08:20:42 UTC

Description mark yarborough 2011-10-03 13:02:39 UTC

Comment 1 mark yarborough 2011-12-19 15:53:31 UTC
Burr Sutter (Product Manager) indicates development complete.

Comment 2 Burr Sutter 2012-03-19 14:35:42 UTC
http://showcase.richfaces.org/

Currently at OpenShift Flex.

End-user Workflow:
1) Import into JBDS 5
2) Use the OpenShift Application wizard to upload to their personal account
3) Push to http://myshowcase-mydomain.rhcloud.com

Comment 3 Brian Leathem 2012-03-20 17:07:13 UTC
is OpenShift Express no longer a target for the WFK Richfaces showcase?

Comment 4 Brian Leathem 2012-04-19 16:23:12 UTC
This is done, the production richfaces showcase (http://showcase.richfaces.org/) runs on OpenShift express:
http://showcase-richfaces.rhcloud.com/

Comment 5 Karel Piwko 2012-06-04 09:05:19 UTC
Moved to ON_QA.

Comment 6 Pavol Pitonak 2012-06-04 14:56:26 UTC
Showcase 2.0.0.ER7 runs on OpenShift.

Comment 7 Karel Piwko 2012-06-18 08:21:06 UTC
Verified in WFK 2.0.0.ER8.

Comment 8 Karel Piwko 2012-06-22 07:22:38 UTC
Closing requirements as CURRENTRELASE for 2.0.0. Bits on CSP were verified.


Note You need to log in before you can comment on or make changes to this bug.