Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 363973 - EJB Client project operation doesn't check supported java version when runtime set
Summary: EJB Client project operation doesn't check supported java version when runtim...
Status: RESOLVED FIXED
Alias: None
Product: WTP EJB Tools
Classification: WebTools
Component: jst.ejb (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 3.2.5 P   Edit
Assignee: Chuck Bridgham CLA
QA Contact: Kaloyan Raev CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 364499 364993
  Show dependency tree
 
Reported: 2011-11-16 15:46 EST by Chuck Bridgham CLA
Modified: 2011-12-01 16:02 EST (History)
1 user (show)

See Also:

Attachments
patch (3.46 KB, patch)
2011-11-16 17:05 EST, Chuck Bridgham CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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