Aaahh I see - Sorry about that.

 

This article by Stephan Wissel should help you out:   http://www.wissel.net/blog/d6plinks/shwl-7mgfbn

 

He documents a method of using an XPage as a call-able agent. 

The XPage doesn't have to actually render anything - Just generate a response.  

 

You simply place the SSJS code you want to compute in the afterRenderResponse event of the XPage, and return the computed value back to the calling script. 

It has worked brilliantly for me, and I have used it in exactly the same scenario as you are proposing. 

 

HOWEVER, I have experienced a strange issue when using this technique. 

I am not sure if it is the technique itself , Domino, or my use of the technique, but I have documented the issue in this forum here: http://www-10.lotus.com/ldd/xpagesforum.nsf/topicThread.xsp?documentId=368D5E33697C708685257846003D4E40&action=openDocument 

 

My agent (Xpage) is called many times over the course of a visit to the site, so I have a feeling it is related to the documented APAR.

It is handled for the moment with an event handler that restarts the HTTP task whenever it goes astray, but I'm hanging out for 8.5.3 to see if that's a cure.

 

Hope this helps this time! 

 ahh thats a very useful link. Thank you Terry, thanks for spending the time for a useful reply.

 

I ended up changing the code so it now all works within a repeat control, so its all ok now. Have a fully working cart system!