| Summary: | jpa project wizard fails to set the target rt for ear | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] Dali JPA Tools | Reporter: | Ram Venkataswamy <ram.venkataswamy> | ||||
| Component: | General | Assignee: | Paul Fullbright <paul.fullbright> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | david_williams, konstantin, neil.hauge | ||||
| Version: | 3.0 | Flags: | david_williams:
pmc_approved+
neil.hauge: pmc_approved? (raghunathan.srinivasan) neil.hauge: pmc_approved? (naci.dai) neil.hauge: pmc_approved? (deboer) neil.hauge: pmc_approved? (neil.hauge) neil.hauge: pmc_approved? (kaloyan) neil.hauge: pmc_approved? (cbridgha) neil.hauge: review+ |
||||
| Target Milestone: | 3.0 RC2 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | PMC_approved | ||||||
| Attachments: |
|
||||||
|
Description
Ram Venkataswamy
Please forward to Java EE tools if you think that's where this bug belong, but Ram has indicated that this problem does not exist in the Web project wizard. Found in Indigo M5. Created attachment 195553 [details]
proposed patch
Problem was that when adding to an ear, the module facet data model needed to have its runtime set. It wasn't enough to have the JPA facet data model runtime set.
The wizard still has the annoying behavior of resetting your previously set facets when setting a runtime, but I've tested this in a number of different orders and conditions, and there is no exception and the ear's runtime is accurately set.
* Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such.
This is an adopter requested fix which results in a EAR that cannot be deployed.
* Is there a work-around? If so, why do you believe the work-around is insufficient?
Workaround is to go into the EAR properties and manually set the Target Runtime
* How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added?
The fix has been tested by Paul and myself. JUnit tests have been run.
* Give a brief technical overview. Who has reviewed this fix?
See comment #3. I have reviewed the fix
* What is the risk associated with this fix?
Risk is low, fix is isolated.
committed for rc1 |