You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by hu...@apache.org on 2002/11/04 17:37:47 UTC
cvs commit: xml-axis-wsif/java/src/org/apache/wsif/catalog Messages_ko.properties Messages.properties
hughesj 2002/11/04 08:37:47
Modified: java/src/org/apache/wsif/catalog Tag: pre1_2_0-patches
Messages_ko.properties Messages.properties
Log:
Update to Korean properties file and typo
Revision Changes Path
No revision
No revision
1.1.2.2 +2 -2 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.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- Messages_ko.properties 1 Nov 2002 14:22:58 -0000 1.1.2.1
+++ Messages_ko.properties 4 Nov 2002 16:37:47 -0000 1.1.2.2
@@ -9,7 +9,7 @@
# 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}
+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.
@@ -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: ���� 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.
1.5.2.1 +1 -1 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
retrieving revision 1.5.2.1
diff -u -r1.5 -r1.5.2.1
--- Messages.properties 6 Sep 2002 16:32:01 -0000 1.5
+++ Messages.properties 4 Nov 2002 16:37:47 -0000 1.5.2.1
@@ -9,7 +9,7 @@
# 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 plugagble providers: {0}
+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.