No, the default is a JSON service registry + InMemory ticket registry. There 
are no JPA transactions involved. 

- Misagh

> On Dec 2, 2015, at 11:28 AM, [email protected] wrote:
> 
> I did not use overlay approach.   I checked out 4.1.x the code and built it.  
> I guess that by default Service Registry is JSON based and Ticket registry is 
>  JPA based.  So I am not sure why there is multiple transaction manager.
> 
> I do not think it is a code issue because if I switch to use 
> DefaultTicketRegistry and everything works fine.
> 
> I will try the overlay approach now and will report back what happened. 
> 
> thanks
> 
> Frank
> 
> 
> 
> On Wednesday, December 2, 2015 at 1:12:39 PM UTC-5, Misagh Moayyed wrote:
> I ran a quick test, with both JPA service registry and JPA ticket registry 
> defined in an overlay using the same transaction manager. No issues. 
> 
> Post your overlay somewhere on github or pastebin and we might be able to 
> spot something. Otherwise so far, it’s more likely a config issue on your 
> end. 
> 
> - Misagh
> 
>> On Dec 1, 2015, at 10:15 PM, Tai Hu <[email protected] <javascript:>> wrote:
>> 
>> Do you find the solution for this "No transactional EntityManager available" 
>> issue? I just ran into the exact same problem. For both PostgreSQL and 
>> MySQL, merge method is never under a transaction. Thanks.
>> 
>> On Monday, November 30, 2015 at 7:48:05 AM UTC-5, robertoschwald wrote:
>> Hi all, 
>> 
>> while configuring CAS 4.1.2 with JpaTicketRegistry, I cannot get it to work. 
>> I always receive the following Exception: 
>> Exception thrown executing 
>> org.jasig.cas.web.flow.GenerateServiceTicketAction@6e6a43a4 in state 
>> 'generateServiceTicket' of flow 'login' 
>> javax.persistence.TransactionRequiredException: No transactional 
>> EntityManager available 
>>         at 
>> org.springframework.orm.jpa.SharedEntityManagerCreator$SharedEntityManagerInvocationHandler.invoke(SharedEntityManagerCreator.java:275)
>>  
>>         at com.sun.proxy.$Proxy49.merge(Unknown Source) 
>>         at 
>> org.jasig.cas.ticket.registry.JpaTicketRegistry.updateTicket(JpaTicketRegistry.java:57)
>>  
>> 
>> 
>> I used the described config in 
>> http://jasig.github.io/cas/4.1.x/installation/JPA-Ticket-Registry.html 
>> <http://jasig.github.io/cas/4.1.x/installation/JPA-Ticket-Registry.html> and 
>> also added some pointcuts described in 
>> 
>> http://stackoverflow.com/a/33663812 <http://stackoverflow.com/a/33663812> 
>> 
>> But it still fails. 
>> 
>> My JPA config is in spring-configuration/ticketRegistry.xml. 
>> 
>> Anything else I’m missing? 
>> 
>> 
>> Robert 
>> 
>> 
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "CAS Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> Visit this group at http://groups.google.com/a/apereo.org/group/cas-user/ 
>> <http://groups.google.com/a/apereo.org/group/cas-user/>.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "CAS Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> Visit this group at http://groups.google.com/a/apereo.org/group/cas-user/ 
> <http://groups.google.com/a/apereo.org/group/cas-user/>.

-- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
Visit this group at http://groups.google.com/a/apereo.org/group/cas-user/.

Reply via email to