1、In this particular case, the application code was constructed for deployment to WebLogic Server 6.1.
2、There is support for editing WebLogic Server Web Services annotations using wizards to configure data bindings.
3、WebLogic Server adds features such as clustering, management, fail-over and reliability.
4、Older versions of WebLogic Server used the proprietary WebLogic Query Language (WL-QL) to specify finder queries for CMP entity beans.
5、Most of the information here also applies to the migration applications from earlier versions of WebLogic Server as well.
6、Database concurrency strategy causes WebLogic Server to delegate locking requests for an entity bean to the underlying datastore.
7、For more help on dealing with dependency cycles, see Learning from Experience: Moving a WebLogic Server Application into WebSphere Studio.
8、If you set this element to False, WebLogic Server does not automatically load the bean into the cache until the first method invocation.
9、This allows users to install Fabric3 extensions such as bindings, policies and support for alternative component implementation types on WebLogic Server.
10、The finders-load-bean element determines whether WebLogic Server loads the EJB into the cache after a call to a finder method that returns a reference to the bean.
11、If you set this element to True (the default) and a reference to a bean is returned by the finder, then WebLogic Server immediately loads the bean into the cache.
