Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] GROUP_ADD XMPP event has no information

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] GROUP_ADD XMPP event has no information


Chronological Thread 
  • From: Chris Hyzer <>
  • To: Erik Froese <>
  • Cc: "" <>
  • Subject: RE: [grouper-users] GROUP_ADD XMPP event has no information
  • Date: Mon, 14 Mar 2011 14:33:33 -0400
  • Accept-language: en-US
  • Acceptlanguage: en-US

Here is the log:

"name":"nyu:apps:atlas:test10",


It does not say:

"groupName":"nyu:apps:atlas:test10",

So, I think your patch is close, but if we have more operations, then it
might be right. When setting the groupName to be name, make sure it is a
GROUP_ADD or GROUP_DELETE... I can add this to grouper. Ok?

Thanks,
Chris


-----Original Message-----
From:


[mailto:]
On Behalf Of Erik Froese
Sent: Monday, March 14, 2011 2:08 PM
To: Chris Hyzer
Cc:

Subject: Re: [grouper-users] GROUP_ADD XMPP event has no information

Look at the event that's logged before it's published though. It looks
like it's filled out.
Why doesn't that information show up in the client? It looks like it
uses JSONUtils to populate the event bean from the message directly.
Erik

On Mon, Mar 14, 2011 at 2:00 PM, Chris Hyzer
<>
wrote:
> I think this is the same problem as before... it's the name not group name
>
> I think we need to adjust this part:
>
> FROM:
>                incrementalRefreshGroup(grouperClientXmppJob,
> esbEvent.getGroupName(),
>                    grouperClientXmppSubject, esbEvent.getEventType());
>
> TO:
>
> Something about seeing the event type, if it is GROUP_ADD/GROUP_DELETE,
> then get esbEvent.getName()...
>
> OK?
>
> Thanks,
> Chris
>
> -----Original Message-----
> From:
>
>
> [mailto:]
> On Behalf Of Erik Froese
> Sent: Monday, March 14, 2011 1:56 PM
> To:
>
> Subject: [grouper-users] GROUP_ADD XMPP event has no information
>
> Hey all,
>
> When my listener receives a GROUP_ADD event all of the fields are
> null. I'm not able to use the groupName, groupExtension, or subject
> parameters.
>
> From the grouper loader publisher log I can see a fully formed event:
>
> 2011-03-14 13:45:00,046: [DefaultQuartzScheduler_Worker-6] DEBUG
> EsbXmppPublisher.dispatchEvent(31) -  - Consumer xmp
> p publishing {  "esbEvent":[
>    {
>      "displayName":"nyu:apps:atlas:test10",
>      "eventType":"GROUP_ADD",
>      "id":"b9fa3e455cfa4963bfc8cdf8635bf6f5",
>      "name":"nyu:apps:atlas:test10",
>      "parentStemId":"db4fae03e7fc43de8ec249e02d78a8af",
>      "sequenceNumber":"369"
>    }
>  ]}
>
> But on the receiving side it I have no information to use.
>
> My handler
>
> https://github.com/efroese/grouper-nakamura/blob/master/xmpp-client/src/main/java/edu/nyu/grouper/xmpp/NakamuraGroupXmppHandler.java
>
> The log statement on line 45 produces:
> FINE: action=GROUP_ADD groupName=null groupExtension=null changeSubject=null
>
> I also have a simple handler to log incoming events. It sees the same thing.
>
> https://github.com/efroese/grouper-nakamura/blob/master/xmpp-client/src/main/java/edu/nyu/grouper/xmpp/SimpleLoggingHandler.java
>
> Mar 14, 2011 1:45:00 PM edu.nyu.grouper.xmpp.SimpleLoggingHandler
> handleIncremental
> FINE: jobName = testLog
>  groupName = null
>  groupExtension = null
>  previousSubjectList =
>  newSubjectList =
>  changeSubject = null
>  action = GROUP_ADD
>
> Can someone point me towards a fix?
>
> Erik
>



Archive powered by MHonArc 2.6.16.

Top of Page