1.1 --- a/json/src/main/resources/org/apidesign/html/json/impl/Bundle.properties	Mon Dec 16 15:48:09 2013 +0100
     1.2 +++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.3 @@ -1,97 +0,0 @@
     1.4 -#
     1.5 -# DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
     1.6 -#
     1.7 -# Copyright 1997-2010 Oracle and/or its affiliates. All rights reserved.
     1.8 -#
     1.9 -# Oracle and Java are registered trademarks of Oracle and/or its affiliates.
    1.10 -# Other names may be trademarks of their respective owners.
    1.11 -#
    1.12 -# The contents of this file are subject to the terms of either the GNU
    1.13 -# General Public License Version 2 only ("GPL") or the Common
    1.14 -# Development and Distribution License("CDDL") (collectively, the
    1.15 -# "License"). You may not use this file except in compliance with the
    1.16 -# License. You can obtain a copy of the License at
    1.17 -# http://www.netbeans.org/cddl-gplv2.html
    1.18 -# or nbbuild/licenses/CDDL-GPL-2-CP. See the License for the
    1.19 -# specific language governing permissions and limitations under the
    1.20 -# License.  When distributing the software, include this License Header
    1.21 -# Notice in each file and include the License file at
    1.22 -# nbbuild/licenses/CDDL-GPL-2-CP.  Oracle designates this
    1.23 -# particular file as subject to the "Classpath" exception as provided
    1.24 -# by Oracle in the GPL Version 2 section of the License file that
    1.25 -# accompanied this code. If applicable, add the following below the
    1.26 -# License Header, with the fields enclosed by brackets [] replaced by
    1.27 -# your own identifying information:
    1.28 -# "Portions Copyrighted [year] [name of copyright owner]"
    1.29 -#
    1.30 -# Contributor(s):
    1.31 -#
    1.32 -# The Original Software is NetBeans. The Initial Developer of the Original
    1.33 -# Software is Oracle. Portions Copyright 2013-2013 Oracle. All Rights Reserved.
    1.34 -#
    1.35 -# If you wish your version of this file to be governed by only the CDDL
    1.36 -# or only the GPL Version 2, indicate your decision by adding
    1.37 -# "[Contributor] elects to include this software in this distribution
    1.38 -# under the [CDDL or GPL Version 2] license." If you do not indicate a
    1.39 -# single choice of license, a recipient has the option to distribute
    1.40 -# your version of this file under either the CDDL, the GPL Version 2 or
    1.41 -# to extend the choice of license to its licensees as provided above.
    1.42 -# However, if you add GPL Version 2 code and therefore, elected the GPL
    1.43 -# Version 2 license, then the option applies only if the new code is
    1.44 -# made subject to such option by the copyright holder.
    1.45 -#
    1.46 -
    1.47 -MSG_Completion_GET=The GET method means retrieve whatever information \
    1.48 - (in the form of an entity) is identified by the Request-URI. \
    1.49 - If the Request-URI refers to a data-producing process, \
    1.50 - it is the produced data which shall be returned as the entity in \
    1.51 - the response and not the source text of the process, \
    1.52 - unless that text happens to be the output of the process.
    1.53 -
    1.54 -MSG_Completion_HEAD=The HEAD method is identical to GET except that the server \
    1.55 - MUST NOT return a message-body in the response. The metainformation \
    1.56 - contained in the HTTP headers in response to a HEAD request SHOULD be \
    1.57 - identical to the information sent in response to a GET request. \
    1.58 - This method can be used for obtaining metainformation about the entity implied \
    1.59 - by the request without transferring the entity-body itself. \
    1.60 - This method is often used for testing hypertext links for validity, \
    1.61 - accessibility, and recent modification.
    1.62 -
    1.63 -MSG_Completion_POST=The POST method is used to request that the origin server \
    1.64 - accept the entity enclosed in the request as a new subordinate of the resource \
    1.65 - identified by the Request-URI in the Request-Line. POST is designed to allow \
    1.66 - a uniform method to cover annotation of existing resources,\ 
    1.67 - posting a message to a bulletin board, newsgroup, mailing list, or similar \
    1.68 - group of articles, providing a block of data, such as the result of submitting a \
    1.69 - form, to a data-handling process or extending a database through an append operation. \
    1.70 - The actual function performed by the POST method is determined by the server \
    1.71 - and is usually dependent on the Request-URI. The posted entity is subordinate \
    1.72 - to that URI in the same way that a file is subordinate to a directory containing it, \
    1.73 - a news article is subordinate to a newsgroup to which it is posted, \
    1.74 - or a record is subordinate to a database.
    1.75 -
    1.76 -MSG_Completion_PUT=The PUT method requests that the enclosed entity be stored \
    1.77 - under the supplied Request-URI. If the Request-URI refers to an already \
    1.78 - existing resource, the enclosed entity SHOULD be considered as a modified \
    1.79 - version of the one residing on the origin server. If the Request-URI does \
    1.80 - not point to an existing resource, and that URI is capable of being defined \
    1.81 - as a new resource by the requesting user agent, the origin server can \
    1.82 - create the resource with that URI. If a new resource is created, the origin \
    1.83 - server MUST inform the user agent via the 201 (Created) response. \
    1.84 - If an existing resource is modified, either the 200 (OK) or 204 (No Content) \
    1.85 - response codes SHOULD be sent to indicate successful completion of the request. \
    1.86 - If the resource could not be created or modified with the Request-URI, an \
    1.87 - appropriate error response SHOULD be given that reflects the nature of the problem. \
    1.88 - The recipient of the entity MUST NOT ignore any Content-* (e.g. Content-Range) \
    1.89 - headers that it does not understand or implement and MUST return \
    1.90 - a 501 (Not Implemented) response in such cases.
    1.91 -
    1.92 -MSG_Completion_DELETE=The DELETE method requests that the origin server delete \
    1.93 - the resource identified by the Request-URI. This method MAY be overridden \
    1.94 - by human intervention (or other means) on the origin server. The client \
    1.95 - cannot be guaranteed that the operation has been carried out, even if \
    1.96 - the status code returned from the origin server indicates that the action \
    1.97 - has been completed successfully. However, the server SHOULD NOT indicate \
    1.98 - success unless, at the time the response is given, it intends to delete \
    1.99 - the resource or move it to an inaccessible location.
   1.100 -