sorted by: recent | see :
popular
Content Tagged with Patterns + J2EE
hibernate.org - Generic Data Access Objects
Hibernate implementation of DAO Pattern
Jt - J2EE Pattern Oriented Framework
Jt is a pattern oriented framework for the rapid implementation of Java applications. This integrated framework is based on a messaging architecture which provides software simplicity , strong encapsulation and loose coupling; framework components can be
hibernate.org - Generic Data Access Objects
Generic Data Access Objects
Hibernate: del.icio.us tag/hibernate
J2EE
Hibernate
dao
Patterns
Articles
Generics
designpatterns
java.net: Exploring ESB Patterns with Mule
Exploring ESB Patterns with Mule
Poll: who uses beehive cotrols? Newsgroups | weblogic.developer.interest.ejb
33.3% (3 votes) on dec 22, 2007
EJB Programming Restrictions
- Using static, nonfinal fields. Declaring all static fields in the EJB component as final is recommended. That ensures consistent runtime semantics so that EJB containers have the flexibility to distribute instances across multiple JVMs.
- Using thread synchronization primitives to synchronize multiple instance execution. By avoiding that feature, you allow the EJB container flexibility to distribute instances across multiple JVMs.
- Using AWT functionality for keyboard input/display output. That restriction exists because server-side business components are meant to provide business functionality that excludes user interface and keyboard I/O functionality.
- Using file access/java.io operations. EJB business components are meant to use resource managers such as JDBC to store and retrieve application data rather than the file system APIs. Also, deployment tools provide the facility for storing environment entry elements (env-entry) into the deployment descriptor, so that EJB components can perform environment entry lookups in a standardized manner via the environment-naming context. Thus, the need to use file system-based property files is mostly eliminated.
- Listening to or accepting socket connections, or using a socket for multicast. EJB components are not meant to provide network socket server functionality; however, the architecture lets EJB components act as a socket client or RMI clients and thus communicate with code outside the container's managed environment.
- Using the Reflection API to query classes that are not otherwise accessible to the EJB component due to Java's security rules. That restriction enforces Java platform security.
- Attempting to create or obtain a class loader, set or create a new security manager, stop the JVM, change the input, output, and error streams. That restriction enforces security and maintains the EJB container's ability to manage the runtime environment.
- Setting the socket factory used by the URL's ServerSocket, Socket, or stream handler. By avoiding that feature, you also enforce security and maintain the EJB container's ability to manage the runtime environment.
- Starting, stopping, or managing threads in any way. That restriction eliminates the possibility of conflicts with the EJB container's responsibilities of managing locking, threading, and concurrency issues.
- By restricting your use of features 10-16, you aim to plug potential security holes:
- Reading or writing a file descriptor directly.
- Obtaining security policy information for a particular code source.
- Loading native libraries.
- Accessing packages and classes that the usual rules of Java make unavailable.
- Defining a class in a package.
- Accessing or modifying security configuration objects (Policy, Security, Provider, Signer, and Identity).
- Using the subclass and object substitution features of the Java Serialization protocol.
- Passing the this reference as an argument or returning the this reference as a result. Instead, you must use the result of the getEJBObject() available in SessionContext or EntityContext.
Apache Beehive Control Video Webinar
BEA recently moved various parts of Workshop into the open source community via the Beehive project. Garrett Conaty is a principal technologist on the Beehive team, and has a good insight on how this happened and what it means for developers. This intervi
Configuring Beehive Controls in WebLogic Console | Changing Annotation Configuration on the Fly (more detail)
clarification of Chris Hogue's previous instructions Z James Bayer's Blog: | August 30, 2007
Service Control Pack | dev2dev
The Workshop Service Control Pack is a collection of controls, processes and services that help demonstrate and facilitate the composition of service-based applications using WebLogic Workshop. This provides the application developer with a wealth of comp
ControlHaus:WorkShop Controls Community Site | May 28, 2004
BEA and codehaus have announced a partnership to host Controlhaus, a complimentary site to codehaus, but specifically for hosting development of BEAs new Weblogic WorkShop Control Pack
Control Tutorial: Testing Controls with JUnit | WLS 10
testing a custom control with ControlTestCase
Control Tutorial: Testing Controls with JUnit | WLS 10
testing a custom control with ControlTestCase
Page 1 | Next >>
