1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/src/share/jaxws_classes/com/sun/xml/internal/ws/resources/wsservlet.properties Wed Apr 27 01:27:09 2016 +0800
1.3 @@ -0,0 +1,248 @@
1.4 +#
1.5 +# Copyright (c) 2005, 2013, Oracle and/or its affiliates. All rights reserved.
1.6 +# DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
1.7 +#
1.8 +# This code is free software; you can redistribute it and/or modify it
1.9 +# under the terms of the GNU General Public License version 2 only, as
1.10 +# published by the Free Software Foundation. Oracle designates this
1.11 +# particular file as subject to the "Classpath" exception as provided
1.12 +# by Oracle in the LICENSE file that accompanied this code.
1.13 +#
1.14 +# This code is distributed in the hope that it will be useful, but WITHOUT
1.15 +# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
1.16 +# FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
1.17 +# version 2 for more details (a copy is included in the LICENSE file that
1.18 +# accompanied this code).
1.19 +#
1.20 +# You should have received a copy of the GNU General Public License version
1.21 +# 2 along with this work; if not, write to the Free Software Foundation,
1.22 +# Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
1.23 +#
1.24 +# Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
1.25 +# or visit www.oracle.com if you need additional information or have any
1.26 +# questions.
1.27 +#
1.28 +
1.29 +no.sunjaxws.xml=Runtime descriptor "{0}" is missing
1.30 +
1.31 +listener.parsingFailed=WSSERVLET11: failed to parse runtime descriptor: {0}
1.32 +JAXRPCSERVLET11.diag.cause.1=WSRuntimeInfoParser could not parse sun-jaxws.xml runtime descriptor
1.33 +WSSERVLET11.diag.check.1=Please check the sun-jaxws.xml file to make sure it is correct
1.34 +WSSERVLET11.diag.cause.2=The sun-jaxws.xml runtime deployment descriptor may be missing
1.35 +WSSERVLET11.diag.check.2=Please check the jaxrpc-ri.xml file to make sure it is present in the war file
1.36 +
1.37 +
1.38 +listener.info.initialize=WSSERVLET12: JAX-WS context listener initializing
1.39 +WSSERVLET12.diag.cause.1=Context listener starting
1.40 +WSSERVLET12.diag.check.1=Normal web service startup
1.41 +
1.42 +listener.info.destroy=WSSERVLET13: JAX-WS context listener destroyed
1.43 +WSSERVLET13.diag.cause.1=Context listener shutdown
1.44 +WSSERVLET13.diag.check.1=Normal web service shutdown
1.45 +
1.46 +servlet.info.initialize=WSSERVLET14: JAX-WS servlet initializing
1.47 +WSSERVLET14.diag.cause.1=Web Services servlet starting up.
1.48 +WSSERVLET14.diag.check.1=Normal Web Service deployment. Deployment of service complete.
1.49 +
1.50 +servlet.info.destroy=WSSERVLET15: JAX-WS servlet destroyed
1.51 +WSSERVLET15.diag.cause.1=Web Services servlet shutdown.
1.52 +WSSERVLET15.diag.check.1=Normal Web service undeployment. Undeployment complete.
1.53 +
1.54 +servlet.warning.missingContextInformation=WSSERVLET16: missing context information
1.55 +WSSERVLET16.diag.cause.1=The jaxrpc-ri.xml file may be missing from the war file
1.56 +WSSERVLET16.diag.check.1=Unjar the service war file; check to see that the jaxrpc-ri-runtime.xml file is present
1.57 +
1.58 +
1.59 +servlet.warning.duplicateEndpointName=WSSERVLET17: duplicate endpoint name
1.60 +WSSERVLET17.diag.cause.1=Two or more endpoints with the same name where found in the jaxrpc-ri.xml runtime descriptor
1.61 +WSSERVLET17.diag.check.1=Note that this may cause problems with service deployment
1.62 +
1.63 +
1.64 +servlet.info.emptyRequestMessage=WSSERVLET18: got empty request message
1.65 +WSSERVLET18.diag.cause.1=Message sent by client is empty
1.66 +WSSERVLET18.diag.check.1=This may or may not be intentional. If not examine client program for errors.
1.67 +
1.68 +servlet.trace.gotRequestForEndpoint=WSSERVLET19: got request for endpoint: {0}
1.69 +WSSERVLET19.diag.cause.1=Client request for this endpoint arrived
1.70 +WSSERVLET19.diag.check.1=Informational message only. Normal operation.
1.71 +
1.72 +servlet.error.noImplementorForEndpoint=WSSERVLET20: no implementor for endpoint: {0}
1.73 +WSSERVLET20.diag.cause.1=Implementation for this service can not be found
1.74 +WSSERVLET20.diag.check.1=Unzip the war, are the tie and serializer classes found?
1.75 +
1.76 +servlet.trace.invokingImplementor=WSSERVLET21: invoking implementor: {0}
1.77 +WSSERVLET21.diag.cause.1=The Web service is being invoked
1.78 +WSSERVLET21.diag.check.1=Normal web service invocation.
1.79 +
1.80 +servlet.error.noEndpointSpecified=WSSERVLET22: no endpoint specified
1.81 +WSSERVLET22.diag.cause.1=A request was invoked with no endpoint
1.82 +WSSERVLET22.diag.check.1=Set endpoint with stub.setTargetEndpoint property
1.83 +
1.84 +servlet.error.noResponseMessage=WSSERVLET23: no response message
1.85 +WSSERVLET23.diag.cause.1=The request generated no response from the service
1.86 +WSSERVLET23.diag.check.1=If a response was expected, check that a request message was actually sent
1.87 +WSSERVLET23.diag.check.2=The request may be malformed and be accepted by the service, yet did not generate a response
1.88 +
1.89 +servlet.trace.writingFaultResponse=WSSERVLET24: writing fault response
1.90 +WSSERVLET24.diag.cause.1=SOAPFault message is being returned to the client.
1.91 +WSSERVLET24.diag.check.1=Tracing message fault recorded.
1.92 +
1.93 +servlet.trace.writingSuccessResponse=WSSERVLET25: writing success response
1.94 +WSSERVLET25.diag.cause.1=SOAPMessage response is being returned to client
1.95 +WSSERVLET25.diag.check.1=Tracing message, normal response.
1.96 +
1.97 +servlet.warning.duplicateEndpointUrlPattern=WSSERVLET26: duplicate URL pattern in endpoint: {0}
1.98 +WSSERVLET26.diag.cause.1=The endpoint URL is a duplicate
1.99 +WSSERVLET26.diag.check.1=This may cause a problem, please remove duplicate endpoints
1.100 +
1.101 +servlet.warning.ignoringImplicitUrlPattern=WSSERVLET27: unsupported implicit URL pattern in endpoint: {0}
1.102 +WSSERVLET27.diag.cause.1=Implicit URLS are not supported in this release
1.103 +WSSERVLET27.diag.check.1=Remove the implicit URL
1.104 +
1.105 +servlet.faultstring.missingPort=WSSERVLET28: Missing port information
1.106 +WSSERVLET28.diag.cause.1=Target endpoint is null
1.107 +WSSERVLET28.diag.check.1=Set target endpoint with stub.setTargetEndpoint() property.
1.108 +
1.109 +servlet.faultstring.portNotFound=WSSERVLET29: Port not found ({0})
1.110 +WSSERVLET29.diag.cause.1=A port is specified, but a corresponding service implementation is not found
1.111 +WSSERVLET29.diag.check.1=Is the port valid? Unzip the war file and make sure the tie and serializers are present
1.112 +
1.113 +servlet.faultstring.internalServerError=WSSERVLET30: Internal server error ({0})
1.114 +WSSERVLET30.diag.cause.1=There was a server error processing the request
1.115 +WSSERVLET30.diag.check.1=This could be due to a number of causes. Check the server log file for exceptions.
1.116 +
1.117 +error.servlet.caughtThrowableWhileRecovering=WSSERVLET51: caught throwable while recovering from a previous exception: {0}
1.118 +WSSERVLET51.diag.cause.1=Service processing of the request generated an exception; while attempting to return a SOAPPFaultMessage a throwable was again generated
1.119 +WSSERVLET51.diag.check.1=Check the server.xml log file for exception information
1.120 +
1.121 +error.servlet.caughtThrowable=WSSERVLET49: caught throwable: {0}
1.122 +WSSERVLET49.diag.cause.1=Service processing of the request generated an exception; while attempting to return a SOAPFaultMessage a throwable was again generated
1.123 +WSSERVLET49.diag.check.1=Check the server.xml log file for exception information
1.124 +
1.125 +error.servlet.caughtThrowableInInit=WSSERVLET50: caught throwable during servlet initialization: {0}
1.126 +WSSERVLET50.diag.cause.1=WS runtime sun-jaxws.xml or web.xml may be incorrect
1.127 +WSSERVLET50.diag.check.1=Verify that sun-jaxws.xml and web.xml are correct in the service war file
1.128 +WSSERVLET50.diag.cause.2=Application server deployment descriptors may be incorrect
1.129 +WSSERVLET50.diag.check.2=Verify that Application server deployment descriptors are correct in the service war file
1.130 +WSSERVLET50.diag.cause.3=There may some Application Server initialization problems
1.131 +WSSERVLET50.diag.check.3=Check the server.xml file in the domain directory for failures
1.132 +
1.133 +publisher.info.applyingTransformation=WSSERVLET31: applying transformation with actual address: {0}
1.134 +WSSERVLET31.diag.cause.1=Transformation being applied
1.135 +WSSERVLET31.diag.check.1=Normal operation
1.136 +
1.137 +publisher.info.generatingWSDL=WSSERVLET32: generating WSDL for endpoint: {0}
1.138 +WSSERVLET32.diag.cause.1=WSDL being generated
1.139 +WSSERVLET32.diag.check.1=Normal Operation.
1.140 +
1.141 +exception.cannotCreateTransformer=WSSERVLET33: cannot create transformer
1.142 +WSSERVLET33.diag.cause.1=When publishing the service wsdl, the http location is patched with the deployed location/endpoint using XSLT transformation. The transformer could not be created to do the transformation.
1.143 +WSSERVLET33.diag.check.1=There maybe a transformation engine being used that is not compatible. Make sure you are using the correct transformer and version.
1.144 +WSSERVLET33.diag.cause.2=When publishing the service wsdl, the http location is patched with the deployed location/endpoint using XSLT transformation. The transformer could not be created to do the transformation.
1.145 +WSSERVLET33.diag.check.2=There maybe a transformation engine may not be supported or compatible. Check the server.xml file for exceptions.
1.146 +
1.147 +
1.148 +exception.transformationFailed=WSSERVLET34: transformation failed : {0}
1.149 +WSSERVLET34.diag.cause.1=The location patching on the wsdl failed when attempting to transform.
1.150 +WSSERVLET34.diag.check.1=Check the log file(s) for more detailed errors/exceptions.
1.151 +
1.152 +exception.templateCreationFailed=WSSERVLET35: failed to create a template object
1.153 +WSSERVLET35.diag.cause.1=A XSLT stylesheet template is create for the wsdl location patching using transformation. Template create failed.
1.154 +WSSERVLET35.diag.check.1=An exception was thrown during creation of the template. View exception and stacktrace for more details.
1.155 +
1.156 +servlet.html.method=WSSERVLET63: must use Post for this type of request
1.157 +WSSERVLET63.diag.cause.1=Web service requests must use HTTP POST method: WSI BP 1.0
1.158 +WSSERVLET63.diag.check.1=Make sure that your HTTP client is using POST requests, not GET requests
1.159 +
1.160 +
1.161 +servlet.faultstring.invalidContentType=WSSERVLET64: Invalid Content-Type, text/xml required
1.162 +WSSERVLET64.diag.cause.1=Web service requests must be a content type text/xml: WSI BP 1.0
1.163 +WSSERVLET64.diag.check.1=Make sure the client request is using text/xml
1.164 +
1.165 +error.implementorFactory.newInstanceFailed=WSSERVLET43: failed to instantiate service implementor for port \"{0}\"
1.166 +WSSERVLET43.diag.cause.1=Instantiation of the web service failed.
1.167 +WSSERVLET43.diag.check.1=Make sure web service is available and public. Examine exception for more details
1.168 +
1.169 +error.implementorFactory.servantInitFailed=WSSERVLET44: failed to initialize the service implementor for port \"{0}\"
1.170 +WSSERVLET44.diag.cause.1=The web service was instantiated, however, it could not be initialized
1.171 +WSSERVLET44.diag.check.1=Check the exception for more details. Make sure all the configuration files are correct.
1.172 +
1.173 +#not used by anything currently
1.174 +servlet.faultstring.invalidSOAPAction=WSSERVLET65: Invalid Header SOAPAction required
1.175 +WSSERVLET65.diag.cause.1=SOAP Action is required
1.176 +WSSERVLET65.diag.check.1=Add SOAPAction and appropriate value
1.177 +
1.178 +# {0} - URI
1.179 +servlet.no.address.available=No address is available for {0}
1.180 +
1.181 +servlet.html.title= Web Services
1.182 +servlet.html.title2=<h1>Web Services</h1>
1.183 +servlet.html.noInfoAvailable=<p>No JAX-WS context information available.</p>
1.184 +servlet.html.columnHeader.portName=Endpoint
1.185 +servlet.html.columnHeader.status=Status
1.186 +servlet.html.columnHeader.information=Information
1.187 +# This is a status code and should not be translated (if you have to, translate it using capital letters).
1.188 +# Usage not found. TODO Remove
1.189 +#servlet.html.status.active=ACTIVE
1.190 +# This is a status code and should not be translated (if you have to, translate it using capital letters).
1.191 +# Usage not found. TODO Remove
1.192 +#servlet.html.status.error=ERROR
1.193 +servlet.html.endpoint.table=<table border=\"0\"><tr><td>Service Name\:</td><td>{0}</td></tr><tr><td>Port Name\:</td><td>{1}</td></tr></table>
1.194 +servlet.html.information.table=<table border=\"0\"><tr><td>Address\:</td><td>{0}</td></tr><tr><td>WSDL\:</td><td><a href\="{0}?wsdl">{0}?wsdl</a></td></tr><tr><td>Implementation class\:</td><td>{1}</td></tr></table>
1.195 +servlet.html.notFound=<h1>404 Not Found: {0}</h1>
1.196 +
1.197 +
1.198 +#
1.199 +#
1.200 +# all the following properties are used by the http/ea package
1.201 +# these properties are not longer used as http/ea is no longer used
1.202 +#
1.203 +error.implementorFactory.noConfiguration=WSSERVLET36: no configuration specified
1.204 +error.implementorFactory.noInputStream=WSSERVLET37: no configuration specified
1.205 +error.implementorRegistry.unknownName=WSSERVLET38: unknown port name: {0}
1.206 +error.implementorRegistry.cannotReadConfiguration=WSSERVLET39: cannot read configuration
1.207 +error.implementorRegistry.classNotFound=WSSERVLET40: class not found: {0}
1.208 +error.implementorRegistry.incompleteInformation=WSSERVLET41: configuration information is incomplete
1.209 +error.implementorRegistry.duplicateName=WSSERVLET42: duplicate port name: {0}
1.210 +
1.211 +error.implementorRegistry.fileNotFound=WSSERVLET45: file not found: {0}
1.212 +error.wsdlPublisher.cannotReadConfiguration=WSSERVLET46: cannot read configuration
1.213 +error.servlet.init.config.parameter.missing=WSSERVLET47: cannot find configuration parameter: \"{0}\"
1.214 +error.servlet.init.config.fileNotFound=WSSERVLET48: config file: \"{0}\" not found
1.215 +#
1.216 +
1.217 +error.servlet.noImplementorForPort=WSSERVLET52: no implementor registered for port: {0}
1.218 +error.servlet.noPortSpecified=WSSERVLET53: no port specified in HTTP POST request URL
1.219 +error.servlet.noResponseWasProduced=WSSERVLET54: no response was produced (internal error)
1.220 +#
1.221 +info.servlet.gotEmptyRequestMessage=WSSERVLET55: got empty request message
1.222 +info.servlet.initializing=WSSERVLET56: JAX-WS servlet: init
1.223 +info.servlet.destroying=WSSERVLET57: JAX-WS servlet: destroy
1.224 +#
1.225 +trace.servlet.requestForPortNamed=WSSERVLET58: got request for port: {0}
1.226 +trace.servlet.handingRequestOverToImplementor=WSSERVLET59: handing request over to implementor: {0}
1.227 +trace.servlet.gotResponseFromImplementor=WSSERVLET60: got response from implementor: {0}
1.228 +trace.servlet.writingFaultResponse=WSSERVLET61: writing fault response
1.229 +trace.servlet.writingSuccessResponse=WSSERVLET62: writing success response
1.230 +#
1.231 +html.nonRootPage.title= Web Service
1.232 +html.nonRootPage.body1= <p>A Web Service is installed at this URL.</p>
1.233 +html.nonRootPage.body2= <p>Invalid request URI.</p><p>Please check your deployment information.</p>
1.234 +# Usage not found. TODO Remove
1.235 +#html.nonRootPage.body3a= <p>Please refer to <a href=\'
1.236 +# Concatenated with html.nonRootPage.body3a
1.237 +#html.nonRootPage.body3b= \'>this page</a> for information about the deployed services.</p>
1.238 +html.wsdlPage.title= Web Service
1.239 +html.wsdlPage.noWsdl=<p>No WSDL document available for publishing.</p><p>Please check your deployment information.</p>
1.240 +html.rootPage.title= Web Service
1.241 +html.rootPage.body1=<p>A Web Service is installed at this URL.</p>
1.242 +html.rootPage.body2a=<p>It supports the following ports:
1.243 +html.rootPage.body2b=</p>
1.244 +# Usage not found. TODO Remove
1.245 +#html.rootPage.body3a=<p>A WSDL description of these ports is available <a href='
1.246 +# Concatenated with html.rootPage.body3a
1.247 +#html.rootPage.body3b='>here.</a></p>
1.248 +html.rootPage.body4=<p>This endpoint is incorrectly configured. Please check the location and contents of the configuration file.</p>
1.249 +
1.250 +message.too.long=\nMessage has been truncated\n\
1.251 +use {0} property to increase the amount of printed part of the message
