Bug 115983

Summary: 'Use context' drop down doesn't pick up new entries once server is started
Product: [Retired] Red Hat Enterprise CMS Reporter: Daniel BerrangĂ© <berrange>
Component: uiAssignee: Scott Seago <sseago>
Status: CLOSED RAWHIDE QA Contact: Jon Orris <jorris>
Severity: medium Docs Contact:
Priority: medium    
Version: nightly   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-03-05 20:17:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 113496    

Description Daniel Berrangé 2004-02-17 14:17:54 UTC 
Description of problem:
When creating a JSP template for a content type, there is a down down
list box populated with TemplateContext objects. It appears, however,
that this is populated at page creation time, rather than pre-request,
so when new contexts are created they never appear until the next
server restart. This severly impacts on the APLAWS subsite &
navigation applications, since they both make heavy use of
TemplateContext objects - creating, editing & deleting them at runtime.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create a new subsite
2. GO to /ccm/content/admin
3. Select 'add template' link
  
Actual results:
New subsite does not appear in template context drop down

Expected results:
New subsite appears.

Additional info:
Comment 1 Scott Seago 2004-02-17 19:45:32 UTC 
Moved SingleSelect population to a PrintListener @40483