Re: announcing Granite - a Wicket-Scala-DB4O web application stack
On Wed, 22 Sep 2010 14:19:17 +, Sam Stainsby wrote: On Wed, 22 Sep 2010 15:34:15 +0200, Erik van Oosten wrote: I have looked at the example and it looks very promising. However, if you want more attention there should at the absolute minimum be a bunch of links somewhere that give starting points for someone to understand the project. E.g. links to important classes, important examples. Either an architecture overview or a small programming guide would be great too of course :) Sure, it must seem pretty obscure to newcomers at the moment. There is a bit more information here now, but still a way to go on the doco side of things: http://sustainablesoftware.com.au/blog/?p=114 Granite: a simple example step-by-step As a prelude to outlining the architecture of Uniscala Granite as it currently stands, I’m going to run through creating a very simple Granite example, starting from the Granite Maven archetype, and ending with the application running on Jetty that can store, display and update meaningful data in the DB4O database. I’m going to assume that you’ve have already checked out Uniscala, and built and installed it with Maven according to the quick start guide.If you’ve followed all of the steps in the guide for using the Maven archetype, you should already have an empty application called ‘myapp’ that will run under Jetty — we’ll use this as a starting point for our example. ... Cheers, Sam. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: announcing Granite - a Wicket-Scala-DB4O web application stack
You could still have couchdb as a database, and also there is the beginnings of an object store layer tucked away in an experimental API, but I think we will stick with DB4O for the primary database. Once you see the ease with which you can store use DB4O, you will see why eg (in Scala sorry): // define a class class C(var x:String), var y:Int) // store an instance db.store(new C(hi, 123)) // find all instances of C in the database val query = Query[C] query in db Cheers, Sam. On Thu, 23 Sep 2010 19:58:03 -0700, 7zark7 wrote: Looks great, thanks for the link. +1 on CouchDB, et al vs only DB4o, Wicket+Scala+Couch is a really nice stack Thanks On 9/21/10 11:42 PM, Thomas Kappler wrote: On 09/22/10 03:41, Sam Stainsby wrote: Today we officially announced our project to provide a Wicket-DB4O-Scala web application stack: http://sustainablesoftware.com.au/blog/?p=77 I’m pleased to announce a new web application framework, called Granite, and an associated set of reusable libraries, called Uniscala. Please note that this is a work in progress: we are not announcing a release yet, or even a beta. A number people have started asking about the project, and so I felt it would be helpful to let the wider world know what is going on. Granite is a lightweight framework for the rapid development of web applications. It is based on the very cool and richly featured Apache Wicket web framework. Granite uses an embedded object database that avoids the need for SQL or Object-Relational Mappers (ORMs), and, in the Wicket tradition, is proud of, if not smug about, its distinct lack of external XML configuration files. Hey, I find that quite exciting. Now that you've done the hard work of fitting a non-relational store into a Wicket-based framework, do you think it would be hard to substitute other data stores such as Redis, CouchDB, BDB for DB4O? -- Thomas - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: announcing Granite - a Wicket-Scala-DB4O web application stack
You could abstract the datastore in the stack using JDO/DataNucleus. It supports DB40. In fact as it also supports RDBMS you could easily create a datastore agnostic Wicket/Scala stack - that would be most awesome! Just as a side note: there is/was an mini example with warp persist which can handle db4o+neodatis (and with some minor work also hibernate): http://karussell.wordpress.com/2010/01/18/crud-with-wicket-guice-db4o-neodatis/ Regards, Peter. -- http://jetwick.com twitter search prototype - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: announcing Granite - a Wicket-Scala-DB4O web application stack
Looks great, thanks for the link. +1 on CouchDB, et al vs only DB4o, Wicket+Scala+Couch is a really nice stack Thanks On 9/21/10 11:42 PM, Thomas Kappler wrote: On 09/22/10 03:41, Sam Stainsby wrote: Today we officially announced our project to provide a Wicket-DB4O-Scala web application stack: http://sustainablesoftware.com.au/blog/?p=77 I’m pleased to announce a new web application framework, called Granite, and an associated set of reusable libraries, called Uniscala. Please note that this is a work in progress: we are not announcing a release yet, or even a beta. A number people have started asking about the project, and so I felt it would be helpful to let the wider world know what is going on. Granite is a lightweight framework for the rapid development of web applications. It is based on the very cool and richly featured Apache Wicket web framework. Granite uses an embedded object database that avoids the need for SQL or Object-Relational Mappers (ORMs), and, in the Wicket tradition, is proud of, if not smug about, its distinct lack of external XML configuration files. Hey, I find that quite exciting. Now that you've done the hard work of fitting a non-relational store into a Wicket-based framework, do you think it would be hard to substitute other data stores such as Redis, CouchDB, BDB for DB4O? -- Thomas - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: announcing Granite - a Wicket-Scala-DB4O web application stack
On 09/22/10 03:41, Sam Stainsby wrote: Today we officially announced our project to provide a Wicket-DB4O-Scala web application stack: http://sustainablesoftware.com.au/blog/?p=77 I’m pleased to announce a new web application framework, called Granite, and an associated set of reusable libraries, called Uniscala. Please note that this is a work in progress: we are not announcing a release yet, or even a beta. A number people have started asking about the project, and so I felt it would be helpful to let the wider world know what is going on. Granite is a lightweight framework for the rapid development of web applications. It is based on the very cool and richly featured Apache Wicket web framework. Granite uses an embedded object database that avoids the need for SQL or Object-Relational Mappers (ORMs), and, in the Wicket tradition, is proud of, if not smug about, its distinct lack of external XML configuration files. Hey, I find that quite exciting. Now that you've done the hard work of fitting a non-relational store into a Wicket-based framework, do you think it would be hard to substitute other data stores such as Redis, CouchDB, BDB for DB4O? -- Thomas -- --- Thomas Kapplerthomas.kapp...@isb-sib.ch Swiss Institute of Bioinformatics Tel: +41 22 379 51 89 CMU, rue Michel Servet 1 1211 Geneve 4 Switzerland http://www.uniprot.org --- - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: announcing Granite - a Wicket-Scala-DB4O web application stack
I have looked at the example and it looks very promising. However, if you want more attention there should at the absolute minimum be a bunch of links somewhere that give starting points for someone to understand the project. E.g. links to important classes, important examples. Either an architecture overview or a small programming guide would be great too of course :) Regards, Erik. Op 22-09-10 03:41, Sam Stainsby schreef: Today we officially announced our project to provide a Wicket-DB4O-Scala web application stack: http://sustainablesoftware.com.au/blog/?p=77 I’m pleased to announce a new web application framework, called Granite, and an associated set of reusable libraries, called Uniscala. Please note that this is a work in progress: we are not announcing a release yet, or even a beta. A number people have started asking about the project, and so I felt it would be helpful to let the wider world know what is going on. Granite is a lightweight framework for the rapid development of web applications. It is based on the very cool and richly featured Apache Wicket web framework. Granite uses an embedded object database that avoids the need for SQL or Object-Relational Mappers (ORMs), and, in the Wicket tradition, is proud of, if not smug about, its distinct lack of external XML configuration files. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Erik van Oosten http://www.day-to-day-stuff.blogspot.com/ - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: announcing Granite - a Wicket-Scala-DB4O web application stack
On Wed, 22 Sep 2010 08:42:20 +0200, Thomas Kappler wrote: On 09/22/10 03:41, Sam Stainsby wrote: Today we officially announced our project to provide a Wicket-DB4O-Scala web application stack: Now that you've done the hard work of fitting a non-relational store into a Wicket-based framework, do you think it would be hard to substitute other data stores such as Redis, CouchDB, BDB for DB4O? It's all a matter of building Wicket models that wrap IDs (or OID) and queries, so probably not hard. I'm not planning to abstract across databases for Granite though. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: announcing Granite - a Wicket-Scala-DB4O web application stack
On Wed, 22 Sep 2010 15:34:15 +0200, Erik van Oosten wrote: I have looked at the example and it looks very promising. However, if you want more attention there should at the absolute minimum be a bunch of links somewhere that give starting points for someone to understand the project. E.g. links to important classes, important examples. Either an architecture overview or a small programming guide would be great too of course :) Sure, it must seem pretty obscure to newcomers at the moment. I plan to add more entries in our blog and use that text to build up a guide. Too much attention at this point in development might be unwarranted in any case :-) Topics will be along the lines of the overall architecture, how Granite's IoC works, and then an explanation of how DB4O is used in Granite. All of these are vital to write any serious Granite app. I also hope to add more examples. There might not be much material before the end of this financial quarter (the end of this month for us in Australia), as I'm busy finalising client commitments ... one of which involves delivering a project based on Granite. Op 22-09-10 03:41, Sam Stainsby schreef: Today we officially announced our project to provide a Wicket-DB4O-Scala web application stack: - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: announcing Granite - a Wicket-Scala-DB4O web application stack
You could abstract the datastore in the stack using JDO/DataNucleus. It supports DB40. In fact as it also supports RDBMS you could easily create a datastore agnostic Wicket/Scala stack - that would be most awesome! -Original Message- From: Sam Stainsby [mailto:s...@sustainablesoftware.com.au] Sent: Thursday, 23 September 2010 12:06 AM To: users@wicket.apache.org Subject: Re: announcing Granite - a Wicket-Scala-DB4O web application stack On Wed, 22 Sep 2010 08:42:20 +0200, Thomas Kappler wrote: On 09/22/10 03:41, Sam Stainsby wrote: Today we officially announced our project to provide a Wicket-DB4O-Scala web application stack: Now that you've done the hard work of fitting a non-relational store into a Wicket-based framework, do you think it would be hard to substitute other data stores such as Redis, CouchDB, BDB for DB4O? It's all a matter of building Wicket models that wrap IDs (or OID) and queries, so probably not hard. I'm not planning to abstract across databases for Granite though. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: announcing Granite - a Wicket-Scala-DB4O web application stack
On Thu, 23 Sep 2010 04:47:24 +1000, Chris Colman wrote: You could abstract the datastore in the stack using JDO/DataNucleus. It supports DB40. In fact as it also supports RDBMS you could easily create a datastore agnostic Wicket/Scala stack - that would be most awesome! That's one path that I have considered. I'm more of a mind to provide an environment where there is one type of embedded root database, but you can still interact meaningfully with other types of database. In fact, my first client project using Granite is a reporting engine for an SQL database that hold gigabytes of log data from a network of health kiosks! I will get around to blogging about that at some stage. I guess you could even have the root database and a JDO facility. --Sam. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
