You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2012/09/21 09:11:09 UTC

[jira] [Updated] (SYNCOPE-209) DB Table connector does not see changes in underlying table until restart

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

Francesco Chicchiriccò updated SYNCOPE-209:
-------------------------------------------

    Fix Version/s:     (was: 1.0.2-incubating)
       Issue Type: Improvement  (was: Bug)

Given the findings reported in above comments, this sounds much like an improvement.
Changing fix version accordingly.
                
> DB Table connector does not see changes in underlying table until restart
> -------------------------------------------------------------------------
>
>                 Key: SYNCOPE-209
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-209
>             Project: Syncope
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.0.1-incubating
>            Reporter: Francesco Chicchiriccò
>            Assignee: fabio martelli
>             Fix For: 1.1.0-incubating
>
>
> Steps to reproduce:
> 1. generate a project from 1.0.2-incubating-SNAPSHOT or 1.1.0-incubating-SNAPSHOT archetypes (both tested)
> 2. mvn clean package
> 3. cd console && mvn -P embedded
> 1. log in http://localhost:9080/syncope-console/
> 2, go to resources -> resource-testdb -> mapping
> 1. go to http://localhost:9082
> 2. select "Generic H2 (Server)"
> 3. set JDBC URL to "jdbc:h2:tcp://localhost:9092/testdb"
> 4. set username 'sa' and password 'sa'
> 5. connect
> 6. send SQL statement 'ALTER TABLE TEST ADD COLUMN newcol VARCHAR(255)'
> 1. log in http://localhost:9080/syncope-console/
> 2, go to resources -> resource-testdb -> mapping
> At this point, when trying to add a new schema mapping, 'newcol' is not shown among available values until restart

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira