WL 8.1

Question

While I am aware that WL 8.1 a.k.a Olympic in in limited beta, it would be
          great if Bea gave us a heads up on what to expect in terms of new features.
          I am particularly interested in JMS enhancements.
          Regards,
          Adarsh
          

Answer 1

The following is from the Beta documentation:
          JMS Enhancements in WebLogic Server 8.1
          The following JMS enhancements are new to this release of WebLogic Server.
          JMS Thin Client
          At approximately 400k, the wljmsclient.jar file provides full WebLogic JMS functionality, yet greatly reduces the client-side
          WebLogic footprint by using a smaller library that contains only the set of supporting files required by client-side programs. The
          new client .jar file is available in the WL_HOME/server/lib subdirectory of the WebLogic Server installation directory (for
          example, c:\bea\weblogic81b\server\lib).
          This .jar provides for full-featured WebLogic Server clients that can support clustering, load balancing, transactions, security,
          and failover.
          Accessing Foreign JMS Providers
          Using the Foreign JMS Server node on the Administration Console, you can quickly map a foreign JMS provider so that its connection
          factories and destinations appear in the WebLogic JNDI tree as a local JMS objects. A Foreign JMS Server configuration can also be
          used to reference remote instances of WebLogic Server in another cluster or domain in the local WebLogic JNDI tree.
          Accessing JMS via Servlets and EJBs
          New "wrappers" make it easier to use JMS inside a J2EE component. The wrappers provide features including automatic pooling of JMS
          Connection and Session objects (and some pooling of MessageProducer objects as well); automatic transaction enlistment for JMS
          providers that support XA; monitoring of the JMS connection and re-establishment after a failure; and security credentials that
          are managed by the container.
          Better Expired Message Handling
          Active message expiration ensures that expired messages are cleaned up immediately. Moreover, expired message auditing gives you
          the option of tracking expired messages, either by logging when a message expires or by redirecting expired messages to a special
          destination.
          Improved Message Flow Control by Blocking Producers
          The "Blocking Send" features help you to avoid receiving message quota errors by temporarily blocking message producers from
          sending messages to a destination (queue or topic) when the destination has exceeded its specified maximum message quota.
          "Adarsh Dattani" <[email protected]> wrote in message news:[email protected]...
          > While I am aware that WL 8.1 a.k.a Olympic in in limited beta, it would be
          > great if Bea gave us a heads up on what to expect in terms of new features.
          > I am particularly interested in JMS enhancements.
          >
          > --
          > Regards,
          > Adarsh
          >
          >