Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 363973

Summary: EJB Client project operation doesn't check supported java version when runtime set
Product: [WebTools] WTP EJB Tools Reporter: Chuck Bridgham <cbridgha>
Component: jst.ejbAssignee: Chuck Bridgham <cbridgha>
Status: RESOLVED FIXED QA Contact: Kaloyan Raev <kaloyan>
Severity: normal    
Priority: P3 CC: ccc
Version: 3.2   
Target Milestone: 3.2.5 P   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Bug Depends on:    
Bug Blocks: 364499, 364993    
Attachments:
Description Flags
patch none

Description Chuck Bridgham CLA 2011-11-16 15:46:15 EST 
Unlike most Faceted project creation operations.  The EJB Client op does not inherit the behavior of synching or reacting to a new runtime set, and checking for the latest java version supported.  This is because it inherits the "default" java version based on the initial fixed facet template.

For instance, if the EJB project version is 3.1, then it defaults to java 6.
Comment 1 Chuck Bridgham CLA 2011-11-16 17:05:40 EST 
Created attachment 207119 [details]
patch

This patch checks the current version of the java facet, and then determines the latest supported version, and switches to this...

Because this operation is only executed by the ejb project creation operation.
Comment 2 Carl Anderson CLA 2011-11-28 12:32:43 EST 
Committed to R3_2_5_patches
Comment 3 Chuck Bridgham CLA 2011-11-28 20:23:43 EST 
Correction - this was an EJB problem.. properly categorizing