You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Ajith Harshana Ranabahu (JIRA)" <ji...@apache.org> on 2005/09/30 07:55:47 UTC

[jira] Commented: (AXIS2-249) Exessive number & size of files generated from WSDL

    [ http://issues.apache.org/jira/browse/AXIS2-249?page=comments#action_12330909 ] 

Ajith Harshana Ranabahu commented on AXIS2-249:
-----------------------------------------------

Here is a small explanation.
1. The number of generated classes. Bulk of the generated classes belong to XMLBeans data binding (around 70% your WSDL consists of the schema!). It's a fact that we cannot change unless another data binding framework is introduced,  which I presume would not change the number drastically.
2. The download side. Sadly this is one thing that we need to improve. If you peep into the binary distribution, it's not really only the bin. It's a complete bundle! it has the samples, the libs and a packaged version of the war (web archive) and even the docs. The duplication of jars created by including the lib seems to be the main culprit. Perhaps introducing several flavors (complete, minimum,war etc) of the distribution would be a better idea!

> Exessive number & size of files generated from WSDL
> ---------------------------------------------------
>
>          Key: AXIS2-249
>          URL: http://issues.apache.org/jira/browse/AXIS2-249
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>   Components: client-api
>     Versions: 0.92
>  Environment: WinXP, JDK 5.0
>     Reporter: Simon Fell
>  Attachments: enterprise.wsdl
>
> The code generated from the WSDL seems to be extremely excessive both in terms of numbers & size, are you code gen'ing the entire runtime engine??
> for the same WSDL, .NET 1.1 generates 1 file that is 220K bytes, Axis 1.1 generates 124 files totaling 1.97Mb, and Axis 2.0 generates 2011 files totally over 10Mb.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira