[
https://issues.apache.org/jira/browse/AXIS2-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5584.
------------------------------------
Resolution: Incomplete
> Unable to generate Custom WSDL using Axis2
> ------------------------------------------
>
> Key: AXIS2-5584
> URL: https://issues.apache.org/jira/browse/AXIS2-5584
> Project: Axis2
> Issue Type: Bug
> Components: jaxws, wsdl
> Affects Versions: 1.6.2
> Environment: Jboss 5.1 GA and Jboss 4.0.5 GA
> Reporter: prathamesh Vagal
> Priority: Blocker
> Fix For: 1.6.2
>
> Original Estimate: 36h
> Remaining Estimate: 36h
>
> I am trying to generate WSDL based on existing custom WSDL provided. Custom
> WSDL was validated using SOAPUI. It generates operations perfectly.
> However, when deployed this WSDL within EAR it is not getting recognized by
> axis2.
> We have tried deploying custom WSDL & Schema (XSD) in EAR as follow
> 1. EAR->WAR->WEB-INF->services->AAR->META-INF->custom wsdl, xsd, services.xml
> 2. EAR->WAR->WEB-INF & xsd->services.xml,wsdl.
> Note: we had kept useoriginalwsdl = true in services.xml for all above cases.
> We didn't receive any error in deployment however we received message as
> Unable to generate WSDL 1.1 for this service If you wish Axis2 to
> automatically generate the WSDL 1.1, then please set useOriginalwsdl as false
> in your services.xml
> We also had kept service name from WSDL,EAR name, WAR name, WSDL name and
> Service name from services.xml same.
> Can anyone provide exact deployment structure of custom WSDL with EAR for
> Axis2?
> It is bit urgent.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
