Ticket #650 (closed Defect: fixed)

Opened 6 years ago

Last modified 6 years ago

Core: Jersey can't recover from a "media type conflict"

Reported by: jri Owned by: jri
Priority: Major Milestone: Release 4.4
Component: DeepaMehta Standard Distribution Version: 4.2
Keywords: Cc: dgf, Malte, carolina
Complexity: 3 Area: Application Framework / API
Module: deepamehta-core

Description

When the developer of a RESTful plugin makes a mistake by defining ambiguous resource methods Jersey reasonably complains:

SEVERE: The following errors and warnings have been detected with resource and/or provider classes:
  SEVERE: Producing media type conflict. The resource methods ... and ... can produce the same media type

But when the developer corrects the error and the plugin gets hot-redeployed Jersey still repeats that error message and even added another one:

SEVERE: The following errors and warnings have been detected with resource and/or provider classes:
  SEVERE: Producing media type conflict. The resource methods ... and ... can produce the same media type
  SEVERE: Conflicting URI templates. The URI template /myresource for root resource class ... and the URI template /myresource transform to the same regular expression /myresource(/.*)?

At this moment both error messages are actually not true. Only restarting DM helps.

Change History

comment:1 Changed 6 years ago by jri

  • Milestone changed from Release 4.3 to Release 4.4

comment:2 Changed 6 years ago by Jörg Richter

Core: Jersey recovers from bad resources (#650).

When the developer makes errors in the REST resources (JAX-RS root resource and provider classes/singletons) Jersey complains properly. As soon as the developer corrects the error Jersey will properly deploy the corrected resources. Restarting the DM server is no longer required.

See #650.

comment:3 Changed 6 years ago by Jörg Richter

Core: refactor Web Publishing service (#650).

WORDING CHANGE

"A plugin's Web Resources" -> "A plugin's Static Resources"

The former term "web resources" is not concise as "the plugin's REST resources" can also be regarded as web resources.
Now the dichotomy is "static resources" vs "REST resources".

See #650.

comment:4 Changed 6 years ago by Jörg Richter

Core: Jersey recovers from bad resources (#650).

When the developer makes errors in the REST resources (JAX-RS root resource and provider classes/singletons) Jersey complains properly. As soon as the developer corrects the error Jersey will properly deploy the corrected resources. Restarting the DM server is no longer required.

See #650.

comment:5 Changed 6 years ago by Jörg Richter

Core: refactor Web Publishing service (#650).

WORDING CHANGE

"A plugin's Web Resources" -> "A plugin's Static Resources"

The former term "web resources" is not concise as "the plugin's REST resources" can also be regarded as web resources.
Now the dichotomy is "static resources" vs "REST resources".

See #650.

comment:6 Changed 6 years ago by jri

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.