[
https://issues.apache.org/jira/browse/SYNCOPE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582441#comment-13582441
]
Hudson commented on SYNCOPE-209:
--------------------------------
Integrated in Syncope-trunk #103 (See
[https://builds.apache.org/job/Syncope-trunk/103/])
[SYNCOPE-319][SYNCOPE-209] Turning PUT into POST for
ConnectorService#reload, as per Jan suggestion (Revision 1448310)
Result = FAILURE
ilgrosso :
Files :
*
/syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/ConnectorServiceProxy.java
*
/syncope/trunk/common/src/main/java/org/apache/syncope/common/services/ConnectorService.java
*
/syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/ConnInstanceController.java
> 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: Francesco Chicchiriccò
> Fix For: 1.1.0
>
>
> 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
