Re: [jsr362-experts:] Prototype of the PortletConfig changes

[Werner Keil <we...@gmail.com>]

Hi,

Thanks for the update. I assume
https://github.com/apache/portals-pluto/tree/V3Prototype is a RO mirror of
the Apache repository.
Is there something to help on the Apache side? I am PMC member of 2 Apache
projects, one (DeviceMap) I helped quite significantly to graduate from
incubator last fall.
I haven't tried commit rights at Portals yet, but happy to help there if I
can. Both DeviceMap (where Mobile optimization of Portals are of interest)
and sooner or later Tamaya (for config management) have potential to be of
value to large Enterprise projects like Pluto, even if those may only be a
RI;-)

Kind Regards,
Werner

Werner Keil | JCP Executive Committee Member, JSR 363 Co Spec Lead |
Eclipse UOMo Lead, Babel Language Champion | Apache Committer | Advisory
Board Member, Java Track Chair, DWX '15

Twitter @wernerkeil | @UnitAPI | @JSR354 | @AgoravaProj | #EclipseUOMo
| #DeviceMap
| #DevOps
Skype werner.keil | Google+ gplus.to/wernerkeil

On Mon, Feb 2, 2015 at 2:07 PM, Martin Scott Nicklous <
Scott.Nicklous@de.ibm.com> wrote:

>
> Hi,
>
> I updated the Pluto V3Prototype branch with an implementation of the
> changes described in issue PORTLETSPEC3-18 concerning new APIs for the
> PortletConfig object. These new APIs make more information from the portlet
> deployment descriptor available to the programmer. During the course of the
> implementation, I ran into an oversight about the method signatures
> described in the Jira issue. The window states and portlet modes are
> dependent on the MIME type, so I added a parameter to each of the methods
> to allow the MIME type to be specified. I also added a method allowing the
> mapping of public render parameter names to QNames as defined in the
> deployment descriptor to be retrieved. Please see the links below for more
> information.
>
> The prototype also contains a portlet that displays the information made
> available through these methods.
>
> Updated version 3.0 Javadoc
> http://msnicklous.github.io/portletspec3/apidocs/index.html
>
> Updated documentation:
> https://java.net/projects/portletspec3/pages/PortletConfiguration
>
> Github mirror of the Apache Pluto V3Prototype branch containing the code
> changes:
> https://github.com/apache/portals-pluto/tree/V3Prototype
>
> Since I need to work on some other things for a couple of days, I am going
> to cancel tomorrow's JSR 362 EG call.
>
> Mit freundlichen Grüßen, / Kind regards,
> Scott Nicklous
>
> WebSphere Portal Standardization Lead & Technology Consultant
> Specification Lead, JSR 362 Portlet Specification 3.0
> IBM Software Group, Application Integration Middleware
> IBM Deutschland Research & Development GmbH / Vorsitzender des
> Aufsichtsrats: Martina Koederitz / Geschäftsführung: Dirk Wittkopp
> Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart,
> HRB 243294
>
>

Re: [jsr362-experts:] Prototype of the PortletConfig changes

[Werner Keil <we...@gmail.com>]

Btw, did anybody propose something Portlet-related to ApacheCon NA this
time?;-)

Maybe still too early, but given there is some movement maybe we could try
for ApacheCon Europe this fall? Happy to participate and at least the other
2 projects where stuff keeps changing and improving, too would be equally
welcome topics for me.

Werner

On Mon, Feb 2, 2015 at 2:12 PM, Werner Keil <we...@gmail.com> wrote:

> Hi,
>
> Thanks for the update. I assume
> https://github.com/apache/portals-pluto/tree/V3Prototype is a RO mirror
> of the Apache repository.
> Is there something to help on the Apache side? I am PMC member of 2 Apache
> projects, one (DeviceMap) I helped quite significantly to graduate from
> incubator last fall.
> I haven't tried commit rights at Portals yet, but happy to help there if I
> can. Both DeviceMap (where Mobile optimization of Portals are of interest)
> and sooner or later Tamaya (for config management) have potential to be of
> value to large Enterprise projects like Pluto, even if those may only be a
> RI;-)
>
> Kind Regards,
> Werner
>
> Werner Keil | JCP Executive Committee Member, JSR 363 Co Spec Lead |
> Eclipse UOMo Lead, Babel Language Champion | Apache Committer | Advisory
> Board Member, Java Track Chair, DWX '15
>
> Twitter @wernerkeil | @UnitAPI | @JSR354 | @AgoravaProj | #EclipseUOMo |
> #DeviceMap | #DevOps
> Skype werner.keil | Google+ gplus.to/wernerkeil
>
> On Mon, Feb 2, 2015 at 2:07 PM, Martin Scott Nicklous <
> Scott.Nicklous@de.ibm.com> wrote:
>
>>
>> Hi,
>>
>> I updated the Pluto V3Prototype branch with an implementation of the
>> changes described in issue PORTLETSPEC3-18 concerning new APIs for the
>> PortletConfig object. These new APIs make more information from the
>> portlet
>> deployment descriptor available to the programmer. During the course of
>> the
>> implementation, I ran into an oversight about the method signatures
>> described in the Jira issue. The window states and portlet modes are
>> dependent on the MIME type, so I added a parameter to each of the methods
>> to allow the MIME type to be specified. I also added a method allowing the
>> mapping of public render parameter names to QNames as defined in the
>> deployment descriptor to be retrieved. Please see the links below for more
>> information.
>>
>> The prototype also contains a portlet that displays the information made
>> available through these methods.
>>
>> Updated version 3.0 Javadoc
>> http://msnicklous.github.io/portletspec3/apidocs/index.html
>>
>> Updated documentation:
>> https://java.net/projects/portletspec3/pages/PortletConfiguration
>>
>> Github mirror of the Apache Pluto V3Prototype branch containing the code
>> changes:
>> https://github.com/apache/portals-pluto/tree/V3Prototype
>>
>> Since I need to work on some other things for a couple of days, I am going
>> to cancel tomorrow's JSR 362 EG call.
>>
>> Mit freundlichen Grüßen, / Kind regards,
>> Scott Nicklous
>>
>> WebSphere Portal Standardization Lead & Technology Consultant
>> Specification Lead, JSR 362 Portlet Specification 3.0
>> IBM Software Group, Application Integration Middleware
>> IBM Deutschland Research & Development GmbH / Vorsitzender des
>> Aufsichtsrats: Martina Koederitz / Geschäftsführung: Dirk Wittkopp
>> Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart,
>> HRB 243294
>>
>>
>