You are viewing a plain text version of this content. The canonical link for it is here.
Posted to axis-cvs@ws.apache.org by na...@apache.org on 2006/11/17 06:24:57 UTC
svn commit: r476052 - in /webservices/axis2/trunk/java/modules:
integration/test/org/apache/axis2/engine/CallUnregisteredServiceTest.java
kernel/src/org/apache/axis2/i18n/resource.properties
Author: nagy
Date: Thu Nov 16 21:24:50 2006
New Revision: 476052
URL: http://svn.apache.org/viewvc?view=rev&rev=476052
Log:
Ported r466399, r467871, and r467877 (Improved message text in resource.properties files)
Modified:
webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/engine/CallUnregisteredServiceTest.java
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/i18n/resource.properties
Modified: webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/engine/CallUnregisteredServiceTest.java
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/engine/CallUnregisteredServiceTest.java?view=diff&rev=476052&r1=476051&r2=476052
==============================================================================
--- webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/engine/CallUnregisteredServiceTest.java (original)
+++ webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/engine/CallUnregisteredServiceTest.java Thu Nov 16 21:24:50 2006
@@ -80,7 +80,7 @@
fail("The test must fail due to wrong service Name");
} catch (AxisFault e) {
- assertTrue(e.getMessage().indexOf("Service not found") >= 0);
+ assertTrue(e.getMessage().indexOf("service could not be found") >= 0);
tearDown();
return;
}
Modified: webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/i18n/resource.properties
URL: http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/i18n/resource.properties?view=diff&rev=476052&r1=476051&r2=476052
==============================================================================
--- webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/i18n/resource.properties (original)
+++ webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/i18n/resource.properties Thu Nov 16 21:24:50 2006
@@ -23,214 +23,214 @@
builtOn=Built on @TODAY@
#############################################################################
-threadpoolshutdown=Thread pool has already been shutdown
+threadpoolshutdown=Thread pool is shut down.
errorWhileSafeShutDown=Error during safe shutdown
-invaliduser=Invalid user name
-invalidSOAPversion=Invalid SOAP URI. Axis2 only supports SOAP 1.1 and 1.2
-cannotInferTransport=Cannot infer transport information from the URL {0}
-cannotInferTransportNoAddr=No address information in EPR, cannot infer transport
-cannotBeNullAxisOperation=Axis Operation can not be null
-cannotBeNullServiceContext=ServiceContext can not be null
-cannotBeNullConfigurationContext=ConfigurationContext can not be null
-cannotBeNullOperationContext=OperationContext can not be null
-nowhereToSendError=Nowhere to send the error, the return response path is missing and fault to has not been specified
-errorwhileProcessingFault=Error occured while processing fault, previous error is given in the stack trace.
-unSupportedMEP=Unsupported MEP {0}
-mepClientSupportOnly=This MEP client supports only {0} , and Axis operations supplied supports {1}
-inputstreamNull=Incoming message input stream is null
-unknownTransport=Unknown transport {0}
-paramIsNotSpecified={0} parameter is not specified
-groovyNoanswer=No answer received from groovy!!!!
-groovyUnableToLoad=Cannot load {0}
-outMessageNull=The out message is NULL, nothing to write
-canNotBeNull={0} can not be NULL
-notFound={0} not found
-transportError=Transport error {0} . Error Message is {1}
-httpTransportError=HTTP Transport error : ''{0}'' - ''{1}''
-preatureEOS=Premature end of stream
+invaliduser=The user name is not valid.
+invalidSOAPversion=The SOAP URI is not valid. Axis2 supports SOAP Version 1.1 and 1.2 only.
+cannotInferTransport=The system cannot infer the transport information from the {0} URL.
+cannotInferTransportNoAddr=Address information does not exist in the Endpoint Reference (EPR).The system cannot infer the transport mechanism.
+cannotBeNullAxisOperation=The Axis operation cannot be null.
+cannotBeNullServiceContext=The ServiceContext cannot be null.
+cannotBeNullConfigurationContext=The ConfigurationContext cannot be null.
+cannotBeNullOperationContext=The OperationContext cannot be null.
+nowhereToSendError=The return response path is missing and fault to is not specified.
+errorwhileProcessingFault=An error occurred while processing the fault. See the previous error in the stack trace for more information.
+unSupportedMEP=An unsupported message exchange pattern (MEP) exists {0}.
+mepClientSupportOnly=This message exchange pattern (MEP) client supports {0} only and the supplied Axis operations supports {1}.
+inputstreamNull=The input stream for an incoming message is null.
+unknownTransport=An unknown transport called {0} exists.
+paramIsNotSpecified=The {0} parameter is not specified.
+groovyNoanswer=An answer has not been received from groovy.
+groovyUnableToLoad=The system cannot load {0}
+outMessageNull=The out message is NULL, nothing to write.
+canNotBeNull={0} cannot be NULL.
+notFound={0} cannot be found.
+transportError=Transport error: {0} Error: {1}
+httpTransportError=HTTP Transport error: ''{0}'' - ''{1}''
+preatureEOS=A premature end of stream has occurred.
responseTimeOut=Time out while waiting for the server to send the response
-callBackCompletedWithError=Callback completed but there was no envelope or error
-2channelNeedAddressing=In order to use two transport channels, WS-Addressing module must be engaged
-useSeparateListenerLimited=useSeparateListener equals false is only supports by the http/tcp and tcp commons transport set as the sender and receiver
-replyNeedStarting=Before asking for ReplyTo, the TransportListener must be started. Transport is {0}
-failedToOpenSocket=failed to open the socket
-noRecep4Email=No recipient is found in the Email
-unknownMsgLabel=Unknown message label {0}
-cannotCorrelateMsg= Can not correlate the Message Operation {0} RelatesTo {1}
-addAfterInvoke00={0}: the chain has already been invoked
-AandBdonotmatch={0} does not match {1} expected {3} but the values was {4}
-rpcNeedmatchingChild=rpc style expect the immediate child of the SOAP body
-unknownStyle=Unknown Style {0}
-rawXmlProviderIsLimited=Raw Xml provider supports only the methods bearing the signature public OMElement <method-name>(OMElement) where the method name can be anything
-methodNotImplemented=Implementation class does not define a method called
-methodDoesNotExistInOut=ServiceClass does not implement required method of the form OMElement {0}(OMElement e)
-methodDoesNotExistInOnly=ServiceClass does not implement required method of the form void {0}(OMElement e)
-implReturnedNull=Implementation class returned null
-invalidMethodName=Invalid method name {0} for service implementation class
-blockInvocationExpectsRes=Blocking invocation always expects a response
-serviceGroupIDNotFound=SOAP session information can not be retrieved from the received correlation id.
+callBackCompletedWithError=The callback completed, but there was no envelope or error
+2channelNeedAddressing=To use two transport channels you must use the WS-Addressing module.
+useSeparateListenerLimited=A false value for the useSeparateListener is supported by the http/tcp and tcp commons transport only when they are set as the sender and receiver.
+replyNeedStarting=Before requesting the ReplyTo value, the system must start the TransportListener. The Transport is {0}
+failedToOpenSocket=The system failed to open the socket.
+noRecep4Email=A recipient is not specified in the e-mail message.
+unknownMsgLabel=An unknown message label has been encountered: {0}
+cannotCorrelateMsg= The system cannot correlate the {0} message operation to RelatesTo {1}
+addAfterInvoke00={0}: The chain already has been invoked.
+AandBdonotmatch=The {0} value does not match {1} value. The system expected the {3} value, but found the {4} value.
+rpcNeedmatchingChild=The remote procedure call (RPC) style expects the immediate child of the SOAP body.
+unknownStyle=The {0} style is an unknown style.
+rawXmlProviderIsLimited=The XML provider supports only the methods that contain the public OMElement <method-name>(OMElement) signature where the method-name variable can be any value.
+methodNotImplemented=The implementation class does not define a method called
+methodDoesNotExistInOut=The ServiceClass object does not implement the required method in the following form: OMElement {0}(OMElement e)
+methodDoesNotExistInOnly=The ServiceClass object does not implement the required method in the following form: void {0}(OMElement e)
+implReturnedNull=The implementation class returned a null value.
+invalidMethodName=The {0} method name is not valid for the service implementation class.
+blockInvocationExpectsRes=The blocking invocation does not contain a response.
+serviceGroupIDNotFound=The SOAP session information cannot be retrieved from the correlation id that was received.
# Client
-operationnotfound=Operation {0} not found
-unsupportedyype=Unsupported type
-unknownsoapversion=Unknown SOAP version
-cannotfindamoduletoprocess=cannot find a module to process {0} type assertions
-noendpointfound=No Endpoint Found in Service, {0}
-endpointnotfound=Endpoint Not found
-unsupportdmep=Unsupported MEP
-noservicefound=No service found
+operationnotfound=The {0} operation cannot be found.
+unsupportedyype=An unsupported type exists.
+unknownsoapversion=The system does not recognize the SOAP version.
+cannotfindamoduletoprocess=The system cannot find a module to process {0} type assertions.
+noendpointfound=An endpoint cannot be found in the Service {0}
+endpointnotfound=An endpoint cannot be found.
+unsupportdmep=An unsupported message exchange pattern (MEP) exists.
+noservicefound=A service was not located.
# context
-servicenotfound=Service not found
-threadpoolset=Thread pool already set.
-transportiniterror=Transport-OUT initialization error : {0}
-invalidserviceinagroup=Invalid service {0} not belong to service group {1}
+servicenotfound=A service cannot be located.
+threadpoolset=The thread pool is already set.
+transportiniterror=A transport-OUT initialization error: {0}
+invalidserviceinagroup=The {0} service, which is not valid, does not belong to the {1} service group.
# Deployment Errors
-invalidWSDLFound=Invalid WSDL found in the service archive file. WSDL File must have either \
- http://www.w3.org/2006/01/wsdl or http://www.w3.org/2004/03/wsdl as the namespace of the document element.
-wsdlfilenotfound=WSDL file not found for the service : {0}
-servicexmlnotfound=services.xml not found for service ''{0}''
-modulexmlnotfound=module.xml not found for the module : {0}
-classnotfound=Class Not found : {0}
-fileNotFound=File not found , {0}
-repocannotbebull=Axis2 repository can not be null
-confignotfound=can not find org/apache/axis2/deployment/axis2.xml
-pathtoconfigcanotnull=path to axis2.xml can not be NULL
+invalidWSDLFound=The WSDL file found in the service archive file is not valid. The WSDL file must have either \
+http://www.w3.org/2006/01/wsdl or http://www.w3.org/2004/03/wsdl as the namespace of the document element.
+wsdlfilenotfound=The WSDL file cannot be found for the service: {0}
+servicexmlnotfound=The services.xml file cannot be found for the service: {0}
+modulexmlnotfound=The module.xml file cannot be found for the module: {0}
+classnotfound=The {0} class cannot be found.
+fileNotFound=The {0} file cannot be found.
+repocannotbebull=The Axis2 repository cannot be null.
+confignotfound=The system cannot find the org/apache/axis2/deployment/axis2.xml file.
+pathtoconfigcanotnull=The path to axis2.xml file cannot be NULL.
modulevalfailed=Module validation failed {0}
-invalidphase=Invalid phases please recheck axis2.xml {0} for the handler {1}
-dispatchPhaseNotFoundOnInflow='Dispatch' phase not found on the global 'InFlow' phase of the axis2.xml. Please recheck
-invalidmoduleref=Service {0} refer to invalid module {1}
-invalidmodulerefbyop=Operation {0} refers to an invalid module {1}
-addingnewmodule=adding new module
-settingcl=Setting class loader {0}
-deployingws=Deploying Web service {0}
-invalidservice=Invalid service {0} due to {1}
-deployeingmodule=Deploying module : {0}
-invalidmodule=Invalid module : {0} caused {1}
-serviceremoved=Undeploying Web service {0}
-typemappingnotallowed=Type Mappings are not allowed in axis2.xml
-errorinloadingmr={0} Error in loading message receiver {1}
-errorinloadingts={0} Error in loading transport sender {1}
-invalidconfigattribute=invalid attributes in axis2.xml {0} {1}
-undefinedFlowType=un-defined flow type {0}
-flowtypeisrequird=Flow type is a required attribute in {0}
-elementisnotallow={0} element is not allowed in the axis2.xml
+invalidphase=The phases are not valid. Recheck the axis2.xml file {0} for the {1} handler.
+dispatchPhaseNotFoundOnInflow=The '"Dispatch'" phase is not found on the global '"InFlow'" phase of the axis2.xml file. Make sure the phase is within the axis2.xml file.
+invalidmoduleref=The {0} service refers to the {1} module, which is not valid.
+invalidmodulerefbyop=The (0) operation refers to the [1} module, which is not valid.
+addingnewmodule=Adding new module
+settingcl=The service is setting the {0} class loader.
+deployingws=The service is deploying the {0} Web service.
+invalidservice=The [0} service is not valid because {1}
+deployeingmodule=The service is deploying the module: {0}
+invalidmodule=The {0} module, which is not valid, caused {1}
+serviceremoved=The service is undeploying the {0} Web service.
+typemappingnotallowed=Type Mappings are not allowed in the axis2.xml file.
+errorinloadingmr=A {0} error occurred in loading the message receiver {1}
+errorinloadingts=A {0} error occurred in loading the transport sender {1}
+invalidconfigattribute=Attributes exist in the axis2.xml file that are not valid. {0} {1}
+undefinedFlowType=An undefined flow type exists {0}
+flowtypeisrequird=The flow type is a required attribute in {0}
+elementisnotallow=The {0} element is not allowed in the axis2.xml file.
outflownotallowedintrin=OUTFlow does not support in AxisTransportIN {0}
-unknownelement=Unknown element {0}
-inflownotallowedintrout=InFlow is not supported in TransportOutDescription {0}
-badarguforservice={0} Bad arguments for the service {1}
-typemappingnotimpl=Type mapping has not been implemented yet
-beanmappingnotimpl=Bean mapping has not been implemented yet
-modulenotfound={0} module is invalid or has not been deployed
-badparaagu=bad parameter arguments name can not be null : {0}
-badlistagu=bad listener arguments
-invalidhandlerdif=Handler cannot have both name and ref {0}
+unknownelement=This element is unknown: {0}
+inflownotallowedintrout=InFlow is not supported in TransportOutDescription {0}
+badarguforservice=The {0} arguments are not valid for the {1} service.
+typemappingnotimpl=Type mapping support is not available.
+beanmappingnotimpl=Bean mapping support is not available.
+modulenotfound=The {0} module is not valid or has not been deployed.
+badparaagu=bad parameter arguments. name cannot be null : {0}
+badlistagu=The listener arguments are not valid.
+invalidhandlerdif= The Handler cannot have both a name and a ref {0}
thisshouldbeimplment=This should be implemented {0}
-opnotfoundinwsdl={0} Operation Name not found in WSDL
-badopattribute=bad attribute in operation {0}
-unknownelementinop=Unknown element in operation {0}
-modulecannothavrbothnameandref=Module canot have both name and ref {0}
-invalideleinmodule={0} elment is not allowed in module.xml
+opnotfoundinwsdl=The {0} Operation Name cannot be found in the WSDL file.
+badopattribute=An attribute that is not valid was found in the operation: {0}
+unknownelementinop=An unknown element exists in the operation: {0}
+modulecannothavrbothnameandref=A module cannot have both a name and a ref {0}
+invalideleinmodule=The {0} element is not allowed in the module.xml file.
invalidphase01=Invalid Phase : {0} for the handler {1} does not exit in axis2.xml or refering to phase in different flow
-invalidmodulerefbyconfig=reference to invalid module {0} by axis2.xml
-phasedosenotspecified=Phase is specified for the handler {0}
-servicemodulecannothaveglobal=Service specific module can not refer system pre-defined phases : {0}
-fnf=File not found
-fnf_e=File not found {0}
+invalidmodulerefbyconfig=A reference by the axis2.xml file is made to the {0} module, which is not valid.
+phasedosenotspecified=A Phase is specified for the {0} handler.
+servicemodulecannothaveglobal=A service-specific module cannot refer system pre-defined phases: {0}
+fnf=The file cannot be found.
+fnf_e=The {0} file cannot be found.
StreamException=XMLStreamException : {0}
-mnf={0} : Module not found
-invalid_storage=Invalid storage class defintion, class name missing
-no_dispatcher_found=No dispatcher has been found , cannot continue ....
+mnf={0} : The module cannot be found.
+invalid_storage=The definition of the storage class is not valid because the class name is missing.
+no_dispatcher_found=A dispatcher cannot be found and cannot continue.
noMetaInf=Invalid service META-INF directory not found
ivs=Invalid service META-INF directory not found
-badModuleFromOperation=Error in engaging module {0} to the operation {1} , invalid module reference at operation
-badModuleFromService=Error in engaging module {0} to the operation {1} , invalid module reference at service
-InstantiationException=InstantiationException in Axis Storage processing {0}
-IllegalAccessException=IllegalAccessException in Axis Storage processing {0}
-transportSenderError=TransportSender Implementation class is required for the transport {0}
-obsererror=Observer Implementation Class is required
-invalidmoduleconfig=Invalid module configuration
-invalidhandler=Invalid Handler {0}
-parameterlockederror=The parameter {0} has been locked at top level can not overide
+badModuleFromOperation=An error occurred in the {0} engaging module {0} to the {1} operation. A module reference that is not valid exists at the operation.
+badModuleFromService=An error occurred in the {0} engaging module to the {1} operation. A module reference that is not valid exists at the service.
+InstantiationException=An InstantiationException error occurred in Axis storage processing {0}
+IllegalAccessException=An IllegalAccessException error occurred in Axis storage processing {0}
+transportSenderError=The TransportSender implementation class is required for the transport {0}
+obsererror=The Observer implementation class is required.
+invalidmoduleconfig=A module configuration exists that is not valid.
+invalidhandler=The following handler exists is not valid: {0}
+parameterlockederror=The {0} parameter is locked at the top level and cannot be overridden.
op_error=Processing Operations Modules {0}
-servicenameeror=Service name required
-invalid_op=Invalid Operation {0}
+servicenameeror=A service name is required.
+invalid_op=The operation is not valid: {0}
cannotCorrelateMsg01=Cannot correlate MessageID {1} to {0}
-fileExistsNoOverwrite=File {0} will not be overwritten.
+fileExistsNoOverwrite=The {0} file cannot be overwritten.
cannotConnectError=Unable to connect
-failedJMSConnectorShutdown=failure in JMSConnectorShutdown
-errorinschemagen=Error in schema generating {0}
-errorininputstreamclose=Error in closing input stream
-phaseclassnotfound=Couldn't find phase class : {0} : {1}
-modulenamecannotnull=Module name can not be null in side default module vresion element
-documentcreatingerror=Exception occured when creating the Document from WSDL {0}
-noserviceelemtfound=No javax.wsdl.Service element is found
-serviceporterror=atleast one port should be specified
-soapbindingerror=atleast one port with a soap binding should be specified
-axisoperationcreateerror=Exception when creating AxisOperation for the AxisService {0}
-wrapperelementcreaterror=Exception occured while creating wrapper element
-policyprocessingerror=Exception occured when processing policy elements
-bothrepoandconfignull=neither repository location nor axis2.xml are given so system will continue using default configuration (using default_axis2.xml)
-cannotfindrepo=System can not find the given repository location: {0}
-norepofoundinaxis2=no repository location found in axis2.xml
-noservicedirfound=no services directory found under {0}
-nomoduledirfound=no modules directory found under {0}
-confdirnotfound=conf directory not found , and no axis2.xml file is given ! System will continue using default_axis2.xml
-noaxis2xmlfound=axis2.xml file not found in conf directory , system will continue using default_axis2.xml
-badelementfound=Looking for ''{0}'' element, but found ''{1}''
-messagelabelcannotfound=message label can not be null
-paramterlockedbyparent=Parameter: {0} is already locked, hence value cannot be overridden
-modulealredyengaged={0} module has already engaged to the operation operation terminated !!!
-mepmappingerror=Could not Map the MEP URI to a axis2 MEP constant value
-mepnotyetimplemented="The MEP you are using {0} has not implemented createClient().
-modulealredyengagetoservice=Trying to engage a module which is already engege: {0}
-invalidoperation=invalid operation : {0}
-noschemafound=no schema found for the service
-modulenotavailble=Trying to engage a module which is not available : {0}
-modulealredyengagedtoservicegroup={0} module has already been engaged on the service Group. Operation terminated !!!
-servicenotfoundinwsdl=Service {0} not found in the wsdl
-noservicefoundinwsdl=No servoce found in the given wsdl
-noporttypefoundfor=No port found for the given port name : {0}
-noporttypefound=no port found in the service element
-modulenf=Module not found
-mepcompleted=Invalid message addition , operation context completed
-invalidacess=In valid acess
-mepiscomplted=MEP is already completed- need to reset() before re-executing.
-outmsgctxnull=Out message context is null please set the out message context before calling this method
-cannotreset=MEP is not yet complete: cannot reset
-cannotaddmsgctx=Can't add message context again until client has been executed
+failedJMSConnectorShutdown=A failure occurred in the JMSConnectorShutdown
+errorinschemagen=The following error occurred during schema generation: {0}
+errorininputstreamclose=An error occurred in closing input stream.
+phaseclassnotfound=The system cannot find the phase class: {0} : {1}
+modulenamecannotnull=The module name cannot be null in the version element for the side default module.
+documentcreatingerror=An exception occurred when creating the document from the WSDL file: {0}
+noserviceelemtfound=The javax.wsdl.Service element cannot be found.
+serviceporterror=The system must specify at least one port.
+soapbindingerror=The system must specify at least one port with a SOAP binding.
+axisoperationcreateerror=An exception when creating AxisOperation for the AxisService: {0}
+wrapperelementcreaterror=An exception occurred when creating the wrapper element.
+policyprocessingerror=An exception occurred when processing policy elements.
+bothrepoandconfignull=The repository location is not specified and the axis2.xml file is not provided. The system will use the default configuration, which uses the default_axis2.xml file.
+cannotfindrepo=The system cannot locate the specified repository location: {0}
+norepofoundinaxis2=A repository location is not found in the axis2.xml file.
+noservicedirfound=No services directory was found under {0}.
+nomoduledirfound=No modules directory was found under {0}.
+confdirnotfound=The conf directory cannot be found and the axis2.xml file is not provided. The system will use the default_axis2.xml file.
+noaxis2xmlfound=The axis2.xml file cannot be found in conf directory. The system will use the default_axis2.xml file.
+badelementfound=The system was looking for the ''{0}'' element, but it found ''{1}''
+messagelabelcannotfound=The message label cannot be null.
+paramterlockedbyparent=The {0} parameter is already locked and the value cannot be overridden.
+modulealredyengaged=The {0} module is already engaged. The operation has been stopped.
+mepmappingerror=The system cannot map the message exchange pattern (MEP) URI to a constant value for the axis2 MEP.
+mepnotyetimplemented=The message exchange pattern (MEP) {0} has not implemented the createClient method.
+modulealredyengagetoservice=The system is attempting to engage a module that is already engaged: {0}
+invalidoperation=The following operation is not valid: {0}
+noschemafound=A schema cannot be found for the service.
+modulenotavailble=The system is attempting to engage a module that is not available: {0}
+modulealredyengagedtoservicegroup=The {0} module has already been engaged on the service group. The operation has been stopped.
+servicenotfoundinwsdl=The {0} service cannot be found in the WSDL file.
+noservicefoundinwsdl=The service cannot be found in the given WSDL file.
+noporttypefoundfor=A port cannot be found for the {0} port name.
+noporttypefound=A port cannot be found in the service element.
+modulenf=A module cannot be found.
+mepcompleted=A message was added that is not valid. However, the operation context was completed.
+invalidacess= An access occurred that is not valid.
+mepiscomplted=The message exchange pattern (MEP) is already completed. Use the reset method before re-running.
+outmsgctxnull=The out message context is null. Set the out message context before calling this method.
+cannotreset=The message exchange pattern (MEP) is not complete. Cannot reset
+cannotaddmsgctx=The system cannot add the message context again until client runs.
#Policy
-emptypolicy=Policy Id is either null or empty
-#outMessageNull=Out message is null
+emptypolicy=The Policy ID is either null or empty.
+#outMessageNull=The out message is null.
malformedURLException00=MalformedURLException:
exception00=Exception:
#Byte code reading for Java2WSDL
-badClassFile00=Error looking for paramter names in bytecode: input does not appear to be a valid class file
-cantLoadByecode=Unable to load bytecode for class "{0}"
-unexpectedEOF00=Error looking for paramter names in bytecode: unexpected end of file
-unexpectedBytes00=Error looking for paramter names in bytecode: unexpected bytes in file
+badClassFile00=An error occurred when looking for parameter names in the bytecode. The input might not be a valid class file.
+cantLoadByecode=The system cannot load the bytecode for the class "{0}"
+unexpectedEOF00=An error occurred when looking for the parameter names in the bytecode. The end of the file was reached unexpectedly.
+unexpectedBytes00=An error occurred when looking for the parameter names in the bytecode. There are unexpected bytes in the file.
#description
servicefound=Found AxisService : {0}
operationfound=Found AxisOperation : {0}
-checkingoperation=Checking for Operation using WSAAction : {0}
-checkingserviceforepr=Checking for Service using toEPR's address : {0}
-checkingrelatesto=Checking RelatesTo : {0}
-twoservicecannothavesamename=Two services can not have same name, a service with {0} already exists in the system
-cannotaddapplicationscopeservice=can not add service with application scope onece the system has started
-invalidservicegroupname=invalid service group name : {0}
-modulealredyengagedglobaly=Attempt to engage an already engaged module {0}
-refertoinvalidmodule=Refer to invalid module , has not bean deployed yet !
-serviceinactive=Trying to acess inactive service : {0}
-servicenamenotvalid=Invalid service name : {0}
-enginestarted=Axis Engine Started
+checkingoperation=The system is checking for the operation using the following WSAAction: {0}
+checkingserviceforepr=The system is checking for the service using the following toEPR address: {0}
+checkingrelatesto=The system is checking the following RelatesTo: {0}
+twoservicecannothavesamename=Two services cannot have same name. A service with the {0} name already exists in the system.
+cannotaddapplicationscopeservice=The system cannot add a service with application scope after the system has started.
+invalidservicegroupname=The {0} service group name is not valid.
+modulealredyengagedglobaly=An attempt was made to engage the {0} module, which is already engaged.
+refertoinvalidmodule=A reference was made to a module that has not been deployed.
+serviceinactive=The system is attempting to access an inactive service: {0}
+servicenamenotvalid=The {0} service name in not valid.
+enginestarted=The Axis engine started.
mustunderstandfailed=Must Understand check failed {0} : {1}
-receivederrormessage=Received Error Message with id {0}
-servicenotfoundforepr=Service Not found EPR is {0}
-operationnotfoundforepr=Operation Not found EPR is {0} and WSA Action = {1}
-unabletofindservice=Service not found operation terminated !!
-invalidservicegrouoid=Invalid Service Group Id {0}
-servicenotfoundinthesystem=Invalid service {0}, not found in the system
-transportnotfound=Transport Not found {0}
-CannotConfigureAxis2=Cannot configure Axis2
-wsaddressingrequirednotpresent=WS-Addressing required but not found.
+receivederrormessage=The system received an error message with the {0} ID.
+servicenotfoundforepr=The endpoint reference (EPR) for the Service not found is {0}
+operationnotfoundforepr=The endpoint reference (EPR) for the Operation not found is {0} and the WSA Action = {1}
+unabletofindservice=The requested service could not be found -- the operation has been stopped.
+invalidservicegrouoid=The {0} Service Group ID is not valid.
+servicenotfoundinthesystem=The {0} service is not found in the system.
+transportnotfound=The transport is not found: {0}
+CannotConfigureAxis2=The system cannot configure Axis2.
+wsaddressingrequirednotpresent=WS-Addressing is required, but it cannot be found.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-cvs-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-cvs-help@ws.apache.org