hughesj 2002/12/17 06:39:07
Modified: java/src/org/apache/wsif/catalog Tag: pre1_2_0-patches
Messages_ko.properties Messages.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:
Ran native2ascii on the .properties files so they are now all in escaped-ASCII format
Revision Changes Path
No revision
No revision
1.1.2.3 +11 -11
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.2.2
retrieving revision 1.1.2.3
diff -u -r1.1.2.2 -r1.1.2.3
--- Messages_ko.properties 4 Nov 2002 16:37:47 -0000 1.1.2.2
+++ Messages_ko.properties 17 Dec 2002 14:39:06 -0000 1.1.2.3
@@ -1,35 +1,35 @@
-WSIF.0001E=WSIF0001E: 요소 유형 ''{0}''에 대한 확장 레지스트리를 찾을 수 없습니다.
+WSIF.0001E=WSIF0001E: \uc694\uc18c \uc720\ud615 ''{0}''\uc5d0 \ub300\ud55c
\ud655\uc7a5 \ub808\uc9c0\uc2a4\ud2b8\ub9ac\ub97c \ucc3e\uc744 \uc218
\uc5c6\uc2b5\ub2c8\ub2e4.
# 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}''\uc5d0\uc11c WSDL \ub85c\ub4dc \uc2dc
\uc7a5\uc560\uac00 \ubc1c\uc0dd\ud588\uc2b5\ub2c8\ub2e4.
# 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: pluggable 프로바이더를 찾는 중 오류가 발생했습니다: {0}
+WSIF.0003W=WSIF0003W: pluggable \ud504\ub85c\ubc14\uc774\ub354\ub97c \ucc3e\ub294
\uc911 \uc624\ub958\uac00 \ubc1c\uc0dd\ud588\uc2b5\ub2c8\ub2e4: {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}''\uc5d0 \ub300\ud574 \uc9c0\uc6d0\ub418\uc9c0
\uc54a\ub294 \uc791\uc5c5 \uc720\ud615 ''{0}''\uc774(\uac00) WSDL\uc5d0
\uc788\uc2b5\ub2c8\ub2e4.
# 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}'' \uba54\uc18c\ub4dc\ub97c \ud638\ucd9c\ud560 \ub54c
\uc624\ub958\uac00 \ubc1c\uc0dd\ud588\uc2b5\ub2c8\ub2e4. (''{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: \ub2e4\uc911 WSIFProvider\uac00 \uac19\uc740 \ub124\uc784
\uc2a4\ud398\uc774\uc2a4 URI ''{0}''\uc744(\ub97c) \uc9c0\uc6d0\ud558\uace0
\uc788\uc2b5\ub2c8\ub2e4. (''{1}'') \ucc3e\uc74c
# 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.
@@ -37,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: namespaceURI ''{1}''에 대해 WSIFProvider ''{0}'' 사용
+WSIF.0007I=WSIF0007I: namespaceURI ''{1}''\uc5d0 \ub300\ud574 WSIFProvider ''{0}''
\uc0ac\uc6a9
# 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: \uc81c\ud55c\uc2dc\uac04\uc73c\ub85c \uc778\ud574
WSIFDefaultCorrelationService\uc5d0\uc11c \uc0c1\uad00\uc790\ub97c \uc81c\uac70
\uc911\uc785\ub2c8\ub2e4. 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: 상관 서비스 사용 - ''{0}''
+WSIF.0009I=WSIF0009I: \uc0c1\uad00 \uc11c\ube44\uc2a4 \uc0ac\uc6a9 - ''{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: \ube44\ub3d9\uae30 \uc751\ub2f5\uc744
\ucc98\ub9ac\ud558\ub294 \uc911 \uc608\uc678\uac00
\ubc1c\uc0dd\ud588\uc2b5\ub2c8\ub2e4 - ''{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: 선호하는 ''{0}'' 포트를 사용할 수 없습니다.
+WSIF.0011I=WSIF0011I: \uc120\ud638\ud558\ub294 ''{0}'' \ud3ec\ud2b8\ub97c
\uc0ac\uc6a9\ud560 \uc218 \uc5c6\uc2b5\ub2c8\ub2e4.
# 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.5.2.2 +65 -65
xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages.properties
Index: Messages.properties
===================================================================
RCS file:
/home/cvs/xml-axis-wsif/java/src/org/apache/wsif/catalog/Messages.properties,v
retrieving revision 1.5.2.1
retrieving revision 1.5.2.2
diff -u -r1.5.2.1 -r1.5.2.2
--- Messages.properties 4 Nov 2002 16:37:47 -0000 1.5.2.1
+++ Messages.properties 17 Dec 2002 14:39:06 -0000 1.5.2.2
@@ -1,65 +1,65 @@
-WSIF.0001E=WSIF0001E: An extension registry was not found for the element type
''{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: A failure occurred in loading WSDL from ''{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: An error occurred finding pluggable providers: {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 contains an operation type ''{0}'' which is not
supported for ''{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: An error occurred when invoking the method ''{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: Multiple WSIFProvider found supporting the same namespace URI
''{0}''. Found (''{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.
-# User Action: A following WSIF0007I message will be issued notifing which
WSIPFProvider will be used.
-# 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: Using WSIFProvider ''{0}'' for 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 removing correlator due to
timeout. 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: Using correlation service - ''{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 thrown while processing asynchronous response -
''{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: Preferred port ''{0}'' was not available
-# 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
+WSIF.0001E=WSIF0001E: An extension registry was not found for the element type
''{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: A failure occurred in loading WSDL from ''{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: An error occurred finding pluggable providers: {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 contains an operation type ''{0}'' which is not
supported for ''{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: An error occurred when invoking the method ''{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: Multiple WSIFProvider found supporting the same namespace URI
''{0}''. Found (''{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.
+# User Action: A following WSIF0007I message will be issued notifing which
WSIPFProvider will be used.
+# 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: Using WSIFProvider ''{0}'' for 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 removing correlator due to
timeout. 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: Using correlation service - ''{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 thrown while processing asynchronous response -
''{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: Preferred port ''{0}'' was not available
+# 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.2 +11 -11
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.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- Messages_ja.properties 1 Nov 2002 14:22:58 -0000 1.1.2.1
+++ Messages_ja.properties 17 Dec 2002 14:39:06 -0000 1.1.2.2
@@ -1,35 +1,35 @@
-WSIF.0001E=WSIF0001E: 둮뮗럔궻깒긙긚긣깏�[궕갂긄깒긽깛긣갋�^귽긵 ''{0}''
궸궰궋궲뙥궰궔귟귏궧귪궳궢궫갃
+WSIF.0001E=WSIF0001E:
\u62e1\u5f35\u5b50\u306e\u30ec\u30b8\u30b9\u30c8\u30ea\u30fc\u304c\u3001\u30a8\u30ec\u30e1\u30f3\u30c8\u30fb\u30bf\u30a4\u30d7
''{0}''
\u306b\u3064\u3044\u3066\u898b\u3064\u304b\u308a\u307e\u305b\u3093\u3067\u3057\u305f\u3002
# 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}'' \u304b\u3089\u306e WSDL
\u306e\u30ed\u30fc\u30c9\u4e2d\u306b\u30a8\u30e9\u30fc\u304c\u767a\u751f\u3057\u307e\u3057\u305f\u3002
# 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: pluggable 긵깓긫귽�_�[: {0} 궻뙚뢯궳긄깋�[궕뵯맯궢귏궢궫갃
+WSIF.0003W=WSIF0003W: pluggable \u30d7\u30ed\u30d0\u30a4\u30c0\u30fc: {0}
\u306e\u691c\u51fa\u3067\u30a8\u30e9\u30fc\u304c\u767a\u751f\u3057\u307e\u3057\u305f\u3002
# 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
\u306b\u3001\u30aa\u30da\u30ec\u30fc\u30b7\u30e7\u30f3\u30fb\u30bf\u30a4\u30d7 ''{0}''
\u304c\u542b\u307e\u308c\u3066\u3044\u307e\u3059\u304c\u3001\u3053\u308c\u306f ''{1}''
\u3067\u306f\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u305b\u3093\u3002
# 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: \u30e1\u30bd\u30c3\u30c9 ''{1}''
\u3092\u8d77\u52d5\u4e2d\u306b\u30a8\u30e9\u30fc\u304c\u767a\u751f\u3057\u307e\u3057\u305f\u3002(''{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: 벏궣긨�[��긚긻�[긚 URI ''{0}'' 귩긖�|�[긣궥귡븸릶궻
WSIFProvider 궕뙥궰궔귟귏궢궫갃 뙚뢯 (''{1}'')
+WSIF.0006W=WSIF0006W: \u540c\u3058\u30cd\u30fc\u30e0\u30b9\u30da\u30fc\u30b9 URI
''{0}'' \u3092\u30b5\u30dd\u30fc\u30c8\u3059\u308b\u8907\u6570\u306e WSIFProvider
\u304c\u898b\u3064\u304b\u308a\u307e\u3057\u305f\u3002 \u691c\u51fa (''{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.
@@ -37,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: namespaceURI ''{1} 궸뫮궢궲 WSIFProvider ''{0}''
귩럊뾭궢궲궋귏궥갃
+WSIF.0007I=WSIF0007I: namespaceURI ''{1} \u306b\u5bfe\u3057\u3066 WSIFProvider
''{0}'' \u3092\u4f7f\u7528\u3057\u3066\u3044\u307e\u3059\u3002
# 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
\u306f\u3001\u76f8\u95a2\u95a2\u4fc2\u5b50\u3092\u3001\u30bf\u30a4\u30e0\u30a2\u30a6\u30c8\u306e\u305f\u3081\u306b\u9664\u53bb\u3057\u3066\u3044\u307e\u3059\u3002ID:''{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: 몜듫긖�[긮긚귩럊뾭궢궲궋귏궥 - ''{0}''
+WSIF.0009I=WSIF0009I:
\u76f8\u95a2\u30b5\u30fc\u30d3\u30b9\u3092\u4f7f\u7528\u3057\u3066\u3044\u307e\u3059 -
''{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:
\u975e\u540c\u671f\u5fdc\u7b54\u3092\u51e6\u7406\u4e2d\u306b\u4f8b\u5916\u304c\u30b9\u30ed\u30fc\u3055\u308c\u307e\u3057\u305f
- ''{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: 딍�]궠귢궫�|�[긣 ''{0}'' 궕뿕뾭븉�\궳궢궫갃
+WSIF.0011I=WSIF0011I: \u5e0c\u671b\u3055\u308c\u305f\u30dd\u30fc\u30c8 ''{0}''
\u304c\u5229\u7528\u4e0d\u80fd\u3067\u3057\u305f\u3002
# 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.2 +7 -7
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.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- Messages_pt_BR.properties 1 Nov 2002 14:22:59 -0000 1.1.2.1
+++ Messages_pt_BR.properties 17 Dec 2002 14:39:06 -0000 1.1.2.2
@@ -1,4 +1,4 @@
-WSIF.0001E=WSIF0001E: Um registro de extens�o n�o foi encontrado para o tipo de
elemento ''{0}''
+WSIF.0001E=WSIF0001E: Um registro de extens\u00e3o n\u00e3o foi encontrado para o
tipo de elemento ''{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.
@@ -15,21 +15,21 @@
# 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}''
+WSIF.0004E=WSIF0004E: O WSDL cont\u00e9m um tipo de opera\u00e7\u00e3o ''{0}'' que
n\u00e3o \u00e9 suportado por ''{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: Ocorreu um erro ao chamar o m�todo ''{1}''. (''{0}'')
+WSIF.0005E=WSIF0005E: Ocorreu um erro ao chamar o m\u00e9todo ''{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: Encontrados v�rios WSIFProvider que suportam o mesmo URI de
espa�o de nomes ''{0}''. Encontrado (''{1}'')
+WSIF.0006W=WSIF0006W: Encontrados v\u00e1rios WSIFProvider que suportam o mesmo URI
de espa\u00e7o de nomes ''{0}''. Encontrado (''{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.
@@ -49,17 +49,17 @@
# 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: Utilizando servi�o de correla豫o - ''{0}''
+WSIF.0009I=WSIF0009I: Utilizando servi\u00e7o de correla\u00e7\u00e3o - ''{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: Exce豫o emitida ao processar resposta ass�ncrona - ''{0}''
+WSIF.0010E=WSIF0010E: Exce\u00e7\u00e3o emitida ao processar resposta
ass\u00edncrona - ''{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: A porta preferida ''{0}'' n�o estava dispon�vel
+WSIF.0011I=WSIF0011I: A porta preferida ''{0}'' n\u00e3o estava dispon\u00edvel
# 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.2 +9 -9
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.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- Messages_fr.properties 1 Nov 2002 14:22:59 -0000 1.1.2.1
+++ Messages_fr.properties 17 Dec 2002 14:39:06 -0000 1.1.2.2
@@ -1,9 +1,9 @@
-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''\u00e9l\u00e9ment ''{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 \u00e0
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.
@@ -15,21 +15,21 @@
# 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\u00e9ration ''{0}'' non
support\u00e9 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\u00e9thode ''{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\u00e9s, supportant l'' URI du
m\u00eame espace de nom ''{0}''. (''{1}'') trouv\u00e9.
# 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.
@@ -43,23 +43,23 @@
# 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\u00e9lateur en raison d''un d\u00e9passement de d\u00e9lai. 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\u00e9lation - ''{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\u00e9e lors du traitement de la r\u00e9ponse
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\u00e9f\u00e9r\u00e9 ''{0}'' n''\u00e9tait 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.2 +11 -11
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.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- Messages_zh.properties 1 Nov 2002 14:22:59 -0000 1.1.2.1
+++ Messages_zh.properties 17 Dec 2002 14:39:06 -0000 1.1.2.2
@@ -1,35 +1,35 @@
-WSIF.0001E=WSIF0001E：灌冷돕禱羹잚謹‘{0}’돨윈嵐鬧꿍깊
+WSIF.0001E=WSIF0001E\uff1a\u672a\u627e\u5230\u5143\u7d20\u7c7b\u578b\u2018{0}\u2019\u7684\u6269\u5c55\u6ce8\u518c\u8868
# 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\uff1a\u4ece\u2018{0}\u2019\u88c5\u5165 WSDL
\u65f6\u53d1\u751f\u6545\u969c
# 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：꿴冷옵꿨흙瓊묩넋埼：{0} 珂놔댄
+WSIF.0003W=WSIF0003W\uff1a\u67e5\u627e\u53ef\u63d2\u5165\u63d0\u4f9b\u7a0b\u5e8f\uff1a{0}
\u65f6\u51fa\u9519
# 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\uff1aWSDL
\u5305\u542b\u64cd\u4f5c\u7c7b\u578b\u2018{0}\u2019\uff0c\u5bf9\u4e8e\u2018{1}\u2019\u4e0d\u652f\u6301\u6b64\u7c7b\u578b
# 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\uff1a\u8c03\u7528\u65b9\u6cd5\u2018{1}\u2019\u65f6\u53d1\u751f\u9519\u8bef\u3002\uff08\u2018{0}\u2019\uff09
# 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：冷돕뜩몸連넣宮谿츰냔왕쇌 URI‘{0}’돨
WSIFProvider。冷돕（‘{1}’）
+WSIF.0006W=WSIF0006W\uff1a\u627e\u5230\u591a\u4e2a\u652f\u6301\u76f8\u540c\u540d\u79f0\u7a7a\u95f4
URI\u2018{0}\u2019\u7684 WSIFProvider\u3002\u627e\u5230\uff08\u2018{1}\u2019\uff09
# 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.
@@ -37,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：賈痰 namespaceURI‘{1}’돨 WSIFProvider‘{0}’
+WSIF.0007I=WSIF0007I\uff1a\u4f7f\u7528 namespaceURI\u2018{1}\u2019\u7684
WSIFProvider\u2018{0}\u2019
# 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
뇜혼宮밑凜綾。깃街：‘{0}’
+WSIF.0008W=WSIF0008W\uff1a\u7531\u4e8e\u8d85\u65f6\u5bfc\u81f4
WSIFDefaultCorrelationService
\u9664\u53bb\u76f8\u5173\u56e0\u5b50\u3002\u6807\u8bc6\uff1a\u2018{0}\u2019
# 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：賈痰宮밑륩蛟 －‘{0}’
+WSIF.0009I=WSIF0009I\uff1a\u4f7f\u7528\u76f8\u5173\u670d\u52a1 \uff0d\u2018{0}\u2019
# 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\uff1a\u5904\u7406\u5f02\u6b65\u54cd\u5e94\u65f6\u629b\u51fa\u5f02\u5e38
\uff0d\u2018{0}\u2019
# 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：看朞돨똥왯‘{0}’꼇옵痰
+WSIF.0011I=WSIF0011I\uff1a\u9996\u9009\u7684\u7aef\u53e3\u2018{0}\u2019\u4e0d\u53ef\u7528
# 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.2 +4 -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.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- Messages_it.properties 1 Nov 2002 14:22:59 -0000 1.1.2.1
+++ Messages_it.properties 17 Dec 2002 14:39:06 -0000 1.1.2.2
@@ -3,13 +3,13 @@
# 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 \u00e8 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}
+WSIF.0003W=WSIF0003W: si \u00e8 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.
@@ -22,14 +22,14 @@
# 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: si � verificato un errore durante il richiamo del metodo
''{1}''. (''{0}'')
+WSIF.0005E=WSIF0005E: si \u00e8 verificato un errore durante il richiamo del metodo
''{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: Sono stati individuati pi� WSIFProvider che supportano lo
stesso spazio nome URI ''{0}''. Trovato (''{1}'')
+WSIF.0006W=WSIF0006W: Sono stati individuati pi\u00f9 WSIFProvider che supportano
lo stesso spazio nome URI ''{0}''. Trovato (''{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.
1.1.2.2 +5 -5
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.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- Messages_es.properties 1 Nov 2002 14:22:59 -0000 1.1.2.1
+++ Messages_es.properties 17 Dec 2002 14:39:06 -0000 1.1.2.2
@@ -1,4 +1,4 @@
-WSIF.0001E=WSIF0001E: No se ha encontrado un registro de extensi�n para el tipo de
elemento ''{0}''
+WSIF.0001E=WSIF0001E: No se ha encontrado un registro de extensi\u00f3n para el
tipo de elemento ''{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.
@@ -15,14 +15,14 @@
# 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}''
+WSIF.0004E=WSIF0004E: WSDL contiene un tipo de operaci\u00f3n ''{0}'' no soportado
para ''{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: Se ha producido un error al invocar el m�todo ''{1}''.
(''{0}'')
+WSIF.0005E=WSIF0005E: Se ha producido un error al invocar el m\u00e9todo ''{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.
@@ -49,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: Utilizando servicio de correlaci�n - ''{0}''
+WSIF.0009I=WSIF0009I: Utilizando servicio de correlaci\u00f3n - ''{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: Se ha producido una excepci�n al procesar la respuesta
as�ncrona - ''{0}''
+WSIF.0010E=WSIF0010E: Se ha producido una excepci\u00f3n al procesar la respuesta
as\u00edncrona - ''{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.2 +11 -11
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.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- Messages_zh_TW.properties 1 Nov 2002 14:22:59 -0000 1.1.2.1
+++ Messages_zh_TW.properties 17 Dec 2002 14:39:06 -0000 1.1.2.2
@@ -1,35 +1,35 @@
-WSIF.0001E=WSIF0001E: ㏛ㄳ⑥ ''{0}'' ㅈ�읔�ガず㈄�疋n웡
+WSIF.0001E=WSIF0001E: \u627e\u4e0d\u5230 ''{0}''
\u5143\u7d20\u985e\u578b\u7684\u5ef6\u4f38\u767b\u9304
# 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: \u5f9e ''{0}'' \u8f09\u5165 WSDL \u6642\u5931\u6557
# 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: 퀾㏛쩳�~굶ず뇩ⓔぬ��좥탊Ν월�~좬{0}
+WSIF.0003W=WSIF0003W:
\u5c0b\u627e\u53ef\u5916\u639b\u7684\u63d0\u4f9b\u8005\u6642\uff0c\u767c\u751f\u932f\u8aa4\uff1a{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}''
+WSIF.0004E=WSIF0004E: WSDL \u542b\u6709\u4e0d\u652f\u63f4 ''{1}''
\u4f7f\u7528\u7684\u4f5c\u696d\u985e\u578b ''{0}''
# 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: \u547c\u53eb ''{1}''
\u65b9\u6cd5\u6642\uff0c\u767c\u751f\u932f\u8aa4\u3002(''{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: \u627e\u5230\u591a\u500b WSIFProvider
\u652f\u63f4\u76f8\u540c\u7684\u540d\u7a31\u7a7a\u9593 URI ''{0}''\u3002\u627e\u5230
(''{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.
@@ -37,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: 켔 WSIFProvider ''{0}'' Ξ⒀ namespaceURI ''{1}
+WSIF.0007I=WSIF0007I: \u5c07 WSIFProvider ''{0}'' \u7528\u65bc 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
�]툾��┱꼐간й츙�]쨖좧ID좬''{0}''
+WSIF.0008W=WSIF0008W: WSIFDefaultCorrelationService
\u56e0\u903e\u6642\u800c\u79fb\u9664\u76f8\u95dc\u56e0\u5b50\u3002ID\uff1a''{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: ⓒΞйㄼ츙첷찥걷 - ''{0}''
+WSIF.0009I=WSIF0009I: \u4f7f\u7528\u76f8\u4e92\u95dc\u4fc2\u670d\u52d9 - ''{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:
\u8655\u7406\u975e\u540c\u6b65\u56de\u61c9\u6642\uff0c\u64f2\u51fa\u7570\u5e38\u72c0\u6cc1
- ''{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: 킠챞ⓒΞ갼쫚ず곧 ''{0}''
+WSIF.0011I=WSIF0011I: \u7121\u6cd5\u4f7f\u7528\u504f\u597d\u7684\u57e0 ''{0}''
# 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.2 +8 -8
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.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- Messages_de.properties 1 Nov 2002 14:22:59 -0000 1.1.2.1
+++ Messages_de.properties 17 Dec 2002 14:39:06 -0000 1.1.2.2
@@ -1,4 +1,4 @@
-WSIF.0001E=WSIF0001E: Es wurde keine Erweiterungs-Registry f�r Elementtyp ''{0}''
gefunden.
+WSIF.0001E=WSIF0001E: Es wurde keine Erweiterungs-Registry f\u00fcr Elementtyp
''{0}'' gefunden.
# 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.
@@ -9,13 +9,13 @@
# 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}
+WSIF.0003W=WSIF0003W: Beim Suchen von Plug-in-f\u00e4higen 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: Die WSDL enth�lt den Operationstyp ''{0}'', der f�r ''{1}''
nicht unterst�tzt wird.
+WSIF.0004E=WSIF0004E: Die WSDL enth\u00e4lt den Operationstyp ''{0}'', der f\u00fcr
''{1}'' nicht unterst\u00fctzt 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.
@@ -29,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. Gefunden wurden (''{1}'').
+WSIF.0006W=WSIF0006W: Es wurden mehrere WSIFProvider gefunden, die den
Namespace-URI ''{0}'' unterst\u00fctzen. 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.
@@ -37,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: Es wird WSIFProvider ''{0}'' f�r namespaceURI ''{1}''
verwendet.
+WSIF.0007I=WSIF0007I: Es wird WSIFProvider ''{0}'' f\u00fcr 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\u00fcberschreitung. 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.
@@ -54,12 +54,12 @@
# 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: W�hrend der Verarbeitung der asynchronen Antwort wurde eine
Ausnahmebedingung ausgel�st: ''{0}''
+WSIF.0010E=WSIF0010E: W\u00e4hrend der Verarbeitung der asynchronen Antwort wurde
eine Ausnahmebedingung ausgel\u00f6st: ''{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: Der bevorzugte Port ''{0}'' war nicht verf�gbar.
+WSIF.0011I=WSIF0011I: Der bevorzugte Port ''{0}'' war nicht verf\u00fcgbar.
# 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
