Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 316342

Summary:	JAXB Class Gen Wizard: Would be nice to add checkboxes for some compiler arguments
Product:	[WebTools] Dali JPA Tools	Reporter:	Andrew Fernandez <ripsi_1>
Component:	JAXB	Assignee:	Tran Le <tranle1>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	neil.hauge, shaun.smith
Version:	unspecified	Keywords:	noteworthy, plan
Target Milestone:	3.0 M1
Hardware:	PC
OS:	Windows XP
Whiteboard:	JAXB

Description Andrew Fernandez

2010-06-09 13:33:08 EDT

Build Identifier: 

Currently the JAXB Class Generation Wizard has options to specify a package, catalog file and bindings files.

It would be nice to add on the bottom of the generation page wizard , or a subsequent page (by clicking next), further options for a user to turn speficy further arguments.

For example a user could:

1) turn off generation of package-info.java
2) make files readonly
3) turn off strict validation
4) Allow vendor extensions

As a comparison, other OEPE web service wizards have added checkboxes for more common command line arguments that a user would want when invoking the wizard.

Otherwise, the wizard might be considered a minimal substitute for running the xjc on the command line.

Reproducible: Always

Steps to Reproduce:
1. Create web service project with latest WLS runtime in OEPE helios
2. Create package under source
3. Create new XSD or copy existing XSD to package
4. Launch JAXB generation wizard
5. Note options on current wizard

Comment 1 Andrew Fernandez

2010-06-09 17:28:59 EDT

making this a normal bug.

We do need checkboxes in the wizard (for some command line args) to provide robust functionality in the wizard. Otherwise, some users might just want to create types on the command line or through an ant script since the wizard might miss some more common customizations.

Comment 2 Neil Hauge

2010-07-19 13:10:24 EDT

I think we will want to add these options on an additional wizard page so the user can easily finish beforehand.  One or perhaps two columns of checkboxes (depending on space constraints) with a text input field on the bottom that can be used to pass in non-standard args to the generation process.  This could perhaps be labeled, "Non-standard arguments:" or "Additional arguments:".  "Additional arguments:" is probably better if we choose not to include all possible class gen compiler options at first.  Some will not make sense given current functionality, but as we provide additional schema input options (from a URL, allowing multiples) we can add relevant options into the compiler options page.

Comment 3 Tran Le

2010-07-27 15:28:47 EDT

Additional 2.1 compiler arguments we might want to add:

 -httpproxy <proxy> : set HTTP/HTTPS proxy. Format is [user[:password]@]proxyHost:proxyPort
 -httpproxyfile <f> : Works like -httpproxy but takes the argument in a file to protect password
 -classpath <arg> : specify where to find user class files

 -no-header : suppress generation of a file header with timestamp
 -target 2.0 : behave like XJC 2.0 and generate code that doesnt use any 2.1 features.
 -xmlschema : treat input as W3C XML Schema (default)
 -relaxng : treat input as RELAX NG (experimental,unsupported)
 -relaxng-compact : treat input as RELAX NG compact syntax (experimental,unsupported)
 -dtd : treat input as XML DTD (experimental,unsupported)
 -wsdl : treat input as WSDL and compile schemas inside it (experimental,unsupported)
 -verbose : be extra verbose
 -quiet : suppress compiler output
 -version : display version information

Comment 4 Neil Hauge

2010-08-12 09:48:14 EDT

Completed for M1.