Index: faces/component/PORTLET_CSS_DEFAULT.java =================================================================== --- faces/component/PORTLET_CSS_DEFAULT.java (revision 28274) +++ faces/component/PORTLET_CSS_DEFAULT.java (working copy) @@ -33,7 +33,7 @@ package com.icesoft.faces.component; /** - * All style class names are extracted from JSR-168 spec + * All style class names were chosen in accordance with JSR-168 spec * */ public class PORTLET_CSS_DEFAULT { Index: jasper/web-app_2_2.dtd =================================================================== --- jasper/web-app_2_2.dtd (revision 28274) +++ jasper/web-app_2_2.dtd (working copy) @@ -1,634 +1,581 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Index: jasper/web-app_2_3.dtd =================================================================== --- jasper/web-app_2_3.dtd (revision 28274) +++ jasper/web-app_2_3.dtd (working copy) @@ -1,1095 +1,1075 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Index: net/messaging/jms/JMSAdapter.java =================================================================== --- net/messaging/jms/JMSAdapter.java (revision 28274) +++ net/messaging/jms/JMSAdapter.java (working copy) @@ -469,109 +469,4 @@ (_topicNamePrefix == null ? "" : _topicNamePrefix) + topicName); } - - /* - * Taken from "Java Message Service - Version 1.1 April 12, 2002": - * - * 2.8 Multithreading - * - * JMS could have required that all its objects support concurrent use. - * Since support for concurrent access typically adds some overhead and - * complexity, the JMS design restricts its requirement for concurrent - * access to those objects that would naturally be shared by a multithreaded - * client. The remainder are designed to be accessed by one logical thread - * of control at a time. - * - * JMS Object | Supports Concurrent Use - * ------------------+------------------------ - * Destination | YES - * ConnectionFactory | YES - * Connection | YES - * Session | NO - * MessageProducer | NO - * MessageConsumer | NO - * - * JMS defines some specific rules that restrict the concurrent use of - * Sessions. Since they require more knowledge of JMS specifics than we have - * presented at this point, they will be described later. Here we will - * describe the rationale for imposing them. - * - * There are two reasons for restricting concurrent access to Sessions. - * First, Sessions are the JMS entity that supports transactions. It is very - * difficult to implement transactions that are multithreaded. Second, - * Sessions support asynchronous message consumption. It is important that - * JMS not require that client code used for asynchronous message - * consumption be capable of handling multiple, concurrent messages. In - * addition, if a Session has been set up with multiple, asynchronous - * consumers, it is important that the client is not forced to handle the - * case where these separate consumers are concurrently executing. These - * restrictions make JMS easier to use for typical clients. More - * sophisticated clients can get the concurrency they desire by using - * multiple sessions. - */ - - /* - * Taken from "Java 2 Platform Enterprise Edition Specification, v1.3" - * - * J2EE.6.7 Java Message Service (JMS) 1.0 Requirements - * - * Note that the JMS API creates threads to deliver messages to message - * listeners. The use of this message listener facility may be limited by - * the restrictions on the use of threads in various containers. In EJB - * containers, for instance, it is typically not possible to create threads. - * The following methods must not be used by application components - * executing in containers that prevent them from creating threads: - * - * - javax.jms.Session method setMessageListener - * - javax.jms.Session method getMessageListener - * - javax.jms.Session method run - * - javax.jms.QueueConnection method createConnectionConsumer - * - javax.jms.TopicConnection method createConnectionConsumer - * - javax.jms.TopicConnection method createDurableConnectionConsumer - * - javax.jms.MessageConsumer method getMessageListener - * - javax.jms.MessageConsumer method setMessageListener - * - * In addition, use of the following methods on javax.jms.Connection objects - * by applications in web and EJB containers may interfere with the - * connection management functions of the container and must not be used: - * - * - setExceptionListener - * - stop - * - setClientID - * - * A J2EE container may throw a JMSException if the application component - * violates these restrictions. - */ - - /* - * Taken from "Java 2 Platform Enterprise Edition Specification, v1.4" - * - * J2EE.6.6 Java Message Service (JMS) 1.1 Requirements - * - * The following methods may only be used by application components - * executing in the application client container: - * - * - javax.jms.Session method setMessageListener - * - javax.jms.Session method getMessageListener - * - javax.jms.Session method run - * - javax.jms.QueueConnection method createConnectionConsumer - * - javax.jms.TopicConnection method createConnectionConsumer - * - javax.jms.TopicConnection method createDurableConnectionConsumer - * - javax.jms.MessageConsumer method getMessageListener - * - javax.jms.MessageConsumer method setMessageListener - * - javax.jms.Connection method setExceptionListener - * - javax.jms.Connection method stop - * - javax.jms.Connection method setClientID - * - * A J2EE container may throw a JMSException (if allowed by the method) if - * the application component violates these restrictions. - * - * Application components in the web and EJB containers must not attempt to - * create more than one active (not closed) Session object per connection. - * An attempt to use the Connection object’s createSession method when an - * active Session object exists for that connection should be prohibited by - * the container. The container may throw a JMSException if the application - * component violates this restriction. Application client containers must - * support the creation of multiple sessions for each connection. - */ }