Hello,
we try the following chain:
-> Definition of Interfaces and Datatypes in Enterprise Service Builder
-> Storage in Enterprise Service Repository
-> Import in NWDS, Implementation of those Interfaces as a Web Service Provider
-> Deployment
-> Publishing in Service Registry
Case #1:
Interface-method with argument of type int (e.g. checkSth(int num) )
In NWDS, this method-signature is imported and represented by Java-Types, so the int-argument is mapped to the Java-Object BigInteger: checkSth(BigInteger num).
Problem: The mapping between simple xsd-types and their corresponding Java-types does not work, only null-values are passed.
The only working mapping is from string to String. I think Strings are no Java core-types and are always represented by the "true" Java-Object "String", so this mapping does work.
Case #2:
Interface-method with arguments of custom complex types, defined in the Service Builder.
This mapping works like a charm. (e.g. Type "customer" with Subelements "name", "street" and "zip")
Summary: The mapping between core-types and their Java-Equivalents does NOT work, however the mapping between complex types works.
Any hints on this issue?
Thanks alot in advance,
Kai