Another thing I noticed:

When I configure the persistence properties to be innodb mysql.
The quartz tables do not get written in the target DB even when they are present in the init sql
file:

[nik@anvil org.apache.syncope]$ grep -c QRTZ ./core/target/syncope/WEB-INF/classes/quartz/tables_mysql_innodb.sql
47
[nik@anvil org.apache.syncope]$

I guess the TYPE=InnoDB in the sql file has no effect, but the syntax should be ENGINE=InnoDB

mysql> use syncope;
Database changed
mysql> show tables;
+------------------------------+
| Tables_in_syncope            |
+------------------------------+
| ACT_GE_BYTEARRAY             |
| ACT_GE_PROPERTY              |
| ACT_HI_ACTINST               |
| ACT_HI_ATTACHMENT            |
| ACT_HI_COMMENT               |
| ACT_HI_DETAIL                |
| ACT_HI_PROCINST              |
| ACT_HI_TASKINST              |
| ACT_HI_VARINST               |
| ACT_ID_GROUP                 |
| ACT_ID_INFO                  |
| ACT_ID_MEMBERSHIP            |
| ACT_ID_USER                  |
| ACT_RE_DEPLOYMENT            |
| ACT_RE_MODEL                 |
| ACT_RE_PROCDEF               |
| ACT_RU_EVENT_SUBSCR          |
| ACT_RU_EXECUTION             |
| ACT_RU_IDENTITYLINK          |
| ACT_RU_JOB                   |
| ACT_RU_TASK                  |
| ACT_RU_VARIABLE              |
| ConnInstance                 |
| ConnInstance_capabilities    |
| Entitlement                  |
| ExternalResource             |
| MAttr                        |
| MAttrUniqueValue             |
| MAttrValue                   |
| MDerAttr                     |
| MDerSchema                   |
| MSchema                      |
| MVirAttr                     |
| MVirSchema                   |
| Membership                   |
| Notification                 |
| NotificationTask_recipients  |
| Notification_events          |
| OPENJPA_SEQUENCES_TABLE      |
| OPENJPA_SEQUENCE_TABLE       |
| Policy                       |
| RAttr                        |
| RAttrUniqueValue             |
| RAttrValue                   |
| RDerAttr                     |
| RDerSchema                   |
| RMapping                     |
| RMappingItem                 |
| RSchema                      |
| RVirAttr                     |
| RVirSchema                   |
| Report                       |
| ReportExec                   |
| ReportletConfInstance        |
| SyncopeConf                  |
| SyncopeLogger                |
| SyncopeRole                  |
| SyncopeRole_Entitlement      |
| SyncopeRole_ExternalResource |
| SyncopeUser                  |
| SyncopeUser_ExternalResource |
| SyncopeUser_passwordHistory  |
| Task                         |
| TaskExec                     |
| UAttr                        |
| UAttrUniqueValue             |
| UAttrValue                   |
| UDerAttr                     |
| UDerSchema                   |
| UMapping                     |
| UMappingItem                 |
| USchema                      |
| UVirAttr                     |
| UVirSchema                   |
| UserRequest                  |
| logging_event                |
| logging_event_exception      |
| logging_event_property       |
| role_search                  |
| role_search_attr             |
| role_search_entitlements     |
| role_search_resource         |
| user_search                  |
| user_search_attr             |
| user_search_membership       |
| user_search_resource         |
+------------------------------+
86 rows in set (0.00 sec)


On 28/05/2013 15:38, Nik wrote:
[...]
When I deploy and access the console

glassfish (GlassFish Server Open Source Edition 3.1.2 (build 23))throws : 2013-05-27 16:05:04.073+0000 (68) StandardWrapperValve[default]: PWC1406: Servlet.service() for servlet default threw exception java.lang.IllegalArgumentException: PWC2788: setAttribute: Non-serializable attribute with name restTemplate

This was recently fixed: I guess that by manually downloading you probably did not get latest ones.

It's still there unfortunately after I remake from scratch and deploy on glassfish.
BTW: this doesn't happen when I deploy and launch the same warson tomcat.

Thanks for reporting: this worths further Glassfish-specific analysis. Besides this exception, is the admin console working fine or not?

Regards.
--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/

Reply via email to