| Summary: | Expose "discover annotated classes" as a product preference | ||
|---|---|---|---|
| Product: | [WebTools] Dali JPA Tools | Reporter: | John Pitman <jpitman> |
| Component: | JPA | Assignee: | Paul Fullbright <paul.fullbright> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | neil.hauge |
| Version: | 2.0 | ||
| Target Milestone: | Future | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
John Pitman
I don't think this is an important item for 2.1 (which is releasing in December). As a result, deferring to 2.2 (Galileo). Please let me know if this is not the case. Investigate for M7. How should this work? Currently the preference is based on whether or not the user is (detectably) going to be deploying to an EE vs SE environment. In an EE environment, regardless of dev time settings (unless deconfigured using the persistence unit setting), the annotated classes *will* be discovered. In an SE environment, they typically will not. What is the use case you want to support? (In reply to comment #3) > How should this work? Currently the preference is based on whether or not the > user is (detectably) going to be deploying to an EE vs SE environment. In an > EE environment, regardless of dev time settings (unless deconfigured using the > persistence unit setting), the annotated classes *will* be discovered. In an > SE environment, they typically will not. > > What is the use case you want to support? > I think they want to "hard-code" the preference so that it is always in discovery mode. The confusing part to me is: is the desired intent to *override* the user election? or just to preselect the dialog? Should the validation for this setting be turned off? If so, is that also a preference? Deferring until we have more information ... Moving JPA specific bugs to new JPA component in bugzilla. This is close enough to the other bug to mark as duplicate. *** This bug has been marked as a duplicate of bug 387586 *** |