Community
Participate
Working Groups
>Problem: the logging messages for JAXB added past TOP-50234 are formatted incorrectly - the current block needs to be moved up to // MESSAGES end around line 382 - new entries for the 5 messages need to be of the form of TOP-50234 at line 644 LoggingLocalizationResource.java:643 { "query_has_joined_attribute_outside_fetch_group.MSGID", "TOP-50234"}, // JAXB Metadata Logging Messages { "jaxb_metadata_warning_ignoring_java_attribute", "Ignoring attribute [{0}] on class [{1}] as no Property was generated for it."}, { "jaxb_metadata_warning_invalid_bound_type", "The bound type [{0}] for adapter class [{1}] is invalid, and will be ignored."}, { "jaxb_metadata_warning_no_classes_to_process", "There are no classes to process for package [{0}]."}, { "jaxb_metadata_warning_ignoring_type_on_map", "Ignoring the type attribute set on xml-element since xml-map is specified on property [{0}]."}, { "jaxb_metadata_warning_invalid_java_attribute", "An unsupported JavaAttribute [{0}] was encountered an will be ignored."} >until this is fixed - no new WARNING logs can be added
>Testing should be added to exercise the 6 logs above - as currently they likely print the following generic message "There is no english translation for jaxb_metadata_warning_ignoring_type_on_map"
>one last review - spelling - "an" should be "and" was encountered an will be ignored
Created attachment 172770 [details] Core - Fix
Fix checked into trunk at rev: 7695
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink