If you're willing to forgo the use of the Web based Services Management GUI you could configure your services directly in deployConfigContext.xml and thus eliminate the need for JPA.
If you running a multi-node setup you'll have to make sure you configure each node the same. Best, Bill On Wed, Jan 18, 2012 at 1:12 PM, Marvin Addison <[email protected]> wrote: >> So please let us know with the current serviceRegistryDao any configuration >> change can be done to avoid this issue while restarting. Or any other method >> is there. Please have a help. > > There's no alternative other than using a durable store. JPA is > probably your best bet. I'd recommend working through the errors. > > M > > -- > You are currently subscribed to [email protected] as: [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
