05 April 2007

WebLogic Server 10 Summary

  • JavaEE5 certified
  • Operations News:
    weblogic.jar split up:
    • Include not only weblogic.jar but also WL_HOME/modules/weblogic.server.modules_10.0.0.0.jar directly in the classpath
    • The java weblogic.version command has a new -verbose optional argument that returns version information about numerous WebLogic Server components.
    • As a consequence of the weblogic.jarreorganization, your existing J2SE security policies may need to be modified to control access to the new separate modules. The default J2SE security policy in WebLogic Server has been modified to grant access to the new modules.
  • EAR libs:
    • APP-INF/lib and/or
    • library-directory defined in deployment descriptor of EAR file
    • library-directory has priority over others
  • MySQL 5.0 Support
  • WebLogic Diagnostic Framework
  • EJB3 + EJB2.1 support
  • JAX-WS 2.0: Java API for XML-Based Web Services
  • JAXB 2.0: Java Architecture for XML Binding
  • Web Services for Java EE 1.2
  • SAAJ 1.3: SOAP With Attachments API For Java
  • WS-SecureConversations 1.3
  • WS-Security 1.1
  • WS-SecurityPolicy 1.2
  • WS-Trust 1.3
  • new set of security policy files that comply with WS-SecurityPolicy 1.2
  • JAX-RPC: support MTOM (Message Transmission Optimization Mechanism) and XOP (XML-binary Optimized Packaging)
  • Filtering Classloader: specify packages to be loaded from the application specific lib folder (WEB-INF/lib) rather than system classpath.
  • Servlet 2.5
  • JSF 1.2
  • JSTL 1.2
  • JSP 2.1
  • Cross-Domain Security
  • Windows NT Authorization Provider Deprecated
  • Admin Console: record actions and store them as WLST scripts
  • Admin Console extensions must be packaged as a WAR file
  • JMX implementation supports the jmx.remote.x.request.waiting.timeout environment parameter (optional in JMX Remote API 1.0)

Full List of standards supported

Java Standards Support

Standard Version
Java EE 5.0
JDKs 5.0 (aka 1.5), 1.4 (clients only)
Java EE Enterprise Web Services 1.2, 1.1
Web Services Metadata for the Java Platform 2.0, 1.1
Java API for XML-Based Web Services (JAX-WS) 2.0
Java EE EJB 3.0, 2.1, 2.0, and 1.1
Java EE JMS 1.1, 1.0.2b
Java EE JDBC (with third-party drivers) 2.0
MS SQL jDriver 1.0
Oracle OCI jDriver 1.0 and some 2.0 features (batching)
Java EE JNDI 1.2
OTS/JTA 1.2 and 1.1
Java EE Servlet 2.5, 2.4, 2.3, and 2.2
Java EE Application Deployment 1.2
Java Authorization Contract for Containers (JACC) 1.1
Java EE JSP 2.1, 2.0, 1.2, and 1.1
RMI/IIOP 1.0
JMX 1.2, 1.0
JavaMail 1.2
JAAS 1.0 Full
Java EE CA 1.5, 1.0
JCE 1.4
Java RMI 1.0
JAX-B 2.0
JAX-P 1.2, 1.1
JAX-RPC 1.1, 1.0
JAX-R 1.0
SOAP Attachments for Java (SAAJ) 1.3, 1.2
Streaming API for XML (StAX) 1.0

Web Services Standards Support

Standard Version
Java EE Enterprise Web Services 1.2, 1.1
Web Services Metadata for the Java Platform (JWS) 2.0, 1.0
Java API for XML-Based Web Services (JAX-WS) 2.0
SOAP 1.1, 1.2
WSDL 1.1
JAX-RPC 1.1
SOAP Attachments for Java (SAAJ) 1.3, 1.2
WS-Security 1.1, 1.0
WS-Policy 1.0
WS-SecurityPolicy 1.2, 1.1
WS-PolicyAttachment 1.0
WS-Addressing 1.0
WS-ReliableMessaging 1.0
WS-Trust 1.0
WS-SecureConversation 1.3, 1.0
UDDI 2.0
JAX-R 1.0
JAX-B 2.0

Other Standards

Standard Version
SSL v3
X.509 v3
Security Assertion Markup Language (SAML) 1.0, 1.1
LDAP v3
TLS v1
HTTP 1.1
SNMP SNMPv1, SNMPv2, SNMPv3
xTensible Access Control Markup Language (XACML) 2.0
Partial implementation of Core and Hierarchical Role Based Access Control (RBAC) Profile of XACML 2.0

2 comments:

Anonymous said...

There is still a problem with Eclipse resolving the classpath. Quite simply, Eclipse 3.3 cannot find the javax.servlet.* classes even thought I have both weblogic.jar and weblogic.server.modules_10.0.0.0.jar in the build path!

Looks like either Eclipse cannot resolve the referenced classpath from weblogic.jar (to weblogic.server.modules_10.0.0.0.jar) or....???

Anonymous said...

Can anyone recommend the best RMM program for a small IT service company like mine? Does anyone use Kaseya.com or GFI.com? How do they compare to these guys I found recently: [url=http://www.n-able.com] N-able N-central system network
[/url] ? What is your best take in cost vs performance among those three? I need a good advice please... Thanks in advance!