[ 
https://issues.apache.org/jira/browse/SYNCOPE-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13670296#comment-13670296
 ] 

Francesco Chicchiriccò commented on SYNCOPE-376:
------------------------------------------------

The exception occurs because Spring's RestTemplate is not Serializable and 
Glassifsh 3.1.2 implements the Servlet specification 3.0, that strictly forbids 
non-serializable session attributes: this means that such problems might happen 
on future versions of other JEE containers as well, including Tomcat.

At the moment there is no better solution that replacing

  <bean id="restTemplate" class="org.springframework.web.client.RestTemplate" 
scope="session">

with

  <bean id="restTemplate" class="org.springframework.web.client.RestTemplate" 
scope="prototype">

in [1] (as it used to be in 1_0_X [2] BTW).

[1] 
https://svn.apache.org/repos/asf/syncope/branches/1_1_X/console/src/main/resources/applicationContext.xml
[2] 
https://svn.apache.org/repos/asf/syncope/branches/1_0_X/console/src/main/resources/applicationContext.xml
                
> Console webapp does not start on Glassfish
> ------------------------------------------
>
>                 Key: SYNCOPE-376
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-376
>             Project: Syncope
>          Issue Type: Bug
>          Components: console
>    Affects Versions: 1.1.1
>         Environment: Glassfish 3.1.2
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>             Fix For: 1.1.2, 1.2.0
>
>
> As reported in [1], the admin console webapp does not start on Glassfish, 
> with exception:
> java.lang.IllegalArgumentException: PWC2788: setAttribute: Non-serializable 
> attribute with name restTemplate
> [1] 
> http://syncope-user.1051894.n5.nabble.com/help-needed-please-to-build-1-1-2-SNAPSHOT-or-1-2-0-SNAPSHOT-project-tp5707061p5707079.html

--
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

Reply via email to