如果有人更新到5.1，这是它是如何工作的

StandardServiceRegistry registry = new StandardServiceRegistryBuilder().configure().build();
                MetadataSources sources = new MetadataSources(registry);
                Metadata metadata = sources.getMetadataBuilder().build();
                sessionFactory = metadata.getSessionFactoryBuilder().build();

而不是hibernate 4.3中的下面

 ServiceRegistry serviceRegistry = new ServiceRegistryBuilder().applySettings(
            configuration.getProperties()). buildServiceRegistry();
    sessionFactory = configuration.buildSessionFactory(serviceRegistry);

在hibernate 5.3.1中，你可以这样做:

ServiceRegistry standardRegistry = 
                new StandardServiceRegistryBuilder().configure().build();

Metadata sources = new MetadataSources(standardRegistry).addAnnotatedClass(MyEntity.class).getMetadataBuilder().build();

SessionFactory sf = sources.buildSessionFactory();

代码已验证可在Hibernate 4.3.0中工作。注意，您可以删除XML文件名参数，或者提供您自己的路径。这与这里的其他帖子类似(但错别字更正了)，但这一篇是正确的。

import org.hibernate.SessionFactory;
import org.hibernate.boot.registry.StandardServiceRegistryBuilder;
import org.hibernate.cfg.Configuration;
import org.hibernate.service.ServiceRegistry;    


Configuration configuration = new Configuration();
configuration.configure("/com/rtw/test/hiber/hibernate.cfg.xml");
ServiceRegistry  serviceRegistry = new StandardServiceRegistryBuilder().applySettings(configuration.getProperties()).build();        
    sessionFactory = configuration.buildSessionFactory(serviceRegistry);

在Hibernate 4.2.2中

import org.hibernate.Session;
import org.hibernate.SessionFactory;
import org.hibernate.Transaction;
import org.hibernate.cfg.Configuration;
import org.hibernate.service.ServiceRegistry;
import org.hibernate.service.ServiceRegistryBuilder;

public class Test {
    public static void main(String[] args) throws Exception
{
    Configuration configuration = new Configuration()
            .configure();

    ServiceRegistry serviceRegistry = new ServiceRegistryBuilder().applySettings(
            configuration.getProperties()).buildServiceRegistry();

    SessionFactory sessionFactory = configuration.buildSessionFactory(serviceRegistry);

    Session session = sessionFactory.openSession();

    Transaction transaction = session.beginTransaction();

    Users users = new Users();

    ... ...

    session.save(users);

    transaction.commit();

    session.close();

    sessionFactory.close();

    }
}

道理很简单:JBoss文档并不是100%维护得很好。按照JavaDoc的说法:buildSessionFactory(ServiceRegistry ServiceRegistry)。

在不同版本的文档之间发现差异并不罕见。大多数开发人员认为文档是一件苦差事，他们倾向于推迟它。

根据经验，如果javadoc说了一件事，而一些非javadoc的文档与之相矛盾，那么javadoc很可能更准确。程序员更倾向于让javadoc与代码的变化保持同步…因为javadoc的“源代码”与代码在同一个文件中。

在@deprecated标记的情况下，javadoc几乎肯定更准确。开发人员经过仔细考虑后反对使用……而且(一般来说)他们不会对它们进行undeprecated。