there are not particular comments on the API itself. It looks good, however issues arise
when you use the API rather than design it.
A single comment for now, I would say that GateIn 4 changes:
- page composition from hierarchy based to zone based instead
- application registry is changed to a content based approach which is a generalisation of
the application registry
Julien Viet
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
All,
I'd like to kindly ask for your comments about a task that I'm
starting on GateIn 3.x, to extend the current API to allow portlet
developers to compose pages and add content to it.
I've put my initial thoughts and incorporated a few early feedback
propositions into the following wiki page, and I'd appreciate if you
could take some minutes to go through it and share your thoughts:
https://community.jboss.org/wiki/RFC-APIForComposingPages
I'm greatly interested in checking if my understanding of the current
situation is accurate, as well as getting attention to points that I
might have missed.
I have a few other smaller tasks to work on and I plan to start some
concrete coding by mid next week, so, I'd appreciate if you could
share your feedback by then -- or at least say "don't start, I've
found a fatal flaw, let's discuss first" :-)
Thanks!
Juca.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -
http://www.enigmail.net/
iQEcBAEBCgAGBQJS18HfAAoJECKM1e+fkPrXqG0H/0tyXzBANobSXJHq3puo7RRP
9xt3HSJL75r7gGrTh+aBhJ68rup5gPiiGo2gztZAtU2wv/J2MFyHA1VmAVjNUQEC
xWccWbAowFZQs9b4nTf9sk/iRWnR84Wu9DuDUaXZERDQzE05IhfQ3p/jJORJCL+X
yrCIKu0vm9q7ooR2RcwG5WcD13Ov2yUWyK+0fHR4oGnE436vozpHYbvzDJHJaq3V
WWPAJ5Z6AV26CiTO5Ik2uOptggXKnxcSkBAwiMpChQw3z5vAP0H0hy42QGFntQYv
18S6jTKBuHnbuvoCs/Xd7zVmAOp1rHLjbERp2zdCy2wGTixZET6ptotzyZbOocA=
=R1o0
-----END PGP SIGNATURE-----
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org (mailto:gatein-dev@lists.jboss.org)
https://lists.jboss.org/mailman/listinfo/gatein-dev