Community
Participate
Working Groups
Process: - Create an EAR without a runtime selected. (Only one, so that it is the default EAR project) - Launch new EJB project wizard. Enter name. Default version for me is 3.0; it may be necessary to create a 3.0 EJB project first so that this is the default. - Open facets dialog, add JPA facet. OK. - Choose "Add project to an EAR". There is a validation message that an EAR project already exists at this location. (which in itself is likely a bug) - Touch the EAR project name dropdown without selecting anything. At this moment, the JPA facet is removed, and the EJB facet version is changed to 3.1. This seems wrong to me. Once I've added a facet, the wizard should not be removing it, even if the new target runtime (determined by the runtime of the now resolved EAR project) has a different set of "default" facets. There should be a validation message instead, I would think.
I should note that I'm doing this in head code.
Or perhaps instead of just setting the list of facets to be the default facets for that runtime, only new facets that are default for that runtime should be added, with existing facets and versions left untouched.
Assigning to Jason Sholl for initial investigation.
Konstantin- this appears to be related to interaction with the facets.
> Konstantin- this appears to be related to interaction with the facets. Depends on what you mean by interaction, but this doesn't appear to be a framework issue. The logic for what to do when user selects an EAR is in Java EE Tools code. Based on what I recall of these discussions from years ago, the described behavior is as designed. There were some strong feelings about resetting facets in this case.
