geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher James Blythe (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (DAYTRADER-24) Clean up plan files in 1.2 branch
Date Tue, 14 Nov 2006 17:15:37 GMT
     [ http://issues.apache.org/jira/browse/DAYTRADER-24?page=all ]

Christopher James Blythe updated DAYTRADER-24:
----------------------------------------------

    Attachment: daytrader-24.patch

I removed the existing files from the plans directory, moved over the jetty and tomcat plans
from the 1.1 branch, and made the following modificatoins:

- Updated the password field to "passwd" in the AccountProfileEJB definition
- Removed the dependency on the pre-built derby database
- Set the create db flag on the Derby data source to true
- Increased the data source max pool size to 30
- Removed the GBean to copy the pre-built derby database

If any of these changes are not warrented, let me know...

The associated patch file is attached. 

As a side note, I applied the patch to another workig copy of the repository and noticed that
the patch program did not remove the old files. Instead, it merely made them 0 byte files.
Is that expected?

Chris

> Clean up plan files in 1.2 branch
> ---------------------------------
>
>                 Key: DAYTRADER-24
>                 URL: http://issues.apache.org/jira/browse/DAYTRADER-24
>             Project: DayTrader
>          Issue Type: Bug
>    Affects Versions: 1.2
>            Reporter: Christopher James Blythe
>            Priority: Minor
>         Attachments: daytrader-24.patch
>
>
> The plan files in the 1.2 branch are are based on Geronimo 1.0 and need to be updated
(similar to what is in the Daytrader 1.1 branch). It would also be nice if we could add plan
files for Oracle and DB2 data sources. However, it looks like we do not include the necessary
Tranql rars in Geronimo to support this out of the box.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message