You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by "Scott Wilson (Created) (JIRA)" <ji...@apache.org> on 2011/11/09 16:29:51 UTC
[jira] [Created] (WOOKIE-288) Allow WAR release artifacts to use an
embedded database
Allow WAR release artifacts to use an embedded database
-------------------------------------------------------
Key: WOOKIE-288
URL: https://issues.apache.org/jira/browse/WOOKIE-288
Project: Wookie
Issue Type: Improvement
Reporter: Scott Wilson
Fix For: 0.9.2
WAR release (and WAR Maven artifacts) should be able to run without needing to configure an external database - e.g. use an embedded db for easy deployment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Commented] (WOOKIE-288) Allow WAR release artifacts to use an embedded database
Posted by Scott Wilson <sc...@gmail.com>.
On 9 Nov 2011, at 15:55, Paul Sharples (Commented) (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/WOOKIE-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147121#comment-13147121 ]
>
> Paul Sharples commented on WOOKIE-288:
> --------------------------------------
>
> I've committed some changes for this, see Revision: 1199782. The WAR Maven artifact should now use the embedded derby DB. I will test it further to make sure its all okay, then put up a snapshot in the repo.
>
> Some things to note...
>
> (1) It creates/checks the user.home folder to see if the DB files exist. I'm not sure if this is a problem or not, but it means under tomcat for example, the DB files are created under tomcat/bin, as that is where the server is booted from. (in fact our ant scripts do the same thing - create the db files in the root of the project where the ant script is run from)
>
> (2) When you download the maven artifact, it will have a different name from its desired web context name.
>
> i.e. in the snapshot repository for in example, it might be called 'wookie-0.9.2-incubating-SNAPSHOT.war'
>
> Once downloaded it would need to be renamed wookie.war, in order to have the correct context name/paths.
It really ought to work no matter what the deployed context name happens to be. I know there are hardcoded /wookie paths in some of the test cases, but the main code *should* work (or its a bug).
>
> On another note, I'm not sure our WAR release build (a la http://people.apache.org/~psharples/wookie/staging-area/0p9p1/rc5/binary/war/) should also use derby. I think this build serves another purpose. I would think that it might be better to leave that one as a Mysql type build - it contains instructions that a user would typically want advice on when installing wookie within a proper server environment (i.e. tomcat & mysql)
>
>> Allow WAR release artifacts to use an embedded database
>> -------------------------------------------------------
>>
>> Key: WOOKIE-288
>> URL: https://issues.apache.org/jira/browse/WOOKIE-288
>> Project: Wookie
>> Issue Type: Improvement
>> Reporter: Scott Wilson
>> Assignee: Paul Sharples
>> Fix For: 0.9.2
>>
>>
>> WAR release (and WAR Maven artifacts) should be able to run without needing to configure an external database - e.g. use an embedded db for easy deployment.
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
[jira] [Commented] (WOOKIE-288) Allow WAR release artifacts to use
an embedded database
Posted by "Paul Sharples (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147121#comment-13147121 ]
Paul Sharples commented on WOOKIE-288:
--------------------------------------
I've committed some changes for this, see Revision: 1199782. The WAR Maven artifact should now use the embedded derby DB. I will test it further to make sure its all okay, then put up a snapshot in the repo.
Some things to note...
(1) It creates/checks the user.home folder to see if the DB files exist. I'm not sure if this is a problem or not, but it means under tomcat for example, the DB files are created under tomcat/bin, as that is where the server is booted from. (in fact our ant scripts do the same thing - create the db files in the root of the project where the ant script is run from)
(2) When you download the maven artifact, it will have a different name from its desired web context name.
i.e. in the snapshot repository for in example, it might be called 'wookie-0.9.2-incubating-SNAPSHOT.war'
Once downloaded it would need to be renamed wookie.war, in order to have the correct context name/paths.
On another note, I'm not sure our WAR release build (a la http://people.apache.org/~psharples/wookie/staging-area/0p9p1/rc5/binary/war/) should also use derby. I think this build serves another purpose. I would think that it might be better to leave that one as a Mysql type build - it contains instructions that a user would typically want advice on when installing wookie within a proper server environment (i.e. tomcat & mysql)
> Allow WAR release artifacts to use an embedded database
> -------------------------------------------------------
>
> Key: WOOKIE-288
> URL: https://issues.apache.org/jira/browse/WOOKIE-288
> Project: Wookie
> Issue Type: Improvement
> Reporter: Scott Wilson
> Assignee: Paul Sharples
> Fix For: 0.9.2
>
>
> WAR release (and WAR Maven artifacts) should be able to run without needing to configure an external database - e.g. use an embedded db for easy deployment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WOOKIE-288) Allow WAR release artifacts to use
an embedded database
Posted by "Paul Sharples (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147142#comment-13147142 ]
Paul Sharples commented on WOOKIE-288:
--------------------------------------
Scott wrote:
It really ought to work no matter what the deployed context name happens to be. I know there are hardcoded /wookie paths in some of the test cases, but the main code *should* work (or its a bug).
Okay, i've just ran it again using its repo name...
http://localhost:8080/wookie-0.9.2-incubating-SNAPSHOT
..and although it ran, there are a few issues. I'll try to resolve them.
> Allow WAR release artifacts to use an embedded database
> -------------------------------------------------------
>
> Key: WOOKIE-288
> URL: https://issues.apache.org/jira/browse/WOOKIE-288
> Project: Wookie
> Issue Type: Improvement
> Reporter: Scott Wilson
> Assignee: Paul Sharples
> Fix For: 0.9.2
>
>
> WAR release (and WAR Maven artifacts) should be able to run without needing to configure an external database - e.g. use an embedded db for easy deployment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WOOKIE-288) Allow WAR release artifacts to use
an embedded database
Posted by "Paul Sharples (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187695#comment-13187695 ]
Paul Sharples commented on WOOKIE-288:
--------------------------------------
Also works using relative paths... (on windows) - relative to $user.dir
-Dwookie.db.uri="jdbc:derby:../mytestfolder/widgetDatabase/widgetDB;create=true"
> Allow WAR release artifacts to use an embedded database
> -------------------------------------------------------
>
> Key: WOOKIE-288
> URL: https://issues.apache.org/jira/browse/WOOKIE-288
> Project: Wookie
> Issue Type: Improvement
> Reporter: Scott Wilson
> Assignee: Paul Sharples
> Fix For: 0.9.2
>
>
> WAR release (and WAR Maven artifacts) should be able to run without needing to configure an external database - e.g. use an embedded db for easy deployment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (WOOKIE-288) Allow WAR release
artifacts to use an embedded database
Posted by "Paul Sharples (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187689#comment-13187689 ]
Paul Sharples edited comment on WOOKIE-288 at 1/17/12 2:03 PM:
---------------------------------------------------------------
I can already add the following as a parameter when running wookie...
-Dwookie.db.uri="jdbc:derby:C:/Users/paul/Desktop/widgetDatabase/widgetDB;create=true"
...which starts derby elsewhere & seems to work ok.
Do you think we also need to add something to the properties file?
was (Author: psharples):
I can already add the following as a parameter when running wookie...
-Dwookie.db.uri="jdbc:derby:C:/Users/paul/Desktop/widgetDatabase/widgetDB;create=true"
...which starts wookie elsewhere & seems to work ok.
Do you think we also need to add something to the properties file?
> Allow WAR release artifacts to use an embedded database
> -------------------------------------------------------
>
> Key: WOOKIE-288
> URL: https://issues.apache.org/jira/browse/WOOKIE-288
> Project: Wookie
> Issue Type: Improvement
> Reporter: Scott Wilson
> Assignee: Paul Sharples
> Fix For: 0.9.2
>
>
> WAR release (and WAR Maven artifacts) should be able to run without needing to configure an external database - e.g. use an embedded db for easy deployment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WOOKIE-288) Allow WAR release artifacts to use
an embedded database
Posted by "Paul Sharples (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187689#comment-13187689 ]
Paul Sharples commented on WOOKIE-288:
--------------------------------------
I can already add the following as a parameter when running wookie...
-Dwookie.db.uri="jdbc:derby:C:/Users/paul/Desktop/widgetDatabase/widgetDB;create=true"
...which starts wookie elsewhere & seems to work ok.
Do you think we also need to add something to the properties file?
> Allow WAR release artifacts to use an embedded database
> -------------------------------------------------------
>
> Key: WOOKIE-288
> URL: https://issues.apache.org/jira/browse/WOOKIE-288
> Project: Wookie
> Issue Type: Improvement
> Reporter: Scott Wilson
> Assignee: Paul Sharples
> Fix For: 0.9.2
>
>
> WAR release (and WAR Maven artifacts) should be able to run without needing to configure an external database - e.g. use an embedded db for easy deployment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira