[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AW: AW: Help with WSDL2RPG
Hello,
thank you for going so deep into this. We don't develop this WSDL, we
got it from a software company which makes the software for our Storage
System.
I'm not sure what they want to describe with that recursivity, perhaps
it should be possible that a location is able to show to another
location.
I've tested the WSDL with the Tool WS-I Compliance of soapUI and got a
"passed" for it.
soapUI generates the following Soap message for it:
<b2m:Location>
<!--Optional:-->
<b2m:EquipmentID>?</b2m:EquipmentID>
<!--Optional:-->
<b2m:EquipmentElementLevel
OtherValue="?">?</b2m:EquipmentElementLevel>
<!--Optional:-->
<b2m:Location/>
<!--Zero or more repetitions:-->
<b2m:Any>
<!--You may enter ANY elements at this point-->
</b2m:Any>
</b2m:Location>
I think in our environment we don't need this "optional" location
element under the element LocationType.
For testing I've now changed the Element Location Type to:
<s:complexType name="LocationType">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="EquipmentID"
type="s:string" />
<s:element minOccurs="0" maxOccurs="1"
name="EquipmentElementLevel" type="s1:EquipmentElementLevelType" />
<s:element minOccurs="0" maxOccurs="unbounded" name="Any"
type="s1:AnyType" />
</s:sequence>
</s:complexType>
and eliminated a second one under MaterialSubLotType.
Now I got the message "Successfully generated 2 Web Service stub
modules: WS0001*. Feel free to ..."!
I'm looking forward to work with your tools.
Thank you and have a nice weekend!
Timo Casaluci
-----Ursprüngliche Nachricht-----
Von: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] Im Auftrag von
thomas.raddatz@xxxxxx
Gesendet: Freitag, 13. Januar 2012 13:26
An: ftpapi@xxxxxxxxxxxxxxxxxxxxxx
Betreff: Re: AW: Help with WSDL2RPG
Timo,
Element 'LocationType' is the one that causes the error. That element
is
part of namespace "[1]http://www.wbf.org/xml/b2mml-v0300"; and it
references
element 's1:LocationType':
<s:schema elementFormDefault="qualified" targetNamespace="
[2]http://www.wbf.org/xml/b2mml-v0300";>
<s:import
namespace="[3]http://www.wbf.org/xml/b2mml-v0300-extensions"; />
...
<s:complexType name="LocationType">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="EquipmentID"
type="s:string" />
<s:element minOccurs="0" maxOccurs="1"
name="EquipmentElementLevel"
type="s1:EquipmentElementLevelType" />
<s:element minOccurs="0" maxOccurs="1" name="Location"
type="s1:LocationType" />
<s:element minOccurs="0" maxOccurs="unbounded" name="Any"
type="s1:AnyType" />
</s:sequence>
</s:complexType>
The value assigned to namespace prefix 's1' is
'http://www.wbf.org/xml/b2mml-v0300', which is the same namespace of
the
element that shall be defined.
<wsdl:definitions
...
xmlns:s1="[4]http://www.wbf.org/xml/b2mml-v0300";
Hence both 'LocationType'(s) are the same:
<s:complexType name="LocationType"> <<== this one is the same as
...
<s:sequence>
...
<s:element minOccurs="0" maxOccurs="1" name="Location"
type="s1:LocationType" /> <<== ... this one
I have no idea to what construct of Java, C# or any other object
oriented
programming language that maps. How did you develop or create the WSDL?
Or
am I missing something?
Thomas.
[5]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx schrieb am 13.01.2012
12:21:09:
> Von: [6]t.casaluci@xxxxxxxx
> An: [7]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> Datum: 13.01.2012 12:27
> Betreff: AW: Help with WSDL2RPG
> Gesendet von: [8]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
>
> Hello,
>
> now I've attached the WSDL File, it's located on a server in our
> intranet. I've expected that the file is correct
> because it?s the standard interface of the stock system we want to
> exchange data with.
> What we want to do in the first step is to send our open orders from
> our ERP System to a web service which is located on a remote server.
> And in a second step we want to get back a similar set of data to a
> web service which is located on our IBM i.
>
> Thanks,
>
> Timo
>
> -----Ursprüngliche Nachricht-----
> Von: [9]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-
> [10]bounces@xxxxxxxxxxxxxxxxxxxxxx] Im Auftrag von
[11]thomas.raddatz@xxxxxxxxxxx
> Gesendet: Freitag, 13. Januar 2012 11:12
> An: HTTPAPI and FTPAPI Projects
> Betreff: Re: Help with WSDL2RPG
>
> Timo,
>
> It is always a good idea to attached the wsdl file when having a
problem
with
> the generator. The problem you reported does not sound good to me. I
> assume that
> there is a recursion in the wsdl file. Please send the wsdl file or
the
URL of
> the wsdl file to me and I am going to try to figure out what wrong
with
it or
> the generator.
>
> Regards,
>
> Thomas.
>
>
>
> "Casaluci, Timo" <[12]t.casaluci@xxxxxxxx> hat am 12. Januar 2012 um
16:41
> geschrieben:
>
> > Hello Mr. Raddatz,
> >
> >
> >
> > I've a question/problem for you.
> >
> > During the generation of my first WS Client Stub program with
WSDL2RPG
I got
> > the following error message:
> >
> >
> >
> > Extract from my Joblog:
> >
> >
> >
> > WSDL2RPG
URL('http://vega-facts01/FactsWebServices/MaterialInformation/Mat
> >
> > erialInformation.asmx?WSDL') SERVICE(*SELECT *SELECT)
SRCFILE(R8LKVSRCI/VE
> >
> > XSRCL) SRCMBR(WS0001) TYPE(*STUB)
> >
> > Member WS000101 added to file VEXSRCL in R8LKVSRCI.
> >
> > Member WS000101 file VEXSRCL in R8LKVSRCI changed.
> >
> > Automatic storage overflow. (MCH4429)
> >
> > Function check. MCH4429 unmonitored by WSDL2RPG at statement
0000101200,
> >
> > instruction X'0000'.
> >
> > The call to main ended in error (C G D F).
> >
> > The call to main ended in error (C G D F).
> >
> >
> >
> >
> >
> > Weitere Nachrichteninformationen
> >
> >
> >
> > Nachrichten-ID . . . . : MCH4429
> >
> > Sendedatum . . . . . . : 12.01.12 Sendezeit . . . . . .
> : 16:30:21
> >
> >
> >
> > Nachricht . . . : Automatic storage overflow.
> >
> >
> >
> > Cause . . . . . : One of the automatic storage stacks
X'00000002'
for the
> >
> > thread has overflowed or a storage access beyond the maximum
size
of a
> >
> > teraspace automatic storage stack was attempted. Further
> program execution
> >
> > within the thread is not possible. Automatic storage stack
> values and their
> >
> > meanings follow:
> >
> > 1 -- System stack in single level storage.
> >
> > 2 -- User stack in single level storage.
> >
> > 3 -- System stack in teraspace.
> >
> > 4 -- User stack in teraspace.
> >
> > Technical description . . . . . . . . : Attempt to reduce the
automatic
> >
> > storage used by programs running in the thread.
> >
> > Ende
> >
> >
> >
> > Would it be helpful to attach the WSDL File?
> >
> >
> >
> > Thanks
> >
> >
> >
> > Timo Casaluci
> >
> >
> >
> >
> >
>
***********************************************************************
*************
> > VEGA Grieshaber KG
> > Kommanditgesellschaft mit Sitz in Wolfach
> > Registergericht Freiburg: HRA 680 687
> >
> > Persönlich haftender Gesellschafter: Jürgen Grieshaber
> >
> > Persönlich haftende Gesellschafterin: Grieshaber Holding GmbH
> > Sitz Wolfach, Registergericht Freiburg: HRB 680 271
> >
> > Geschäftsführer: Jürgen Grieshaber, Günter Kech, Rainer Mielke
> >
>
***********************************************************************
*************
> [Anhang "MaterialInformation.WSDL" gelöscht von Thomas Raddatz/OBI/
> DE]
-----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubscribe, please go to:
> [13]http://www.scottklement.com/mailman/listinfo/ftpapi
>
-----------------------------------------------------------------------
--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the
intended recipient only. Access, disclosure, copying, distribution, or
reliance on any of it by anyone else is prohibited and may be a
criminal
offence. Please delete if obtained in error and email confirmation to
the sender.
References
1. http://www.wbf.org/xml/b2mml-v0300
2. http://www.wbf.org/xml/b2mml-v0300
3. http://www.wbf.org/xml/b2mml-v0300-extensions
4. http://www.wbf.org/xml/b2mml-v0300
5. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
6. mailto:t.casaluci@xxxxxxxx
7. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
8. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
9. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
10. mailto:bounces@xxxxxxxxxxxxxxxxxxxxxx
11. mailto:thomas.raddatz@xxxxxxxxxxx
12. mailto:t.casaluci@xxxxxxxx
13. http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------