3:15 p.m.
Author: richard.opalka(a)jboss.com
Date: 2011-05-06 16:15:01 -0400 (Fri, 06 May 2011)
New Revision: 14289
Modified:
stack/cxf/trunk/modules/client/src/main/java/org/jboss/wsf/stack/cxf/client/serviceref/CXFServiceObjectFactoryJAXWS.java
stack/cxf/trunk/modules/client/src/main/java/org/jboss/wsf/stack/cxf/client/serviceref/CXFServiceReferenceableJAXWS.java
stack/cxf/trunk/modules/dist/management/src/main/pclwebapp/WEB-INF/web.xml
stack/cxf/trunk/modules/dist/management/src/main/webapp/WEB-INF/web.xml
stack/cxf/trunk/modules/dist/src/main/doc/JBossWS-Endpointmanagement.xml
stack/cxf/trunk/modules/dist/src/main/doc/JBossWS-Recordsmanagement.xml
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/WebServiceContextFactoryImpl.java
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/BusDeploymentAspect.java
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/DescriptorDeploymentAspect.java
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/JMSEndpointDeploymentAspect.java
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/JMSEndpointDeploymentAspectDelegate.java
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/JMSEndpointRegistryDeploymentAspect.java
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/JMSEndpointRegistryDeploymentAspectDelegate.java
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/ResourceResolverDeploymentAspect.java
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/metadata/MetadataBuilder.java
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/metadata/services/DDBeans.java
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/transport/ServletHelper.java
stack/cxf/trunk/modules/server/src/main/resources/jbossws-cxf-config-as6.xml
stack/cxf/trunk/modules/server/src/main/resources/jbossws-cxf-config-as7.xml
stack/cxf/trunk/modules/server/src/main/resources/jbossws-cxf-server.jar/META-INF/services/org.jboss.wsf.spi.DeploymentAspectManagerLocator
stack/cxf/trunk/modules/server/src/main/resources/jbossws-jaxrpc-config-as6.xml
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/wsrm/BasicDocTestCase.java
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/wsrm/BasicRPCTestCase.java
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/samples/jmsendpoints/jmstransport/JMSEndpointsTestCase.java
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/samples/jmstransport/FromJavaJMSTransportTestCase.java
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/samples/jmstransport/JMSTransportTestCase.java
stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/jaxbintros/JAXBIntroTestCase.java
stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/logging/JDKLoggingTestCase.java
stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/jaxws/samples/mtom/MtomTestCase.java
stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/saaj/jbws3084/ServiceImpl.java
Log:
[JBWS-3289] refactoring packages: org.jboss.wsf.common -> org.jboss.ws.common;
org.jboss.wsf.framework -> org.jboss.ws.common
Modified:
stack/cxf/trunk/modules/client/src/main/java/org/jboss/wsf/stack/cxf/client/serviceref/CXFServiceObjectFactoryJAXWS.java
===================================================================
---
stack/cxf/trunk/modules/client/src/main/java/org/jboss/wsf/stack/cxf/client/serviceref/CXFServiceObjectFactoryJAXWS.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/client/src/main/java/org/jboss/wsf/stack/cxf/client/serviceref/CXFServiceObjectFactoryJAXWS.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -29,7 +29,7 @@
import org.apache.cxf.BusFactory;
import org.apache.cxf.bus.spring.SpringBusFactory;
import org.apache.cxf.configuration.Configurer;
-import org.jboss.wsf.common.serviceref.AbstractServiceObjectFactoryJAXWS;
+import org.jboss.ws.common.serviceref.AbstractServiceObjectFactoryJAXWS;
import org.jboss.wsf.spi.deployment.UnifiedVirtualFile;
import org.jboss.wsf.spi.metadata.j2ee.serviceref.UnifiedServiceRefMetaData;
import org.jboss.wsf.stack.cxf.client.configuration.JBossWSSpringBusFactory;
Modified:
stack/cxf/trunk/modules/client/src/main/java/org/jboss/wsf/stack/cxf/client/serviceref/CXFServiceReferenceableJAXWS.java
===================================================================
---
stack/cxf/trunk/modules/client/src/main/java/org/jboss/wsf/stack/cxf/client/serviceref/CXFServiceReferenceableJAXWS.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/client/src/main/java/org/jboss/wsf/stack/cxf/client/serviceref/CXFServiceReferenceableJAXWS.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -21,7 +21,7 @@
*/
package org.jboss.wsf.stack.cxf.client.serviceref;
-import org.jboss.wsf.common.serviceref.AbstractServiceReferenceableJAXWS;
+import org.jboss.ws.common.serviceref.AbstractServiceReferenceableJAXWS;
import org.jboss.wsf.spi.metadata.j2ee.serviceref.UnifiedServiceRefMetaData;
/**
Modified: stack/cxf/trunk/modules/dist/management/src/main/pclwebapp/WEB-INF/web.xml
===================================================================
--- stack/cxf/trunk/modules/dist/management/src/main/pclwebapp/WEB-INF/web.xml 2011-05-06
20:12:14 UTC (rev 14288)
+++ stack/cxf/trunk/modules/dist/management/src/main/pclwebapp/WEB-INF/web.xml 2011-05-06
20:15:01 UTC (rev 14289)
@@ -8,7 +8,7 @@
<servlet>
<servlet-name>ContextServlet</servlet-name>
-
<servlet-class>org.jboss.wsf.framework.management.ContextServlet</servlet-class>
+
<servlet-class>org.jboss.ws.common.management.ContextServlet</servlet-class>
</servlet>
<servlet>
Modified: stack/cxf/trunk/modules/dist/management/src/main/webapp/WEB-INF/web.xml
===================================================================
--- stack/cxf/trunk/modules/dist/management/src/main/webapp/WEB-INF/web.xml 2011-05-06
20:12:14 UTC (rev 14288)
+++ stack/cxf/trunk/modules/dist/management/src/main/webapp/WEB-INF/web.xml 2011-05-06
20:15:01 UTC (rev 14289)
@@ -12,7 +12,7 @@
<servlet>
<servlet-name>ContextServlet</servlet-name>
-
<servlet-class>org.jboss.wsf.framework.management.ContextServlet</servlet-class>
+
<servlet-class>org.jboss.ws.common.management.ContextServlet</servlet-class>
</servlet>
<!-- now the mappings -->
Modified: stack/cxf/trunk/modules/dist/src/main/doc/JBossWS-Endpointmanagement.xml
===================================================================
--- stack/cxf/trunk/modules/dist/src/main/doc/JBossWS-Endpointmanagement.xml 2011-05-06
20:12:14 UTC (rev 14288)
+++ stack/cxf/trunk/modules/dist/src/main/doc/JBossWS-Endpointmanagement.xml 2011-05-06
20:15:01 UTC (rev 14289)
@@ -12,7 +12,7 @@
e.printStackTrace();
}
</screen></section>
-<section
id="JBossWS-Endpointmanagement_Metrics"><title>Metrics</title><para>For
each deployed endpoint you'll find an
<emphasis>org.jboss.wsf.framework.management.ManagedEndpoint</emphasis> MBean
providing basic start/stop functionalities and metrics. Calling a stopped endpoint will
always result in a SOAP fault message.</para><para>The metrics available for
each managed endpoint are:</para><itemizedlist><listitem><para>
Min, max, average and total processing time: processing includes both the WS stack plus
application server work and the user business logic
</para></listitem><listitem><para> Last start and stop time
</para></listitem><listitem><para> Request, response and fault
count</para></listitem></itemizedlist></section>
+<section
id="JBossWS-Endpointmanagement_Metrics"><title>Metrics</title><para>For
each deployed endpoint you'll find an
<emphasis>org.jboss.ws.common.management.ManagedEndpoint</emphasis> MBean
providing basic start/stop functionalities and metrics. Calling a stopped endpoint will
always result in a SOAP fault message.</para><para>The metrics available for
each managed endpoint are:</para><itemizedlist><listitem><para>
Min, max, average and total processing time: processing includes both the WS stack plus
application server work and the user business logic
</para></listitem><listitem><para> Last start and stop time
</para></listitem><listitem><para> Request, response and fault
count</para></listitem></itemizedlist></section>
<section
id="JBossWS-Endpointmanagement_Records"><title>Records</title><para>JBossWS
features a highly configurable records' collection and management system. Each record
is basically composed of a message plus additional information (for example the caller
address and the called endpoint operation).</para><para>Endpoints can be
configured with record processors that are invoked whenever a message flow is detected and
records are thus created.</para><para>Every deployed endpoint is configured
with default record processors. However custom processors as well as record filters can be
easily plugged in and managed at any time through JMX. This gives users the chance of
performing advanced analysis of the webservice traffic according to their business
requirements.</para><para>Please refer to the <ulink
url="http://jbossws.jboss.org/mediawiki/index.php?title=Records_mana...
management page</ulink> for further details.</para></section>
<section
id="JBossWS-Endpointmanagement_Snapshots_and_threshold_monitors"><title>Snapshots
and threshold monitors</title><para>As previously said, the <ulink
url="http://wiki.jboss.org/wiki/Wiki.jsp?page=WebConsole">JBoss Web
Console</ulink> has interesting features including <ulink
url="http://wiki.jboss.org/wiki/Wiki.jsp?page=WebConsoleSnapshots&qu...
and <ulink
url="http://wiki.jboss.org/wiki/Wiki.jsp?page=WebConsoleMonitoring&q...
monitors</ulink>.</para><para>Snapshots allow users to record changes of
a given MBean attribute within a defined time interval. Data are sampled at a given rate
and may be plotted to graphs with a few clicks. Snapshots are listed in the Web console
and can be created simply browsing to <ulink
url="http://localhost:8080/web-console/createSnapshot.jsp">http://localhost:8080/web-console/createSnapshot.jsp</ulink>
.</para><para>Threshold monitors allow users to be notified whenever a given
MBean attribute exceed a certain range!
of values. The threshold monitor's creation and management processes are similar to
those mentioned above for the snapshots. Simply browse to <ulink
url="http://localhost:8080/web-console/createThresholdMonitor.jsp">http://localhost:8080/web-console/createThresholdMonitor.jsp</ulink>
.</para><para>Speaking of WS availability and SLA, this all becomes
interesting because users can monitor and take snapshots of critical attributes like the
average/max processing time of a managed endpoint. Moreover, advanced analysis can be
performed leveraging ad-hoc attributes of custom <ulink
url="http://jbossws.jboss.org/mediawiki/index.php?title=Endpoint_man...
processors</ulink>.</para></section>
</chapter>
\ No newline at end of file
Modified: stack/cxf/trunk/modules/dist/src/main/doc/JBossWS-Recordsmanagement.xml
===================================================================
--- stack/cxf/trunk/modules/dist/src/main/doc/JBossWS-Recordsmanagement.xml 2011-05-06
20:12:14 UTC (rev 14288)
+++ stack/cxf/trunk/modules/dist/src/main/doc/JBossWS-Recordsmanagement.xml 2011-05-06
20:15:01 UTC (rev 14289)
@@ -1,10 +1,10 @@
<?xml version="1.0" encoding="UTF-8"?><chapter
id="chap_JBossWS-Recordsmanagement"><title>JBossWS-Recordsmanagement</title><para>JBossWS
records' collection and management system gives administrators a means of performing
custom analysis of their webservice traffic as well as exporting communication
logs.</para><para/><para> </para><section
id="JBossWS-Recordsmanagement_What_is_recorded"><title>What is
recorded</title><para>Each record is basically composed of a message plus
additional information; here are the current record
attributes:</para><itemizedlist><listitem><para> Creation date
</para></listitem><listitem><para> Source host
</para></listitem><listitem><para> Destination host
</para></listitem><listitem><para> Message type (in/out)
</para></listitem><listitem><para> Invoked endpoint operation
</para></listitem><listitem><para> Message envelope (including
both soap:header and soap:body for SOAP messages)
</para></listitem><listitem><para> Http headers
</para></list!
item><listitem><para> Record group ID (allowing records belonging to the
same message flow to be linked together)
</para></listitem></itemizedlist><para>Of course records may also
have meaningful values for a subset of the afore mentioned record
attributes.</para><para> </para></section>
<section id="JBossWS-Recordsmanagement_Use_cases"><title>Use
cases</title><para>What are records useful for? In spite of <link
linkend="chap_JBossWS-Endpointmanagement">endpoint metrics</link> that
provide response time information and counts of invocations, records provide users with
rich data about the content of the exchanged messages and their sender/receiver. The
record system allows fine grained management and is customizable according to the users
need; some of the use cases supported by the default configuration
are:</para><itemizedlist><listitem><para> Logging request and
response messages: being able to record messages received from and sent to a given service
consumer without stopping the provider may be really useful. You just need to set the
<emphasis>recording</emphasis> attribute of their endpoint's LogRecorder
to true. The added value of this logging solution comes from the use of filters through
which messages coming from a given address and related to a gi!
ven wsdl operation only can be logged.
</para></listitem><listitem><para> Accountability: service
providers may want to know which consumers are actually hitting a given service. This can
be done for example using the <emphasis>getClientHosts</emphasis>
functionality of the MemoryBufferRecorder once it has been switched to recording state.
</para></listitem><listitem><para> Getting statistics, filtering
records: service administrators might want to see the last records related to a given
endpoint or operation, the last records related to messages coming from a given customer
and the response the system gave them, etc. These information can be obtained using the
<emphasis>getRecordsByOperation</emphasis>,
<emphasis>getRecordsByClientHost</emphasis> or the more general
<emphasis>getMatchingRecords</emphasis> functionality of the
MemoryBufferRecorder.</para></listitem></itemizedlist><para> </para></section>
<section
id="JBossWS-Recordsmanagement_How_it_works_and_how_to_use_it"><title>How
it works and how to use it</title><para>The recording system is composed
of</para><itemizedlist><listitem><para> JAX-WS handlers
intercepting inbound and outbound communication
</para></listitem><listitem><para> Record processors plugged into
deployed endpoints; handlers collect records and send them to every processors through the
current endpoint. Processors may store records, convert them, log them, ...
</para></listitem><listitem><para> MBean views of processors that
can be used to configure and fine tune recording at runtime
</para></listitem><listitem><para> Record filters allowing
selection of information to be recorded as well as providing means of performing custom
queries on the saved
records.</para></listitem></itemizedlist><para> </para><section
id="JBossWS-Recordsmanagement_Server_side"><title>Server
side</title><para>On server side records are collected by JAX-WS handlers and
pa!
ssed to the configured processors. JBossWS comes with two default record processors that
are plugged into every endpoint during the
deployment:</para><itemizedlist><listitem><para> LogRecorder: a
simple record processor that writes records to the configured log.
</para></listitem><listitem><para> MemoryBufferRecorder: a record
processor that keeps the last received records in memory and allows user to search / get
statistics on them. </para></listitem></itemizedlist><para>Every
processors can be fine tuned to process some record attributes only according to the user
and/or performance requirements. Default processors are not in recording mode upon
creation, thus you need to switch them to recording mode through their MBean interfaces
(see the <emphasis>Recording</emphasis> flag in the
jmx-console).</para><para>Common processor properties and their respective
defaults values are:</para><itemizedlist><listitem><para>
processDestinationHost (true) </para></listitem><listitem><!
para> processSourceHost (true) </para></listitem><listitem><pa!
ra> proc
essHeaders (true) </para></listitem><listitem><para>
processEnvelope (true) </para></listitem><listitem><para>
processMessageType (true) </para></listitem><listitem><para>
processOperation (true) </para></listitem><listitem><para>
processDate (true) </para></listitem><listitem><para> recording
(false) </para></listitem></itemizedlist><para>The recorders can
be configured in the stacks bean configuration</para><screen
xml:space="preserve"> <!-- Installed Record Processors-->
- <bean name="WSMemoryBufferRecorder"
class="org.jboss.wsf.framework.management.recording.MemoryBufferRecorder">
+ <bean name="WSMemoryBufferRecorder"
class="org.jboss.ws.common.monitoring.MemoryBufferRecorder">
<property name="recording">false</property>
</bean>
- <bean name="WSLogRecorder"
class="org.jboss.wsf.framework.management.recording.LogRecorder">
+ <bean name="WSLogRecorder"
class="org.jboss.ws.common.monitoring.LogRecorder">
<property name="recording">false</property>
</bean>
</screen><para>The recording system is available for all the JBossWS
supported stacks. However slightly different procedure is required to enable it depending
on the used
stack.</para><variablelist><varlistentry><term><emphasis
role="bold">Native stack</emphasis>
</term><listitem/></varlistentry></variablelist><para>Native
stack comes with <ulink
url="http://community.jboss.org/docs/DOC-13512">JBossWS - JAX-WS Endpoint
Configuration</ulink>. The default standard endpoint already has the server side
recording handler:</para><screen xml:space="preserve">
<endpoint-config>
@@ -14,20 +14,20 @@
<javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings>
<javaee:handler>
<javaee:handler-name>Recording
Handler</javaee:handler-name>
-
<javaee:handler-class>org.jboss.wsf.framework.invocation.RecordingServerHandler</javaee:handler-class>
+
<javaee:handler-class>org.jboss.ws.common.invocation.RecordingServerHandler</javaee:handler-class>
</javaee:handler>
</javaee:handler-chain>
</pre-handler-chains>
</endpoint-config>
-</screen><para>thus nothing is required to use it since it is automatically
installed in the pre-handler-chain. Of course you might want to add it to other endpoint
configurations you're
using.</para><variablelist><varlistentry><term><emphasis
role="bold">Metro and CXF stacks
</emphasis></term><listitem/></varlistentry></variablelist><para>Other
stacks require users to manually add the
<emphasis>org.jboss.wsf.framework.invocation.RecordingServerHandler</emphasis>
to their endpoint handler chain. This can be done <link
linkend="chap_JBossWS-UserGuide">the same way common user handlers are
added</link>.</para><para>Once the handler is properly added to the
chain, log recording configuration is agnostic to the used stack. Users just need to tune
the processors parameters though their MBean
interfaces.</para><para> </para></section>
+</screen><para>thus nothing is required to use it since it is automatically
installed in the pre-handler-chain. Of course you might want to add it to other endpoint
configurations you're
using.</para><variablelist><varlistentry><term><emphasis
role="bold">Metro and CXF stacks
</emphasis></term><listitem/></varlistentry></variablelist><para>Other
stacks require users to manually add the
<emphasis>org.jboss.ws.common.invocation.RecordingServerHandler</emphasis> to
their endpoint handler chain. This can be done <link
linkend="chap_JBossWS-UserGuide">the same way common user handlers are
added</link>.</para><para>Once the handler is properly added to the
chain, log recording configuration is agnostic to the used stack. Users just need to tune
the processors parameters though their MBean
interfaces.</para><para> </para></section>
<section id="JBossWS-Recordsmanagement_Client_side"><title>Client
side</title><para>JMX management of processors is of course available on
server side only. However users might also be interested in collecting and processing
records on client side. Since handlers can be set on client side too, customer handlers
could be configured to capture messages almost like the
<emphasis>RecordingServerHandler</emphasis> does. This is left to the users
since it is directly linked to their custom needs. For instance a common use could be to
pass client side collected records to the
LogRecorder.</para><para> </para></section>
</section>
-<section
id="JBossWS-Recordsmanagement_Advanced_hints"><title>Advanced
hints</title><section
id="JBossWS-Recordsmanagement_Adding_custom_recorders"><title>Adding
custom recorders</title><para>As previously said, the recording system is
extensible: JBossWS users can write their own processors and plug them at runtime into
their deployed endpoints through the <emphasis>addRecordProcessor</emphasis>
functionality of the ManagedEndpoint MBean. Every processor needs to implement the
<emphasis>org.jboss.wsf.spi.management.recording.RecordProcessor</emphasis>
interface. Then you can choose one of the two following
options:</para><itemizedlist><listitem><para> Give you record
processor an MBean interface declaring the manageable attributes: the recording system
will plug your processor to the endpoint and register a management MBean for it using your
interface. This allows you to create highly configurable custom processors. For an example
of this development option, take a look at!
the
<emphasis>org.jboss.wsf.framework.management.recording.MemoryBufferRecorder</emphasis>.
</para></listitem><listitem><para> Add your record processor to
the managed endpoint as is: the recording system will plug it to the endpoint and register
a standard management MBean for its basic processing configuration. The
<emphasis>org.jboss.wsf.framework.management.recording.LogRecorder</emphasis>
is an example of this development option.
</para></listitem></itemizedlist><para>A code snippet showing how
to get the MBeanProxy instance which you can invoke MBean with can be found <link
linkend="chap_JBossWS-Endpointmanagement">here</link>.</para></section>
+<section
id="JBossWS-Recordsmanagement_Advanced_hints"><title>Advanced
hints</title><section
id="JBossWS-Recordsmanagement_Adding_custom_recorders"><title>Adding
custom recorders</title><para>As previously said, the recording system is
extensible: JBossWS users can write their own processors and plug them at runtime into
their deployed endpoints through the <emphasis>addRecordProcessor</emphasis>
functionality of the ManagedEndpoint MBean. Every processor needs to implement the
<emphasis>org.jboss.wsf.spi.management.recording.RecordProcessor</emphasis>
interface. Then you can choose one of the two following
options:</para><itemizedlist><listitem><para> Give you record
processor an MBean interface declaring the manageable attributes: the recording system
will plug your processor to the endpoint and register a management MBean for it using your
interface. This allows you to create highly configurable custom processors. For an example
of this development option, take a look at!
the
<emphasis>org.jboss.ws.common.monitoring.MemoryBufferRecorder</emphasis>.
</para></listitem><listitem><para> Add your record processor to
the managed endpoint as is: the recording system will plug it to the endpoint and register
a standard management MBean for its basic processing configuration. The
<emphasis>org.jboss.wsf.framework.management.recording.LogRecorder</emphasis>
is an example of this development option.
</para></listitem></itemizedlist><para>A code snippet showing how
to get the MBeanProxy instance which you can invoke MBean with can be found <link
linkend="chap_JBossWS-Endpointmanagement">here</link>.</para></section>
<section
id="JBossWS-Recordsmanagement_Handlers_position"><title>Handler's
position</title><para>Of course the recording handler's position in the
handler chain influences the collected records. As a matter of fact some information may
or may not be available at a given point of the handler chain execution. The standard
endpoint configuration declares the RecordingServerHandler into the pre-handler-chain.
Speaking of the native stack, this means for example that you'll get the invoked
operation data and that decrypted messages will be recorded if using WS-Security, since
the WS-Security handler runs in the post-handler-chain. Users might want to change the
recording handler's position in the chain according to their
requirements.</para></section>
<section
id="JBossWS-Recordsmanagement_Multiple_handlers"><title>Multiple
handlers</title><para>Records attributes include a record group ID that is
meant to link records whose messages belong to the same message flow (a request-response
for example). In order to set the right group ID to the records, the current ID is
associated to the thread that is processing the endpoint invocation. This means that
multiple related records can be linked together and extracted together from a
processor.</para><para>For this reason, you might want to install multiple
recording handlers into different points of the handler chain. For instance, it could make
sense to record messages both before and after encryption/decryption when using
WS-Security.</para></section>
</section>
<section
id="JBossWS-Recordsmanagement_Future_extensions"><title>Future
extensions</title><para>This paragraph covers eventual future extensions
and/or idea JBossWS users may want to leverage for their own
business.</para><section
id="JBossWS-Recordsmanagement_Database_recorder"><title>Database
recorder</title><para>The MemoryBufferRecorder provides interesting
functionalities to query the collected records set. For obvious reasons, records are
discarded once a given size of the buffer is reached.</para><para>A DB based
recorder could be developed; it should work the same way the MemoryBufferRecorder does,
except for records that should be saved through a given datasource. This will provide
persistence of data even in case of application server reboot and webservice application
redeploy. It will also allow records coming from different node of a cluster to be stored
together. Finally this would allow administrators to directly query the database, which
might be far more eff!
icient.</para></section>
<section
id="JBossWS-Recordsmanagement_Custom_log_writer"><title>Custom log
writer</title><para>The idea of getting statistics from collected records
could be further exploited getting custom logs from the records. These logs could be
outputted by a custom processor in standard or proprietary formats allowing them to be
imported into eventual third-party log processing tools which might offer complex/funky
graphic or statistic functionalities and so on.</para></section>
</section>
-<section
id="JBossWS-Recordsmanagement_References"><title>References</title><para>You
might want to take a look at the
<emphasis>org.jboss.wsf.framework.management.recording</emphasis> and
<emphasis>org.jboss.wsf.spi.management.recording</emphasis> packages in the
source code to better understand how all this works and can be
used.</para></section>
+<section
id="JBossWS-Recordsmanagement_References"><title>References</title><para>You
might want to take a look at the
<emphasis>org.jboss.ws.common.monitoring</emphasis> and
<emphasis>org.jboss.wsf.spi.management.recording</emphasis> packages in the
source code to better understand how all this works and can be
used.</para></section>
</chapter>
\ No newline at end of file
Modified:
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/WebServiceContextFactoryImpl.java
===================================================================
---
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/WebServiceContextFactoryImpl.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/WebServiceContextFactoryImpl.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -24,8 +24,8 @@
import javax.xml.ws.handler.MessageContext;
import org.apache.cxf.jaxws.context.WebServiceContextImpl;
-import org.jboss.wsf.common.invocation.WebServiceContextEJB;
-import org.jboss.wsf.common.invocation.WebServiceContextJSE;
+import org.jboss.ws.common.invocation.WebServiceContextEJB;
+import org.jboss.ws.common.invocation.WebServiceContextJSE;
import org.jboss.wsf.spi.invocation.ExtensibleWebServiceContext;
import org.jboss.wsf.spi.invocation.InvocationType;
import org.jboss.wsf.spi.invocation.WebServiceContextFactory;
Modified:
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/BusDeploymentAspect.java
===================================================================
---
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/BusDeploymentAspect.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/BusDeploymentAspect.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -30,8 +30,8 @@
import org.apache.cxf.BusFactory;
import org.apache.cxf.configuration.Configurer;
import org.jboss.ws.api.binding.BindingCustomization;
-import org.jboss.wsf.common.integration.AbstractDeploymentAspect;
-import org.jboss.wsf.common.integration.WSConstants;
+import org.jboss.ws.common.integration.AbstractDeploymentAspect;
+import org.jboss.ws.common.integration.WSConstants;
import org.jboss.wsf.spi.deployment.ArchiveDeployment;
import org.jboss.wsf.spi.deployment.Deployment;
import org.jboss.wsf.spi.deployment.ResourceResolver;
Modified:
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/DescriptorDeploymentAspect.java
===================================================================
---
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/DescriptorDeploymentAspect.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/DescriptorDeploymentAspect.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -27,8 +27,8 @@
import java.util.Map;
import org.jboss.logging.Logger;
-import org.jboss.wsf.common.integration.AbstractDeploymentAspect;
-import org.jboss.wsf.common.integration.WSConstants;
+import org.jboss.ws.common.integration.AbstractDeploymentAspect;
+import org.jboss.ws.common.integration.WSConstants;
import org.jboss.wsf.spi.deployment.ArchiveDeployment;
import org.jboss.wsf.spi.deployment.Deployment;
import org.jboss.wsf.spi.deployment.Deployment.DeploymentType;
@@ -170,7 +170,7 @@
*
* @param dep webservice deployment
* @param cxfURL CXF DD URL
- * @see org.jboss.wsf.common.integration.WSConstants.STACK_CONTEXT_PARAMS
+ * @see org.jboss.ws.common.integration.WSConstants.STACK_CONTEXT_PARAMS
*/
@SuppressWarnings("unchecked")
private void putCXFConfigToDeployment(Deployment dep, URL cxfURL)
Modified:
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/JMSEndpointDeploymentAspect.java
===================================================================
---
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/JMSEndpointDeploymentAspect.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/JMSEndpointDeploymentAspect.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -21,7 +21,7 @@
*/
package org.jboss.wsf.stack.cxf.deployment.aspect;
-import org.jboss.wsf.common.integration.JMSDeploymentAspect;
+import org.jboss.ws.common.integration.JMSDeploymentAspect;
import org.jboss.wsf.spi.deployment.Deployment;
import org.jboss.wsf.stack.cxf.client.util.SpringUtils;
Modified:
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/JMSEndpointDeploymentAspectDelegate.java
===================================================================
---
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/JMSEndpointDeploymentAspectDelegate.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/JMSEndpointDeploymentAspectDelegate.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -25,7 +25,7 @@
import org.apache.cxf.Bus;
import org.apache.cxf.BusFactory;
-import org.jboss.wsf.common.integration.JMSDeploymentAspect;
+import org.jboss.ws.common.integration.JMSDeploymentAspect;
import org.jboss.wsf.spi.deployment.Deployment;
import org.jboss.wsf.spi.metadata.jms.JMSEndpointsMetaData;
import org.jboss.wsf.stack.cxf.client.configuration.JBossWSSpringBusFactory;
Modified:
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/JMSEndpointRegistryDeploymentAspect.java
===================================================================
---
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/JMSEndpointRegistryDeploymentAspect.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/JMSEndpointRegistryDeploymentAspect.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -21,7 +21,7 @@
*/
package org.jboss.wsf.stack.cxf.deployment.aspect;
-import org.jboss.wsf.common.integration.JMSDeploymentAspect;
+import org.jboss.ws.common.integration.JMSDeploymentAspect;
import org.jboss.wsf.spi.deployment.Deployment;
import org.jboss.wsf.stack.cxf.client.util.SpringUtils;
Modified:
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/JMSEndpointRegistryDeploymentAspectDelegate.java
===================================================================
---
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/JMSEndpointRegistryDeploymentAspectDelegate.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/JMSEndpointRegistryDeploymentAspectDelegate.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -32,7 +32,7 @@
import org.apache.cxf.transport.Destination;
import org.apache.cxf.transport.jms.JMSConfiguration;
import org.apache.cxf.transport.jms.JMSDestination;
-import org.jboss.wsf.common.integration.JMSDeploymentAspect;
+import org.jboss.ws.common.integration.JMSDeploymentAspect;
import org.jboss.wsf.spi.SPIProvider;
import org.jboss.wsf.spi.SPIProviderResolver;
import org.jboss.wsf.spi.deployment.Deployment;
Modified:
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/ResourceResolverDeploymentAspect.java
===================================================================
---
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/ResourceResolverDeploymentAspect.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/deployment/aspect/ResourceResolverDeploymentAspect.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -21,7 +21,7 @@
*/
package org.jboss.wsf.stack.cxf.deployment.aspect;
-import org.jboss.wsf.common.integration.AbstractDeploymentAspect;
+import org.jboss.ws.common.integration.AbstractDeploymentAspect;
import org.jboss.wsf.spi.deployment.ArchiveDeployment;
import org.jboss.wsf.spi.deployment.Deployment;
import org.jboss.wsf.spi.deployment.Endpoint;
Modified:
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/metadata/MetadataBuilder.java
===================================================================
---
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/metadata/MetadataBuilder.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/metadata/MetadataBuilder.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -34,7 +34,7 @@
import javax.xml.ws.soap.SOAPBinding;
import org.jboss.logging.Logger;
-import org.jboss.wsf.common.JavaUtils;
+import org.jboss.ws.common.JavaUtils;
import org.jboss.wsf.spi.deployment.ArchiveDeployment;
import org.jboss.wsf.spi.deployment.Deployment;
import org.jboss.wsf.spi.deployment.Deployment.DeploymentType;
Modified:
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/metadata/services/DDBeans.java
===================================================================
---
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/metadata/services/DDBeans.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/metadata/services/DDBeans.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -31,7 +31,7 @@
import java.util.List;
import org.jboss.wsf.spi.deployment.WSFDeploymentException;
-import org.jboss.wsf.common.IOUtils;
+import org.jboss.ws.common.IOUtils;
/**
* Metadata model for cxf.xml
Modified:
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/transport/ServletHelper.java
===================================================================
---
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/transport/ServletHelper.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/server/src/main/java/org/jboss/wsf/stack/cxf/transport/ServletHelper.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -41,8 +41,8 @@
import org.apache.cxf.jaxws.support.JaxWsEndpointImpl;
import org.apache.cxf.management.InstrumentationManager;
import org.apache.cxf.management.counters.CounterRepository;
-import org.jboss.wsf.common.ObjectNameFactory;
-import org.jboss.wsf.common.injection.InjectionHelper;
+import org.jboss.ws.common.ObjectNameFactory;
+import org.jboss.ws.common.injection.InjectionHelper;
import org.jboss.wsf.spi.SPIProvider;
import org.jboss.wsf.spi.SPIProviderResolver;
import org.jboss.wsf.spi.classloading.ClassLoaderProvider;
Modified: stack/cxf/trunk/modules/server/src/main/resources/jbossws-cxf-config-as6.xml
===================================================================
---
stack/cxf/trunk/modules/server/src/main/resources/jbossws-cxf-config-as6.xml 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/server/src/main/resources/jbossws-cxf-config-as6.xml 2011-05-06
20:15:01 UTC (rev 14289)
@@ -6,12 +6,12 @@
<bean name="CXFInitializer"
class="org.jboss.wsf.stack.cxf.config.CXFInitializer" />
<!-- The registry for web service endpoints -->
- <bean name="WSEndpointRegistry"
class="org.jboss.wsf.framework.management.ManagedEndpointRegistry">
+ <bean name="WSEndpointRegistry"
class="org.jboss.ws.common.management.ManagedEndpointRegistry">
<property name="mbeanServer"><inject
bean="WSMBeanServerLocator"
property="mbeanServer"/></property>
</bean>
<!-- Logging redirector -->
- <bean name="JDKLogRedirector"
class="org.jboss.wsf.common.logging.JDKLogRedirector">
+ <bean name="JDKLogRedirector"
class="org.jboss.ws.common.logging.JDKLogRedirector">
<property name="namespaces">
<list class="java.util.LinkedList"
elementClass="java.lang.String">
<value>org.apache.cxf</value>
@@ -20,7 +20,7 @@
</bean>
<!-- This should actually be in the stack-agnostic config file, it's here to
avoid installing a CI -->
- <bean name="WSDescriptorParser"
class="org.jboss.wsf.framework.deployment.WebservicesDescriptorParserImpl">
+ <bean name="WSDescriptorParser"
class="org.jboss.ws.common.deployment.WebservicesDescriptorParserImpl">
<property name="descriptorName">webservices.xml</property>
</bean>
@@ -29,15 +29,15 @@
</bean>
<!-- Installed Record Processors-->
- <bean name="WSMemoryBufferRecorder"
class="org.jboss.wsf.framework.management.recording.MemoryBufferRecorder">
+ <bean name="WSMemoryBufferRecorder"
class="org.jboss.ws.common.monitoring.MemoryBufferRecorder">
<property name="recording">false</property>
</bean>
- <bean name="WSLogRecorder"
class="org.jboss.wsf.framework.management.recording.LogRecorder">
+ <bean name="WSLogRecorder"
class="org.jboss.ws.common.monitoring.LogRecorder">
<property name="recording">false</property>
</bean>
<!-- The stack specific deployment aspects -->
- <bean name="WSCXFContextPropertiesDeploymentAspect"
class="org.jboss.wsf.framework.deployment.ContextPropertiesDeploymentAspect">
+ <bean name="WSCXFContextPropertiesDeploymentAspect"
class="org.jboss.ws.common.deployment.ContextPropertiesDeploymentAspect">
<property name="provides">ContextProperties</property>
<property name="contextProperties">
<map keyClass="java.lang.String"
valueClass="java.lang.String">
@@ -64,13 +64,13 @@
<property name="forJaxRpc">false</property>
</bean>
- <bean name="WSCXFEndpointHandlerDeploymentAspect"
class="org.jboss.wsf.framework.deployment.EndpointHandlerDeploymentAspect">
+ <bean name="WSCXFEndpointHandlerDeploymentAspect"
class="org.jboss.ws.common.deployment.EndpointHandlerDeploymentAspect">
<property name="requires">ContainerMetaData</property>
<property name="provides">StackEndpointHandler</property>
<property name="forJaxRpc">false</property>
</bean>
- <bean name="WSCXFEndpointRecordProcessorDeploymentAspect"
class="org.jboss.wsf.framework.deployment.EndpointRecordProcessorDeploymentAspect">
+ <bean name="WSCXFEndpointRecordProcessorDeploymentAspect"
class="org.jboss.ws.common.deployment.EndpointRecordProcessorDeploymentAspect">
<property name="mbeanServer"><inject
bean="WSMBeanServerLocator"
property="mbeanServer"/></property>
<property name="requires">RegisteredEndpoint</property>
<property name="provides">EndpointRecordProcessors</property>
@@ -83,7 +83,7 @@
<property name="forJaxRpc">false</property>
</bean>
- <bean name="WSCXFJAXBIntroDeploymentAspect"
class="org.jboss.wsf.framework.deployment.JAXBIntroDeploymentAspect">
+ <bean name="WSCXFJAXBIntroDeploymentAspect"
class="org.jboss.ws.common.deployment.JAXBIntroDeploymentAspect">
<property name="provides">JAXBIntros</property>
<property name="forJaxRpc">false</property>
</bean>
Modified: stack/cxf/trunk/modules/server/src/main/resources/jbossws-cxf-config-as7.xml
===================================================================
---
stack/cxf/trunk/modules/server/src/main/resources/jbossws-cxf-config-as7.xml 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/server/src/main/resources/jbossws-cxf-config-as7.xml 2011-05-06
20:15:01 UTC (rev 14289)
@@ -24,7 +24,7 @@
<deploymentAspects xmlns="urn:jboss:ws:deployment:aspects:1.0">
- <deploymentAspect
class="org.jboss.wsf.framework.deployment.ContextPropertiesDeploymentAspect">
+ <deploymentAspect
class="org.jboss.ws.common.deployment.ContextPropertiesDeploymentAspect">
<property name="provides"
class="java.lang.String">ContextProperties</property>
<property name="contextProperties"
class="java.util.HashMap">
<map keyClass="java.lang.String"
valueClass="java.lang.String">
@@ -51,13 +51,13 @@
<property name="forJaxRpc"
class="boolean">false</property>
</deploymentAspect>
- <deploymentAspect
class="org.jboss.wsf.framework.deployment.EndpointHandlerDeploymentAspect">
+ <deploymentAspect
class="org.jboss.ws.common.deployment.EndpointHandlerDeploymentAspect">
<property name="requires"
class="java.lang.String">ContainerMetaData</property>
<property name="provides"
class="java.lang.String">StackEndpointHandler</property>
<property name="forJaxRpc"
class="boolean">false</property>
</deploymentAspect>
- <deploymentAspect
class="org.jboss.wsf.framework.deployment.JAXBIntroDeploymentAspect">
+ <deploymentAspect
class="org.jboss.ws.common.deployment.JAXBIntroDeploymentAspect">
<property name="provides"
class="java.lang.String">JAXBIntros</property>
<property name="forJaxRpc"
class="boolean">false</property>
</deploymentAspect>
@@ -81,7 +81,7 @@
<property name="forJaxRpc"
class="boolean">false</property>
</deploymentAspect>
- <deploymentAspect
class="org.jboss.wsf.framework.deployment.EndpointRecordProcessorDeploymentAspect">
+ <deploymentAspect
class="org.jboss.ws.common.deployment.EndpointRecordProcessorDeploymentAspect">
<property name="mbeanServer"><inject
bean="WSMBeanServerLocator"
property="mbeanServer"/></property>
<property name="requires"
class="java.lang.String">RegisteredEndpoint</property>
<property name="provides"
class="java.lang.String">EndpointRecordProcessors</property>
Modified:
stack/cxf/trunk/modules/server/src/main/resources/jbossws-cxf-server.jar/META-INF/services/org.jboss.wsf.spi.DeploymentAspectManagerLocator
===================================================================
---
stack/cxf/trunk/modules/server/src/main/resources/jbossws-cxf-server.jar/META-INF/services/org.jboss.wsf.spi.DeploymentAspectManagerLocator 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/server/src/main/resources/jbossws-cxf-server.jar/META-INF/services/org.jboss.wsf.spi.DeploymentAspectManagerLocator 2011-05-06
20:15:01 UTC (rev 14289)
@@ -1 +1 @@
-org.jboss.wsf.framework.DeploymentAspectManagerLocatorImpl
\ No newline at end of file
+org.jboss.ws.common.DeploymentAspectManagerLocatorImpl
\ No newline at end of file
Modified: stack/cxf/trunk/modules/server/src/main/resources/jbossws-jaxrpc-config-as6.xml
===================================================================
---
stack/cxf/trunk/modules/server/src/main/resources/jbossws-jaxrpc-config-as6.xml 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/server/src/main/resources/jbossws-jaxrpc-config-as6.xml 2011-05-06
20:15:01 UTC (rev 14289)
@@ -3,7 +3,7 @@
<deployment xmlns="urn:jboss:bean-deployer:2.0">
<!-- The stack specific deployment aspects -->
- <bean name="WSNativeContextPropertiesDeploymentAspect"
class="org.jboss.wsf.framework.deployment.ContextPropertiesDeploymentAspect">
+ <bean name="WSNativeContextPropertiesDeploymentAspect"
class="org.jboss.ws.common.deployment.ContextPropertiesDeploymentAspect">
<property name="provides">ContextProperties,
StackDescriptor</property>
<property name="contextProperties">
<map keyClass="java.lang.String"
valueClass="java.lang.String">
@@ -22,7 +22,7 @@
<property name="forJaxWs">false</property>
</bean>
- <bean name="WSNativeEndpointHandlerDeploymentAspect"
class="org.jboss.wsf.framework.deployment.EndpointHandlerDeploymentAspect">
+ <bean name="WSNativeEndpointHandlerDeploymentAspect"
class="org.jboss.ws.common.deployment.EndpointHandlerDeploymentAspect">
<property name="requires">ContainerMetaData</property>
<property name="provides">StackEndpointHandler</property>
<property name="forJaxWs">false</property>
Modified:
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/wsrm/BasicDocTestCase.java
===================================================================
---
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/wsrm/BasicDocTestCase.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/wsrm/BasicDocTestCase.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -28,7 +28,7 @@
import junit.framework.Test;
-import org.jboss.wsf.common.DOMUtils;
+import org.jboss.ws.common.DOMUtils;
import org.jboss.wsf.test.JBossWSCXFTestSetup;
import org.jboss.wsf.test.JBossWSTest;
import org.w3c.dom.Element;
Modified:
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/wsrm/BasicRPCTestCase.java
===================================================================
---
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/wsrm/BasicRPCTestCase.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/wsrm/BasicRPCTestCase.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -28,7 +28,7 @@
import junit.framework.Test;
-import org.jboss.wsf.common.DOMUtils;
+import org.jboss.ws.common.DOMUtils;
import org.jboss.wsf.test.JBossWSCXFTestSetup;
import org.jboss.wsf.test.JBossWSTest;
import org.w3c.dom.Element;
Modified:
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/samples/jmsendpoints/jmstransport/JMSEndpointsTestCase.java
===================================================================
---
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/samples/jmsendpoints/jmstransport/JMSEndpointsTestCase.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/samples/jmsendpoints/jmstransport/JMSEndpointsTestCase.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -38,8 +38,8 @@
import junit.framework.TestSuite;
import org.apache.cxf.transport.jms.spec.JMSSpecConstants;
-import org.jboss.wsf.common.DOMUtils;
-import org.jboss.wsf.common.ObjectNameFactory;
+import org.jboss.ws.common.DOMUtils;
+import org.jboss.ws.common.ObjectNameFactory;
import org.jboss.wsf.test.JBossWSCXFTestSetup;
import org.jboss.wsf.test.JBossWSTest;
import org.jboss.wsf.test.JBossWSTestHelper;
Modified:
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/samples/jmstransport/FromJavaJMSTransportTestCase.java
===================================================================
---
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/samples/jmstransport/FromJavaJMSTransportTestCase.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/samples/jmstransport/FromJavaJMSTransportTestCase.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -38,8 +38,8 @@
import junit.framework.TestSuite;
import org.jboss.test.ws.jaxws.samples.jmsendpoints.jmstransport.JMSEndpointsTestCase;
-import org.jboss.wsf.common.DOMUtils;
-import org.jboss.wsf.common.ObjectNameFactory;
+import org.jboss.ws.common.DOMUtils;
+import org.jboss.ws.common.ObjectNameFactory;
import org.jboss.wsf.test.JBossWSTest;
import org.jboss.wsf.test.JBossWSTestHelper;
import org.jboss.wsf.test.JBossWSTestSetup;
Modified:
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/samples/jmstransport/JMSTransportTestCase.java
===================================================================
---
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/samples/jmstransport/JMSTransportTestCase.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/testsuite/cxf-spring-tests/src/test/java/org/jboss/test/ws/jaxws/samples/jmstransport/JMSTransportTestCase.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -46,8 +46,8 @@
import org.apache.cxf.frontend.ClientProxy;
import org.apache.cxf.interceptor.LoggingInInterceptor;
import org.apache.cxf.interceptor.LoggingOutInterceptor;
-import org.jboss.wsf.common.DOMUtils;
-import org.jboss.wsf.common.ObjectNameFactory;
+import org.jboss.ws.common.DOMUtils;
+import org.jboss.ws.common.ObjectNameFactory;
import org.jboss.wsf.test.JBossWSCXFTestSetup;
import org.jboss.wsf.test.JBossWSTest;
import org.jboss.wsf.test.JBossWSTestHelper;
Modified:
stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/jaxbintros/JAXBIntroTestCase.java
===================================================================
---
stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/jaxbintros/JAXBIntroTestCase.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/jaxbintros/JAXBIntroTestCase.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -29,7 +29,7 @@
import junit.framework.Test;
-import org.jboss.wsf.common.DOMUtils;
+import org.jboss.ws.common.DOMUtils;
import org.jboss.wsf.test.JBossWSCXFTestSetup;
import org.jboss.wsf.test.JBossWSTest;
import org.w3c.dom.Element;
Modified:
stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/logging/JDKLoggingTestCase.java
===================================================================
---
stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/logging/JDKLoggingTestCase.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/logging/JDKLoggingTestCase.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -24,7 +24,7 @@
import java.util.logging.Handler;
import java.util.logging.Logger;
-import org.jboss.wsf.common.logging.JDKLogHandler;
+import org.jboss.ws.common.logging.JDKLogHandler;
import org.jboss.wsf.test.JBossWSTest;
/**
Modified:
stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/jaxws/samples/mtom/MtomTestCase.java
===================================================================
---
stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/jaxws/samples/mtom/MtomTestCase.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/jaxws/samples/mtom/MtomTestCase.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -32,7 +32,7 @@
import org.apache.cxf.helpers.IOUtils;
import org.jboss.wsf.test.JBossWSCXFTestSetup;
-import org.jboss.wsf.common.DOMUtils;
+import org.jboss.ws.common.DOMUtils;
import org.jboss.wsf.test.JBossWSTest;
import org.w3c.dom.Element;
import org.w3c.dom.NodeList;
Modified:
stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/saaj/jbws3084/ServiceImpl.java
===================================================================
---
stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/saaj/jbws3084/ServiceImpl.java 2011-05-06
20:12:14 UTC (rev 14288)
+++
stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/saaj/jbws3084/ServiceImpl.java 2011-05-06
20:15:01 UTC (rev 14289)
@@ -35,7 +35,7 @@
import javax.xml.ws.WebServiceContext;
import javax.xml.ws.handler.MessageContext;
-import org.jboss.wsf.common.IOUtils;
+import org.jboss.ws.common.IOUtils;
@WebService(portName = "SaajServicePort", serviceName =
"SaajService", wsdlLocation = "WEB-INF/wsdl/SaajService.wsdl",
targetNamespace = "http://www.jboss.org/jbossws/saaj", endpointInterface =
"org.jboss.test.ws.saaj.jbws3084.ServiceIface")
public class ServiceImpl implements ServiceIface