[jira] Closed: (AXIS-1240) Enhance wsdl2java generation to selectively generate classes

[ji...@apache.org]

Message:

   The following issue has been closed.

   Resolver: Davanum Srinivas
       Date: Tue, 23 Mar 2004 6:15 AM

Already applied patch in cvs. Please reopen if necessary.
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/secure/ViewIssue.jspa?key=AXIS-1240

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1240
    Summary: Enhance wsdl2java generation to selectively generate classes
       Type: Bug

     Status: Closed
 Resolution: FIXED

    Project: Axis
 Components: 
             WSDL processing
   Fix Fors:
             current (nightly)
   Versions:
             1.2 Alpha

   Assignee: 
   Reporter: jim

    Created: Tue, 24 Feb 2004 1:27 PM
    Updated: Tue, 23 Mar 2004 6:15 AM
Environment: Operating System: All
Platform: All

Description:
This enhancement request and posted solution has to do with the desire for a
straight forward way to deletively generate certain classes from a WSDL file, so
that we can use externally generated beans with our generated static
stubs/skeletion code.

One has the ability to create any number of namespaces within the WSDL and
assign each namespace a separate java package. The current approach is to have
the code generation generate all ocde to a temproary directory and then copy out
the classes that are needed and leave behind the classes that are externally
generated.

The requested/supplied approach adds a few additional options to the WSDL to
Java generation. An nsexclude option specifically excludes named namespaces from
being generated and a nsinclude option specifically includes named namespaces
(defaults to all that were not excluded) in the generated code.

This might have been done as a custom JavaGeneratorFactory excedpt that the
current design of the wsdl to java generation does not allow properties to be
defined/passed to the factory. A third parameter was added to the candidate
solution which allows an undefined name/value set of properties to be assigned
to the emitter and usable by the custom factory.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira