<div dir="ltr">done:<div><br></div><div><a href="https://community.jboss.org/wiki/EnableDisableUsers">https://community.jboss.org/wiki/EnableDisableUsers</a><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Fri, Apr 12, 2013 at 12:28 PM, <span dir="ltr"><<a href="mailto:gatein-dev-request@lists.jboss.org" target="_blank">gatein-dev-request@lists.jboss.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Send gatein-dev mailing list submissions to<br>
<a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.jboss.org/mailman/listinfo/gatein-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/gatein-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:gatein-dev-request@lists.jboss.org">gatein-dev-request@lists.jboss.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:gatein-dev-owner@lists.jboss.org">gatein-dev-owner@lists.jboss.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of gatein-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: PortletApplicationDeployer listeners (Ken Finnigan)<br>
2. Re: PortletApplicationDeployer listeners (Julien Viet)<br>
3. enable/disable users (Luca Stancapiano)<br>
4. Re: enable/disable users (Boles?aw Dawidowicz)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 11 Apr 2013 12:03:29 -0400 (EDT)<br>
From: Ken Finnigan <<a href="mailto:kfinniga@redhat.com">kfinniga@redhat.com</a>><br>
Subject: Re: [gatein-dev] PortletApplicationDeployer listeners<br>
To: Julien Viet <<a href="mailto:julien@julienviet.com">julien@julienviet.com</a>><br>
Cc: <a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><br>
Message-ID: <<a href="mailto:734306130.3082080.1365696209274.JavaMail.root@redhat.com">734306130.3082080.1365696209274.JavaMail.root@redhat.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
That's fine, initially it didn't seem like the same listener instances would be applied to all deployments, not a problem.<br>
<br>
In terms of retrieving the portlet filter instance to actually perform injection on, is there a cleaner way to get it than this:<br>
<br>
filterClasses.add(ActionFilter.class);<br>
filterClasses.add(EventFilter.class);<br>
filterClasses.add(RenderFilter.class);<br>
filterClasses.add(ResourceFilter.class);<br>
<br>
ManagedPortletFilter managedPortletFilter = (ManagedPortletFilter) managedObject;<br>
<br>
PortletFilterImpl portletFilterImpl = (PortletFilterImpl) managedPortletFilter.getPortletFilter();<br>
<br>
PortletFilter portletFilterInstance;<br>
<br>
for (Class type : filterClasses) {<br>
portletFilterInstance = (PortletFilter) portletFilterImpl.instance(type);<br>
<br>
// If not null, then use it and skip rest of loop<br>
<br>
}<br>
<br>
Thanks<br>
Ken<br>
<br>
----- Original Message -----<br>
<br>
> From: "Julien Viet" <<a href="mailto:julien@julienviet.com">julien@julienviet.com</a>><br>
> To: "Ken Finnigan" <<a href="mailto:kfinniga@redhat.com">kfinniga@redhat.com</a>><br>
> Cc: <a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><br>
> Sent: Tuesday, April 9, 2013 8:12:20 PM<br>
> Subject: Re: [gatein-dev] PortletApplicationDeployer listeners<br>
<br>
> Yes it is expected.<br>
<br>
> The listener may want to be aware of all deployments (for maintaining a<br>
> registry of all portlets with a single listener instead of adding/removing N<br>
> listeners where N is the number of deployments).<br>
<br>
> This is similar to the JMX JMImplementation MBean that send notifications<br>
> about MBean life cycle for any MBean added/removed from the MBeanServer as<br>
> the intent is originally the same.<br>
<br>
> What is wrong with having a single listener if you can associate the CDI meta<br>
> data with the deployed portlets ?<br>
<br>
> I would proceed in two steps :<br>
<br>
> 1/ upon deployment : prepare the CDI info for all portlets and add to a map a<br>
> list of portlet id -> cdi meta data for the portlet (injection etc?)<br>
> 2/ upon portlet created event : lookup for cdi work to do from portlet id and<br>
> if it exists then honour the cdi integration<br>
<br>
> On Apr 9, 2013, at 10:14 PM, Ken Finnigan < <a href="mailto:kfinniga@redhat.com">kfinniga@redhat.com</a> > wrote:<br>
<br>
> > All,<br>
><br>
<br>
> > In implementing CDI injection into GenericPortlet and PortletFilter<br>
> > instances, I had assumed that I could add a<br>
> > ManagedObjectRegistryEventListener, specifically for CDI processing, and<br>
> > add<br>
> > it to the broadcaster in PortletApplicationDeployer for only those<br>
> > PortletApplicationDeployment's that needed CDI injection. ie. the listener<br>
> > would be added before creating a PortletApplicationDeployment and then<br>
> > removed straight afterwards to ensure that portlet deployments that had<br>
> > nothing to do with CDI, were not calling the listener for all event<br>
> > notifications for no reason.<br>
><br>
<br>
> > An unexpected consequence of this is that I've discovered the broadcaster<br>
> > list of listeners is the exact same instance across all<br>
> > PortletApplicationDeployment instances. So when I removed the CDI listener<br>
> > from broadcaster on PortletApplicationDeployer, it also removed that<br>
> > listener from the PortletApplicationDeployment that had just been created.<br>
><br>
<br>
> > Is that expected? I'd find it unusual that its not possible to add a<br>
> > listener<br>
> > specific to a deployment that should not be applied to all of them.<br>
><br>
<br>
> > Wondering if ManagedObjectRegistryEventBroadcaster needs to support cloning<br>
> > to facilitate this functionality?<br>
><br>
<br>
> > Any other thoughts on a better way to do this are appreciated, as I<br>
> > certainly<br>
> > feel it unnecessary to defensively code my listener for all types of<br>
> > portlets it can be attached to when it doesn't need to.<br>
><br>
<br>
> > Ken<br>
><br>
> > ========================<br>
><br>
> > Senior Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.<br>
><br>
<br>
> > _______________________________________________<br>
><br>
> > gatein-dev mailing list<br>
><br>
> > <a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><br>
><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/gatein-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/gatein-dev</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.jboss.org/pipermail/gatein-dev/attachments/20130411/47f5d991/attachment-0001.html" target="_blank">http://lists.jboss.org/pipermail/gatein-dev/attachments/20130411/47f5d991/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 11 Apr 2013 21:25:35 +0200<br>
From: Julien Viet <<a href="mailto:julien@julienviet.com">julien@julienviet.com</a>><br>
Subject: Re: [gatein-dev] PortletApplicationDeployer listeners<br>
To: Ken Finnigan <<a href="mailto:kfinniga@redhat.com">kfinniga@redhat.com</a>><br>
Cc: <a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><br>
Message-ID: <<a href="mailto:5D2D0218-7B8E-4DBE-92B1-8E410391EC28@julienviet.com">5D2D0218-7B8E-4DBE-92B1-8E410391EC28@julienviet.com</a>><br>
Content-Type: text/plain; charset="windows-1252"<br>
<br>
no there is not (because there was no need to expose such internal things until we work out this integration).<br>
<br>
you should add a Filter getFilter() on the class that returns the instance.<br>
<br>
On Apr 11, 2013, at 6:03 PM, Ken Finnigan <<a href="mailto:kfinniga@redhat.com">kfinniga@redhat.com</a>> wrote:<br>
<br>
> That's fine, initially it didn't seem like the same listener instances would be applied to all deployments, not a problem.<br>
><br>
> In terms of retrieving the portlet filter instance to actually perform injection on, is there a cleaner way to get it than this:<br>
><br>
> filterClasses.add(ActionFilter.class);<br>
> filterClasses.add(EventFilter.class);<br>
> filterClasses.add(RenderFilter.class);<br>
> filterClasses.add(ResourceFilter.class);<br>
><br>
> ManagedPortletFilter managedPortletFilter = (ManagedPortletFilter) managedObject;<br>
><br>
> PortletFilterImpl portletFilterImpl = (PortletFilterImpl) managedPortletFilter.getPortletFilter();<br>
><br>
> PortletFilter portletFilterInstance;<br>
><br>
> for (Class type : filterClasses) {<br>
> portletFilterInstance = (PortletFilter) portletFilterImpl.instance(type);<br>
><br>
> // If not null, then use it and skip rest of loop<br>
><br>
> }<br>
><br>
><br>
> Thanks<br>
> Ken<br>
><br>
> From: "Julien Viet" <<a href="mailto:julien@julienviet.com">julien@julienviet.com</a>><br>
> To: "Ken Finnigan" <<a href="mailto:kfinniga@redhat.com">kfinniga@redhat.com</a>><br>
> Cc: <a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><br>
> Sent: Tuesday, April 9, 2013 8:12:20 PM<br>
> Subject: Re: [gatein-dev] PortletApplicationDeployer listeners<br>
><br>
> Yes it is expected.<br>
><br>
> The listener may want to be aware of all deployments (for maintaining a registry of all portlets with a single listener instead of adding/removing N listeners where N is the number of deployments).<br>
><br>
> This is similar to the JMX JMImplementation MBean that send notifications about MBean life cycle for any MBean added/removed from the MBeanServer as the intent is originally the same.<br>
><br>
> What is wrong with having a single listener if you can associate the CDI meta data with the deployed portlets ?<br>
><br>
> I would proceed in two steps :<br>
><br>
> 1/ upon deployment : prepare the CDI info for all portlets and add to a map a list of portlet id -> cdi meta data for the portlet (injection etc?)<br>
> 2/ upon portlet created event : lookup for cdi work to do from portlet id and if it exists then honour the cdi integration<br>
><br>
><br>
><br>
> On Apr 9, 2013, at 10:14 PM, Ken Finnigan <<a href="mailto:kfinniga@redhat.com">kfinniga@redhat.com</a>> wrote:<br>
><br>
> All,<br>
><br>
> In implementing CDI injection into GenericPortlet and PortletFilter instances, I had assumed that I could add a ManagedObjectRegistryEventListener, specifically for CDI processing, and add it to the broadcaster in PortletApplicationDeployer for only those PortletApplicationDeployment's that needed CDI injection. ie. the listener would be added before creating a PortletApplicationDeployment and then removed straight afterwards to ensure that portlet deployments that had nothing to do with CDI, were not calling the listener for all event notifications for no reason.<br>
><br>
> An unexpected consequence of this is that I've discovered the broadcaster list of listeners is the exact same instance across all PortletApplicationDeployment instances. So when I removed the CDI listener from broadcaster on PortletApplicationDeployer, it also removed that listener from the PortletApplicationDeployment that had just been created.<br>
><br>
> Is that expected? I'd find it unusual that its not possible to add a listener specific to a deployment that should not be applied to all of them.<br>
><br>
> Wondering if ManagedObjectRegistryEventBroadcaster needs to support cloning to facilitate this functionality?<br>
><br>
> Any other thoughts on a better way to do this are appreciated, as I certainly feel it unnecessary to defensively code my listener for all types of portlets it can be attached to when it doesn't need to.<br>
><br>
> Ken<br>
> ========================<br>
> Senior Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.<br>
><br>
> _______________________________________________<br>
> gatein-dev mailing list<br>
> <a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/gatein-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/gatein-dev</a><br>
><br>
><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.jboss.org/pipermail/gatein-dev/attachments/20130411/c126ae7b/attachment-0001.html" target="_blank">http://lists.jboss.org/pipermail/gatein-dev/attachments/20130411/c126ae7b/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Fri, 12 Apr 2013 12:21:41 +0200<br>
From: Luca Stancapiano <<a href="mailto:l.stancapiano@sourcesense.com">l.stancapiano@sourcesense.com</a>><br>
Subject: [gatein-dev] enable/disable users<br>
To: <a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><br>
Message-ID:<br>
<CAO3WqDVOGgig5AdjEf=cNA5dOFmiY5HTppGX+4Sf=+<a href="mailto:ASF%2BRc7w@mail.gmail.com">ASF+Rc7w@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Hi, I've seen there is not still the workflow for the enabling or disabling<br>
of the users. It was in the old jboss portal. Are there developements in<br>
progress?<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.jboss.org/pipermail/gatein-dev/attachments/20130412/a30e28a6/attachment-0001.html" target="_blank">http://lists.jboss.org/pipermail/gatein-dev/attachments/20130412/a30e28a6/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Fri, 12 Apr 2013 12:28:40 +0200<br>
From: Boles?aw Dawidowicz <<a href="mailto:bdawidow@redhat.com">bdawidow@redhat.com</a>><br>
Subject: Re: [gatein-dev] enable/disable users<br>
To: <a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><br>
Message-ID: <<a href="mailto:5167E1D8.9030803@redhat.com">5167E1D8.9030803@redhat.com</a>><br>
Content-Type: text/plain; charset=UTF-8; format=flowed<br>
<br>
Could you start a specification for this?<br>
<br>
<a href="https://community.jboss.org/wiki/GateInSpecifications" target="_blank">https://community.jboss.org/wiki/GateInSpecifications</a><br>
<br>
After you write down requirements you have in mind we could discuss and<br>
agree on how it should look in final form.<br>
<br>
On 04/12/2013 12:21 PM, Luca Stancapiano wrote:<br>
> Hi, I've seen there is not still the workflow for the enabling or<br>
> disabling of the users. It was in the old jboss portal. Are there<br>
> developements in progress?<br>
><br>
><br>
> _______________________________________________<br>
> gatein-dev mailing list<br>
> <a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/gatein-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/gatein-dev</a><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
gatein-dev mailing list<br>
<a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/gatein-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/gatein-dev</a><br>
<br>
End of gatein-dev Digest, Vol 43, Issue 7<br>
*****************************************<br>
</blockquote></div><br></div>