arishanapalli / wsdl2objc

Automatically exported from code.google.com/p/wsdl2objc
MIT License
0 stars 0 forks source link

request xml (xsi:type=) #34

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. make a webservice with jboss seam 
2. use wsdl2objc with attached wsdl
3.

What is the expected output?
  <soap:Body>
    <SupportServiceSvc:login>
      <username>admin</username>
      <password>admin</password>
    </SupportServiceSvc:login>
  </soap:Body>

What do you see instead?
  <soap:Body>
    <login xsi:type="SupportServiceSvc:login">
      <username>admin</username>
      <password>admin</password>
    </login>
  </soap:Body>

What version of the product are you using? On what operating system?
mac osx 10.5.8; xcode 3.1.4; wsdl2objc 0.6; jboss 5.0.0.0; seam 2.1

Please provide any additional information below.
wsdl2objc creates xml's wich produces this error:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
   <env:Header/>
   <env:Body>
      <env:Fault>
         <faultcode>env:Client</faultcode>
         <faultstring>Endpoint 
{http://ws.controller.support.navitas.de/}SupportServicePort does not contain 
operation meta data for: login</faultstring>
      </env:Fault>
   </env:Body>
</env:Envelope>

is there a way to change the output xml in that kind i showed above? i'm really 
new to 
objc development and a bit confused by the generated code.

i tryed my changed xml by sending the changed xml by hand an it works fine. any 
sugestions on handle this?

best regards!

Original issue reported on code.google.com by dustin.b...@googlemail.com on 18 Sep 2009 at 3:28

Attachments:

GoogleCodeExporter commented 9 years ago
i better ad both complete versions 

not working (original)
<?xml version="1.0"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xs="http://www.w3.org/2001/XMLSchema" 
xmlns:SupportServiceSvc="http://ws.controller.support.navitas.de/" 
xsl:version="1.0">
  <soap:Body>
    <login xsi:type="SupportServiceSvc:login">
      <username>admin</username>
      <password>admin</password>
    </login>
  </soap:Body>
</soap:Envelope>

working (changed)

<?xml version="1.0"?>
<soap:Envelope 

xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xs="http://www.w3.org/2001/XMLSchema" 
xmlns:SupportServiceSvc="http://ws.controller.support.navitas.de/" 
xsl:version="1.0">

  <soap:Body>
    <SupportServiceSvc:login>
      <username>admin</username>
      <password>admin</password>
    </SupportServiceSvc:login>
  </soap:Body>

</soap:Envelope>

Original comment by dustin.b...@googlemail.com on 18 Sep 2009 at 3:31

GoogleCodeExporter commented 9 years ago
I have the same problem, I had to hack the source code to fix this. It is 
because of some namespace issue. I hope 
this get fixed soon. If you want I may send my updated source code (it is a 
hack, so I am not sure if it will work 
for everyone).

Original comment by gabrielg...@gmail.com on 22 Sep 2009 at 5:47

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Please send that patch to me and I'll take a look as soon as I get some time.
You can find my contact info on henri.tel

Original comment by hasse...@gmail.com on 22 Sep 2009 at 9:27

GoogleCodeExporter commented 9 years ago
@ gabrielnnrinaldi:please send me your hacks , too .. 

Original comment by dustin.b...@googlemail.com on 25 Sep 2009 at 10:02

GoogleCodeExporter commented 9 years ago
Here is my code, please let me know if you need anything! I hope I helped :)

Original comment by gabrielg...@gmail.com on 25 Sep 2009 at 2:36

Attachments:

GoogleCodeExporter commented 9 years ago
This fixed an issue I was seeing with <soap:Text xml:lang="en">Unable to handle 
request without a valid action 
parameter. Please supply a valid soap action.</soap:Text>.

Original comment by rtwo...@gmail.com on 2 Oct 2009 at 6:42

GoogleCodeExporter commented 9 years ago
sry of my, maybe, stupid question:
if i try to compile the outputted files from  gabrielnnrinaldi patch .. ill get 
some errors

ServiceSvc.h:27: error: expected specifier-qualifier-list before 'unsignedShort'
.....

ServiceSvc.m:360: warning: receiver 'xs_unsignedShort' is a forward class and 
corresponding @interface may 
not exist

am i missing something to include the unsignedShort stuff?! i am new to objc 
but is this a custom wrapper 
class for unsigned short int?

maybe you can help me :)

Original comment by dustin.b...@googlemail.com on 7 Oct 2009 at 2:27

GoogleCodeExporter commented 9 years ago
I have a similar issue with using an ASP.net service.  Their expected format 
looks like

<soap:Body>
    <Request xmlns="http://example.org/">
      <Param1>boolean</Param1>
      <Param2>int</Param2>
    </Request>
</soap:Body>

Personally I don't see how the syntax conforms to XML specs, but I've had to 
hack
this into the source to get my app to work.

Perhaps the request could be generated differently depending on where the WSDL 
file
came from?

Original comment by Uncorr...@gmail.com on 14 Oct 2009 at 7:37

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I have noticed a pattern with this generation example.  If the namespace for 
the 
request is the same as the namespace of the parameters then this bug occurs.  
If the 
namespaces are different the request is generated correctly.

Original comment by tony%cha...@gtempaccount.com on 12 Jan 2010 at 10:15