on 05-07-2012 12:56 PM
Hi,
I have a sceanrio where SAOP is the receiver adapter. We are provided with WSDL files and XSD structures.
I have imported WSDL files along with the XSD structures in External definition.
But when I drag WSDL message to the message mapping, I am not able to get the structure.
Its showing "Java null pointer exception"
Please let me know what could be the reason for this.
Thanks
Suma S
Hi Suma,
Import Wsdl and .XSD file at the same place in namespace. Use the following path Tools-->Externe Definitionen importieren .... to import the WSDL and XSD.
You will be able to see the original structure. Plz also check whether the .WSDL contain import tag and original names as mentioned by Grzegroz.
Hope it helps.
Thanks,
Pankaj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check Whether your wsdl message is proper. Like the strucuture is proper not.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
@Bhavani Senkar
I wouldn't agree here. Service Interface is only related to Operation Mapping, you do not need to create SI for Message Mapping.
@Suma S:
I am not really sure what you mean by "drag WSDL message to the message mapping". Simply select the right message from your External Definition, using the button I marked red here:
Hope this helps,
Greg
Just few cents....
You can validate the WSDL using soapUI or XMLSPY and see that your WSDL has any syntax error.If so, Please talk to the target system. I hope you did not edit anything in WSDL. Also some time third party provides few XSDs and the main XSD import the other XSDs. BTW, if the third party provides WSDL, why do you need XSD then? Just import the WSDL using external definition and choose the same in the service interface for the request and response message. Then use the same in the message mapping.
Hope that helps.
Then that means you need to import both wsdl and xsd files as external definition. Otherwise you can copy the XSD conternt within the WSDL and remove the import references if that is feasible and see how that works. So that you will have just one import file. We are not changing any content in WSDL.
Also you might want to know the difference between import and include statement in XSD.
The fundamental difference between include and import is that you must use import to refer to declarations or definitions that are in a different target namespace and you must use include to refer to declarations or definitions that are (or will be) in the same target namespace.
Hope that helps.
Hi Suma,
In my opinion, you do not have to modify the wsdl/xsd to achieve your goal. I have just checked one .wsdl file that I used in one of my scenarios and it contains 3 import statements for some additional .xsd files (so it's similar to your scenario). I have imported them all to PI and they are working fine together. I am not really sure if it makes any difference, but you might try using External Definitions -> right-click -> Import External Definitions, in order to maintain the original name.
Hope this helps,
Greg
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.