You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jspwiki.apache.org by David Emerson <de...@spindrift.com> on 2014/12/02 02:12:15 UTC
JDBCProvider
I've been using a really old version of JSPWiki and storing pages via the
old JDBCProvider. I'd like to update to the latest release, but the page
provider isn't compatible at the moment. For fun, I tried to get the latest
version of the code I could find to compile against the latest JSPWiki
code, which I was able to do. I also need to add a new SQL query for a new
overload of pageExists, but that looks pretty straightforward.
If I can get this working it makes sense to contribute it back to the
project, but I have a few questions. I moved the code from it's original
package to a new package under the existing package for the core providers.
Would you want it moved out of there back to it's original package
structure? I'd like to contribute this, but don't want to commit to owning
it long term (of course I'm fine with fixing bugs until it seems stable). I
also don't really want to host it's download. I actually think it makes
sense for it to be a core provider, but I'm not sure if there are issues
with that since it was originally developed as a contributed provider.
Also, if you folks have access to JDBCProvider code more recent than June
2006, I'd re-do my fixes against that instead. Any suggestions on how to
proceed?
Re: JDBCProvider
Posted by David Vittor <dv...@gmail.com>.
Thanks for sharing with us David E.
Cheers,
David V :)
On Sat, Dec 27, 2014 at 3:26 AM, David (spindift) <de...@spindrift.com>
wrote:
> An initial beta release of a JDBCProvider is now available on GitHub at
> https://github.com/djemerson01/jspwiki-jdbcprovider/releases/tag/v2.
> 10.1-Beta.1
>
> There are still a few issues, but it is currently useable. If anyone on
> the list has any insight into the problems described in the release notes,
> I'd appreciate a pointer in the right direction. Otherwise, I'll work on
> debugging it after the holidays. I'd appreciate any other feedback as well.
>
> -Dave Emerson
>
>
>
> On 12/24/2014 5:55 PM, David Emerson wrote:
>
>> I'm pretty close to putting out a refactoring of the previous
>> JDBCProvider on github. It'll include all the source and scripts. I got a
>> bit side-tracked by the holidays, but I'll be putting out the whole thing
>> with SQL scripts to initialize several DBs fairly soon. I did start from
>> the newest code base released for that project and worked on getting it to
>> compile and run against the latest JSPWiki codebase. Your more than welcome
>> to use it as you wish. If you had any interest in trying to combine the
>> projects, I'd be fine with that. I'll announce availability on this list
>> and link to it in the JSPWiki doc.
>>
>>
>>
>
Re: JDBCProvider
Posted by "David (spindift)" <de...@spindrift.com>.
An initial beta release of a JDBCProvider is now available on GitHub at
https://github.com/djemerson01/jspwiki-jdbcprovider/releases/tag/v2.10.1-Beta.1
There are still a few issues, but it is currently useable. If anyone on
the list has any insight into the problems described in the release
notes, I'd appreciate a pointer in the right direction. Otherwise, I'll
work on debugging it after the holidays. I'd appreciate any other
feedback as well.
-Dave Emerson
On 12/24/2014 5:55 PM, David Emerson wrote:
> I'm pretty close to putting out a refactoring of the previous
> JDBCProvider on github. It'll include all the source and scripts. I
> got a bit side-tracked by the holidays, but I'll be putting out the
> whole thing with SQL scripts to initialize several DBs fairly soon. I
> did start from the newest code base released for that project and
> worked on getting it to compile and run against the latest JSPWiki
> codebase. Your more than welcome to use it as you wish. If you had any
> interest in trying to combine the projects, I'd be fine with that.
> I'll announce availability on this list and link to it in the JSPWiki
> doc.
>
>
Re: JDBCProvider
Posted by David Emerson <de...@spindrift.com>.
I'm pretty close to putting out a refactoring of the previous JDBCProvider
on github. It'll include all the source and scripts. I got a bit
side-tracked by the holidays, but I'll be putting out the whole thing with
SQL scripts to initialize several DBs fairly soon. I did start from the
newest code base released for that project and worked on getting it to
compile and run against the latest JSPWiki codebase. Your more than welcome
to use it as you wish. If you had any interest in trying to combine the
projects, I'd be fine with that. I'll announce availability on this list
and link to it in the JSPWiki doc.
Re: JDBCProvider
Posted by David Vittor <dv...@gmail.com>.
Hi David Emerson,
Great to hear you are working on a JDBC provider. I'm actually thinking of
doing a similar thing, and think I'm pretty close, although I've only done
it for one database, and need to convert it to hibernate to make it DB
independant.
However I was wondering do you have DB Schema for the old version. I'd like
to make the new DB tables as compatible to the old ones as possible, and
having access to an old DB would be great. Is it possible for you to
provide me the schema for the old JDBC provider? Or even better a sample DB
dump?
Cheers,
David V
On Tue, Dec 2, 2014 at 7:51 PM, Juan Pablo Santos Rodríguez <
juanpablo.santos@gmail.com> wrote:
> Hi David,
>
> first of all, thanks for your efforts bringing back to life the
> jdbcprovider :-) Maybe I'm mistaken, but I recall we dropped from the core
> distribution b/c it wasn't widely used at the time, and having it as a
> separate jar didn't seem much hassle. However, due to package renaming, the
> API changed and the provider stopped working on recent versions. Having it
> as contributed provider again is the first step of merging it into trunk,
> being the second enough people using it.
>
> As for the contribution questions, you can name the package as you prefere;
> it's your contribution so you're free to do as you want. Regarding the
> hosting, perhaps the simpler way is to upload it to a new page on JSPWiki's
> wiki, or you may open a project on github or similar. In any case, please
> do reference it from
> https://jspwiki-wiki.apache.org/Wiki.jsp?page=ContributedProviders
>
> Btw, https://jspwiki-wiki.apache.org/Edit.jsp?page=HowToWriteAPageProvider
> still needs to be written... O:-D
>
>
> br,
> juan pablo
>
>
> On Tue, Dec 2, 2014 at 2:12 AM, David Emerson <de...@spindrift.com>
> wrote:
>
> > I've been using a really old version of JSPWiki and storing pages via the
> > old JDBCProvider. I'd like to update to the latest release, but the page
> > provider isn't compatible at the moment. For fun, I tried to get the
> latest
> > version of the code I could find to compile against the latest JSPWiki
> > code, which I was able to do. I also need to add a new SQL query for a
> new
> > overload of pageExists, but that looks pretty straightforward.
> >
> > If I can get this working it makes sense to contribute it back to the
> > project, but I have a few questions. I moved the code from it's original
> > package to a new package under the existing package for the core
> providers.
> > Would you want it moved out of there back to it's original package
> > structure? I'd like to contribute this, but don't want to commit to
> owning
> > it long term (of course I'm fine with fixing bugs until it seems
> stable). I
> > also don't really want to host it's download. I actually think it makes
> > sense for it to be a core provider, but I'm not sure if there are issues
> > with that since it was originally developed as a contributed provider.
> > Also, if you folks have access to JDBCProvider code more recent than June
> > 2006, I'd re-do my fixes against that instead. Any suggestions on how to
> > proceed?
> >
> >
> >
> >
> >
>
Re: JDBCProvider
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Hi David,
first of all, thanks for your efforts bringing back to life the
jdbcprovider :-) Maybe I'm mistaken, but I recall we dropped from the core
distribution b/c it wasn't widely used at the time, and having it as a
separate jar didn't seem much hassle. However, due to package renaming, the
API changed and the provider stopped working on recent versions. Having it
as contributed provider again is the first step of merging it into trunk,
being the second enough people using it.
As for the contribution questions, you can name the package as you prefere;
it's your contribution so you're free to do as you want. Regarding the
hosting, perhaps the simpler way is to upload it to a new page on JSPWiki's
wiki, or you may open a project on github or similar. In any case, please
do reference it from
https://jspwiki-wiki.apache.org/Wiki.jsp?page=ContributedProviders
Btw, https://jspwiki-wiki.apache.org/Edit.jsp?page=HowToWriteAPageProvider
still needs to be written... O:-D
br,
juan pablo
On Tue, Dec 2, 2014 at 2:12 AM, David Emerson <de...@spindrift.com>
wrote:
> I've been using a really old version of JSPWiki and storing pages via the
> old JDBCProvider. I'd like to update to the latest release, but the page
> provider isn't compatible at the moment. For fun, I tried to get the latest
> version of the code I could find to compile against the latest JSPWiki
> code, which I was able to do. I also need to add a new SQL query for a new
> overload of pageExists, but that looks pretty straightforward.
>
> If I can get this working it makes sense to contribute it back to the
> project, but I have a few questions. I moved the code from it's original
> package to a new package under the existing package for the core providers.
> Would you want it moved out of there back to it's original package
> structure? I'd like to contribute this, but don't want to commit to owning
> it long term (of course I'm fine with fixing bugs until it seems stable). I
> also don't really want to host it's download. I actually think it makes
> sense for it to be a core provider, but I'm not sure if there are issues
> with that since it was originally developed as a contributed provider.
> Also, if you folks have access to JDBCProvider code more recent than June
> 2006, I'd re-do my fixes against that instead. Any suggestions on how to
> proceed?
>
>
>
>
>