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/10 18:50:08 UTC
[jira] [Created] (SYNCOPE-209) DB Table connector does not see
changes in underlying table until restart
Francesco Chicchiriccò created SYNCOPE-209:
----------------------------------------------
Summary: 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ò
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
[jira] [Commented] (SYNCOPE-209) DB Table connector does not see
changes in underlying table until restart
Posted by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNCOPE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458708#comment-13458708 ]
Francesco Chicchiriccò commented on SYNCOPE-209:
------------------------------------------------
+1
It seems like a more general solution (affecting any connector, not just DB).
> 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
[jira] [Commented] (SYNCOPE-209) DB Table connector does not see
changes in underlying table until restart
Posted by "fabio martelli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNCOPE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458788#comment-13458788 ]
fabio martelli commented on SYNCOPE-209:
----------------------------------------
It seems that we cannot perform a reload of the connector instance simply reloading the ConnectorFacadeProxy: ConnId framework keep instantiated connectors into a connection pool and doesn't provide a way to retrieve a specific connector.
Maybe, the last possibility to solve this issue is to have a feature to dispose and reload all the connectors pooled by the framework: the core can expose the rest method to dispose and reload all the connectors; the console could provide a button onto the resource management page to invoke this method.
What do you think?
> 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
[jira] [Updated] (SYNCOPE-209) DB Table connector does not see
changes in underlying table until restart
Posted by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (SYNCOPE-209) DB Table connector does not see
changes in underlying table until restart
Posted by "fabio martelli (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (SYNCOPE-209) DB Table connector does not see
changes in underlying table until restart
Posted by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNCOPE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458791#comment-13458791 ]
Francesco Chicchiriccò commented on SYNCOPE-209:
------------------------------------------------
If you provide a confirmation window with an enormous warning, yes :-)
I say so because disposing and reallocating all connector instances is potentially a very costing operation; anyway I agree that this could be very useful, especially when developing.
So, fine for me.
> 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
[jira] [Assigned] (SYNCOPE-209) DB Table connector does not see
changes in underlying table until restart
Posted by "fabio martelli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNCOPE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
fabio martelli reassigned SYNCOPE-209:
--------------------------------------
Assignee: fabio martelli
> 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