hughesj 2002/11/01 06:22:59
Modified: java/src/org/apache/wsif/catalog Tag: pre1_2_0-patches
Messages_ko.properties Messages_ja.properties
Messages_pt_BR.properties Messages_fr.properties
Messages_zh.properties Messages_it.properties
Messages_es.properties Messages_zh_TW.properties
Messages_de.properties
Log:
Latest translated properties files
Revision Changes Path
No revision
No revision
1.1.2.1 +14 -8
xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages_ko.properties
Index: Messages_ko.properties
===================================================================
RCS file:
/home/cvs/xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages_ko.properties,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- Messages_ko.properties 25 Jul 2002 09:15:28 -0000 1.1
+++ Messages_ko.properties 1 Nov 2002 14:22:58 -0000 1.1.2.1
@@ -1,29 +1,35 @@
-WSIF.0001E=WSIF0001E: 요소 유형 ''{0}''에 대한 확장 레지스트리를 찾을 수 없습니다.
+WSIF.0001E=WSIF0001E: 요소 유형 ''{0}''에 대한 확장 레지스트리를 찾을 수 없습니다.
# Parameter(s): {0} element type
# Description: No extension registry was found for the element type specfied.
# User Action: Add the appropriate extension registry to the port factory in
your code.
-WSIF.0002E=WSIF0002E: ''{0}''에서 WSDL 로드 시 장애가 발생했습니다.
+WSIF.0002E=WSIF0002E: ''{0}''에서 WSDL 로드 시 장애가 발생했습니다.
# Parameter(s): {0} location of the WSDL file
# Description: The WSDL file could not be found at the location specified or
did not parse correctly
# User Action: Check that the location of the WSDL file is correct. Check that
any network connections required are available.
# Check that the WSDL file contains valid WSDL.
+
+WSIF.0003W=WSIF0003W: plugagble 제공자를 찾는 중 오류가 발생했습니다: {0}
+# Parameter(s): {0} specific details about the error
+# Description: There was a problem locating a WSIF pluggable provider using the
J2SE 1.3 JAR file extensions to support service providers architecture. The WSIF trace
file will contain the full exception details.
+# User Action: Verify that a META-INF/services/org.apache.wsif.spi.WSIFProvider
file exists in a provider jar, that each class referenced in the META-INF file exists
in the classpath, and that each class implements org.apache.wsif.spi.WSIFProvider.
+# The class in error will be ignored and WSIF will continue
locating other pluggable providers.
-WSIF.0004E=WSIF0004E: ''{1}''에 대해 지원되지 않는 작업 유형 ''{0}''이(가) WSDL에
있습니다.
+WSIF.0004E=WSIF0004E: ''{1}''에 대해 지원되지 않는 작업 유형 ''{0}''이(가) WSDL에
있습니다.
# Parameter(s): {0} name of the operation type specified
# {1} name of the portType for the operation
# Description: An operation type which is not supported has been specified in
the WSDL.
# User Action: Remove any operations of the unsupported type from the WSDL. If
the operation is required then make sure all messages
# have been correctly specified for the operation.
-WSIF.0005E=WSIF0005E: ''{1}'' 메소드를 호출할 때 오류가 발생했습니다. (''{0}'')
+WSIF.0005E=WSIF0005E: ''{1}'' 메소드를 호출할 때 오류가 발생했습니다. (''{0}'')
# Parameter(s): {0} name communication type e.g. EJB or ApacheSOAP
# {1} name of the method which failed
# Description: An error was encountered when invoking a method on the web
service using the communication shown in brackets.
# User Action: Check that the method exists on the web service and that the
correct parts have been added to the operation as described in the WSDL.
# Network problems might be a cause if the method is remote and so
check any required connections.
-WSIF.0006W=WSIF0006W: 다중 WSIFProvider가 같은 이름 공간 URI ''{0}''을(를) 지원하고
있습니다. (''{1}'') 찾음
+WSIF.0006W=WSIF0006W: 다중 WSIFProvider가 같은 이름 공간 URI ''{0}''을(를) 지원하고
있습니다. (''{1}'') 찾음
# Parameter(s): {0} the namespace URI
# {1} a list of the WSIFProvider found
# Description: There are multiple org.apache.wsif.spi.WSIFProvider classes in
the service provider path that support the same namespace URI.
@@ -31,7 +37,7 @@
# Which WSIFProvider is choosen is based on settings in the
wsif.properties file, or if not defined in the properties, the last WSIFProvider found
will be used.
# See the wsif.properties file for more details on how to define
which provider should be used to support a namespace URI.
-WSIF.0007I=WSIF0007I: 이름 공간 URI ''{1}''에 대해 WSIFProvider ''{0}'' 사용
+WSIF.0007I=WSIF0007I: namespaceURI ''{1}''에 대해 WSIFProvider ''{0}'' 사용
# Parameter(s): {0} the classname of the WSIFProvider being used.
# {1} the namespaceURI the provider will be used to support.
# Description: Either a previous WSIF0006W message has been issued or the
SetDynamicWSIFProvider method has been used to override the provider used to support a
namespaceURI.
@@ -43,12 +49,12 @@
# User Action: Determine why no response has been received for the asynchronous
request within the timeout period.
# The wsif.asyncrequest.timeout property of the wsif.properties
file defines the length of the timeout period.
-WSIF.0009I=WSIF0009I: 상관 서비스 사용 - ''{0}''
+WSIF.0009I=WSIF0009I: 상관 서비스 사용 - ''{0}''
# Parameter(s): {0} the name of the correlation service being used
# Description: This identifies the name of the correlation service that will be
used to prccess asynchronous requests.
# User Action: None. If a correlation service other than the default WSIF
supplied one is required, ensure that it is correclty registered in the JNDI
java:comp/wsif/WSIFCorrelationService namespace.
-WSIF.0010E=WSIF0010E: 비동기 응답을 처리하는 중 예외가 발생했습니다 - ''{0}''
+WSIF.0010E=WSIF0010E: 비동기 응답을 처리하는 중 예외가 발생했습니다 - ''{0}''
# Parameter(s): {0} the error message string of the exception
# Description: While processing the response from an
executeRequestResponseAsync call an exception was thrown.
# User Action: Use the exception error message string to determine the cause of
the error. The WSIF trace will have more details on the error including the exception
stack trace.
1.1.2.1 +8 -2
xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages_ja.properties
Index: Messages_ja.properties
===================================================================
RCS file:
/home/cvs/xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages_ja.properties,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- Messages_ja.properties 25 Jul 2002 09:15:28 -0000 1.1
+++ Messages_ja.properties 1 Nov 2002 14:22:58 -0000 1.1.2.1
@@ -8,6 +8,12 @@
# Description: The WSDL file could not be found at the location specified or
did not parse correctly
# User Action: Check that the location of the WSDL file is correct. Check that
any network connections required are available.
# Check that the WSDL file contains valid WSDL.
+
+WSIF.0003W=WSIF0003W: pluggable 긵깓긫귽�_�[: {0} 궻뙚뢯궳긄깋�[궕뵯맯궢귏궢궫갃
+# Parameter(s): {0} specific details about the error
+# Description: There was a problem locating a WSIF pluggable provider using the
J2SE 1.3 JAR file extensions to support service providers architecture. The WSIF trace
file will contain the full exception details.
+# User Action: Verify that a META-INF/services/org.apache.wsif.spi.WSIFProvider
file exists in a provider jar, that each class referenced in the META-INF file exists
in the classpath, and that each class implements org.apache.wsif.spi.WSIFProvider.
+# The class in error will be ignored and WSIF will continue
locating other pluggable providers.
WSIF.0004E=WSIF0004E: WSDL 궸갂긆긻깒�[긘깈깛갋�^귽긵 ''{0}''
궕듵귏귢궲궋귏궥궕갂궞귢궼 ''{1}'' 궳궼긖�|�[긣궠귢궲궋귏궧귪갃
# Parameter(s): {0} name of the operation type specified
@@ -31,13 +37,13 @@
# Which WSIFProvider is choosen is based on settings in the
wsif.properties file, or if not defined in the properties, the last WSIFProvider found
will be used.
# See the wsif.properties file for more details on how to define
which provider should be used to support a namespace URI.
-WSIF.0007I=WSIF0007I: namespaceURI ''{1} 궸뫮궢궲 WSIFProvider ''{0}'' 귩럊뾭뭷
+WSIF.0007I=WSIF0007I: namespaceURI ''{1} 궸뫮궢궲 WSIFProvider ''{0}''
귩럊뾭궢궲궋귏궥갃
# Parameter(s): {0} the classname of the WSIFProvider being used.
# {1} the namespaceURI the provider will be used to support.
# Description: Either a previous WSIF0006W message has been issued or the
SetDynamicWSIFProvider method has been used to override the provider used to support a
namespaceURI.
# User Action: None. See also WSIF0006W.
-WSIF.0008W=WSIF0008W: WSIFDefaultCorrelationService
궼갂몜듫듫똚럔귩갂�^귽��귺긂긣궻궫귕궸룣땸궢궲궋귏궥갃ID:''{0}''
+WSIF.0008W=WSIF0008W: WSIFDefaultCorrelationService
궼갂몜듫듫똚럔귩갂�^귽��귺긂긣궻궫귕궸룣땸궢궲궋귏궥갃ID:''{0}''
# Parameter(s): {0} the id of the correlator being removed from the correlation
service
# Description: A stored correlator is being removed from the correlation
service due to its timeout expiring.
# User Action: Determine why no response has been received for the asynchronous
request within the timeout period.
1.1.2.1 +7 -1
xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages_pt_BR.properties
Index: Messages_pt_BR.properties
===================================================================
RCS file:
/home/cvs/xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages_pt_BR.properties,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- Messages_pt_BR.properties 25 Jul 2002 09:15:28 -0000 1.1
+++ Messages_pt_BR.properties 1 Nov 2002 14:22:59 -0000 1.1.2.1
@@ -8,6 +8,12 @@
# Description: The WSDL file could not be found at the location specified or
did not parse correctly
# User Action: Check that the location of the WSDL file is correct. Check that
any network connections required are available.
# Check that the WSDL file contains valid WSDL.
+
+WSIF.0003W=WSIF0003W: Um erro ocorreu ao localizar provedores que podem ser
conectados: {0}
+# Parameter(s): {0} specific details about the error
+# Description: There was a problem locating a WSIF pluggable provider using the
J2SE 1.3 JAR file extensions to support service providers architecture. The WSIF trace
file will contain the full exception details.
+# User Action: Verify that a META-INF/services/org.apache.wsif.spi.WSIFProvider
file exists in a provider jar, that each class referenced in the META-INF file exists
in the classpath, and that each class implements org.apache.wsif.spi.WSIFProvider.
+# The class in error will be ignored and WSIF will continue
locating other pluggable providers.
WSIF.0004E=WSIF0004E: O WSDL cont�m um tipo de opera豫o ''{0}'' que n�o � suportado
por ''{1}''
# Parameter(s): {0} name of the operation type specified
@@ -31,7 +37,7 @@
# Which WSIFProvider is choosen is based on settings in the
wsif.properties file, or if not defined in the properties, the last WSIFProvider found
will be used.
# See the wsif.properties file for more details on how to define
which provider should be used to support a namespace URI.
-WSIF.0007I=WSIF0007I: Utilizando WSIFProvider ''{0}'' para namespaceURI ''{1}
+WSIF.0007I=WSIF0007I: Utilizando o WSIFProvider ''{0}'' para namespaceURI ''{1}''
# Parameter(s): {0} the classname of the WSIFProvider being used.
# {1} the namespaceURI the provider will be used to support.
# Description: Either a previous WSIF0006W message has been issued or the
SetDynamicWSIFProvider method has been used to override the provider used to support a
namespaceURI.
1.1.2.1 +16 -10
xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages_fr.properties
Index: Messages_fr.properties
===================================================================
RCS file:
/home/cvs/xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages_fr.properties,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- Messages_fr.properties 25 Jul 2002 09:15:28 -0000 1.1
+++ Messages_fr.properties 1 Nov 2002 14:22:59 -0000 1.1.2.1
@@ -1,29 +1,35 @@
-WSIF.0001E=WSIF0001E: registre d''extensions introuvable pour le type d''�l�ment
''{0}''
+WSIF.0001E=WSIF0001E: Registre d''extensions introuvable pour le type d''�l�ment
''{0}''
# Parameter(s): {0} element type
# Description: No extension registry was found for the element type specfied.
# User Action: Add the appropriate extension registry to the port factory in
your code.
-WSIF.0002E=WSIF0002E : Un incident s''est produit lors du chargement WSDL � partir
de ''{0}''
+WSIF.0002E=WSIF0002E: Un incident s''est produit lors du chargement WSDL � partir
de ''{0}''
# Parameter(s): {0} location of the WSDL file
# Description: The WSDL file could not be found at the location specified or
did not parse correctly
# User Action: Check that the location of the WSDL file is correct. Check that
any network connections required are available.
# Check that the WSDL file contains valid WSDL.
+
+WSIF.0003W=WSIF0003W: Une erreur s''est produite lors de la recherche des
fournisseurs tiers : {0}
+# Parameter(s): {0} specific details about the error
+# Description: There was a problem locating a WSIF pluggable provider using the
J2SE 1.3 JAR file extensions to support service providers architecture. The WSIF trace
file will contain the full exception details.
+# User Action: Verify that a META-INF/services/org.apache.wsif.spi.WSIFProvider
file exists in a provider jar, that each class referenced in the META-INF file exists
in the classpath, and that each class implements org.apache.wsif.spi.WSIFProvider.
+# The class in error will be ignored and WSIF will continue
locating other pluggable providers.
-WSIF.0004E=WSIF0004E: WSDL contient un type d''op�ration ''{0}'' non support� pour
''{1}''
+WSIF.0004E=WSIF0004E: WSDL contient un type d''op�ration ''{0}'' non support� pour
''{1}''
# Parameter(s): {0} name of the operation type specified
# {1} name of the portType for the operation
# Description: An operation type which is not supported has been specified in
the WSDL.
# User Action: Remove any operations of the unsupported type from the WSDL. If
the operation is required then make sure all messages
# have been correctly specified for the operation.
-WSIF.0005E=WSIF0005E : Une erreur s''est produite lors de l''appel de la m�thode
''{1}''. (''{0}'')
+WSIF.0005E=WSIF0005E: Une erreur s''est produite lors de l''appel de la m�thode
''{1}''. (''{0}'')
# Parameter(s): {0} name communication type e.g. EJB or ApacheSOAP
# {1} name of the method which failed
# Description: An error was encountered when invoking a method on the web
service using the communication shown in brackets.
# User Action: Check that the method exists on the web service and that the
correct parts have been added to the operation as described in the WSDL.
# Network problems might be a cause if the method is remote and so
check any required connections.
-WSIF.0006W=WSIF0006W: plusieurs WSIFProvider trouv�s, supportant l'' URI du m�me
espace de nom ''{0}''. (''{1}'') trouv�.
+WSIF.0006W=WSIF0006W: Plusieurs WSIFProvider trouv�s, supportant l'' URI du m�me
espace de nom ''{0}''. (''{1}'') trouv�.
# Parameter(s): {0} the namespace URI
# {1} a list of the WSIFProvider found
# Description: There are multiple org.apache.wsif.spi.WSIFProvider classes in
the service provider path that support the same namespace URI.
@@ -31,29 +37,29 @@
# Which WSIFProvider is choosen is based on settings in the
wsif.properties file, or if not defined in the properties, the last WSIFProvider found
will be used.
# See the wsif.properties file for more details on how to define
which provider should be used to support a namespace URI.
-WSIF.0007I=WSIF0007I: utilisation de WSIFProvider ''{0}'' pour l''URI d''espace de
nom ''{1}''
+WSIF.0007I=WSIF0007I: Utilisation de WSIFProvider ''{0}'' pour namespaceURI ''{1}''.
# Parameter(s): {0} the classname of the WSIFProvider being used.
# {1} the namespaceURI the provider will be used to support.
# Description: Either a previous WSIF0006W message has been issued or the
SetDynamicWSIFProvider method has been used to override the provider used to support a
namespaceURI.
# User Action: None. See also WSIF0006W.
-WSIF.0008W=WSIF0008W : WSIFDefaultCorrelationService lors du retrait du corr�lateur
en raison d''un d�passement de d�lai. ID :''{0}''
+WSIF.0008W=WSIF0008W: WSIFDefaultCorrelationService lors du retrait du corr�lateur
en raison d''un d�passement de d�lai. ID :''{0}''
# Parameter(s): {0} the id of the correlator being removed from the correlation
service
# Description: A stored correlator is being removed from the correlation
service due to its timeout expiring.
# User Action: Determine why no response has been received for the asynchronous
request within the timeout period.
# The wsif.asyncrequest.timeout property of the wsif.properties
file defines the length of the timeout period.
-WSIF.0009I=WSIF0009I : Utilisation du service de corr�lation - ''{0}''
+WSIF.0009I=WSIF0009I: Utilisation du service de corr�lation - ''{0}''
# Parameter(s): {0} the name of the correlation service being used
# Description: This identifies the name of the correlation service that will be
used to prccess asynchronous requests.
# User Action: None. If a correlation service other than the default WSIF
supplied one is required, ensure that it is correclty registered in the JNDI
java:comp/wsif/WSIFCorrelationService namespace.
-WSIF.0010E=WSIF0010E : Exception lanc�e lors du traitement de la r�ponse asynchrone
- ''{0}''
+WSIF.0010E=WSIF0010E: Exception lanc�e lors du traitement de la r�ponse asynchrone
- ''{0}''
# Parameter(s): {0} the error message string of the exception
# Description: While processing the response from an
executeRequestResponseAsync call an exception was thrown.
# User Action: Use the exception error message string to determine the cause of
the error. The WSIF trace will have more details on the error including the exception
stack trace.
-WSIF.0011I=WSIF0011I : Le port pr�f�r� ''{0}'' n''�tait pas disponible
+WSIF.0011I=WSIF0011I: Le port pr�f�r� ''{0}'' n''�tait pas disponible
# Parameter(s): {0} the user's preferred port
# Description: The preferred port set by the user on
org.apache.wsif.WSIFService is not available
# User Action: None unless this message appears for long periods of time in
which case the user might want to pick a different port as their preferred port
1.1.2.1 +8 -2
xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages_zh.properties
Index: Messages_zh.properties
===================================================================
RCS file:
/home/cvs/xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages_zh.properties,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- Messages_zh.properties 25 Jul 2002 09:15:28 -0000 1.1
+++ Messages_zh.properties 1 Nov 2002 14:22:59 -0000 1.1.2.1
@@ -8,8 +8,14 @@
# Description: The WSDL file could not be found at the location specified or
did not parse correctly
# User Action: Check that the location of the WSDL file is correct. Check that
any network connections required are available.
# Check that the WSDL file contains valid WSDL.
+
+WSIF.0003W=WSIF0003W：꿴冷옵꿨흙瓊묩넋埼：{0} 珂놔댄
+# Parameter(s): {0} specific details about the error
+# Description: There was a problem locating a WSIF pluggable provider using the
J2SE 1.3 JAR file extensions to support service providers architecture. The WSIF trace
file will contain the full exception details.
+# User Action: Verify that a META-INF/services/org.apache.wsif.spi.WSIFProvider
file exists in a provider jar, that each class referenced in the META-INF file exists
in the classpath, and that each class implements org.apache.wsif.spi.WSIFProvider.
+# The class in error will be ignored and WSIF will continue
locating other pluggable providers.
-WSIF.0004E=WSIF0004E：WSDL 관벵꾸鱗잚謹‘{0}’，늪잚謹꼇連넣‘{1}’
+WSIF.0004E=WSIF0004E：WSDL 관벵꾸鱗잚謹‘{0}’，뚤黨‘{1}’꼇連넣늪잚謹
# Parameter(s): {0} name of the operation type specified
# {1} name of the portType for the operation
# Description: An operation type which is not supported has been specified in
the WSDL.
@@ -31,7 +37,7 @@
# Which WSIFProvider is choosen is based on settings in the
wsif.properties file, or if not defined in the properties, the last WSIFProvider found
will be used.
# See the wsif.properties file for more details on how to define
which provider should be used to support a namespace URI.
-WSIF.0007I=WSIF0007I：賈痰츰냔왕쇌 URI‘{1}’돨 WSIFProvider‘{0}’
+WSIF.0007I=WSIF0007I：賈痰 namespaceURI‘{1}’돨 WSIFProvider‘{0}’
# Parameter(s): {0} the classname of the WSIFProvider being used.
# {1} the namespaceURI the provider will be used to support.
# Description: Either a previous WSIF0006W message has been issued or the
SetDynamicWSIFProvider method has been used to override the provider used to support a
namespaceURI.
1.1.2.1 +10 -4
xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages_it.properties
Index: Messages_it.properties
===================================================================
RCS file:
/home/cvs/xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages_it.properties,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- Messages_it.properties 25 Jul 2002 09:15:28 -0000 1.1
+++ Messages_it.properties 1 Nov 2002 14:22:59 -0000 1.1.2.1
@@ -3,11 +3,17 @@
# Description: No extension registry was found for the element type specfied.
# User Action: Add the appropriate extension registry to the port factory in
your code.
-WSIF.0002E=WSIF0002E: si � verificato un errore durante il caricamento di WSDL da
''{0}''
+WSIF.0002E=WSIF0002E: si � verificato un errore durante il caricamento di WSDL da
''{0}''
# Parameter(s): {0} location of the WSDL file
# Description: The WSDL file could not be found at the location specified or
did not parse correctly
# User Action: Check that the location of the WSDL file is correct. Check that
any network connections required are available.
# Check that the WSDL file contains valid WSDL.
+
+WSIF.0003W=WSIF0003W: si � verificato un errore durante la ricerca dei provider
collegabili: {0}
+# Parameter(s): {0} specific details about the error
+# Description: There was a problem locating a WSIF pluggable provider using the
J2SE 1.3 JAR file extensions to support service providers architecture. The WSIF trace
file will contain the full exception details.
+# User Action: Verify that a META-INF/services/org.apache.wsif.spi.WSIFProvider
file exists in a provider jar, that each class referenced in the META-INF file exists
in the classpath, and that each class implements org.apache.wsif.spi.WSIFProvider.
+# The class in error will be ignored and WSIF will continue
locating other pluggable providers.
WSIF.0004E=WSIF0004E: WSDL contiene un tipo di operazione ''{0}'' non supportato
per ''{1}''
# Parameter(s): {0} name of the operation type specified
@@ -31,7 +37,7 @@
# Which WSIFProvider is choosen is based on settings in the
wsif.properties file, or if not defined in the properties, the last WSIFProvider found
will be used.
# See the wsif.properties file for more details on how to define
which provider should be used to support a namespace URI.
-WSIF.0007I=WSIF0007I: Uso di WSIFProvider ''{0}'' per namespaceURI ''{1}
+WSIF.0007I=WSIF0007I: Uso di WSIFProvider ''{0}'' per namespaceURI ''{1}''
# Parameter(s): {0} the classname of the WSIFProvider being used.
# {1} the namespaceURI the provider will be used to support.
# Description: Either a previous WSIF0006W message has been issued or the
SetDynamicWSIFProvider method has been used to override the provider used to support a
namespaceURI.
@@ -43,12 +49,12 @@
# User Action: Determine why no response has been received for the asynchronous
request within the timeout period.
# The wsif.asyncrequest.timeout property of the wsif.properties
file defines the length of the timeout period.
-WSIF.0009I=WSIF0009I: uso del servizio di correlazione in corso - ''{0}''
+WSIF.0009I=WSIF0009I: uso del servizio di correlazione in corso - ''{0}''
# Parameter(s): {0} the name of the correlation service being used
# Description: This identifies the name of the correlation service that will be
used to prccess asynchronous requests.
# User Action: None. If a correlation service other than the default WSIF
supplied one is required, ensure that it is correclty registered in the JNDI
java:comp/wsif/WSIFCorrelationService namespace.
-WSIF.0010E=WSIF0010E: eccezione generata durante l''elaborazione della risposta
asincrona - ''{0}''
+WSIF.0010E=WSIF0010E: eccezione generata durante l''elaborazione della risposta
asincrona - ''{0}''
# Parameter(s): {0} the error message string of the exception
# Description: While processing the response from an
executeRequestResponseAsync call an exception was thrown.
# User Action: Use the exception error message string to determine the cause of
the error. The WSIF trace will have more details on the error including the exception
stack trace.
1.1.2.1 +7 -1
xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages_es.properties
Index: Messages_es.properties
===================================================================
RCS file:
/home/cvs/xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages_es.properties,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- Messages_es.properties 25 Jul 2002 09:15:28 -0000 1.1
+++ Messages_es.properties 1 Nov 2002 14:22:59 -0000 1.1.2.1
@@ -8,6 +8,12 @@
# Description: The WSDL file could not be found at the location specified or
did not parse correctly
# User Action: Check that the location of the WSDL file is correct. Check that
any network connections required are available.
# Check that the WSDL file contains valid WSDL.
+
+WSIF.0003W=WSIF0003W: Se ha producido un error al buscar los proveedores
conectables: {0}
+# Parameter(s): {0} specific details about the error
+# Description: There was a problem locating a WSIF pluggable provider using the
J2SE 1.3 JAR file extensions to support service providers architecture. The WSIF trace
file will contain the full exception details.
+# User Action: Verify that a META-INF/services/org.apache.wsif.spi.WSIFProvider
file exists in a provider jar, that each class referenced in the META-INF file exists
in the classpath, and that each class implements org.apache.wsif.spi.WSIFProvider.
+# The class in error will be ignored and WSIF will continue
locating other pluggable providers.
WSIF.0004E=WSIF0004E: WSDL contiene un tipo de operaci�n ''{0}'' no soportado para
''{1}''
# Parameter(s): {0} name of the operation type specified
@@ -31,7 +37,7 @@
# Which WSIFProvider is choosen is based on settings in the
wsif.properties file, or if not defined in the properties, the last WSIFProvider found
will be used.
# See the wsif.properties file for more details on how to define
which provider should be used to support a namespace URI.
-WSIF.0007I=WSIF0007I: Utilizaci�n de WSIFProvider ''{0}'' para namespaceURI ''{1}
+WSIF.0007I=WSIF0007I: Utilizando WSIFProvider ''{0}'' para namespaceURI ''{1}''
# Parameter(s): {0} the classname of the WSIFProvider being used.
# {1} the namespaceURI the provider will be used to support.
# Description: Either a previous WSIF0006W message has been issued or the
SetDynamicWSIFProvider method has been used to override the provider used to support a
namespaceURI.
1.1.2.1 +6 -0
xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages_zh_TW.properties
Index: Messages_zh_TW.properties
===================================================================
RCS file:
/home/cvs/xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages_zh_TW.properties,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- Messages_zh_TW.properties 25 Jul 2002 09:15:28 -0000 1.1
+++ Messages_zh_TW.properties 1 Nov 2002 14:22:59 -0000 1.1.2.1
@@ -8,6 +8,12 @@
# Description: The WSDL file could not be found at the location specified or
did not parse correctly
# User Action: Check that the location of the WSDL file is correct. Check that
any network connections required are available.
# Check that the WSDL file contains valid WSDL.
+
+WSIF.0003W=WSIF0003W: 퀾㏛쩳�~굶ず뇩ⓔぬ��좥탊Ν월�~좬{0}
+# Parameter(s): {0} specific details about the error
+# Description: There was a problem locating a WSIF pluggable provider using the
J2SE 1.3 JAR file extensions to support service providers architecture. The WSIF trace
file will contain the full exception details.
+# User Action: Verify that a META-INF/services/org.apache.wsif.spi.WSIFProvider
file exists in a provider jar, that each class referenced in the META-INF file exists
in the classpath, and that each class implements org.apache.wsif.spi.WSIFProvider.
+# The class in error will be ignored and WSIF will continue
locating other pluggable providers.
WSIF.0004E=WSIF0004E: WSDL 쬽┳ㄳㅴ누 ''{1}'' ⓒΞず�@�~층ガ ''{0}''
# Parameter(s): {0} name of the operation type specified
1.1.2.1 +11 -5
xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages_de.properties
Index: Messages_de.properties
===================================================================
RCS file:
/home/cvs/xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages_de.properties,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- Messages_de.properties 25 Jul 2002 09:15:28 -0000 1.1
+++ Messages_de.properties 1 Nov 2002 14:22:59 -0000 1.1.2.1
@@ -3,13 +3,19 @@
# Description: No extension registry was found for the element type specfied.
# User Action: Add the appropriate extension registry to the port factory in
your code.
-WSIF.0002E=WSIF0002E: Beim Laden von WSDL aus ''{0}'' ist ein Fehler aufgetreten.
+WSIF.0002E=WSIF0002E: Beim Laden der WSDL-Datei aus ''{0}'' ist ein Fehler
aufgetreten.
# Parameter(s): {0} location of the WSDL file
# Description: The WSDL file could not be found at the location specified or
did not parse correctly
# User Action: Check that the location of the WSDL file is correct. Check that
any network connections required are available.
# Check that the WSDL file contains valid WSDL.
+
+WSIF.0003W=WSIF0003W: Beim Suchen von Plug-in-f�higen Providern ist ein Fehler
aufgetreten: {0}
+# Parameter(s): {0} specific details about the error
+# Description: There was a problem locating a WSIF pluggable provider using the
J2SE 1.3 JAR file extensions to support service providers architecture. The WSIF trace
file will contain the full exception details.
+# User Action: Verify that a META-INF/services/org.apache.wsif.spi.WSIFProvider
file exists in a provider jar, that each class referenced in the META-INF file exists
in the classpath, and that each class implements org.apache.wsif.spi.WSIFProvider.
+# The class in error will be ignored and WSIF will continue
locating other pluggable providers.
-WSIF.0004E=WSIF0004E: WSDL enth�lt einen Operationstyp ''{0}'', der f�r ''{1}''
nicht unterst�tzt wird.
+WSIF.0004E=WSIF0004E: Die WSDL enth�lt den Operationstyp ''{0}'', der f�r ''{1}''
nicht unterst�tzt wird.
# Parameter(s): {0} name of the operation type specified
# {1} name of the portType for the operation
# Description: An operation type which is not supported has been specified in
the WSDL.
@@ -23,7 +29,7 @@
# User Action: Check that the method exists on the web service and that the
correct parts have been added to the operation as described in the WSDL.
# Network problems might be a cause if the method is remote and so
check any required connections.
-WSIF.0006W=WSIF0006W: Es wurden mehrere WSIFProvider gefunden, die den
Namespace-URI ''{0}'' unterst�tzen. Die gefundenen WSIFProvider sind (''{1}'')
+WSIF.0006W=WSIF0006W: Es wurden mehrere WSIFProvider gefunden, die den
Namespace-URI ''{0}'' unterst�tzen. Gefunden wurden (''{1}'').
# Parameter(s): {0} the namespace URI
# {1} a list of the WSIFProvider found
# Description: There are multiple org.apache.wsif.spi.WSIFProvider classes in
the service provider path that support the same namespace URI.
@@ -31,13 +37,13 @@
# Which WSIFProvider is choosen is based on settings in the
wsif.properties file, or if not defined in the properties, the last WSIFProvider found
will be used.
# See the wsif.properties file for more details on how to define
which provider should be used to support a namespace URI.
-WSIF.0007I=WSIF0007I: Der WSIFProvider ''{0}'' wird f�r den Namespace-URI ''{1}
verwendet.
+WSIF.0007I=WSIF0007I: Es wird WSIFProvider ''{0}'' f�r namespaceURI ''{1}''
verwendet.
# Parameter(s): {0} the classname of the WSIFProvider being used.
# {1} the namespaceURI the provider will be used to support.
# Description: Either a previous WSIF0006W message has been issued or the
SetDynamicWSIFProvider method has been used to override the provider used to support a
namespaceURI.
# User Action: None. See also WSIF0006W.
-WSIF.0008W=WSIF0008W: WSIFDefaultCorrelationService entfernt den Korrelationswert
aufgrund einer Zeitlimit�berschreitung. ID:''{0}''
+WSIF.0008W=WSIF0008W: WSIFDefaultCorrelationService entfernt den Korrelationswert
aufgrund einer Zeitlimit�berschreitung. ID:''{0}''
# Parameter(s): {0} the id of the correlator being removed from the correlation
service
# Description: A stored correlator is being removed from the correlation
service due to its timeout expiring.
# User Action: Determine why no response has been received for the asynchronous
request within the timeout period.
