JPA Namespace missing

[Former Member]

Hello,

I'm trying to follow "SAP JPA 1.0, EJB 3.0 and WebService -Modeling Your First JPA Entity in CE 7.1" tutorial.

All is running well till I try to generate the DDL file (on my ejb project, I right click and select JPA Tools).

Each time I'm getting the same error : "ERROR: Namespace in FORMINFO is missing (Rule: namespace_suffix)" where FORMINFO is the name of the table to which my JPA entity FormInfo is linked.

I get also the same error in JPA entity class.

I was not able to fin a way to solve this issue. Anyone can help?

Thanks,

[Former Member · Accepted solution]

Hi Xavier,

You have skipped the prefix of the table name - instead of FORMINFO, name your table TMP_FORMINFO or something...

This is a specific requirement of Java Dictionary, which is used in this tutorial.

I hope that helps.

Best,

Yordan

[Former Member · Accepted solution]

Thank you Yordan,

it solves my issue!

Edited by: Xavier Tendron on Oct 16, 2009 3:57 PM

[Former Member · Accepted solution]

I am working with 7.2 ... and it seems that the DDL is not generated (at least it is nowhere I searched )

It initially complained that it was not connected to the dictionnary.

After I restarted the IDE, it did not complained anymore

The only major difference I find between the Tutorial and my project is the file persistence.xml

<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.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_1_0.xsd">

  <persistence-unit name="LocalDevelopment~LocalDevelopment~employee_app~demo.vertomind.com">
    <jta-data-source>EMPLOYEE_DS</jta-data-source>
  </persistence-unit>
<!-- 
Trying to map the name used generated Errors
  <persistence-unit name="EMPLOYEE_PU">
  </persistence-unit>
   -->
</persistence>

\T,

--

I feel like an idiot ...

I created a new Connection employee_conn2 and now DDL generation worked ....

Grrrrrrrrrrrr ...

Edited by: tsmets on Aug 13, 2010 4:15 PM

Edited by: tsmets on Aug 13, 2010 4:18 PM