axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samuel Listopad (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (AXIS2-4583) axis2 wsdl2java - more than one part for message
Date Wed, 16 Jun 2010 17:20:24 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879383#action_12879383
] 

Samuel Listopad edited comment on AXIS2-4583 at 6/16/10 1:18 PM:
-----------------------------------------------------------------

According to the WSDL spec I do not believe there is anything wrong with this WSDL, however
it does not conform to the WS-I spec.  I am having the same problem.

I believe AXIS should be able to deal with messages that do not follow the WS-I spec.

      was (Author: samlii):
    According to the WSDL spec I do not believe there is anything wrong with this WSDL.  I
amhaving the same problem.

I believe AXIS should create a wrapper type when the message is multi-part.
  
> 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: wsdl
>         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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message