[RESULT] [VOTE] Isis to enter the incubator
The vote for Isis to enter the incubator is now closed, and has been ACCEPTED. +9 (binding): Matthias Wessendorf, Tim Williams, Mark Struberg, Bertrand Delacatraz, Alan D. Cabrera, Niclas Hedhman, Benson Marguiles, Jim Jagielski, Craig L Russell +4 (non-binding): Mohammad Nour El-Din, Leif Hedstrom, Ulrich Stark, Martijn Dashorst Many thanks to all. I'll contact our mentors off-list initially for guidance as to the next steps. Thanks again, Dan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Isis to enter the incubator
+1 binding Craig On Sep 1, 2010, at 2:42 AM, Dan Haywood wrote: The Isis proposal has now been updated with a champion and several new mentors (thanks again guys), and is ready to be voted on. The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text is also copied below. Please, cast your vote. [ ] +1, please indicate whether binding [ ] =0 [ ] -1, please indicate your reason I'll close the vote at end of Monday 6th Sept PST, to include the weekend and the US' Labor Day holiday. That's about 6 days (144 hours) from now. Thanks, Dan -- = 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 synergy between the two ideas, the NO framework now uses DDD terminology, such as repository, domain service and value. As mentioned in the proposal section, Isis will consist of both the original NO framework, along with a number of sister projects. These sister projects were written by Dan Haywood to support a book he wrote about the framework, [[http://pragprog.com/titles/dhnako| Domain Driven Design using Naked Objects]] (Pragmatic Bookshelf, 2009). T
Re: [VOTE] Isis to enter the incubator
+1 On Wed, Sep 1, 2010 at 11:42 AM, Dan Haywood wrote: > The Isis proposal has now been updated with a champion and several new > mentors (thanks again guys), and is ready to be voted on. > > The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text > is also copied below. > > Please, cast your vote. > > [ ] +1, please indicate whether binding > [ ] =0 > [ ] -1, please indicate your reason > > I'll close the vote at end of Monday 6th Sept PST, to include the weekend > and the US' Labor Day holiday. That's about 6 days (144 hours) from now. > > Thanks, > Dan > > -- > = 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 synergy between the two ideas, the NO framework now > uses DDD terminology, such as repository, domain service and value. > > As mentioned in the proposal section, Isis will consist of both the original > NO framework, along with a number of sister projects. These sister projects > were written by Dan Haywood to support a book he wrote about the framework, > [[http://pragprog.com/titles/dhnako|Domain Driven Design using Naked > Objects]] (Pr
Re: [VOTE] Isis to enter the incubator
Just a reminder - this vote closes at the end of today. So if you want to cast a vote, you've still got a chance to do so. Thanks, Dan The Isis proposal has now been updated with a champion and several new mentors (thanks again guys), and is ready to be voted on. The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text is also copied below. Please, cast your vote. [ ] +1, please indicate whether binding [ ] =0 [ ] -1, please indicate your reason I'll close the vote at end of Monday 6th Sept PST, to include the weekend and the US' Labor Day holiday. That's about 6 days (144 hours) from now. Thanks, Dan -- = 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 synergy between the two ideas, the NO framework now uses DDD terminology, such as repository, domain service and value. As mentioned in the proposal section, Isis will consist of both the original NO framework, along with a number of sister projects. These sister projects were written by Dan Haywood to support a book he wrote about the framework, [[http://pragprog.com/titles/dhnako|Domain Driven Design using Naked Objects]] (Pragmatic Bookshelf, 2009). The inten
Re: [VOTE] Isis to enter the incubator
+1: binding On Sep 1, 2010, at 5:42 AM, Dan Haywood wrote: > The Isis proposal has now been updated with a champion and several new > mentors (thanks again guys), and is ready to be voted on. > > The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text > is also copied below. > > Please, cast your vote. > > [ ] +1, please indicate whether binding > [ ] =0 > [ ] -1, please indicate your reason > > I'll close the vote at end of Monday 6th Sept PST, to include the weekend and > the US' Labor Day holiday. That's about 6 days (144 hours) from now. > > Thanks, > Dan > > -- > = 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 synergy between the two ideas, the NO framework now > uses DDD terminology, such as repository, domain service and value. > > As mentioned in the proposal section, Isis will consist of both the original > NO framework, along with a number of sister projects. These sister projects > were written by Dan Haywood to support a book he wrote about the framework, > [[http://prag
Re: [VOTE] Isis to enter the incubator
+1 (not binding) Uli On 01.09.2010 11:42, Dan Haywood wrote: The Isis proposal has now been updated with a champion and several new mentors (thanks again guys), and is ready to be voted on. The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text is also copied below. Please, cast your vote. [ ] +1, please indicate whether binding [ ] =0 [ ] -1, please indicate your reason I'll close the vote at end of Monday 6th Sept PST, to include the weekend and the US' Labor Day holiday. That's about 6 days (144 hours) from now. Thanks, Dan -- = 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 synergy between the two ideas, the NO framework now uses DDD terminology, such as repository, domain service and value. As mentioned in the proposal section, Isis will consist of both the original NO framework, along with a number of sister projects. These sister projects were written by Dan Haywood to support a book he wrote about the framework, [[http://pragprog.com/titles/dhnako|Domain Driven Design using Naked Objects]] (Pragmatic Bookshelf, 2009). The intent of these projects was to demonstrate the pluggable nature of the framework. Both N
Re: [VOTE] Isis to enter the incubator
(+1 binding) On Wed, Sep 1, 2010 at 9:18 AM, Niclas Hedhman wrote: > +1, binding > > On Wed, Sep 1, 2010 at 5:42 PM, Dan Haywood wrote: >> The Isis proposal has now been updated with a champion and several new >> mentors (thanks again guys), and is ready to be voted on. >> >> The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text >> is also copied below. >> >> Please, cast your vote. >> >> [ ] +1, please indicate whether binding >> [ ] =0 >> [ ] -1, please indicate your reason >> >> I'll close the vote at end of Monday 6th Sept PST, to include the weekend >> and the US' Labor Day holiday. That's about 6 days (144 hours) from now. >> >> Thanks, >> Dan >> >> -- >> = 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 synergy between the two ideas, the NO framework now >> uses DDD terminology, such as repository, domain service and value. >> >> As mentioned in the proposal section, Isis will consist of both the original >> NO framework, along with a number of sister projects. These sister pr
Re: [VOTE] Isis to enter the incubator
On Sep 1, 2010, at 3:42 AM, Dan Haywood wrote: > The Isis proposal has now been updated with a champion and several new > mentors (thanks again guys), and is ready to be voted on. > > The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text > is also copied below. > > Please, cast your vote. > > [ ] +1, please indicate whether binding > [ ] =0 > [ ] -1, please indicate your reason +1 (not binding) -- Leif - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Isis to enter the incubator
+1, binding On Wed, Sep 1, 2010 at 5:42 PM, Dan Haywood wrote: > The Isis proposal has now been updated with a champion and several new > mentors (thanks again guys), and is ready to be voted on. > > The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text > is also copied below. > > Please, cast your vote. > > [ ] +1, please indicate whether binding > [ ] =0 > [ ] -1, please indicate your reason > > I'll close the vote at end of Monday 6th Sept PST, to include the weekend > and the US' Labor Day holiday. That's about 6 days (144 hours) from now. > > Thanks, > Dan > > -- > = 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 synergy between the two ideas, the NO framework now > uses DDD terminology, such as repository, domain service and value. > > As mentioned in the proposal section, Isis will consist of both the original > NO framework, along with a number of sister projects. These sister projects > were written by Dan Haywood to support a book he wrote about the framework, > [[http://pragprog.com/titles/dhnako|Domain Driven Design using Naked > Objec
Re: [VOTE] Isis to enter the incubator
+1 (binding) Regards, Alan On Sep 1, 2010, at 2:42 AM, Dan Haywood wrote: > The Isis proposal has now been updated with a champion and several new > mentors (thanks again guys), and is ready to be voted on. > > The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text > is also copied below. > > Please, cast your vote. > > [ ] +1, please indicate whether binding > [ ] =0 > [ ] -1, please indicate your reason > > I'll close the vote at end of Monday 6th Sept PST, to include the weekend and > the US' Labor Day holiday. That's about 6 days (144 hours) from now. > > Thanks, > Dan > > -- > = 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 synergy between the two ideas, the NO framework now > uses DDD terminology, such as repository, domain service and value. > > As mentioned in the proposal section, Isis will consist of both the original > NO framework, along with a number of sister projects. These sister projects > were written by Dan Haywood to support a book he wrote about the framework,
Re: [VOTE] Isis to enter the incubator
> [X ] +1, binding Cool to see a project enter incubation with already two books written ;-) -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Isis to enter the incubator
+1 (Not binding) On Wed, Sep 1, 2010 at 10:40 AM, Mark Struberg wrote: > +1 (binding) > > LieGrue, > strub > > --- On Wed, 9/1/10, Dan Haywood wrote: > >> From: Dan Haywood >> Subject: [VOTE] Isis to enter the incubator >> To: general@incubator.apache.org >> Cc: nakedobjects-contribut...@lists.sourceforge.net >> Date: Wednesday, September 1, 2010, 9:42 AM >> The Isis proposal has now been >> updated with a champion and several new mentors (thanks >> again guys), and is ready to be voted on. >> >> The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the >> text is also copied below. >> >> Please, cast your vote. >> >> [ ] +1, please indicate whether binding >> [ ] =0 >> [ ] -1, please indicate your reason >> >> I'll close the vote at end of Monday 6th Sept PST, to >> include the weekend and the US' Labor Day holiday. That's >> about 6 days (144 hours) from now. >> >> Thanks, >> Dan >> >> -- >> = 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
Re: [VOTE] Isis to enter the incubator
+1 (binding) LieGrue, strub --- On Wed, 9/1/10, Dan Haywood wrote: > From: Dan Haywood > Subject: [VOTE] Isis to enter the incubator > To: general@incubator.apache.org > Cc: nakedobjects-contribut...@lists.sourceforge.net > Date: Wednesday, September 1, 2010, 9:42 AM > The Isis proposal has now been > updated with a champion and several new mentors (thanks > again guys), and is ready to be voted on. > > The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the > text is also copied below. > > Please, cast your vote. > > [ ] +1, please indicate whether binding > [ ] =0 > [ ] -1, please indicate your reason > > I'll close the vote at end of Monday 6th Sept PST, to > include the weekend and the US' Labor Day holiday. That's > about 6 days (144 hours) from now. > > Thanks, > Dan > > -- > = 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 &g
Re: [VOTE] Isis to enter the incubator
On Wed, Sep 1, 2010 at 5:42 AM, Dan Haywood wrote: > The Isis proposal has now been updated with a champion and several new > mentors (thanks again guys), and is ready to be voted on. > > The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text > is also copied below. > > Please, cast your vote. > > [ ] +1, please indicate whether binding > [ ] =0 > [ ] -1, please indicate your reason +1, binding... --tim - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Isis to enter the incubator
+1 (binding) -Matthias On Wed, Sep 1, 2010 at 11:42 AM, Dan Haywood wrote: > The Isis proposal has now been updated with a champion and several new > mentors (thanks again guys), and is ready to be voted on. > > The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text > is also copied below. > > Please, cast your vote. > > [ ] +1, please indicate whether binding > [ ] =0 > [ ] -1, please indicate your reason > > I'll close the vote at end of Monday 6th Sept PST, to include the weekend > and the US' Labor Day holiday. That's about 6 days (144 hours) from now. > > Thanks, > Dan > > -- > = 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 synergy between the two ideas, the NO framework now > uses DDD terminology, such as repository, domain service and value. > > As mentioned in the proposal section, Isis will consist of both the original > NO framework, along with a number of sister projects. These sister projects > were written by Dan Haywood to support a book he wrote about the framework, > [[http://pragprog.com/titles/dhnako|Domain Driven Design using
[VOTE] Isis to enter the incubator
The Isis proposal has now been updated with a champion and several new mentors (thanks again guys), and is ready to be voted on. The proposal is at: http://wiki.apache.org/incubator/IsisProposal , the text is also copied below. Please, cast your vote. [ ] +1, please indicate whether binding [ ] =0 [ ] -1, please indicate your reason I'll close the vote at end of Monday 6th Sept PST, to include the weekend and the US' Labor Day holiday. That's about 6 days (144 hours) from now. Thanks, Dan -- = 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 synergy between the two ideas, the NO framework now uses DDD terminology, such as repository, domain service and value. As mentioned in the proposal section, Isis will consist of both the original NO framework, along with a number of sister projects. These sister projects were written by Dan Haywood to support a book he wrote about the framework, [[http://pragprog.com/titles/dhnako|Domain Driven Design using Naked Objects]] (Pragmatic Bookshelf, 2009). The intent of these projects was to demonstrate the pluggable nature of the framework. Both Naked Objects and its sister projec
