[
https://issues.apache.org/jira/browse/AXIS2-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi resolved AXIS2-4583.
-------------------------------------------------
Resolution: Won't Fix
According to the Basic profile you need to declare the part you going to use at
the soap binding if more than
one part is given in the message.
Axis2 Codegen follows most of the ws-i recommendations in order to make the
code generation simplified.
> axis2 wsdl2java - more than one part for message
> ------------------------------------------------
>
> Key: AXIS2-4583
> URL: https://issues.apache.org/jira/browse/AXIS2-4583
> Project: Axis2
> Issue Type: Bug
> Components: codegen
> Environment: Windows XP SP3, Eclipse Java EE IDE for Web Developers,
> JBoss 4.0
> Reporter: Aaron Witt
> Attachments: screenshot-1.jpg
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> I am trying to generate code off of a WSDL
> (https://thefinder.tax.ohio.gov/OHFinderService/OHFinderService.asmx?WSDL)
> using the wsdl2java utility provided in the Axis2 v1.5.1 jar. Whenever I try
> this, regardless of the different switches that can be used, I get the error,
> "more than one part for message GetOHSalesTaxByAddressSoapIn." I've done a
> fair amount of researching on the issue, and, obviously, there is something
> not spec about this WSDL. However, this being the Ohio Department of
> Taxation's WSDL, I am not getting much of a response from them on the issue,
> and, assuming this is fairly widely used throughout Ohio, at least, most
> people must be working fine with this WSDL as it stands. Another interesting
> note is that using .NET or axis (the first one, specifically 1.4), I am able
> to generate the code from this WSDL. I cannot use axis1, though, because our
> production system is using quite a few axis2 jars, and we have experienced
> nothing but jar hell trying to get those two to mix in our production
> environment. Does anyone out there have an idea as to why I am getting this
> error? Is there something I can do to correct their WSDL while still abiding
> by the original communication contract? Or perhaps there is a switch of
> which I'm unaware that will be less stringent about generating code off of a
> WSDL? I know that you people are going to be helping me, so I don't mean to
> sound petulant here (and I preemptively apologize if I do sound that way),
> but this is a time-sensitive matter for me, so the quicker the help, the
> better. Thanks.
--
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]
