Excellent summary of the issues as well as the overall goal of the service itself.
One thing I would assume is that the underlying Repository could be a variety of implemenations (RDMBS, LDAP, Serialized Java etc) and that we will provide drivers or adapters that would allow different deployment types depending upon the client. Obviously a longer term target, but I think it's important from the repository metadata standpoint to not get 'locked' in to an particular implementation right off the bat.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992180#3992180
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992180
It got deployed. Thanks Tom.
If anyone interested, this is what done to resolve the issue.
the hibernate should be configured to identify the ehcache class and the ehcache.xml file.
this can be done either in the .properties file or in the .cfg.xml file and this file should be in the classpath.
hibernate.properties file contains
hibernate.cache.provider_class=net.sf.ehcache.hibernate.EhCacheProvider
net.sf.ehcache.configurationResourceName=/ehcache.xml
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992161#3992161
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992161