You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "fabio martelli (JIRA)" <ji...@apache.org> on 2012/09/19 16:10:07 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13458705#comment-13458705 ]
fabio martelli commented on SYNCOPE-209:
----------------------------------------
Schema is cached by the connector. This cache could be updated just reloading the connector bean.
I'd suggest to add a "reload action" to each resource, listed by the console, in order to reload the connector bean if required.
> 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: Bug
> Components: core
> Affects Versions: 1.0.1-incubating
> Reporter: Francesco Chicchiriccò
> Assignee: fabio martelli
> Fix For: 1.0.2-incubating, 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