Bug 824380

Summary: JPA errors in orm.xml file in Petclinic example when importing JBDS 5 Beta3
Product: [Retired] JBoss Enterprise WFK Platform 2 Reporter: Tomas Repel <trepel>
Component: ExamplesAssignee: Marius Bogoevici <mariusb>
Status: CLOSED DUPLICATE QA Contact: Karel Piwko <kpiwko>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0.0.ER5CC: bsutter, mnovotny, myarboro, rruss
Target Milestone: ER1   
Target Release: 2.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: petclinic
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-11 08:42:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tomas Repel 2012-05-23 11:27:12 UTC
Description of problem:

Following error is shown in JBDS 5 Beta3:

Attribute "visits" in class "Pet" cannot be resolved
/petclinic/src/main/resources/META-INF/orm.xml
line 91
JPA Problem

The line from orm.xml file that causes the error:

<transient name="visits"/>

Version-Release number of selected component (if applicable):

WFK2 ER5
JBDS 5 Beta3

How reproducible:

Always.

Steps to Reproduce:
1. import petclinic example into JBDS
  
Actual results:

Five errors occur, one error is described above, another four similar errors 
occur too.

Expected results:

No error occurs.

Comment 1 Marius Bogoevici 2012-06-08 03:04:05 UTC
This looks like a spurious error to me. The deployment succeeds, which proves 
that the mapping is correct.

Comment 2 Karel Piwko 2012-09-24 14:29:43 UTC
This should be reverified with JBDS 5.0.1.GA.

Comment 3 Marek Novotny 2012-09-25 07:33:09 UTC
Marking as fixed in ER1 for verification with JBDS 5.0.1.GA

Comment 4 Tomas Repel 2012-10-01 15:26:35 UTC
These errors appear in JBDS 5.0.1.GA too.

Comment 6 Marek Novotny 2012-10-11 08:42:15 UTC
This issue is duplication of https://bugzilla.redhat.com/show_bug.cgi?id=801406

*** This bug has been marked as a duplicate of bug 801406 ***