Expand my Community achievements bar.

SOLVED

SessionManagerBase.publishItem signature changed in 10.1 swc...

Avatar

Former Community Member

I'm extending SessionManagerBase for our own custom localmanager used for unit testing. ( Which I'm happy to share if anyone is interested. ) Unfortunately, between the 10.0 swc and the 10.1 swc, the method signature has changed.

It used to be:

session_internal function publishItem(p_collectionName:String, p_nodeName:String, p_itemVO:Object, p_overWrite:Boolean=false):void

Now it looks like there's an additional Boolean at the end. ( According to my describeType sleuthing )

What's the actual signature?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

HI Sandy,

P2pDataMessaging was added as a parameter to handle p2p data stuff. The actual signature is

session_internal function publishItem(p_collectionName:String, p_nodeName:String, p_itemVO:Object, p_overWrite:Boolean=false,p_p2pDataMessaging:Boolean=false):void

In few weeks , we will have a release that will carry 10.1 source too. Then you wont be having issues on looking up such things

Hope this helps

Thanks

Hironmay

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

HI Sandy,

P2pDataMessaging was added as a parameter to handle p2p data stuff. The actual signature is

session_internal function publishItem(p_collectionName:String, p_nodeName:String, p_itemVO:Object, p_overWrite:Boolean=false,p_p2pDataMessaging:Boolean=false):void

In few weeks , we will have a release that will carry 10.1 source too. Then you wont be having issues on looking up such things

Hope this helps

Thanks

Hironmay

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----