Stefan,
There is no reason to believe that the Jira WSDL violates the WSDL
standard. The use of "element" instead of "type" for faults is
required by the WS-I profile, but I'm not sure if this particular
requirement also applies to rpc/encoded services.
Andreas
On 18 Mar 2008, at 23:14, stlecho wrote:
Andreas,
When reading through the referenced post, I conclude that the WSDL
provided
by Jira should be modified when using Axis2. Personally I find this
quite
annoying :o(.
It would be interesting to verify (but unfortunately I'm not a WSDL
expert)
if the Jira WSDL violates certain aspects of the WSDL standard. If
this is
the case, Atlassian could be asked to change it so that it conforms
with the
WSLD standard.
Any help from a "WSDL expert" to have a look at this issue?
Regards, Stefan.
Andreas Veithen wrote:
On 18 Mar 2008, at 21:58, stlecho wrote:
Second error message: "Part 'fault' of fault message
'{...}RemoteException'
must be defined with 'element=QName' and not 'type=QName'". Solved
by
removing fault elements, but I have no clue on why these elements
are
causing problems.
A similar issue has been discussed some time ago:
http://www.nabble.com/BP2113-warning-on-WS-Interoperability-test-to15135587.html#a15143012
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Generating-client-for-Jira-webservice-tp16121946p16131937.html
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
