Author: alessio.soldano(a)jboss.com Date: 2013-04-16 12:09:00 -0400 (Tue, 16 Apr 2013) New Revision: 17495 Modified: stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/noIntegration/DisabledWSSubsystemTestCase.java Log: Fixing comment Modified: stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/noIntegration/DisabledWSSubsystemTestCase.java =================================================================== --- stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/noIntegration/DisabledWSSubsystemTestCase.java 2013-04-15 23:23:31 UTC (rev 17494) +++ stack/cxf/trunk/modules/testsuite/cxf-tests/src/test/java/org/jboss/test/ws/jaxws/cxf/noIntegration/DisabledWSSubsystemTestCase.java 2013-04-16 16:09:00 UTC (rev 17495) @@ -38,7 +38,7 @@ * Verifies a plain Apache CXF ws endpoint war can be deployed on * AS similarly as on a Tomcat instance (the Apache CXF libs from * the AS modules are used instead of embedding them in the war). - * This is is NOT the suggest approach as any Java EE support is + * This is is NOT the suggested approach as any Java EE support is * actually disabled / skipped (including any JBossWS-CXF * integration additions, JSR-109, etc.) *