tag:blogger.com,1999:blog-6992129293870658291.post2269423559828382560..comments2024-02-13T00:36:59.095+11:00Comments on Impossible Siebel: InvokeMethod with ParametersJason Lehttp://www.blogger.com/profile/13322055780076477366noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6992129293870658291.post-53206284482218952732012-05-28T09:01:34.096+10:002012-05-28T09:01:34.096+10:00nice article its explore and provide technical sol...nice article its explore and provide technical solutions of business problems that are documented as product limitations, impossible to achieve.error 134http://best-registry-fixer.blogspot.com/2012/02/wow-error-134-fix.htmlnoreply@blogger.comtag:blogger.com,1999:blog-6992129293870658291.post-84581871319340850662012-04-26T08:39:47.052+10:002012-04-26T08:39:47.052+10:00This may be an alternative... it combines idea 2 a...This may be an alternative... it combines idea 2 and 3... http://yetanothersiebelframework.blogspot.com/2010/06/from-browser-side-down-then-back-up.html <br /><br />I never really got round to documenting the thing fully, but briefly the principles of how the Framework allow data/parameters pass from client side to server side and back are:<br /><br />1. use a single named client service that the framework code wraps - so all calls from client call that, and all returns use the same return<br />2. use "JSON like" code to flatten an un-flatten objects/parameter arrays (this allows complex arguments/objects be passed as a single string - crucial for the return value<br /><br />Having all client to server calls routing through the one service saves having to write code on each specific buscomp/service etc where you want to call methods...MattWhttps://www.blogger.com/profile/02126839469138161358noreply@blogger.com