glassfish
  1. glassfish
  2. GLASSFISH-18997

Message IDs are missing for the messages in webservices-osgi.jar

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.0_b45
    • Fix Version/s: 4.0_b72_EE7MS4
    • Component/s: web_services
    • Labels:
      None

      Description

      Message IDs are missing for the messages in webservices-osgi.jar
      Extract glassfish3/glassfish/modules/webservices-osgi.jar
      Open each .properties file and check the message. Several messages don't have ID. For example,

      runtime.modeler.oneway.operation.no.checked.exceptions=Oneway operation should not throw any checked exceptions class:

      {0} method: {1} throws: {2}
      runtime.modeler.invalid.soapbinding.parameterstyle= Incorrect usage of Annotation {0}

      on

      {1}

      , ParameterStyle can only be WRAPPED with RPC Style Web service.

      Please check other messages as well, because these are just examples. In fact, many other messages in this jar file don't have ID.

        Activity

        Hide
        Lukas Jungmann added a comment -

        Assigning to myself.

        Do all messages coming from 'external' library have to have IDs? Is there some guideline for this? How the ID should look like - is ie METROXXXX good enough?

        Show
        Lukas Jungmann added a comment - Assigning to myself. Do all messages coming from 'external' library have to have IDs? Is there some guideline for this? How the ID should look like - is ie METROXXXX good enough?
        Hide
        tak09 added a comment -

        Please refer to this guideline.
        https://wikis.oracle.com/display/GlassFish/GlassFishV3LoggingMessageFormat
        "For v3 the requirement applies to SEVERE and WARNING messages only. In later versions of v3 message ids are required for INFO level messages too." Thank you.

        Show
        tak09 added a comment - Please refer to this guideline. https://wikis.oracle.com/display/GlassFish/GlassFishV3LoggingMessageFormat "For v3 the requirement applies to SEVERE and WARNING messages only. In later versions of v3 message ids are required for INFO level messages too." Thank you.
        Hide
        Lukas Jungmann added a comment -

        as of r58443 all messages should have ID

        Show
        Lukas Jungmann added a comment - as of r58443 all messages should have ID

          People

          • Assignee:
            Lukas Jungmann
            Reporter:
            tak09
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: