--- glassfishV2/trunk/SRC/glassfish/appserv-commons/src/java/com/sun/logging/enterprise/system/util/LogStrings.properties	(revision 1955)
+++ glassfishV2/trunk/SRC/glassfish/appserv-commons/src/java/com/sun/logging/enterprise/system/util/LogStrings.properties	(revision 1956)
@@ -17,7 +17,7 @@
 enterprise_util.orbmgr_config_excep=UTIL6008:ConfigException in ORBManager.
 enterprise_util.excep_in_createorb=UTIL6009:Unexcpected Exception in createORB.
 enterprise_util.cannot_load_library=UTIL6010:Error Cannot load library. [{0}]
-enterprise_util.prop_jms_client_id_deprec=UTIL6011:'jms-client-id' is an obsolete property.  Set client id on a JMS Connection Factory and use the 'mdb-connection-factory'  property instead.
+enterprise_util.prop_jms_client_id_deprec=UTIL6011:''jms-client-id'' is an obsolete property.  Set client id on a JMS Connection Factory and use the ''mdb-connection-factory''  property instead.
 enterprise_util.mdb_with_cmt_jms_ack=UTIL6012:message-driven beans with container-managed transactions can't have a jms acknowledge mode.
 enterprise_util.entity_bmt_n_session_mlt=UTIL6013:You have chosen to make this bean manage its own transactions. This is illegal for entity beans, and the (session) bean cannot specifiy any method level container transactions.
 enterprise_util.error_converting_prop_file=UTIL6014: error converting properties file.
--- glassfishV2/trunk/SRC/glassfish/appserv-commons/src/java/com/sun/logging/enterprise/resource/resourceadapter/LogStrings.properties	(revision 1955)
+++ glassfishV2/trunk/SRC/glassfish/appserv-commons/src/java/com/sun/logging/enterprise/resource/resourceadapter/LogStrings.properties	(revision 1956)
@@ -41,20 +41,20 @@
 RAR5045.diag.cause.2=The Naming provider is not up
 RAR5045.diag.check.1=Check the jndi.properties file has the naming provider host and port specified
 RAR5045.diag.check.2=Check if the naming provider is up and listening on the port specified in the domain.xml
-jndi.factory_load_error=RAR5009:Cannot load external-jndi-resource factory-class '[{0}]'
+jndi.factory_load_error=RAR5009:Cannot load external-jndi-resource factory-class [{0}]
 RAR5009.diag.cause.1=Could not create an instance of factory-class.
 RAR5009.diag.check.1=Make sure that factory-class name is configured correctly.
 RAR5009.diag.check.2=Make sure that factory-class is available in the classpath of the application server
-jndi.factory_class_unexpected=RAR5010:external-jndi-resource factory-class '[{0}]' must be of type javax.naming.spi.InitialContextFactory
+jndi.factory_class_unexpected=RAR5010:external-jndi-resource factory-class [{0}] must be of type javax.naming.spi.InitialContextFactory
 RAR5010.diag.cause.1=External JNDI resource has a wrong factory-class configuration
 RAR5010.diag.check.1=Verify that factory class is an instance of javax.naming.spi.InitialContextFactory
-jndi.initial_context_error=RAR5011:Exception thrown creating initial context for external JNDI factory '[{0}]'
+jndi.initial_context_error=RAR5011:Exception thrown creating initial context for external JNDI factory [{0}]
 RAR5011.diag.cause.1=Could not create Initial Context.
 RAR5011.diag.check.1=Make sure that the external-jndi-resource configuration is sufficient to create an initial context.
 jndi.initial_context_error_excp=RAR5047:Exception thrown creating initial context for external JNDI factory [{0}]
 RAR5047.diag.cause.1=Could not create Initial Context.
 RAR5047.diag.check.1=Make sure that the external-jndi-resource configuration is sufficient to create an initial context.
-jndi.factory_create_error=RAR5012:Cannot create external-jndi-resource factory-class '[{0}]'
+jndi.factory_create_error=RAR5012:Cannot create external-jndi-resource factory-class [{0}]
 RAR5012.diag.cause.1=Could not create Initial context factory.
 RAR5012.diag.check.1=Make sure that the external-jndi-resource configuration is sufficient to create an initial context factory
 jndi.factory_install_error=RAR5013:Error in installing connection factories