Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Dali 3.0.1

Revision as of 11:55, 20 September 2011 by Jolene.moffitt.oracle.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Dali 3.0

Dali 3.0.1 Manual Testing

Manual Testing for 3.0.1 Release
Bug No. Description Test Steps Test Step Results
316022 NPE refreshing out of sync entity Create JPA Project, Create Entity for the project Project and Entity are created successfully
... ... Close the project and open the entity (ex. employee.java) in a text editor outside of eclipse and change something (ex. @Column(name="MANAGER_ID") to @Column(name="MANAGERID") ) Save the file File is updated and saved
... ... Go back to Eclipse and open the project, open the edited entity by using the Project Explorer>JPA Content tree and double clicking the entity Verify no errors appear in log and message states you need to refresh
... ... Hit F5 to refresh
338413 NPE moving orm.xml to a subfolder in META-INF Create a new JPA 2.0, Generic 2.0 project Project is created successfully
... ... R-Click on project and Add JPA orm.xml mapping file JPA orm.xml mapping file is added successfully in the META-INF

folder.

... ... Create a new subfolder in META-INF Subfolder is created successfully
... ... Drag the orm.xml file to the subfolder (move) Verify orm.xml is moved into the subfolder without error
... ... Move orm.xml out of subfolder and back into META-INF folder orm.xml is moved back successfully without error
... ... R-Click on orm.xml and select Move Move Resources dialog appears
... ... Select the subfolder and click on OK button Verify orm.xml is moved into subfolder without error
338948 Cancel rename of an attribute and the diagram still gets edited Create JPA 1.0, Generic 1.0 project JPA Project is created successfully
... ... Create a JPA entity with 2 or 3 attributes and make sure there is at least one validation error (ex. use an incorrect column name for an attribute) Entity is created and some validation errors appear
... ... R-Click on the project, Select JPA Tools > Open Diagram... Diagram editor is opened
... ... R-Click in the Diagram editor and select Show all Entities Verify the Entity appears in diagram and the attribute shows an error
... ... Click on the attribute name (that has the error) twice and rename the attribute and hit the enter button on the keyboard Rename Method dialog appears
... ... Click on the Cancel button Verify the dialog closes and the name is not updated
339418 Incorrectly enabled converter widgets in virtual orm.xml attribute Create JPA 2.0, EL 2.1.x project, Create an Entity with 2 or 3 attributes Project and Entity are created successfully
... ... For an attribute withing the entity in the JPA Details select Converted radio button and select serialized from the converter name drop down Verify editor is updated with @Convert("serialized") for the attribute
... ... Add an eclipselink-orm.xml mapping file to the project eclispelink-orm.xml mapping file is added successfully
... ... Add the Entity to the el-orm.xml mapping file and select the attribute you added the converter too Verify the Converted radio button is selected but grayed out and the Converter name drop down shows serialized but is also grayed out.
342624 ASTTools.findTypeInHierarchy() does not handle parameterized type reference Create JPA 2.0, EclipseLink 2.2.x project, Create JPA Entity and make sure it is added to the persistence.xml Project and entity are created successfully and the entity appears in persistence.xml
... ... Create a New Interface with the following - import org.eclipse.persistence.config.DescriptorCustomizer;
  public interface MyInterface<T> extends DescriptorCustomizer {
  }
The Interface is added successfully
... ... Create a new class that implements the interface:
  import org.eclipse.persistence.descriptors.ClassDescriptor;
  public class MyClass implements MyInterface<Object> {
     public void customize(ClassDescriptor descriptor) throws Exception {
     }
  }
Verify the Class is added successfully
... ... Select the Entity in the JPA Structure Pane, Expand the Advanced section in the JPA Details pane, Click on the Browse button for Customizer Class Class Selection dialog appears
... ... Select the New class you added previously and click on the OK button, Save the Project. Verify the project is saved successfully and no errors appear
344645 IllegalStateException when clicking Daily expiry radio button more than once Create a JPA 2.0 EclipseLink 2.2.x Project, create 2 or 3 entities from tables JPA project and entities are created successfully
... ... Select an entity in JPA Structure Pane and in JPA Details Pane expand caching section Caching information appears
... ... Expand Advanced section and click on Daily Expiry radio button twice Verify no errors appear and the radio button is selected
345031 ClassCastException: SourceField/SourceMethod cannot be cast to JavaResourceAbstractType Create JAXB Project JAXB Project is created successfully
... ... R-Click on JAXB Project and select New > Class New Java Class dialog appears
... ... Enter a package name (ex. model) and Name (ex. Foo)and click on Finish Class is created successfully without error
... ... Add the following to the class and Save
       private Integer Address_ID; 
 	 private String City;

public Integer getAddress_ID() {

		return this.Address_ID;

}

public String getCity() {

		return this.City;

}

Class is updated and no errors appear
... ... Add the following to the Class before public class Foo
  import javax.xml.bind.annotation.XmlType;
  @XmlType
Verify no errors appear in problems pane or Error Log
... ... Enter @XmlType prior the the first field and Save Verify no errors appear in error log but 2 errors appear in Problems pane
... ... Remove @XmlType from before the first field to be in the middle of the two fields and Save Verify the errors in the problems pane remain the same and no errros appear in Error log
345293 Add JPA entity - Create new mapping file (orm.xml) cannot continue Create New > JPA Project using all default values JPA Project is created successfully
... ... Select New > JPA Entity, Enter package, Enter Name, Check the Add to entity mappings in XML checkbox and Click on Browse button Mapping File dialog appears
... ... Click on the New button New Mapping File dialog appears
... ... Leave the default location and file name (orm.xml), Click on Finish Verify orm.xml appears for Choose mapping file
... ... Click on OK button Verify META-INF/orm.xml appears in the mapping file text field, Verify the Next button is enabled.
... ... Remove the text from the mapping file field Verify Next button is disabled, Verify message states The mapping file does not exist.
... ... Add META-INF/orm.xml back into the mapping file text field Verify Next button is enabled.
... ... Click on Next button, Add 2 or 3 fields to the Entity and click on Finish Verify JPA Entity is created successfully without error
346997 Customizing of generated entities with interfaces and superclasses does not work Create JPA project (with connection to DB), create Interface and Class (using defaults) Project, Interface and Class are all created successfully
... ... R-click on project select JPA Tools > Generate Entities from Tables... Generate Custom Entities dialog appears
... ... Select two tables and click on the Next button 3 times The last page of the Wizard appears Customize Individual Entities
... ... Select an Entity and click on the Add button for the Interface and select the Interface you created and Click on OK Verify the Interface appears in the list
... ... Click on the other Entity Verify no Interface appears for this Entity
... ... Click back and forth on the two entities Verify the Interface always appears for the Entity it was assigned to and none appears for the other Entity
... ... Select the Entity that does not contain the Interface and click on the Browse button Superclass Selection dialog appears
... ... Select the Class you created and click on the OK button Verify the selected class appears in the Superclass field
... ... Click back and forth on the two entities Verify the Interface always appears for the Entity it was assigned and no Superclass appears for that one and then a Superclass appears for the other but no Interface
... ... Select the entity with the Interface and remove the interface Verify the Interface is removed
... ... Click back and forth on the two entities Verify the Superclass still appears for the entity it was assigned and no Interface appears for the Entity that it was removed from.
... ... Select the entity with the Superclas and remove the superclass Verify the Superclass is removed
... ... Click back and forth on the two entities Verify no superclass or interface appears for either entity
347219 NullPointerException: Change a mapping to element collection mapping Create JPA Project, create Entities from tables, Create orm mapping file Project, entities and mapping file are created successfully
... ... R-click on the mapping file in the JPA Structure tab and select Add Class Add Class dialog appears
... ... Select an entity that you created (ex. Employee) and click on OK Class appears in the orm mapping file
... ... R-click on an attribute in the JPA Structure tab, select Add Attribute to XML and Map... Add Attribute dialog appears
... ... Click on ok button Attribute is added to xml and mapping file
... ... R-Click on the added attribute and select Map As > Element Collection Verify xml and mapping is updated without any errors
347814 NullPointerException: Change a mapping to many-to-one or one-to-one mapping Create JPA project, create Entities from tables, create orm mapping file Project, entities and mapping file are created successfully
... ... Add Class (ex. Employee) to the mapping file via the JPA Structure Pane Class is added successfully
... ... In the JPA structure pane, right-click an attribute and add it to the XML Attribute is added to orm mapping file without error
... ... Again right-click the added attribute and try to change the type of it to

many-to-one or one-to-one

Verify the orm mapping file is updated with the selected type and no errors appear
347977 Exception in error log while renaming entity Create JPA project, R-Click and select JPA Tools > Open Diagram Project is created successfully and diagram is opened in editor
... ... Create a JPA entity within the diagram Entity is created in the diagram successfully
... ... R-Click on the entity in the diagram and select Refactor Entity Class > Rename Rename Compliance Unit dialog appears
... ... Enter a new name into the New Name field and click on Next button, then click on the Finish button Verify name is updated and no errors appear in the Error Log
348143 NullPointerException: Add entity to XML Create a brand new JPA project with a mapping xml created along with it

(selecting "Create mapping file (orm.xml) checkbox" when creating the JPA project)

Project is created successfully
... ... Right-click the created JPA project and select New -> JPA Entity to create

an entity, select "Add to entity mappings in XML" checkbox when it shows, create a couple of fields for the entity (make at least 1 of them an ID, Key), and hit Finish.

Verify the Entity is created without any errors and the fields appear correctly as you entered them.
348667 Delete diagram editor, then Save, receive errors Create a JPA project then R-Click on the project and select JPA Tools >Open Diagram. Verify diagram.xml opens in editor
... ... Delete the diagram folder (which contains the diagram.xml) Verify the diagram editor closes without error
... ... R-Click on the project and select JPA Tools > Open Diagram, Add a Java Entity to the diagram editor Entity appears in the editor without error
... ... Delete the diagram.xml file Verify the diagram editor closes without error
349031 [EclipseLink] descriptor customizer validation incorrect when default zero arg constructor Create JPA 2.0, EclipseLink 2.2.x project Project is created successfully
... ... Create JPA Entity (MyCustomizer), with one field (Id) Entity is created successfully
... ... Change implements Serializable to implements DescriptorCustomizer, and import DescriptorCustomizer and then add public void customize (ClassDescriptor descriptor) throws Exception { } & then remove the serializable warning items and Save Project Project is saved without warnings
... ... Remove public MyCustomizeClass() {

super(); } and then Save the project

Verify no errors appear
... ... Go to the Entity JPA Details pane, Expand Advanced, Add MyCustomizer to the Customizer Class field and then Save the project Verify no errors still appear for the project
349071 [EclipseLink] eclipselink 2.3 schemas not up to date Get latest Dali build and install, open eclipse>plugins>org.eclipse.jpt.common.eclipselink.cor_1.0.0.jar file Verify the latest files exist - eclipselink_orm_2_3.xsd file from 7/25/11, eclipselink_oxm_2_3.xsd from 6/24/11, eclipselink_persistence_map_2_3.xsd from 6/24/11
... ... For workaround, go to an older install, launch Eclipse, Select Window>Preferences Preferences dialog appears
... ... Select XML Catalog, Select User Specified Entries, click on Add button Add XML Catalog Element dialog appears
... ... Click on File system and browse to the latest version of the eclipselink_orm_2_3.xsd file, select open, for the Key enter the same value as the key for the .xsd file you are replacing in the plugin entries and click on ok button Verify the entry appears under the User Specified Entries and no errors appear.
349337 [API] CCE generating metamodel classes Create a Generic 2.0 JPA project with an orm.xml file JPA project is created successfully
... ... R-Click on the JPA Project and select properties, Properties dialog appears
... ... Set a canonical metamodel source folder and click on OK Properties dialog closes successfully
... ... Add the following JPA entity - @Entity

public class Bar {

   @Id
   private int id;

}

Entity is created successfully
... ... Go to the orm.xml file in the JPA Structure pane and Add the entity to the orm.xml mapping file Verify the entity is added to the orm.xml without error
349722 NPE deleting generator name from "Generator name" combo Create JPA project, Create Entity that contains an ID mapping Project and Entity are created successfully
... ... Select the Id mapping in the Entity in the JPA Structure pane Id mapping appears in the JPA Details view
... ... Expand the Primary Key Generation section in the JPA Details pane Primary Key checkbox is not checked and the Strategy and Generator Name fields are enabled
... ... Enter 'Testing' into the Generator Name field Verify the following annotation appears in the editor for the entity - @GeneratedValue(generator = "testing")
... ... Delete the generator name (either by removing it from the Entity editor and removing it from the field in the JPA Details pane Verify the generator name is removed from the editor and the JPA Details pane without error
351409 Strange event when saving the diagram Create JPA project, R-Click on the project and select JPA Tools > Open Diagram... Project is created successfully and diagram is open in the editor
... ... Add a JPA Entity via the diagram editor and Save Entity is added and saved successfully
... ... Highlight the Entity, R-Click and Select Remove All Entities From Diagram > ...and Save Changes Verify Entity is removed and the Diagram is saved
... ... Add a JPA Entity via the diagram editor and Save Entity is added and saved successfully and the diagram remains open
... ... R-Click on the Entity and Select Remove All Entities From Diagram > ... and Discard Changes Remove All Entities From Diagram dialog appears
... ... Click on the Cancel button Verify the Entity is not removed
... ... R-Click on the Entity and Select Remove All Entities From Diagram > ... and Discard Changes and Click on OKbutton Verify Entity is removed from the Diagram and diagram remains open
... ... R-Click on the Diagrams Folder in the Project Explorer Pane and select Delete Verify the Diagram folder is deleted and the diagram editor is closed successfully
353017 Validation show problems with NamedQuery with subquery in where clause Create JPA project, Create JPA Entity JPA project and Entity are created successfully
... ... Select Entity in the JPA Structure pane, Expand the Queries section in the JPA Details pane for the Entity and click on the Add button
... ... Enter a name for the query and select Named Query from the from the Type drop down and click on OK button Query appears in entity editor
... ... Add the following query into query text editor in JPA Details - select t from Address t where t.id = (select max(tt.id) from Address tt) and Save the project Project is saved and the
353146 Make Persistent Wizard: Cannot select mapping file from the folder other than META-INF Create JPA project JPA Project is created successfully and verify the following error does not appear - The identification variable ' ' is not defined in the FROM clause
... ... Create a new folder under the src folder New folder is created under src folder
... ... R-Click on the new folder and select New>JPA orm mapping file New Mapping File dialog appears
... ... Click on Next and then Finish Verify orm.xml exists under the new folder in the src folder
... ... Add the orm.xml mapping file to the persistence.xml orm.xml is added to persistence.xml successfully without error
... ... R-click on the project and select New > Class New Java Class dialog appears
... ... Leave the defaults and Add the new class New Class is added successfully to Project without error
... ... R-Click on the new class and select JPA Tools > Make Persistent... Make Persistent dialog appears
... ... Select Add to XML mapping file radio button and click on Browse button Mapping File dialog appears
... ... Select the orm.xml file and click on OK Verify you return to the Make Persistent dialog and the orm.xml appears in the Mapping File text field without any errors.
... ... Click on the finish button Verify dialog closes and no errors appear
353555 Inconsistent diagram name Create a JPA Project Project is created successfully
... ... Open persistence.xml in the editor, Go to the General and change the name (from JPA Project name to something else) Verify name is updated
... ... R-Click on project and select JPA Tools > Open Diagram Diagram opens in editor and verify the name of the diagram is the name of the project.xml
354363 Delete entity from diagram doesn't remove it from the project tree Create JPA Project JPA project is created successfully
... ... R-Click on the JPA project and select JPA Tools > Open Diagram... Diagram editor is opened
... ... Add a Java Entity to the diagram via the editor Entity is added in the diagram editor and in the project tree under the src/org.persistence/ folder
... ... R-Click on the Entity in the diagram editor and select Delete or select the Entity in the editor and click on the Trash can icon Confirm Delete dialog appears
... ... Click on No button Verify entity is not deleted in the editor or the project tree
... ... R-Click on the entity in the diagram editor and select Delete and click on the Yes button in the Confirm Delete dialog Verify the entity is removed from the diagram editor and is also removed from the src/org.persistence folder in the project tree.
354444 Invalid ORM ElementCollection target-class validation with package element Launch Eclipse, Import the example project attached to the bug Element collection project appears in Project Explorer
... ... R-Click on the project and click on properties and add the needed library and click on OK The project is updated and most errors are removed.
... ... R-Click on the project and select validate Verify Validation Results dialog appears with results
... ... Click on OK button to close validation results dialog Verify the following error appears - Collection table "PropertyRecord_parcels" cannot be resolved
354669 Invalid map key class validation in orm.xml element collection Create JPA 2.0, Generic 2.0 project Project is created successfully
... ... Create JPA Entity, with 2 fields (one as Id type and the other as a Collection type) Entity is created successfully
... ... Add orm.xml mapping file to the project and add the JPA entity to the orm.xml mapping file Entity is added to orm.xml mapping file successfully without error
... ... Go to the JPA Structure pane for the Entity Mappings (orm.xml) and R-Click on the Collection Type attribute and select Add Attribute to XML and map... Add Attribute dialog appears
... ... Select Element Collection from the Map As drop down and click on OK button Verify it is added to orm.xml mapping file and the error stating 'Map key class is not defined does not appear in the Problems pane as an error
355502 Invalid ORM id-class validation with package element Select File > Import, Select General > Existing Projects into Workspace and Import the project attached to this bug Project is imported successfully but contains errors
... ... R-click on the imported project and select Properties, Add the EclipseLink 2.3.0 - Indigo library and click on OK button Verify errors are removed from project
... ... R-click on the project and select Validate Verify no errors appear on validation
355978 NPE adding persistence-unit-defaults element to eclipselink-orm.xml file Create JPA 2.0, EL 2.0 project Project is created successfully
... ... R-Click on the project and select New - Eclipselink ORM Mapping File The eclipselink-orm.xml is opened in the editor
... ... Add the following to the source and Save <persistence-unit-metadata>

<persistence-unit-defaults></persistence-unit-defaults></persistence-unit-metadata>

Verify it is saved successfully and no errors appear
356292 Validation error for entities with @AttributeOverride on attribute marked as @Version in mapped superclass Create a JPA 2.0, Generic 2.0 project with connection to a db Project is created successfully
... ... Create two JPA entities copy the entity information for A and for B from the bug attachments JPA Entities are created successfully
... ... Fix the few validation errors by making the db table connection corrections Verify all errors are removed and error stating - Attribute override "version" cannot be resolved to an attribute on the mapped superclass "A" does not appear

Back to the top