Hello!
I would like to comment on the usage of proprietary J2EE extensions. These extensions cannot be avoided when CMP entity beans are used. In such cases the Object/Relational mapping information is described in a vendor-specific deployment descriptor.
My advice to people who port applications containing proprietary metadata is to read carefully the corresponding sections from the Development Manual that describe the development of components, which they use in their applications..
The reason for this posting is part of Volker Steil's SPJ article concerning entitiesÂ’ primary key generation. According to the article, BEA WebLogic supports such an extension, whereas SAP Web AS does not, which is incorrect. The SAP EJB Container also provides automatic primary key generation and it is well documented in the EJB development manual (http://help.sap.com/saphelp_nw04/helpdata/en/b3/b238bfd13a8f408958d70a6989d001/frameset.htm). This manual contains also hints on vendor-specific features and performance optimization options.
Best regards,
Svetoslav
1 Answer
-
Posted on Feb 18, 2005 at 09:01 AM
Hello again,
I would like to add my apologies to Volker personally, as the initial intension of my posting was not to discredit his article. Actually, I find his article a really helpful source of information. From our exchange of mails, it turned out that the incorrect piece of information was caused by misunderstanding in the communication.
The goal of my posting was to reveal as much information as possible about the SAP Web AS EJB implementation.
The automatic key generation is a helpful feature supported by SAP Web AS, as well as most of the J2EE application server providers. The different providers’ implementations, however, are proprietary and applications using this feature need migration.
Best regards,
Svetoslav
Add a comment
Add a comment