RuntimeLogger.Log(new CustomLog(ssrecord));
Well, I did, but afterwards extended it a bit, so I can't share it, sorry :).
- Create a new variable/property in the soapextension class, to control whether logging is active or not
- Change the methods that are logging to check that variable
- Create a new extension method that:
- obtains the current instance of the soap extension (check how I do it to check if the soap extension is already registered)
- Set the new property on that instance to True/False
Remember that SoapExtensions run outside of a particular request (they are like Singletons in the .Net pipeline). So, if there are 2 concurrent requests, you have no guarantee that once you set it to "off" it will occur or not (if the other request is concurrently setting it to "on")… Hope it helps
I'm trying to get this to work, but no succes. I've done the things Kilian 3 posts above describes, but the table that should contain the logging remains empty. The log in Service Center doesn't show a error for this application
I'm on OutSystems 10 by the way, using the OutSystems 10 PAAS (don't know if that matters).
I've made a very small application with one Webservice and one Webmethod as an example.You find it attached.
Can anyone point me in the right direction ?
Hi Martijn,
Could you please not necro 5.5 year old topics next time? Thanks. :) I'll PM you for the above.
The logs that the platform provides aren't enough for you? this is a old post and this functionality still didn't exist on the platform. but now there are there on the monitoring tab of service center. maybe you just need to change the log levels of the soap to get what you want. you have a quick guide on how to use the platform integrations logging here. the guide talk about rest but soap is the same thing.
Regards,
Marcelo