EJB & JPA Unexpected Results

[Glen Divers]

Hi

I have two entities, Client and Telephone

 @Entity
public class Client implements Serializable {
    
    private static final long serialVersionUID = 1L;
    
    @OneToMany(mappedBy = "client", fetch = FetchType.LAZY,
       cascade = {CascadeType.ALL })
    private List<Telephone> telephones;
   
    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private int id;
   

 @Entity
public class Telephone implements Serializable {

    private static final long serialVersionUID = 1L;
    @Id
    private Long number;

    @ManyToOne
    private Client client;
   

and I'm using the Netbeans generated AbstractFacade handle the persistence. My persistence code is;

 
    @EJB
    private ClientFacade clientDao;   

.......

          telephone.setClient(client);
           client.getTelephones().add(telephone);
           clientDao.create(client);

If I create a new client with a unique telephone number everything works. However, if I create a new client and reuse an existing persisted
telephone number, I get an exception because the phone number already exists in the database as expected, but the new client is still created in the database. I was expecting a rollback and neither client nor telephone to be persisted.

What am I missing/have I done wrong?

Regards

[James Sutherland]

Check your transaction options. It seems you are using a SessionBean, so need to being using a JTA DataSource, but probably are not.

Include your persistence.xml.

[Glen Divers]

Thanks for your response, persistance.xml is specifying JTA

 <?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
  <persistence-unit name="PembridgePU" transaction-type="JTA">
    <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
    <jta-data-source>jdbc/pembridge</jta-data-source>
    <properties>
      <property name="eclipselink.ddl-generation" value="drop-and-create-tables"/>
    </properties>
  </persistence-unit>
</persistence>   

[James Sutherland]

Ensure that you have defined "jdbc/pembridge" as a JTA enabled DataSource in Glassfish.

[Glen Divers]

James Sutherland wrote:Ensure that you have defined "jdbc/pembridge" as a JTA enabled DataSource in Glassfish.

jdbc/pembridge is defined in terms of a connection pool. There doesn't appear to be any other options. The connection pool is defined as a resource type javax.sql.ConnectionPoolDataSource with a datasource classname of com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource.

Glassfish offers alternative resource types of javax.sql.Driver, javax.sql.DataSource and javax.sql.XADataSource. I can't find anything that indicates/mentions JTA.

One odd thing however, Glassfish seems to be creating it's own connection & pool definition. It's created its own connection "pembridge" connnected to pool "mysql_Pembridge_RootPool" which is defined with a resource type of javax.sql.DataSource with a datasource class name of com.mysql.jdbc.jdbc2.optional.MysqlDataSource. If I delete these, they appear to be re-created when I deploy my application, although it never uses this (there's no database userid or password defined for it)

Regards

[James Sutherland]

I believe the JTA DataSource is the javax.sql.XADataSource one.