Interoperable WebServices for J2EE
JSR-109 facilitates the building of interoperable WebServices in the J2EE environment. It standardizes the deployment of WebServices in a J2EE container.
- Stateless session beans and servlet end-points can be exposed as WebServices.
- J2EE components can be consumers of WebServices.
Standardized Server management with JSR-77
JSR-77 J2EE Management Model abstracts manageable aspects of J2EE architecture and provides a well-defined model for implementing instrumentation and information access. J2EE vendors implement a vendor-neutral API, making their servers manageable by JSR-77-aware tools created by other software vendors.
- Use any JSR-77 compliant tool to discover and access the Pramati Management Bean Server
- Navigate the MBeans using JSR-77 specified object names and gather information.
JCA 1.5 Connectors
- Inbound communication. The new standard brings MDB-functionality to non-JMS messaging systems and message-oriented middleware - EIS, which can now communicate and work with J2EE components deployed in the application server.
- Transaction inflow. Distributed transactions started inside the EIS can be propagated to the application server, enabling EIS components to control such transactions.
- Message inflow. MDBs can implement any custom message listener interface, not just JMS, and receive messages from any EIS component.
- JMS adapter. The Server provides a JCA 1.5 JMS adapter that enables standards-based connectivity between a JMS server and a J2EE server.
Web Server: JSP 2.0 & Servlet 2.4 features
- Expression Language (EL) is supported. This is useful for web developers who want to build scriptless JSP pages. JSP 2.0 standard adopts EL from the JSP Standard Tag Library (JSTL) 1.0, and enhances it to add functions that can be used to call static Java methods from web pages without using Java code.
- Tag files (*.tag) allow web developers to write reusable custom tags for JSP pages. You can create custom tags without writing any Java code using the tag files. The JSP 2.0 server takes the tag files, parses them, generates Java tag handlers, and compiles them automatically.
JSP debugger through JSR-45
The JSP/Servlet engine in Pramati Server 5.0 embeds support for JSR-45, offering full debugging (JSP and classes) when using Pramati as a development server.
Standardized deployment from JSR-88 compliant IDEs
JSR-88 defines standard APIs to enable deployment of J2EE applications and stand-alone modules to J2EE product platforms.
Templatized deployment plans
Store environment-specific configuration and tuning information for various deployment scenarios (development, staging, production, or customer-specific). A Deployment Plan XML can be created for each environment.
Enhancements in EJB QL
Pramati Server 5.0 supports more complex queries to access database, such as ORDER BY CLAUSE, aggregate functions and MOD function.
Pluggable authorization via JACC
Pramati Server 5.0 supports Java Authorization Contract for Containers (JACC) specification that enables third-party security providers to handle the J2EE authorization. The providers are required to store the policy information in their repository during application deployment. The providers then use this information to make authorization decisions when called by the Server.
- Authorization of J2EE resources like EJB method and Web resource permissions are delegated to a JACC provider.
- Plug-in third-party JACC implementation for authorization.
- As per JSR-94, the JACC provider can be extended to support rule-based access control for J2EE applications.
- Each application can use a different JACC provider for authorizing its resources.
|
