J2EE Design Mode: CMP to BMP mode (2)

Weblogic-ejb-jar.xml for specific vendors
We first define vendor-specific information in weblogic-ejb-jar.xml. Here we will tell the server where to store the local stub (stub) and where to find the CMP ING.
Persistent ing information:
& Lt; persistence-type & gt;
& Lt; type-identifier & gt; WebLogic_CMP_RDBMS & lt;/type-identifier & gt;
& Lt; type-version & gt; 6.0 & lt;/type-version & gt;
& Lt; type-storage & gt; META-INF/weblogic-cmp-rdbms-jar.xml & lt;
/Type-storage & gt;
& Lt;/persistence-type & gt;
Local JNDI name
& Lt; local-jndi-name & gt; InventoryHome & lt;/local-jndi-name & gt;
Weblogic-cmp-rdbms-jar.xml for specific vendors
Data Source Name: (this data source is created during configuration)
& Lt; data-source-name & gt; InventoryDB & lt;/data-source-name & gt;
Table name:
& Lt; table-name & gt; inventory & lt;/table-name & gt;
Field ing
& Lt; field-map & gt;
& Lt; cmp-field & gt; stock & lt;/cmp-field & gt;
& Lt; dbms-column & gt; stock & lt;/dbms-column & gt;
& Lt;/field-map & gt;
& Lt; field-map & gt;
& Lt; cmp-field & gt; item & lt;/cmp-field & gt;
& Lt; dbms-column & gt; item & lt;/dbms-column & gt;
& Lt;/field-map & gt;
& Lt; field-map & gt;
& Lt; cmp-field & gt; price & lt;/cmp-field & gt;
& Lt; dbms-column & gt; price & lt;/dbms-column & gt;
& Lt;/field-map & gt;
Now we have everything we want. Containers use abstract classes and deployment information to make everything work well. For some reason, we may have this CMPbean transplanted to BMP. Which of the following is why we want to do this?
1. Portability: currently, it only works in WebLogic 6.1, and we do not want to learn other tools. This is normal if we want to sell this database component-it can run on any server.
2. Performance: if we want to run SQL well (using stored procedures, table Union, etc ).
3. Replaceable data sources: if we want to access different data sources rather than RDBMS.
Transplant Bean with BMP
Here we will discuss the porting mode. We can port CMP to BMP in the "change to persistent manager" mode. We can see that the persistent manager extends the abstract class we created and implements the abstract class method! The final design looks like Figure 2: