Hi Sander!
I have managed to build and run your application on my box, using
Postgres, and it works like a charm! So what do you think about this
plan:
------------------------------------------------
1. I'm going to play around with your code and try to split it in two projects:
- "jooq-wicket" for the generic parts
- "jooq-wicket-example" for your example webapp
2. I'll check this in and maybe we can release that in beta mode with
1.6.4 and get some community feedback both from the jOOQ users and
from the wicket users
3. If the feedback was good, then we'll continue with these two
modules. I'm thinking about creating standardised integration tests
using selenium, across all database schemata (using my t_book /
t_author) tables.
------------------------------------------------
If such a plan is interesting for you, we'll need to discuss business
(if you prefer, we can also continue this discussion privately). I
could see these copyright and ownership models for the new jOOQ
extensions:
1. You keep the copyright as you did the original implementation. That
would mean that you would maintain this extension yourself on your own
servers. It would not be part of jOOQ, but I will advertise it for you
and maybe take some inspiration from it in my own "jooq-wicket"
integration.
2. We share the copyright for a given amount of time. If we'd like to
discontinue sharing the copyright in the future, we can then both fork
the current version and continue maintaining our own. With that model,
I'd propose that "jooq-wicket" and "jooq-wicket-example" will be
hosted on sourceforge as regular jOOQ modules and distributed in a
dedicated jOOQ-web.zip package and also in the org.jooq maven group.
You would become a regular committer with sourceforge SVN access (also
for "jOOQ-core" if needed) and we would both maintain the new
extension. This is not an obligation to do any work though. I'd
suggest, the extensions would also be licensed with the Apache 2.0
license: http://www.apache.org/licenses/LICENSE-2.0. To me, this is
the simplest and most business-friendly license out there
3. I take over the copyright and you can become a "user" of it under
the Apache 2.0 license
What do you think about this? For me, 2 and 3 are equally interesting.
Cheers
Lukas
2011/7/26 Lukas Eder <[email protected]>:
> Very nice, thank you very much for that nice example! And for putting
> us on the same level with very influential people ;-)
> I'll have a look at this some time this week, asap!
>
> Cheers
> Lukas
>
> 2011/7/26 Sander Plas <[email protected]>:
>> I have cleaned up my integration code a bit and created a small sample
>> project, with lots of comments in the code, so that you (and maybe
>> others) can at least take a look at the code and maybe use it as a
>> starting point.
>>
>> You can see it working at http://test-www.seeas.nl:8080/jooq-wicket-example/
>> .
>>
>> The source can be downloaded at http://www.oele.net/jooq-wicket-example/
>> .
>>
>> To get it to work on your own machine:
>> - open the project (from the ZIP file) in your IDE
>> - create a PostgreSQL database using the the .sql file and make it
>> available under java:comp/env/jdbc/jooq_wicket_example
>> - change the database settings in jooq-codegen.properties
>> - build & run the project.
>>
>
