cancel
Showing results for 
Search instead for 
Did you mean: 

Add WSLD (HTTPS) - Unexpected end of file after null

SOLVED
Highlighted
New Contributor

Add WSLD (HTTPS) - Unexpected end of file after null

Hi,

when i try to add the WSDL https://90277891-test-retail-ondemand.cegid.cloud/Y2/CustomerWcfService.svc?wsdl , I receive the "Unexpected end of file after null".
The WSDL URL works fine by browser, postman etc. The problem is only on Soap UI (last version 5.5).

Bigf00t_0-1599558073548.png
Could you help me please?

Best regards,

Alessio

 

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
New Contributor

Re: Add WSLD (HTTPS) - Unexpected end of file after null

I solved using single WSDL: https://....../CustomerWcfService.svc?singleWsdl

View solution in original post

6 REPLIES 6
Highlighted
Community Hero

Re: Add WSLD (HTTPS) - Unexpected end of file after null

Hey @Bigf00t,

I think i stumbled across this issue last week.

Regarding the .wsdl. have you got inline schemas or are they being imported? If theyre being imported then a possible fix is to alter the schemaLocation tag to the correct path to the schema.

Just a suggestion,

Rich
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta
Highlighted
New Contributor

Re: Add WSLD (HTTPS) - Unexpected end of file after null

Hi Richie,
thank you for the reply.
I have got the inline schemas.

 

Regards,

Alessio

 

Highlighted
Community Hero

Re: Add WSLD (HTTPS) - Unexpected end of file after null

Hey @Bigf00t 

 

One other possible cause I found was cos the .wsdl was schema invalid, I dont mean wellformed.

 

Can you chuck your .wsdl into something like XMLSpy and try and validate it?

 

have a look at the stackoverflow post - this has a possible fix for the issue

 

the

 

ta

 

rich

if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta
Highlighted
New Contributor

Re: Add WSLD (HTTPS) - Unexpected end of file after null

The WSDL is valid because it works with other clients as Postman etc.

 

Thank you

Alessio

Highlighted
Community Hero

Re: Add WSLD (HTTPS) - Unexpected end of file after null

Hey @Bigf00t 

 

not necessarily.  Last week I had a .wsdl that worked fine in Postman - but didn't in ReadyAPI!

 

when I checked the content thats when I found it was invalid.

 

ta

 

rich

if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta
Highlighted
New Contributor

Re: Add WSLD (HTTPS) - Unexpected end of file after null

I solved using single WSDL: https://....../CustomerWcfService.svc?singleWsdl

View solution in original post

New Here?
Join us and watch the welcome video:
Announcements
Top Kudoed Authors