Return-Path: Delivered-To: apmail-portals-jetspeed-dev-archive@www.apache.org Received: (qmail 68159 invoked from network); 15 Jan 2008 07:52:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Jan 2008 07:52:53 -0000 Received: (qmail 22482 invoked by uid 500); 15 Jan 2008 07:52:42 -0000 Delivered-To: apmail-portals-jetspeed-dev-archive@portals.apache.org Received: (qmail 22168 invoked by uid 500); 15 Jan 2008 07:52:42 -0000 Mailing-List: contact jetspeed-dev-help@portals.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Jetspeed Developers List" Delivered-To: mailing list jetspeed-dev@portals.apache.org Received: (qmail 22157 invoked by uid 99); 15 Jan 2008 07:52:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jan 2008 23:52:41 -0800 X-ASF-Spam-Status: No, hits=3.2 required=10.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [69.147.64.88] (HELO smtp115.sbc.mail.sp1.yahoo.com) (69.147.64.88) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 15 Jan 2008 07:52:27 +0000 Received: (qmail 16498 invoked from network); 15 Jan 2008 07:52:18 -0000 Received: from unknown (HELO ?192.168.1.65?) (davidseantaylor2@sbcglobal.net@71.142.94.177 with plain) by smtp115.sbc.mail.sp1.yahoo.com with SMTP; 15 Jan 2008 07:52:18 -0000 X-YMail-OSG: 5o_vi6QVM1mwyqOIiTo_Fpxwh6.pQiYtqMXx9eprYxhnX1EQfdSxZeVf9ahe.YrQC4og.5XEppIaQgW7tzTxD42L70XtbK8Xl01MwR.lnL5n5JE7JQ-- Mime-Version: 1.0 (Apple Message framework v753) To: Jetspeed Developers List Message-Id: <1736D3E5-B62E-43C9-B739-EAA78EADBEC4@bluesunrise.com> Content-Type: multipart/alternative; boundary=Apple-Mail-121-885520493 From: David Sean Taylor Subject: j2-admin refactoring in 2.2 Date: Mon, 14 Jan 2008 23:52:16 -0800 X-Mailer: Apple Mail (2.753) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-121-885520493 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed I would like to start a discussion on the j2-admin refactoring for 2.2 =46rom a discussion with Ate: --- One thing I think we really need to determine first is what the goal is. I can easily think of many different ones, like: 1 - only rewrite (one or more of) of the portlets but stick to the =20 current features and (most of the) ui, just to build up experience with Wicket and see how it goes 2 - allow a ui design overhaul but stick to the current features 3 - allow for some functional redesign/improvements (dangerous: when/=20 where to stop) 4 - do a complete functional overhaul, e.g. like for the security =20 portlets, (like JS2-27, JS2-241) My current idea is we probably should start with the first or =20 possibly second goal, anything beyond that is very difficult to =20 manage and plan for. --- I agree that a first prototype is best. Which portlet? Well, many of the portlets are actually made up of two portlets, such =20= as the User Manager or Role Manager But we still do not have JSR-286 support So maybe its best to combine the browser and details portlets into =20 one portlet. There are advantages to both approaches. The interesting part of separating the browser from the details is =20 that the browser can be used in combination with other details. Too bad the 286 support isn't resolved yet I think the Role Manager would be an interesting one to start with. =20 Its not as complicated as the User Manager, but has the 1 to many =20 type requirements that recur in many other admin portlets. Of course this is open to discussion and I invite your comments. Before we go too far I would to give anyone who believes JSF is a =20 better choice for writing the admin portlets a chance to speak up now. I think there are some advantages to JSF, such as being the standard, =20= and having a rich set of components. What I like about Wicket is that it is component-based and =20 extensible. I am always dealing with extending the admin portlets, =20 especially the self-registration. I would like to see how easy it is for someone to extend a Wicket =20 component, can anyone explain that in a paragraph or so? Other requirements I am looking to properly implement this time around: 1. Virtual -- all browser must be virtual. We should not load all =20 users into the user browser 2. Extensibility - we need an easy way for users to customize and =20 extend the admin portlets where we have done a decent job with this in portlets like the =20 User Details, having a large set of preferences, I recently went through extending the User Registration portlet =20 and kept running into hard-coded features All hard-coding has to go and we need to better consider how =20 users can easily extend the portlets I am hoping leveraging Wicket can help here 3. Document features in help mode, about mode. The admin portlets are =20= not well documented. Lets not neglect that responsibility this time =20 around. 4. support edit_defaults in all portlets 5. Notifications - not all, but some portlets are not properly hooked =20= into notifications (such as deployment events -> PAM portlet) or the profiler portlet is not notified of profiler changes made =20= during an import. 6. Software Design - lets do a prototype first. then check it in for =20 review and comment, and iteratively design from there 7. Web Design - I believe the portlets should be skinned with a new =20 decorator to introduce a new, modernized feel to these web1.0 portlets 8. Web 2.0 - make use of any web 2.0 features available in Wicket =20 (again I plead ignorance to these features) 9. leverage the Jetspeed AJAX API where applicable Finally, I want to move the j2-admin application out of Jetspeed and =20 into a new Portals project, Portals Applications I know that j2-admin can only be used by Jetspeed, but I am of the =20 opinion that it should be released on its on release cycle --=20 David Sean Taylor Bluesunrise Software david@bluesunrise.com [office] +01 707 773-4646 [mobile] +01 707 529 9194 =EF=BF=BC --Apple-Mail-121-885520493 Content-Type: multipart/related; type="text/html"; boundary=Apple-Mail-122-885520493 --Apple-Mail-122-885520493 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1 I would like to start a discussion on the j2-admin refactoring for = 2.2

=46rom a = discussion with Ate:

---
One thing I think we really need to determine first = is what the goal is.

I can easily = think of many different ones, like:

1 - only = rewrite (one or more of) of the portlets but stick to the current = features and (most of the) ui,
=A0 just to = build up experience with Wicket and see how it goes

2 - allow a ui design overhaul but stick to the = current features
3 - allow for some functional = redesign/improvements (dangerous: when/where to stop)
4 - do a complete functional overhaul, e.g. like for = the security portlets, (like JS2-27, JS2-241)

My current = idea is we probably should start with the first or possibly second goal, = anything beyond that is very difficult to manage and plan for.
---

I agree that = a first prototype is best. Which portlet?
Well, = many of the portlets are actually made up of two portlets, such as the = User Manager or Role Manager
But we still = do not have JSR-286 support
So maybe its = best to combine the browser and details portlets into one = portlet.
There are advantages to both = approaches.
The interesting part of = separating the browser from the details is that the browser can be used = in combination with other details.
Too bad the = 286 support isn't resolved yet

I think the = Role Manager would be an interesting one to start with. Its not as = complicated as the User Manager, but has the 1 to many type requirements = that recur in many other admin portlets.
Of = course this is open to discussion and I invite your comments.

Before we go too far I would to give anyone who = believes JSF is a better choice for writing the admin portlets a chance = to speak up now.
I think there are some = advantages to JSF, such as being the standard, and having a rich set of = components.
What I like about Wicket is that = it is component-based and extensible. I am always dealing with extending = the admin portlets, especially the self-registration.
I would like to see how easy it is for someone to = extend a Wicket component, can anyone explain that in a paragraph or = so?

Other = requirements I am looking to properly implement this time = around:

1. Virtual -- = all browser must be virtual. We should not load all users into the user = browser
2.=A0Extensibility - we need an = easy way for users to customize and extend the admin portlets
=A0=A0 =A0where we have done a decent job with this = in portlets like the User Details, having a large set of = preferences,
=A0=A0 =A0I recently went = through extending the User Registration portlet and kept running into = hard-coded features
=A0=A0 =A0All hard-coding = has to go and we need to better consider how users can easily extend the = portlets
=A0=A0 =A0I am hoping leveraging = Wicket can help here
3. Document features in = help mode, about mode. The admin portlets are not well documented. Lets = not neglect that responsibility this time around.
4. support edit_defaults in all portlets
5.=A0Notifications - not all, but some portlets are = not properly hooked into notifications (such as deployment events -> = PAM portlet)
=A0=A0 =A0or the profiler = portlet is not notified of profiler changes made during an = import.=A0
6. Software Design - lets do a = prototype first. then check it in for review and comment, and = iteratively design from there
7. Web Design = - I believe the portlets should be skinned with a new decorator to = introduce a new, modernized feel to these web1.0 portlets
8. Web 2.0 - make use of any web 2.0 features = available in Wicket (again I plead ignorance to these = features)
9. leverage the Jetspeed AJAX = API where applicable

Finally, I = want to move the j2-admin application out of Jetspeed and into a new = Portals project, Portals Applications
I know = that j2-admin can only be used by Jetspeed, but I am of the opinion that = it should be released on its on release cycle

=
--=A0
David Sean = Taylor
Bluesunrise Software
[office] +01 707 773-4646
[mobile] +01 707 529 9194


 =

= --Apple-Mail-122-885520493 Content-Transfer-Encoding: base64 Content-Id: <354D5BAC-9F17-4128-8311-CFA687780F61@local> Content-Type: image/jpeg; x-unix-mode=0644; name=bsr.jpg Content-Disposition: inline; filename=bsr.jpg /9j/4AAQSkZJRgABAQEAYABgAAD//gAcU29mdHdhcmU6IE1pY3Jvc29mdCBPZmZpY2X/2wBDAAoH BwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIfIiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8 SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7 Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAYAHUDASIAAhEBAxEB/8QAGgABAQADAQEAAAAAAAAAAAAA AAQDBQYBB//EADEQAAEDAwMDAgQEBwAAAAAAAAECAwQABRESITEGE0EUUSJhcYEHFUKRFiMyUnKh sf/EABgBAQEBAQEAAAAAAAAAAAAAAAABAgME/8QAHxEAAwEAAQQDAAAAAAAAAAAAAAECERIDITFB UeHw/90ABAAo/9oADAMBAAIRAxEAPwD6zc5K4VskyWwCpppS0hXBIGahidTW5yGy9IlNtqWhJWQD pSryM/Wrbsw5JtMuO0nU46ypCRxkkEVqI5vEe1s202VpagyGy4Xk9rjG45rrKlyea6tX28Z8F8q5 rZvFtitBtTMwOEqzv8IBGP3q5uXHdacdbdSpDZKVkeCOR9q0LdjmQF2YtH1SYPcS6SrScL9s+B/w US1d4TcyCzbkvpfccW2+HglICsncHfP0o5l5jMz1LTfJfsX2bl66wI7DT7sltLbwy0c5K9s7DzSL dYU0qSxISpaRlSCClQHvg1oJVinqjWp5oK7sJjtusod0Kzgf0q4zmststUp24omyo8lospUlHqJI WSSMYwkY0/fkVeE5ulXV6rrOJdG6pscuWiKxcG1uOKKWzghK1b7JURgnY7A+KvjT4szvemfQ76dw tO6f0LHIPzri7fab5Alx2IcF22RWHwt8OzEvRA2DlXbSr4kk5O+2N/er4jF7sU65MxrSmczcJS5L chMhKEt6gBhYO/jkZqVE+md1T03H8UWMRI8v8zY7EkqSyvOzhScED3IO1ZbffbZdFOIhy0uONAKW 2oFKkj3KTg4rkunulbpBjdMIlx0A296UuQNYIRrKigj35HHFb1y1S1dcKuYaHpjbDHDmoZ7mvOMc 8VbiE8TKnT8mK43qLcoSzary20Y4D7r2hRb0DkFWNvtvVKepbZGhxjMuTLjj7aXUlhClBSFcKAGS B8zULdmmtfhw5aRGxLMVaO0lQ3Uc+eN81qxY7nCt9qWi0y1S2be1HW7AnJadSpKd0LCvhKc+Rmrk 5m+zOd+R17l9tTNvanrnsemewGnArIWTwE45ry3322XR1TUSUlbqRqU2oFCwPfSQDjauVndM9QSo VlmSHkPXC3FwvNx3AyVhX9igMBQHy3qmy2SdJvcW53CHOjmIlegzJ4eXlQxgBIxjnk+BtWXE55Km 9OzpSlcjZgkxhJjuMqWpIWMZTyK1jnTTDq8rmSsdjs4S5pJ2UM5H+RwOBt7ClKEK2bS0w+3IDry3 UNpbKlLzqAzyOP1f6FSnpqMXQ4ZczZ9T2kO4GSpKtPyTlI2+vuaUoNMLHSMNkHMua7/LW2nuPE4C koTn5kBAwT7k8mr4tobiy1SRIfcUpsIKFqykbAEgeM6Rxt+9KUKQO9IxHYXpFzJhbLTjR1OA7L1D yPAWcfbnFXqtKFIW36h7QpxDiU5HwFJzgHHBPOffbFKUBhT09GBwp59bfYDJQpfKRjzz4qlm2NsT fUoedwGg0loq+AAHOce9KUBXimKUoD3GaAYpSgPaUpQH/9k= --Apple-Mail-122-885520493-- --Apple-Mail-121-885520493--