Re: [PROPOSAL] Apache Isis
On 30/08/2010 07:26, Tim Williams wrote: Your proposal caused me to poke around the NO site and the first forum topic I came upon[1] had someone providing a [simple] patch. This has me curious about the code provenance. Assuming this isn't the only one, could you say something about getting clearance from outside contributors? At least, it seems to me that it could be slightly more complicated than the two parties you mention above. Just to update this thread... there have been very few patches historically. Indeed, we've searched through our email archives (back to 2002), through the SVN commit logs, and through the current codebase for any comments, and found only 1 one-liner from 2008, and the three patches in 2010 all from the same user (one of which was the patch you quoted). In addition, we have three contributors/committers who have made changes. What we're doing is contacting the guy who gave us these patches, and getting a formal ok from the existing contributors/committers; when I have this I'll update the proposal. Tim, I appreciate you taking the time to look into our affairs, though... I'm very keen that we get this right. Thx Dan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Isis
On Tue, Aug 31, 2010 at 6:28 AM, Dan Haywood dkhayw...@gmail.com wrote: On 30/08/2010 07:26, Tim Williams wrote: Your proposal caused me to poke around the NO site and the first forum topic I came upon[1] had someone providing a [simple] patch. This has me curious about the code provenance. Assuming this isn't the only one, could you say something about getting clearance from outside contributors? At least, it seems to me that it could be slightly more complicated than the two parties you mention above. Just to update this thread... there have been very few patches historically. Indeed, we've searched through our email archives (back to 2002), through the SVN commit logs, and through the current codebase for any comments, and found only 1 one-liner from 2008, and the three patches in 2010 all from the same user (one of which was the patch you quoted). In addition, we have three contributors/committers who have made changes. What we're doing is contacting the guy who gave us these patches, and getting a formal ok from the existing contributors/committers; when I have this I'll update the proposal. Hi Dan, that's great, you can just update your proposal to acknowledge this and then solve it during incubation. I think it's important to identify these things prior to incubation but you can work it while you're incubating [and, obviously, prior to any release]... --tim - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Meta-mentoring needed (was: Re: [PROPOSAL] Apache Isis)
We're making progress on the Apache Isis proposal, and now have four mentors. However, only one is currently a mentor (and still quite a newbie), and another is really emeritus rather than active. I'm wondering if there is any grizzled old mentor out there who might do a bit of meta-mentoring, ie someone for our mentors to turn to for an experienced eye? The benefits are two-fold: a) Isis improves its chance of incubating successfully b) the Incubator itself ends up with some new mentors who might be disposed to mentor subsequent projects. Looking forward to one or two +ve replies...! Thanks Dan On 26/08/2010 12:24, Matthias Wessendorf wrote: +1 (binding) On Thu, Aug 26, 2010 at 6:23 PM, Benson Marguliesbimargul...@gmail.com wrote: +1, binding. On Thu, Aug 26, 2010 at 12:12 PM, Siegfried Goeschl siegfried.goes...@it20one.at wrote: Hi Dan, +1 (non-binding) Cheers, Siegfried Goeschl On 24.08.10 19:12, Dan Haywood wrote: I'd like to formally propose a new project for the incubator, Apache Isis. If accepted, Isis will combine the existing open source Naked Objects framework with a collection of sister projects, providing an extensible Java-based framework for rapidly developing domain-driven applications. I floated the idea of Isis on this mailing list about a month or so ago, and we got some positive feedback and a couple of expressions of interest in contributing. Since then, we've put together a proposal (also copied in below) onto the incubator wiki. The proposal is at: http://wiki.apache.org/incubator/IsisProposal. The current codebase is at: http://nakedobjects.org, with sister projects hosted at: http://starobjects.org We currently have two mentors, but require more, and we still need a champion. I'm hoping that this post will generate some further interest to develop the proposal further. All being well we hope to put this proposal to a vote in a week or two's time. Thanks for reading, looking forward to your feedback. Dan Haywood ~~~ = Isis Proposal = The following presents the proposal for creating a new project within the Apache Software Foundation called Isis. == Abstract == Isis will be an extensible standards-based framework to rapidly develop and enterprise level deploy domain-driven (DDD) applications. == Proposal == The Isis project will bring together a collection of open source projects that collectively support the rapid development of domain-driven applications. The heart of Isis is the Naked Objects Framework, an established open source project that has been around since 2002. In addition, it will incorporate a number of sister projects that build on Naked Objects' pluggable architecture and which extend the reach of Naked Objects in several key areas. In addition, the project will be reorganising the existing projects to logically separate out the components into [[http://docs.jboss.org/weld/reference/1.0.1-Final/en-US/html/|JSR-299]] beans. We believe that the JSR-299 programming model is likely to become widely used for enterprise Java applications; adopting it should make it easier for new contributors to understand how the framework fits together and therefore to develop their own extensions. In turn, we hope this will further extend the reach of the framework to other complementary open source frameworks (either within Apache or outside of it). == Background == Naked Objects is an open source Java framework that was originally developed to explore the idea of enterprise systems that treat the user as a problem solver, not a process follower. Conceived by Richard Pawson, the first version of the framework was written by Robert Matthews (2002). Richard and Rob also wrote a book, Naked Objects (Wiley, 2002), to explain the idea. More generally, Naked Objects is an implementation of the naked objects architectural pattern. In its purest form, all the developer has to do is develop their domain model as pojos; Naked Objects then provides: a object-oriented user interface by rendering those pojos; persistence by extracting the content of the pojos; security by wrapping access to the pojos; remoting by turning local calls into remote ones; and localisation by adapting all the names used in the metamodel. All of this is done reflectively at runtime so that the developer can concentrate on the most important aspect - the application itself. You can think of Naked Objects' OOUI generation as analogous to Hibernate and other ORMs, but rather than reflecting the pojo into the persistence layer, they are reflected into the presentation layer. A number of other open source frameworks cite it as their inspiration, including [[http://jmatter.org|JMatter]], [[http://openxava.org|OpenXava]], and [[http://www.trailsframework.org|Trails]]. Over this time Naked Objects has attracted a fair degree of attention among the early adopter crowd, generally splitting opinion as either a very good idea or a very bad
Re: [PROPOSAL] Apache Isis
On Tue, Aug 24, 2010 at 1:12 PM, Dan Haywood dkhayw...@gmail.com wrote: I'd like to formally propose a new project for the incubator, Apache Isis. ... snipped == Source and IP Submission Plan == As mentioned earlier, the NO framework is ASLv2 but copyright belongs to Naked Objects Group Ltd. NOGL is happy to donate the relevant rights to Apache, while Dan is also happy to donate the various sister projects that he has written. Having a single legal entity - ASF - owning the relevant rights to all this software would be very desirable. Your proposal caused me to poke around the NO site and the first forum topic I came upon[1] had someone providing a [simple] patch. This has me curious about the code provenance. Assuming this isn't the only one, could you say something about getting clearance from outside contributors? At least, it seems to me that it could be slightly more complicated than the two parties you mention above. Thanks, --tim [1] - http://sourceforge.net/projects/nakedobjects/forums/forum/544071/topic/3742184 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Isis
Hi Tim... From this link - http://sourceforge.net/projects/nakedobjects - project details section, it is stated that the code of this project is licensed under (Apache License v2.0), and hence it is the responsibility of the person who contributed any code to the project to understand that his/her contribution is going to be under the same license as long as it is committed as a patch to source code of project they contributed to, just like what happens from contributors contributing code to different Apache projects. I hope this can reply your question ? :) On Mon, Aug 30, 2010 at 11:26 AM, Tim Williams william...@gmail.com wrote: On Tue, Aug 24, 2010 at 1:12 PM, Dan Haywood dkhayw...@gmail.com wrote: I'd like to formally propose a new project for the incubator, Apache Isis. ... snipped == Source and IP Submission Plan == As mentioned earlier, the NO framework is ASLv2 but copyright belongs to Naked Objects Group Ltd. NOGL is happy to donate the relevant rights to Apache, while Dan is also happy to donate the various sister projects that he has written. Having a single legal entity - ASF - owning the relevant rights to all this software would be very desirable. Your proposal caused me to poke around the NO site and the first forum topic I came upon[1] had someone providing a [simple] patch. This has me curious about the code provenance. Assuming this isn't the only one, could you say something about getting clearance from outside contributors? At least, it seems to me that it could be slightly more complicated than the two parties you mention above. Thanks, --tim [1] - http://sourceforge.net/projects/nakedobjects/forums/forum/544071/topic/3742184 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Author of (WebSphere Application Server Community Edition 2.0 User Guide) http://www.redbooks.ibm.com/abstracts/sg247585.html - LinkedIn: http://www.linkedin.com/in/mnour - Blog: http://tadabborat.blogspot.com Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein Writing clean code is what you must do in order to call yourself a professional. There is no reasonable excuse for doing anything less than your best. - Clean Code: A Handbook of Agile Software Craftsmanship Stay hungry, stay foolish. - Steve Jobs - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Isis
On Mon, Aug 30, 2010 at 7:39 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: Hi Tim... From this link - http://sourceforge.net/projects/nakedobjects - project details section, it is stated that the code of this project is licensed under (Apache License v2.0), and hence it is the responsibility of the person who contributed any code to the project to understand that his/her contribution is going to be under the same license as long as it is committed as a patch to source code of project they contributed to, just like what happens from contributors contributing code to different Apache projects. I hope this can reply your question ? :) Short answer is that I am not totally sure - I just saw that there were clearly other sources for the code other than the two parties mentioned and so I thought that should be highlighted in the IP Clearance section. The question, AIUI, isn't about the license of the code being patched, it's the granting of the code in the patch itself. We ask contributors to either submit an ICLA or check the Grant for inclusion... checkbox in JIRA. I don't have a lot of Incubator experience so I'll defer on this one, it just caught my eye - my own understanding is that contributors would need to be tracked down[1]. --tim [1] - http://incubator.apache.org/guides/mentor.html#initial-ip-clearance On Mon, Aug 30, 2010 at 11:26 AM, Tim Williams william...@gmail.com wrote: On Tue, Aug 24, 2010 at 1:12 PM, Dan Haywood dkhayw...@gmail.com wrote: I'd like to formally propose a new project for the incubator, Apache Isis. ... snipped == Source and IP Submission Plan == As mentioned earlier, the NO framework is ASLv2 but copyright belongs to Naked Objects Group Ltd. NOGL is happy to donate the relevant rights to Apache, while Dan is also happy to donate the various sister projects that he has written. Having a single legal entity - ASF - owning the relevant rights to all this software would be very desirable. Your proposal caused me to poke around the NO site and the first forum topic I came upon[1] had someone providing a [simple] patch. This has me curious about the code provenance. Assuming this isn't the only one, could you say something about getting clearance from outside contributors? At least, it seems to me that it could be slightly more complicated than the two parties you mention above. Thanks, --tim [1] - http://sourceforge.net/projects/nakedobjects/forums/forum/544071/topic/3742184 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Author of (WebSphere Application Server Community Edition 2.0 User Guide) http://www.redbooks.ibm.com/abstracts/sg247585.html - LinkedIn: http://www.linkedin.com/in/mnour - Blog: http://tadabborat.blogspot.com Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein Writing clean code is what you must do in order to call yourself a professional. There is no reasonable excuse for doing anything less than your best. - Clean Code: A Handbook of Agile Software Craftsmanship Stay hungry, stay foolish. - Steve Jobs - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Isis
Um, Well, maven still uses Codehaus JIRA that lacks the 'grant to Apache' checkbox. Perhaps they separately negotiate iclas. On Mon, Aug 30, 2010 at 7:57 AM, Tim Williams william...@gmail.com wrote: On Mon, Aug 30, 2010 at 7:39 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: Hi Tim... From this link - http://sourceforge.net/projects/nakedobjects - project details section, it is stated that the code of this project is licensed under (Apache License v2.0), and hence it is the responsibility of the person who contributed any code to the project to understand that his/her contribution is going to be under the same license as long as it is committed as a patch to source code of project they contributed to, just like what happens from contributors contributing code to different Apache projects. I hope this can reply your question ? :) Short answer is that I am not totally sure - I just saw that there were clearly other sources for the code other than the two parties mentioned and so I thought that should be highlighted in the IP Clearance section. The question, AIUI, isn't about the license of the code being patched, it's the granting of the code in the patch itself. We ask contributors to either submit an ICLA or check the Grant for inclusion... checkbox in JIRA. I don't have a lot of Incubator experience so I'll defer on this one, it just caught my eye - my own understanding is that contributors would need to be tracked down[1]. --tim [1] - http://incubator.apache.org/guides/mentor.html#initial-ip-clearance On Mon, Aug 30, 2010 at 11:26 AM, Tim Williams william...@gmail.com wrote: On Tue, Aug 24, 2010 at 1:12 PM, Dan Haywood dkhayw...@gmail.com wrote: I'd like to formally propose a new project for the incubator, Apache Isis. ... snipped == Source and IP Submission Plan == As mentioned earlier, the NO framework is ASLv2 but copyright belongs to Naked Objects Group Ltd. NOGL is happy to donate the relevant rights to Apache, while Dan is also happy to donate the various sister projects that he has written. Having a single legal entity - ASF - owning the relevant rights to all this software would be very desirable. Your proposal caused me to poke around the NO site and the first forum topic I came upon[1] had someone providing a [simple] patch. This has me curious about the code provenance. Assuming this isn't the only one, could you say something about getting clearance from outside contributors? At least, it seems to me that it could be slightly more complicated than the two parties you mention above. Thanks, --tim [1] - http://sourceforge.net/projects/nakedobjects/forums/forum/544071/topic/3742184 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Author of (WebSphere Application Server Community Edition 2.0 User Guide) http://www.redbooks.ibm.com/abstracts/sg247585.html - LinkedIn: http://www.linkedin.com/in/mnour - Blog: http://tadabborat.blogspot.com Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein Writing clean code is what you must do in order to call yourself a professional. There is no reasonable excuse for doing anything less than your best. - Clean Code: A Handbook of Agile Software Craftsmanship Stay hungry, stay foolish. - Steve Jobs - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Isis
+1 LieGrue, strub - Original Message From: Dan Haywood dkhayw...@gmail.com To: general@incubator.apache.org Cc: nakedobjects-contribut...@lists.sourceforge.net Sent: Tue, August 24, 2010 7:12:10 PM Subject: [PROPOSAL] Apache Isis I'd like to formally propose a new project for the incubator, Apache Isis. If accepted, Isis will combine the existing open source Naked Objects framework with a collection of sister projects, providing an extensible Java-based framework for rapidly developing domain-driven applications. I floated the idea of Isis on this mailing list about a month or so ago, and we got some positive feedback and a couple of expressions of interest in contributing. Since then, we've put together a proposal (also copied in below) onto the incubator wiki. The proposal is at: http://wiki.apache.org/incubator/IsisProposal. The current codebase is at: http://nakedobjects.org, with sister projects hosted at: http://starobjects.org We currently have two mentors, but require more, and we still need a champion. I'm hoping that this post will generate some further interest to develop the proposal further. All being well we hope to put this proposal to a vote in a week or two's time. Thanks for reading, looking forward to your feedback. Dan Haywood ~~~ = Isis Proposal = The following presents the proposal for creating a new project within the Apache Software Foundation called Isis. == Abstract == Isis will be an extensible standards-based framework to rapidly develop and enterprise level deploy domain-driven (DDD) applications. == Proposal == The Isis project will bring together a collection of open source projects that collectively support the rapid development of domain-driven applications. The heart of Isis is the Naked Objects Framework, an established open source project that has been around since 2002. In addition, it will incorporate a number of sister projects that build on Naked Objects' pluggable architecture and which extend the reach of Naked Objects in several key areas. In addition, the project will be reorganising the existing projects to logically separate out the components into [[http://docs.jboss.org/weld/reference/1.0.1-Final/en-US/html/|JSR-299]] beans. We believe that the JSR-299 programming model is likely to become widely used for enterprise Java applications; adopting it should make it easier for new contributors to understand how the framework fits together and therefore to develop their own extensions. In turn, we hope this will further extend the reach of the framework to other complementary open source frameworks (either within Apache or outside of it). == Background == Naked Objects is an open source Java framework that was originally developed to explore the idea of enterprise systems that treat the user as a problem solver, not a process follower. Conceived by Richard Pawson, the first version of the framework was written by Robert Matthews (2002). Richard and Rob also wrote a book, Naked Objects (Wiley, 2002), to explain the idea. More generally, Naked Objects is an implementation of the naked objects architectural pattern. In its purest form, all the developer has to do is develop their domain model as pojos; Naked Objects then provides: a object-oriented user interface by rendering those pojos; persistence by extracting the content of the pojos; security by wrapping access to the pojos; remoting by turning local calls into remote ones; and localisation by adapting all the names used in the metamodel. All of this is done reflectively at runtime so that the developer can concentrate on the most important aspect - the application itself. You can think of Naked Objects' OOUI generation as analogous to Hibernate and other ORMs, but rather than reflecting the pojo into the persistence layer, they are reflected into the presentation layer. A number of other open source frameworks cite it as their inspiration, including [[http://jmatter.org|JMatter]], [[http://openxava.org|OpenXava]], and [[http://www.trailsframework.org|Trails]]. Over this time Naked Objects has attracted a fair degree of attention among the early adopter crowd, generally splitting opinion as either a very good idea or a very bad one. A common misconception is that naked objects is only appropriate for simple CRUD based applications. While developing CRUD applications is indeed trivial, an important innovation is that the UI generated by NO also renders the pojo's commands/behaviors (we call them actions). Simply stated: any public method that does not represent a property or collection is rendered so it can be invoked, eg with a button, a menu item or a hyperlink. We characterize entities with such behaviors as behaviorally complete. It's OO as your mother taught it to you.
Re: [PROPOSAL] Apache Isis
Hi Dan, +1 (non-binding) Cheers, Siegfried Goeschl On 24.08.10 19:12, Dan Haywood wrote: I'd like to formally propose a new project for the incubator, Apache Isis. If accepted, Isis will combine the existing open source Naked Objects framework with a collection of sister projects, providing an extensible Java-based framework for rapidly developing domain-driven applications. I floated the idea of Isis on this mailing list about a month or so ago, and we got some positive feedback and a couple of expressions of interest in contributing. Since then, we've put together a proposal (also copied in below) onto the incubator wiki. The proposal is at: http://wiki.apache.org/incubator/IsisProposal. The current codebase is at: http://nakedobjects.org, with sister projects hosted at: http://starobjects.org We currently have two mentors, but require more, and we still need a champion. I'm hoping that this post will generate some further interest to develop the proposal further. All being well we hope to put this proposal to a vote in a week or two's time. Thanks for reading, looking forward to your feedback. Dan Haywood ~~~ = Isis Proposal = The following presents the proposal for creating a new project within the Apache Software Foundation called Isis. == Abstract == Isis will be an extensible standards-based framework to rapidly develop and enterprise level deploy domain-driven (DDD) applications. == Proposal == The Isis project will bring together a collection of open source projects that collectively support the rapid development of domain-driven applications. The heart of Isis is the Naked Objects Framework, an established open source project that has been around since 2002. In addition, it will incorporate a number of sister projects that build on Naked Objects' pluggable architecture and which extend the reach of Naked Objects in several key areas. In addition, the project will be reorganising the existing projects to logically separate out the components into [[http://docs.jboss.org/weld/reference/1.0.1-Final/en-US/html/|JSR-299]] beans. We believe that the JSR-299 programming model is likely to become widely used for enterprise Java applications; adopting it should make it easier for new contributors to understand how the framework fits together and therefore to develop their own extensions. In turn, we hope this will further extend the reach of the framework to other complementary open source frameworks (either within Apache or outside of it). == Background == Naked Objects is an open source Java framework that was originally developed to explore the idea of enterprise systems that treat the user as a problem solver, not a process follower. Conceived by Richard Pawson, the first version of the framework was written by Robert Matthews (2002). Richard and Rob also wrote a book, Naked Objects (Wiley, 2002), to explain the idea. More generally, Naked Objects is an implementation of the naked objects architectural pattern. In its purest form, all the developer has to do is develop their domain model as pojos; Naked Objects then provides: a object-oriented user interface by rendering those pojos; persistence by extracting the content of the pojos; security by wrapping access to the pojos; remoting by turning local calls into remote ones; and localisation by adapting all the names used in the metamodel. All of this is done reflectively at runtime so that the developer can concentrate on the most important aspect - the application itself. You can think of Naked Objects' OOUI generation as analogous to Hibernate and other ORMs, but rather than reflecting the pojo into the persistence layer, they are reflected into the presentation layer. A number of other open source frameworks cite it as their inspiration, including [[http://jmatter.org|JMatter]], [[http://openxava.org|OpenXava]], and [[http://www.trailsframework.org|Trails]]. Over this time Naked Objects has attracted a fair degree of attention among the early adopter crowd, generally splitting opinion as either a very good idea or a very bad one. A common misconception is that naked objects is only appropriate for simple CRUD based applications. While developing CRUD applications is indeed trivial, an important innovation is that the UI generated by NO also renders the pojo's commands/behaviors (we call them actions). Simply stated: any public method that does not represent a property or collection is rendered so it can be invoked, eg with a button, a menu item or a hyperlink. We characterize entities with such behaviors as behaviorally complete. It's OO as your mother taught it to you. At the same time that we have been developing our ideas on the naked objects, there has been a resurgent interest in object modelling at the enterprise level, specifically as described by Eric Evans' book, [[http://domaindrivendesign.org/books|Domain Driven Design]]. Recognizing that there's a lot of
Re: [PROPOSAL] Apache Isis
+1, binding. On Thu, Aug 26, 2010 at 12:12 PM, Siegfried Goeschl siegfried.goes...@it20one.at wrote: Hi Dan, +1 (non-binding) Cheers, Siegfried Goeschl On 24.08.10 19:12, Dan Haywood wrote: I'd like to formally propose a new project for the incubator, Apache Isis. If accepted, Isis will combine the existing open source Naked Objects framework with a collection of sister projects, providing an extensible Java-based framework for rapidly developing domain-driven applications. I floated the idea of Isis on this mailing list about a month or so ago, and we got some positive feedback and a couple of expressions of interest in contributing. Since then, we've put together a proposal (also copied in below) onto the incubator wiki. The proposal is at: http://wiki.apache.org/incubator/IsisProposal. The current codebase is at: http://nakedobjects.org, with sister projects hosted at: http://starobjects.org We currently have two mentors, but require more, and we still need a champion. I'm hoping that this post will generate some further interest to develop the proposal further. All being well we hope to put this proposal to a vote in a week or two's time. Thanks for reading, looking forward to your feedback. Dan Haywood ~~~ = Isis Proposal = The following presents the proposal for creating a new project within the Apache Software Foundation called Isis. == Abstract == Isis will be an extensible standards-based framework to rapidly develop and enterprise level deploy domain-driven (DDD) applications. == Proposal == The Isis project will bring together a collection of open source projects that collectively support the rapid development of domain-driven applications. The heart of Isis is the Naked Objects Framework, an established open source project that has been around since 2002. In addition, it will incorporate a number of sister projects that build on Naked Objects' pluggable architecture and which extend the reach of Naked Objects in several key areas. In addition, the project will be reorganising the existing projects to logically separate out the components into [[http://docs.jboss.org/weld/reference/1.0.1-Final/en-US/html/|JSR-299]] beans. We believe that the JSR-299 programming model is likely to become widely used for enterprise Java applications; adopting it should make it easier for new contributors to understand how the framework fits together and therefore to develop their own extensions. In turn, we hope this will further extend the reach of the framework to other complementary open source frameworks (either within Apache or outside of it). == Background == Naked Objects is an open source Java framework that was originally developed to explore the idea of enterprise systems that treat the user as a problem solver, not a process follower. Conceived by Richard Pawson, the first version of the framework was written by Robert Matthews (2002). Richard and Rob also wrote a book, Naked Objects (Wiley, 2002), to explain the idea. More generally, Naked Objects is an implementation of the naked objects architectural pattern. In its purest form, all the developer has to do is develop their domain model as pojos; Naked Objects then provides: a object-oriented user interface by rendering those pojos; persistence by extracting the content of the pojos; security by wrapping access to the pojos; remoting by turning local calls into remote ones; and localisation by adapting all the names used in the metamodel. All of this is done reflectively at runtime so that the developer can concentrate on the most important aspect - the application itself. You can think of Naked Objects' OOUI generation as analogous to Hibernate and other ORMs, but rather than reflecting the pojo into the persistence layer, they are reflected into the presentation layer. A number of other open source frameworks cite it as their inspiration, including [[http://jmatter.org|JMatter]], [[http://openxava.org|OpenXava]], and [[http://www.trailsframework.org|Trails]]. Over this time Naked Objects has attracted a fair degree of attention among the early adopter crowd, generally splitting opinion as either a very good idea or a very bad one. A common misconception is that naked objects is only appropriate for simple CRUD based applications. While developing CRUD applications is indeed trivial, an important innovation is that the UI generated by NO also renders the pojo's commands/behaviors (we call them actions). Simply stated: any public method that does not represent a property or collection is rendered so it can be invoked, eg with a button, a menu item or a hyperlink. We characterize entities with such behaviors as behaviorally complete. It's OO as your mother taught it to you. At the same time that we have been developing our ideas on the naked objects, there has been a resurgent interest in object
Re: [PROPOSAL] Apache Isis
+1 (binding) On Thu, Aug 26, 2010 at 6:23 PM, Benson Margulies bimargul...@gmail.com wrote: +1, binding. On Thu, Aug 26, 2010 at 12:12 PM, Siegfried Goeschl siegfried.goes...@it20one.at wrote: Hi Dan, +1 (non-binding) Cheers, Siegfried Goeschl On 24.08.10 19:12, Dan Haywood wrote: I'd like to formally propose a new project for the incubator, Apache Isis. If accepted, Isis will combine the existing open source Naked Objects framework with a collection of sister projects, providing an extensible Java-based framework for rapidly developing domain-driven applications. I floated the idea of Isis on this mailing list about a month or so ago, and we got some positive feedback and a couple of expressions of interest in contributing. Since then, we've put together a proposal (also copied in below) onto the incubator wiki. The proposal is at: http://wiki.apache.org/incubator/IsisProposal. The current codebase is at: http://nakedobjects.org, with sister projects hosted at: http://starobjects.org We currently have two mentors, but require more, and we still need a champion. I'm hoping that this post will generate some further interest to develop the proposal further. All being well we hope to put this proposal to a vote in a week or two's time. Thanks for reading, looking forward to your feedback. Dan Haywood ~~~ = Isis Proposal = The following presents the proposal for creating a new project within the Apache Software Foundation called Isis. == Abstract == Isis will be an extensible standards-based framework to rapidly develop and enterprise level deploy domain-driven (DDD) applications. == Proposal == The Isis project will bring together a collection of open source projects that collectively support the rapid development of domain-driven applications. The heart of Isis is the Naked Objects Framework, an established open source project that has been around since 2002. In addition, it will incorporate a number of sister projects that build on Naked Objects' pluggable architecture and which extend the reach of Naked Objects in several key areas. In addition, the project will be reorganising the existing projects to logically separate out the components into [[http://docs.jboss.org/weld/reference/1.0.1-Final/en-US/html/|JSR-299]] beans. We believe that the JSR-299 programming model is likely to become widely used for enterprise Java applications; adopting it should make it easier for new contributors to understand how the framework fits together and therefore to develop their own extensions. In turn, we hope this will further extend the reach of the framework to other complementary open source frameworks (either within Apache or outside of it). == Background == Naked Objects is an open source Java framework that was originally developed to explore the idea of enterprise systems that treat the user as a problem solver, not a process follower. Conceived by Richard Pawson, the first version of the framework was written by Robert Matthews (2002). Richard and Rob also wrote a book, Naked Objects (Wiley, 2002), to explain the idea. More generally, Naked Objects is an implementation of the naked objects architectural pattern. In its purest form, all the developer has to do is develop their domain model as pojos; Naked Objects then provides: a object-oriented user interface by rendering those pojos; persistence by extracting the content of the pojos; security by wrapping access to the pojos; remoting by turning local calls into remote ones; and localisation by adapting all the names used in the metamodel. All of this is done reflectively at runtime so that the developer can concentrate on the most important aspect - the application itself. You can think of Naked Objects' OOUI generation as analogous to Hibernate and other ORMs, but rather than reflecting the pojo into the persistence layer, they are reflected into the presentation layer. A number of other open source frameworks cite it as their inspiration, including [[http://jmatter.org|JMatter]], [[http://openxava.org|OpenXava]], and [[http://www.trailsframework.org|Trails]]. Over this time Naked Objects has attracted a fair degree of attention among the early adopter crowd, generally splitting opinion as either a very good idea or a very bad one. A common misconception is that naked objects is only appropriate for simple CRUD based applications. While developing CRUD applications is indeed trivial, an important innovation is that the UI generated by NO also renders the pojo's commands/behaviors (we call them actions). Simply stated: any public method that does not represent a property or collection is rendered so it can be invoked, eg with a button, a menu item or a hyperlink. We characterize entities with such behaviors as behaviorally complete. It's OO as your mother taught it to you. At the same time that we
Re: [PROPOSAL] Apache Isis
Thanks for that, Siegfried. I'm not actually putting this to a vote, yet, because we still need to find more mentors and a champion. If haven't yet done any cold calling of possible would-be mentors, but if you have any suggestions of anyone who might have the bandwidth for either role, I'd very much appreciate it! Thanks Dan ~~~ On 26/08/2010 17:12, Siegfried Goeschl wrote: Hi Dan, +1 (non-binding) Cheers, Siegfried Goeschl On 24.08.10 19:12, Dan Haywood wrote: I'd like to formally propose a new project for the incubator, Apache Isis. If accepted, Isis will combine the existing open source Naked Objects framework with a collection of sister projects, providing an extensible Java-based framework for rapidly developing domain-driven applications. I floated the idea of Isis on this mailing list about a month or so ago, and we got some positive feedback and a couple of expressions of interest in contributing. Since then, we've put together a proposal (also copied in below) onto the incubator wiki. The proposal is at: http://wiki.apache.org/incubator/IsisProposal. The current codebase is at: http://nakedobjects.org, with sister projects hosted at: http://starobjects.org We currently have two mentors, but require more, and we still need a champion. I'm hoping that this post will generate some further interest to develop the proposal further. All being well we hope to put this proposal to a vote in a week or two's time. Thanks for reading, looking forward to your feedback. Dan Haywood ~~~ = Isis Proposal = The following presents the proposal for creating a new project within the Apache Software Foundation called Isis. == Abstract == Isis will be an extensible standards-based framework to rapidly develop and enterprise level deploy domain-driven (DDD) applications. == Proposal == The Isis project will bring together a collection of open source projects that collectively support the rapid development of domain-driven applications. The heart of Isis is the Naked Objects Framework, an established open source project that has been around since 2002. In addition, it will incorporate a number of sister projects that build on Naked Objects' pluggable architecture and which extend the reach of Naked Objects in several key areas. In addition, the project will be reorganising the existing projects to logically separate out the components into [[http://docs.jboss.org/weld/reference/1.0.1-Final/en-US/html/|JSR-299]] beans. We believe that the JSR-299 programming model is likely to become widely used for enterprise Java applications; adopting it should make it easier for new contributors to understand how the framework fits together and therefore to develop their own extensions. In turn, we hope this will further extend the reach of the framework to other complementary open source frameworks (either within Apache or outside of it). == Background == Naked Objects is an open source Java framework that was originally developed to explore the idea of enterprise systems that treat the user as a problem solver, not a process follower. Conceived by Richard Pawson, the first version of the framework was written by Robert Matthews (2002). Richard and Rob also wrote a book, Naked Objects (Wiley, 2002), to explain the idea. More generally, Naked Objects is an implementation of the naked objects architectural pattern. In its purest form, all the developer has to do is develop their domain model as pojos; Naked Objects then provides: a object-oriented user interface by rendering those pojos; persistence by extracting the content of the pojos; security by wrapping access to the pojos; remoting by turning local calls into remote ones; and localisation by adapting all the names used in the metamodel. All of this is done reflectively at runtime so that the developer can concentrate on the most important aspect - the application itself. You can think of Naked Objects' OOUI generation as analogous to Hibernate and other ORMs, but rather than reflecting the pojo into the persistence layer, they are reflected into the presentation layer. A number of other open source frameworks cite it as their inspiration, including [[http://jmatter.org|JMatter]], [[http://openxava.org|OpenXava]], and [[http://www.trailsframework.org|Trails]]. Over this time Naked Objects has attracted a fair degree of attention among the early adopter crowd, generally splitting opinion as either a very good idea or a very bad one. A common misconception is that naked objects is only appropriate for simple CRUD based applications. While developing CRUD applications is indeed trivial, an important innovation is that the UI generated by NO also renders the pojo's commands/behaviors (we call them actions). Simply stated: any public method that does not represent a property or collection is rendered so it can be invoked, eg with a button, a menu item or a hyperlink. We characterize
Re: [PROPOSAL] Apache Isis
+1 (Not binding) On Tue, Aug 24, 2010 at 5:12 PM, Dan Haywood dkhayw...@gmail.com wrote: I'd like to formally propose a new project for the incubator, Apache Isis. If accepted, Isis will combine the existing open source Naked Objects framework with a collection of sister projects, providing an extensible Java-based framework for rapidly developing domain-driven applications. I floated the idea of Isis on this mailing list about a month or so ago, and we got some positive feedback and a couple of expressions of interest in contributing. Since then, we've put together a proposal (also copied in below) onto the incubator wiki. The proposal is at: http://wiki.apache.org/incubator/IsisProposal. The current codebase is at: http://nakedobjects.org, with sister projects hosted at: http://starobjects.org We currently have two mentors, but require more, and we still need a champion. I'm hoping that this post will generate some further interest to develop the proposal further. All being well we hope to put this proposal to a vote in a week or two's time. Thanks for reading, looking forward to your feedback. Dan Haywood ~~~ = Isis Proposal = The following presents the proposal for creating a new project within the Apache Software Foundation called Isis. == Abstract == Isis will be an extensible standards-based framework to rapidly develop and enterprise level deploy domain-driven (DDD) applications. == Proposal == The Isis project will bring together a collection of open source projects that collectively support the rapid development of domain-driven applications. The heart of Isis is the Naked Objects Framework, an established open source project that has been around since 2002. In addition, it will incorporate a number of sister projects that build on Naked Objects' pluggable architecture and which extend the reach of Naked Objects in several key areas. In addition, the project will be reorganising the existing projects to logically separate out the components into [[http://docs.jboss.org/weld/reference/1.0.1-Final/en-US/html/|JSR-299]] beans. We believe that the JSR-299 programming model is likely to become widely used for enterprise Java applications; adopting it should make it easier for new contributors to understand how the framework fits together and therefore to develop their own extensions. In turn, we hope this will further extend the reach of the framework to other complementary open source frameworks (either within Apache or outside of it). == Background == Naked Objects is an open source Java framework that was originally developed to explore the idea of enterprise systems that treat the user as a problem solver, not a process follower. Conceived by Richard Pawson, the first version of the framework was written by Robert Matthews (2002). Richard and Rob also wrote a book, Naked Objects (Wiley, 2002), to explain the idea. More generally, Naked Objects is an implementation of the naked objects architectural pattern. In its purest form, all the developer has to do is develop their domain model as pojos; Naked Objects then provides: a object-oriented user interface by rendering those pojos; persistence by extracting the content of the pojos; security by wrapping access to the pojos; remoting by turning local calls into remote ones; and localisation by adapting all the names used in the metamodel. All of this is done reflectively at runtime so that the developer can concentrate on the most important aspect - the application itself. You can think of Naked Objects' OOUI generation as analogous to Hibernate and other ORMs, but rather than reflecting the pojo into the persistence layer, they are reflected into the presentation layer. A number of other open source frameworks cite it as their inspiration, including [[http://jmatter.org|JMatter]], [[http://openxava.org|OpenXava]], and [[http://www.trailsframework.org|Trails]]. Over this time Naked Objects has attracted a fair degree of attention among the early adopter crowd, generally splitting opinion as either a very good idea or a very bad one. A common misconception is that naked objects is only appropriate for simple CRUD based applications. While developing CRUD applications is indeed trivial, an important innovation is that the UI generated by NO also renders the pojo's commands/behaviors (we call them actions). Simply stated: any public method that does not represent a property or collection is rendered so it can be invoked, eg with a button, a menu item or a hyperlink. We characterize entities with such behaviors as behaviorally complete. It's OO as your mother taught it to you. At the same time that we have been developing our ideas on the naked objects, there has been a resurgent interest in object modelling at the enterprise level, specifically as described by Eric Evans' book,
