You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@roller.apache.org by "David Johnson (JIRA)" <ji...@apache.org> on 2010/07/19 05:05:50 UTC

[jira] Resolved: (ROL-1188) "rollerdb" is hardcoded in src/org/apache/roller/ui/core/RollerContext.java

     [ https://issues.apache.org/jira/browse/ROL-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Johnson resolved ROL-1188.
--------------------------------

    Resolution: Fixed

Fixed long ago. The JNDI datasource name can now be set in roller-custom.properties and defaults to jdbc/rollerdb

> "rollerdb" is hardcoded in src/org/apache/roller/ui/core/RollerContext.java
> ---------------------------------------------------------------------------
>
>                 Key: ROL-1188
>                 URL: https://issues.apache.org/jira/browse/ROL-1188
>             Project: Roller
>          Issue Type: Bug
>          Components: Database Access & Data Model
>    Affects Versions: 2.3
>            Reporter: Henri Yandell
>            Assignee: Roller Unassigned
>
> The automatic check to see if the database needs upgrading in RollerContext is hardcoded to look at "java:comp/env/jdbc/rollerdb". This causes errors if you have changed the name of the resources.
> There are two reasons to change the name of the resource. The first is to run two Rollers within one container. This is very worrying as it means the 2nd Roller install is checking whether it needs to upgrade the other Roller install's database. The second is that (I think) there are containers who don't support the "java:comp/env..." part; at least JIRA lets you modify that when installing so I presume that's true.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.