Mention of JAXBRI Binding File Name extension property in wsdl2java usage text 
poorly placed
--------------------------------------------------------------------------------------------

                 Key: AXIS2-4740
                 URL: https://issues.apache.org/jira/browse/AXIS2-4740
             Project: Axis2
          Issue Type: Bug
          Components: codegen
    Affects Versions: 1.5.1
            Reporter: Andrew
            Priority: Trivial


When running the wsdl2java.sh command, the usage message places the line

{noformat}
-EbindingFileName <path>               (for jaxbri) - specify the file path for 
the episode file
{noformat}

just below the line

{noformat}
-scn <class-name>        Skeleton class name...
{noformat}

when it should actually go after the line

{noformat}
xmlbeans distribution and replace the Axis2 generated classes with correct 
classes
{noformat}

More specifically, it currently looks like this:

{noformat}
  -E<key> <value>          Extra configuration options specific to certain 
databindings. Examples:
                           -Ebindingfile <path>                   (for jibx) - 
specify the file path for the binding file
                           -Etypesystemname <my_type_system_name> (for 
xmlbeans) - override the randomly generated type system name
                           -Ejavaversion 1.5                      (for 
xmlbeans) - generates Java 1.5 code (typed lists instead of arrays) 
                           -Emp <package name> (for ADB) - extension mapper 
package name
                           -Eosv (for ADB) - turn off strict validation.
                           -Ewdc (for xmlbeans) - Generate code with a dummy 
schema. if someone use this option
                              they have to generate the xmlbeans code 
seperately with the scomp command comes with the
                              xmlbeans distribution and replace the Axis2 
generated classes with correct classes
  --noBuildXML             Dont generate the build.xml in the output directory
  --noWSDL                 Dont generate WSDLs in the resources directory
  --noMessageReceiver      Dont generate a MessageReceiver in the generated 
sources
  --http-proxy-host <host> Proxy host address if you are behind a firewall
  --http-proxy-port <port> Proxy port address if you are behind a firewall
  -ep <package-name-list>  Exclude packages - these packages are deleted after 
code generation
  -sin <interface-name>    Skeleton interface name - used to specify a name for 
skeleton interface other than the default one 
  -scn <class-name>        Skeleton class name - used to specify a name for 
skeleton class other than the default one
                           -EbindingFileName <path>               (for jaxbri) 
- specify the file path for the episode file
{noformat}

While it should look like this:

{noformat}
  -E<key> <value>          Extra configuration options specific to certain 
databindings. Examples:
                           -Ebindingfile <path>                   (for jibx) - 
specify the file path for the binding file
                           -Etypesystemname <my_type_system_name> (for 
xmlbeans) - override the randomly generated type system name
                           -Ejavaversion 1.5                      (for 
xmlbeans) - generates Java 1.5 code (typed lists instead of arrays) 
                           -Emp <package name> (for ADB) - extension mapper 
package name
                           -Eosv (for ADB) - turn off strict validation.
                           -Ewdc (for xmlbeans) - Generate code with a dummy 
schema. if someone use this option
                              they have to generate the xmlbeans code 
seperately with the scomp command comes with the
                              xmlbeans distribution and replace the Axis2 
generated classes with correct classes
                           -EbindingFileName <path>               (for jaxbri) 
- specify the file path for the episode file
{noformat}

I missed it the first time through the usage text, since it wasn't where I 
expected it to be, and I was worried that Axis2 might not support the binding 
file for JAXB at all...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to