[ http://issues.apache.org/jira/browse/AXIS2-663?page=all ]

Deepal Jayasinghe reassigned AXIS2-663:
---------------------------------------

    Assign To: Ajith Harshana Ranabahu

> WSDL2Java: allow user to specify separate destination folders for src and 
> resources
> -----------------------------------------------------------------------------------
>
>          Key: AXIS2-663
>          URL: http://issues.apache.org/jira/browse/AXIS2-663
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Improvement

>   Components: Tools
>     Versions: 1.0
>  Environment: Axis2 1.0 RC5
>     Reporter: Thilo Frotscher
>     Assignee: Ajith Harshana Ranabahu

>
> WSDL2Java generates source code, resources (service.xml, wsdl, xsd) and a 
> build.xml file.
> The user can specify a destination folder for all of these files, but they 
> all go into the same folder.
> When generating code for more than one service, you'll generally want to have 
> the source code for all services in the same src-folder.
> That's why you would specify the same destination folder for all services. 
> However, in this causes the problem that the build.xml files 
> and the resources for all the services go into the same folder as well and 
> interfere with each other, or a overwritten respectively.
> Therefore, it would be great if the user could specify two separate 
> destination folders: one for the source code and the second one for 
> the build file and the resources. Of course, the build files would have to 
> reflect the new folder structure.
> Alternative suggestion: WSDL2Java could do this automatically by introducing 
> a service-specific folder
> under resouces:
> /resources/MyService1/service.xml
> /resources/MyService1/MyService.wsdl
> /resources/MyService1/MyService.xsd
> /resources/MyService2/service.xml
> /resources/MyService2/MyService.wsdl
> /resources/MyService2/MyService.xsd
> For the build files a similar solution could be used.

-- 
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

Reply via email to