Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
Read More & Register today!
SOLVED

userManager binding warning when running the MulticastTest sdk sample

Avatar

Level 3
Level 3
8/16/11 9:23:42 PM

Right after compilation it shows

warning: unable to bind to property 'userManager' on class 'com.adobe.rtc.session::ConnectSessionContainer'

Views

931

Replies

2
Sign in to like this content

Total Likes

Translate
Translate
1 Accepted Solution

Avatar

Correct answer by
Former Community Member
8/19/11 1:11:16 PM

Hi Mickey,

I'm through being stubborn - this has been fixed for the next release =).

  thanks for taking the time to report it!

   nigel

View solution in original post

Views

429

Replies

0

Total Likes

Translate
Translate
Jump to reply
2 Replies

Avatar

Employee
Employee
8/17/11 7:21:55 AM

This is an harmless warning that has been there since day 0 in all versions of the SDK. But we are stubborn and still didn't "fix" it

Views

352

Replies

0
Sign in to like this content

Total Likes

Translate
Translate

Avatar

Correct answer by
Former Community Member
8/19/11 1:11:16 PM

Hi Mickey,

I'm through being stubborn - this has been fixed for the next release =).

  thanks for taking the time to report it!

   nigel

Views

430

Replies

0

Total Likes

Translate
Translate
Jump to reply
Related Conversations
My data source works in Preview PDF mode but not when I generate the form Solved

Views

2.3K

Likes

0

Replies

2
Header at the end of row item issue Solved

Views

1.3K

Likes

0

Replies

1
Floating field with pagenumbers in a fragment is messing up when used in masterpages Solved

Views

1.4K

Likes

0

Replies

2
Unable to convert the HTML to PDF using PDF generator in Adobe workbench Solved

Views

1.6K

Likes

0

Replies

6
How to create Rows dynamically from Code without binding

Views

1.0K

Likes

0

Replies

1
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] ----