Wisej-1.5.4 to Wisej-1.5.16 breaks ApiController

0
0

Hi,

I have just discovered that upgrading Wisej-1.5.4 to Wisej-1.5.16 breaks ApiController functionality.

I’ve detailed my ApiController implementation in another post … essentially I created a new ASP.NET Web Application, selected the “Web API” checkbox, let it create a plumbed project, then copied all the plumbing to my WiseJ project.  The API functionality worked fine in 1.5.4, but has broken in 1.5.16 (no response all from the /api URL).

Regards,
Neil

  • You must to post comments
0
0

Hi Neil,

now also fixed in our latest release (1.5.23).

Best regards
Frank

  • You must to post comments
0
0

Hi Frank,

I can confirm that the ApiController functionality appears to work correctly in the prerelease version Wisej-1.5.21.

Cheers,
Neil

  • You must to post comments
0
0

Hi Luca,

Sorry for the delay – client cut over to a new module of the app this week – so beyond busy!

No, the API is autonomous – in the other I mentioned that it was a separate project in the solution and you (I think) noted there was no reason it couldn’t be combined – which I did successfully.  Aside from moving the API “plumbing” into the WiseJ project, they don’t “know” about each other, they just both access the same underlying service layer.

Cheers,
Neil

  • You must to post comments
0
0

Are you using the Wisej session from the api call?

  • You must to post comments
Showing 4 results
Your Answer

Please first to submit.