CWSCA0001W: \"{0}\" is not a valid Service Component Definition Language (SCDL) file for the reason: {1}.
Explanation: The file does not conform to the SCDL schema
User Action: Check the file to make sure it conforms to the SCDL schema

 

CWSCA0002W: The namespace \"{0}\" has already been registered.

 

CWSCA2001E: The SCA MDB ran into exception {0}

 

CWSCA2002W: The SCA MDB fails to store error message with id {0}, exception {1}

 

CWSCA2003W: The SCA MDB fails to retrieve error message with id {0}, exception {1}

 

CWSCA2004W: The SCA MDB fails to send error message with id {0}, exception {1}

 

CWSCA2005W: The SCA Asynchronous Source Handler was invoked with the wrong interaction type: {0}

 

CWSCA2006W: The SCA Asynchronous Target Handler was invoked with the wrong interaction type: {0}

 

CWSCA2007E: The SCA link mediation received exception {0}

 

CWSCA2008W: The SCA MDB fails to restore the original system classloader, exception {0}

 

CWSCA3001I: The SCA runtime is initializing.

 

CWSCA3002I: The SCA runtime has been initialized.

 

CWSCA3003I: The SCA runtime is being destroyed.

 

CWSCA3004I: The SCA runtime has been destroyed.

 

CWSCA3005I: The SCA runtime is starting.

 

CWSCA3006I: The SCA runtime started successfully.

 

CWSCA3007I: The SCA runtime is stopping.

 

CWSCA3008I: The SCA runtime has been stopped.

 

CWSCA3009I: The SCA module {0} is starting.

 

CWSCA3010I: The SCA module started successfully.

 

CWSCA3011I: The SCA module {0} is stopping.

 

CWSCA3012I: The SCA module has been stopped.

 

CWSCA3013I: Resources for the SCA application {0} are being configured.

 

CWSCA3014I: Resources for the SCA application {0} have been configured successfully.

 

CWSCA3015I: Resources for the SCA application {0} were not configured.

 

CWSCA3016I: Archive {0} is being processed.

 

CWSCA3017I: Installation task {0} is running.

 

CWSCA3018I: Resources for the SCA application {0} are being removed.

 

CWSCA3019I: Resources for the SCA application {0} have been removed successfully.

 

CWSCA3020I: The SCA application {0} is being updated.

 

CWSCA3021I: The SCA application {0} has been updated.

 

CWSCA3022E: The SCA application {0} was not updated; exception {1} occurred.

 

CWSCA3023I: The EAR file {0} is being loaded for the SCA module.

 

CWSCA3024W: The operation failed due to exception {0}.

 

CWSCA4001I: SCA module artifacts are being installed for resource adapter {0}

 

CWSCA4002I: Custom properties for the SCA module resource adapter are being configured.

 

CWSCA4003I: SCA module {0} destination on service integration bus \"{1}\" with JNDI name \"{2}\" and type \"{3}\" is being installed.

 

CWSCA4004I: SCA module {0} destination JNDI name \"{1}\" is being installed.

 

CWSCA4005I: SCA module {0} ActivationSpec JNDI name \"{1}\" is being installed.

 

CWSCA4006I: SCA module {0} connection factory JNDI name \"{1}\" is being installed.

 

CWSCA4007I: SCDL module {0} is being loaded. Import \"{1}\".

 

CWSCA4008I: SCDL module {0} is being loaded. Export \"{1}\".

 

CWSCA5001I: Could not find a messaging engine for the destination. The deployment target \"{0}\" has not been prepared to have SCA applications deployed to it. Prepare \"{0}\" by creating the appropriate messaging engines or defining the server or cluster to host the messaging engines.

 

CWSCA5002I: Could not find a messaging engine for the destination. The deployment target \"{0}\" has been configured to host destinations at \"{1}\". \"{1}\" has not been prepared for creating the destinations. Prepare \"{1}\" by creating the appropriate messaging engines.