Summary: | Support invocation of JAXB schema generator | ||||||
---|---|---|---|---|---|---|---|
Product: | [WebTools] Dali JPA Tools | Reporter: | Shaun Smith <shaun.smith> | ||||
Component: | JAXB | Assignee: | Tran Le <tranle1> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | enhancement | ||||||
Priority: | P3 | CC: | karenfbutzke, neil.hauge, tranle1 | ||||
Version: | 2.3 | Keywords: | PII, plan | ||||
Target Milestone: | 2.3 M7 | Flags: | neil.hauge:
pmc_approved?
(david_williams) neil.hauge: pmc_approved? (raghunathan.srinivasan) neil.hauge: pmc_approved? (naci.dai) neil.hauge: pmc_approved? (deboer) neil.hauge: pmc_approved+ neil.hauge: pmc_approved? (kaloyan) neil.hauge: review+ |
||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | PMC_approved | ||||||
Attachments: |
|
Description
Shaun Smith
2009-11-30 13:23:49 EST
This implementation should follow the general design laid out in bug 296502 comment 2. Below is a proposal for the user interaction. This functionality should originate in the standard New... Wizard in one or both of the following locations (feedback welcome): "JAXB" (new folder) "XML" (existing folder) > "Schema from JAXB Classes" In addition, a JAXB Tools" menu could be added to Java projects, but I would lean against this to avoid additional menu clutter. The New wizard dialog should filter out projects that are not Java projects (for project selection). Once a project has been selected, the user will need to select the package or classes that they wish to use for the generation. Something similar to Export->Archive would be called for here. (I assume we would need this level of granularity, or would be it be reasonable to only offer only the ability to select a project, where all annotated entities will be used in the schema gen?) Another item required would be the schema destination folder. The last item would be an extension dependent checkbox to specify if you are using EclipseLink as your JAXB implementation. Created attachment 161679 [details]
Schema Generator
Notes:
- this patch for JAXB schema generation generates from all classes included in a package.
- jaxb.properties file need to be present
- bunddle org.eclipse.jpt.jaxb.core.schemagen has to be exported to a jar and put in ECLIPSE_HOME/plugins
- package, project, folder may be selected to start the generation wizard.
Requesting PMC approval of UI change associated with this planned feature exception. There is a new JAXB folder in the "New..." wizard associated with this change, with one wizard inside of this new folder for the purpose of XSD Generation using either the Sun RI JAXB Schema Gen or the EclipseLink JAXB Schema Gen. Approving as this was for notification purposes. This change requires compiling against EclipseLink but doesn't require shipping any EclipseLink components. This was released in time for last night's I-build candidate. verified fixed in WTP build I-3.2.0-20100427043043 |