Manual Testing for 3.0 M5 Release
Bug No. |
Description |
Test Steps |
Test Step Results
|
256003
|
Validation needed for converter name
|
...
|
...
|
326717
|
Containment mappings for generic JAXB to support validation
|
...
|
...
|
327918
|
Generic schema/namespace support for JAXB 2.2
|
...
|
...
|
330355
|
Schema gen doesn't work on default package
|
...
|
...
|
331369
|
If only one package is used in schema gen, schema name is not used
|
...
|
...
|
331558
|
Need validation for converter class
|
...
|
...
|
331610
|
Need validation for queries
|
...
|
...
|
332673
|
Need validation when entities have same name but no name attribute explicitly specified
|
Create JPA Project, connected to Oracle DB, Create JPA Entity named Address in package1, Add one field (Address_Id)that can be used for the primary key and check the Key checkbox.
|
JPA Project is created and contains a JPA Entity within package1, which appears in the persistence.xml, with error about no primary key
|
...
|
...
|
Create another JPA Entity named Addess, but in package2, Add one field (Address_Id)for the primary key and check the key checkbox.
|
JPA Entity is created successfully, however two errors appear stating - Duplicate entity "Address" found in this persistent unit. Each entity must have a unique name within a persistent unit.
|
...
|
...
|
Select New>JPA ORM Mapping File. Then add both of the Address entity's to the orm mapping file.
|
Verify two Infos appears stating - Class "package2.Address" is already specified in mapping file orm.xml
|
...
|
...
|
Change the Address entity in package to a mapped superclass and save the project
|
Verify the errors still remain no matter what type it is mapped as.
|
333754
|
Wrong message text for entity name (for it's fully qualified class name)
|
...
|
...
|