[jboss-svn-commits] JBL Code SVN: r37310 - in labs/jbossesb/branches/JBESB_4_10_CP/product: docs/Programmers_Guide/en-US/OOB-Actions and 1 other directories.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Wed Jul 27 08:08:32 EDT 2011
Author: mageshbk at jboss.com
Date: 2011-07-27 08:08:32 -0400 (Wed, 27 Jul 2011)
New Revision: 37310
Modified:
labs/jbossesb/branches/JBESB_4_10_CP/product/docs/Programmers_Guide/en-US/OOB-Actions/OOB_Actions_webservices_SOAP.xml
labs/jbossesb/branches/JBESB_4_10_CP/product/docs/Programmers_Guide/en-US/Web_Services_Support.xml
labs/jbossesb/branches/JBESB_4_10_CP/product/services/soap/src/main/java/org/jboss/soa/esb/actions/soap/SOAPProcessor.java
Log:
[JBESB-3567] - Removed ThreadLocal usage from SOAPProcessor.
Modified: labs/jbossesb/branches/JBESB_4_10_CP/product/docs/Programmers_Guide/en-US/OOB-Actions/OOB_Actions_webservices_SOAP.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_10_CP/product/docs/Programmers_Guide/en-US/OOB-Actions/OOB_Actions_webservices_SOAP.xml 2011-07-27 11:03:00 UTC (rev 37309)
+++ labs/jbossesb/branches/JBESB_4_10_CP/product/docs/Programmers_Guide/en-US/OOB-Actions/OOB_Actions_webservices_SOAP.xml 2011-07-27 12:08:32 UTC (rev 37310)
@@ -96,30 +96,6 @@
</orderedlist>
</section>
-
- <section id="sect-webservicessoap-esb-message-aware-webservice-endpoints">
- <title>"ESB Message Aware" Webservice Endpoints</title>
- <para>
- Note that JBossWS-Native Webservice endpoints exposed via this
- action have direct access to the current JBossESB Message instance
- used to invoke this action's process(Message) method. It can access
- the current Message instance via the SOAPProcessor.getMessage()
- method and can change the Message instance via the
- SOAPProcessor.setMessage(Message) method. This means that
- JBossWS-Native Webservice endpoints exposed using this action are
- "ESB Message Aware".
- </para>
-
- <important>
- <para>
- This feature has been deprecated and may no longer be
- available in future releases. Users are not encouraged to rely
- on this feature.
- </para>
- </important>
-
- </section>
-
<section id="sect-webservicessoap-webservice-endpoint-deployment">
<title>Webservice Endpoint Deployment</title>
Modified: labs/jbossesb/branches/JBESB_4_10_CP/product/docs/Programmers_Guide/en-US/Web_Services_Support.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_10_CP/product/docs/Programmers_Guide/en-US/Web_Services_Support.xml 2011-07-27 11:03:00 UTC (rev 37309)
+++ labs/jbossesb/branches/JBESB_4_10_CP/product/docs/Programmers_Guide/en-US/Web_Services_Support.xml 2011-07-27 12:08:32 UTC (rev 37310)
@@ -33,17 +33,8 @@
the ESB (“SOAP onto the bus”). This allows you to
use JBossESB to expose Webservice Endpoints
(wrapper Webservices) for services that don't
- expose a Webservice Interface. JBossWS Webservice
- Endpoints exposed via this JBossESB action are “ESB
- Message Aware” and can be used to invoke Webservice
- Endpoints over any transport channel supported by
- the ESB.
- </para>
- <caution>
- <para>
- JBossWS-CXF Endpoints are not "ESB Message Aware”.
- </para>
- </caution>
+ expose a Webservice Interface.
+ </para>
</listitem>
<listitem>
Modified: labs/jbossesb/branches/JBESB_4_10_CP/product/services/soap/src/main/java/org/jboss/soa/esb/actions/soap/SOAPProcessor.java
===================================================================
--- labs/jbossesb/branches/JBESB_4_10_CP/product/services/soap/src/main/java/org/jboss/soa/esb/actions/soap/SOAPProcessor.java 2011-07-27 11:03:00 UTC (rev 37309)
+++ labs/jbossesb/branches/JBESB_4_10_CP/product/services/soap/src/main/java/org/jboss/soa/esb/actions/soap/SOAPProcessor.java 2011-07-27 12:08:32 UTC (rev 37310)
@@ -63,15 +63,6 @@
* exposing that Service via endpoints (listeners) running on the ESB. This also means that these Services
* are invocable over any transport channel supported by the ESB (http, ftp, jms etc).
*
- * <h3>"ESB Message Aware" Webservice Endpoints</h3>
- * Note that Webservice endpoints exposed via this action have direct access to the current
- * JBossESB {@link org.jboss.soa.esb.message.Message} instance used to invoke this action's
- * {@link #process(org.jboss.soa.esb.message.Message)} method. It can access
- * the current {@link org.jboss.soa.esb.message.Message} instance via the {@link #getMessage()} method
- * and can change the {@link org.jboss.soa.esb.message.Message} instance via the
- * {@link #setMessage(org.jboss.soa.esb.message.Message)} method. This means that Webservice endpoints
- * exposed via this action are "ESB Message Aware".
- *
* <h3>Webservice Endpoint Deployment</h3>
* Any JBossWS Webservice endpoint can be exposed via ESB listeners using this action. That includes endpoints that are deployed
* from inside (i.e. the Webservice .war is bundled inside the .esb) and outside (e.g. standalone Webservice .war deployments,
@@ -113,7 +104,6 @@
@Publish(JBossWSWebserviceContractPublisher.class)
public class SOAPProcessor extends AbstractActionPipelineProcessor {
- private static ThreadLocal<Message> messageTL = new ThreadLocal<Message>();
private String jbossws_endpoint;
private String jbossws_context;
private MessagePayloadProxy payloadProxy;
@@ -151,8 +141,6 @@
soapMessage = getSOAPMessagePayload(message);
try {
- messageTL.set(message);
-
RequestHandler requestHandler = endpoint.getRequestHandler();
final Map<String, List<String>> headers = new HashMap<String, List<String>>() ;
@@ -228,9 +216,6 @@
Thread.currentThread().setContextClassLoader(old);
EndpointAssociation.removeEndpoint();
}
-
- // This may have been changed, make sure we get the current version.
- message = messageTL.get();
final Properties responseProperties = message.getProperties() ;
final String contentType = servletResponse.getContentType() ;
final Map<String, List<String>> responseHeaders = servletResponse.getHeaders() ;
@@ -268,8 +253,6 @@
}
} catch (Exception ex) {
throw new ActionProcessingException("Cannot process SOAP request", ex);
- } finally {
- messageTL.remove();
}
return message;
@@ -324,37 +307,4 @@
}
return soapMessage;
}
-
- /**
- * Set the {@link org.jboss.soa.esb.message.Message} instance for this invocation context.
- * <p/>
- * This allows message aware Webservice endpoints modify the {@link org.jboss.soa.esb.message.Message}
- * instance for the current Action Processing Pipeline.
- *
- * @param message The new message instance.
- */
- public static void setMessage(final Message message) {
- messageTL.set(message);
- }
-
- /**
- * Get the {@link org.jboss.soa.esb.message.Message} instance for this invocation context.
- *
- * @return The message instance.
- * @deprecated
- */
- public static Message getMessage() {
- Message message = messageTL.get();
- if (message == null)
- throw new RuntimeException("ESB message not found!");
- return message;
- }
-
- /**
- * Removes {@link org.jboss.soa.esb.message.Message} instance for this invocation context.
- *
- */
- public static void removeMessage() {
- messageTL.remove();
- }
}
\ No newline at end of file
More information about the jboss-svn-commits
mailing list