Hitachi

uCosminexus Application Server Messages


8.5.1 Details of sub-messages

The following table lists and describes the examples of sub-messages displayed in the KDJJ10006-E error message and the KDJJ20003-W warning message. If a sub-message not listed in this table is displayed, determine the cause of the error based on the contents of the message and then resolve the error.

Table 8‒1: Examples of sub-messages

No.

Sub-messages

1

Missing dependency for constructor aa....aa at parameter index bb....bb

2

Missing dependency for field: aa....aa

3

Illegal URI template for root resource class aa....aa: bb....bb

4

Illegal URI template for sub-resource method aa....aa: bb....bb

5

Illegal URI template for sub-resource locator aa....aa: bb....bb

6

Missing dependency for method aa....aa at parameter at index bb....bb

7

Method, aa....aa, annotated with bb....bb of resource, cc....cc, is not recognized as valid resource method.

8

The class aa....aa is an interface and cannot be instantiated.

9

A sub-resource locator, aa....aa, cannot have an entity parameter. Try to move the parameter to the corresponding resource method.

10

The class aa....aa does not have a public constructor and cannot be instantiated.

11

A (sub-)resource method, aa....aa, should have only one HTTP method designator. It currently has the following designators defined: bb....bb

12

Conflicting URI templates. The URI template aa....aa for root resource class bb....bb and the URI template cc....cc transform to the same regular expression dd....dd

13

Conflicting URI templates. The URI template aa....aa for sub-resource locator bb....bb and the URI template cc....cc transform to the same regular expression dd....dd

14

Consuming media type conflict. The resource methods aa....aa and bb....bb can consume the same media type

15

Producing media type conflict. The resource methods aa....aa and bb....bb can produce the same media type

16

A sub-resource locator, aa....aa, MUST return a non-void type.

17

A HTTP GET method, aa....aa, should not consume any entity.

18

A resource method, aa....aa, MUST be public scoped otherwise the method is ignored

19

A sub-resource method, aa....aa, MUST be public scoped otherwise the method is ignored

20

A sub-resource locator, aa....aa, MUST be public scoped otherwise the method is ignored

21

A HTTP GET method, aa....aa, MUST return a non-void type.

22

The class aa....aa is an abstract class and cannot be instantiated.

23

Return type aa....aa of method bb....bb is not resolvable to a concrete type

24

Parameter aa....aa of type bb....bb from cc....cc is not resolvable to a concrete type

The description and action corresponding to the example sub-messages are as follows:

Organization of this subsection

(1) Missing dependency for constructor aa....aa at parameter index bb....bb

aa....aa: Constructor name

bb....bb: Position of the parameter

Description

The dependency for the constructor parameter cannot be resolved.

Action

Use a supported parameter type in the injection annotation.

(2) Missing dependency for field: aa....aa

aa....aa: Field name

Description

The dependency for the field cannot be resolved.

Action

Use a supported parameter type in the injection annotation.

(3) Illegal URI template for root resource class aa....aa: bb....bb

aa....aa: Class name

bb....bb: Details

Description

The URI template for the root resource class is invalid.

Action

Remove the cause of the error based on the displayed details. For the examples on details, see 8.6 Inner messages displayed in the sub-messages (details when the URI template is invalid). If details not existing in 8.6 Inner messages displayed in the sub-messages (details when the URI template is invalid) are displayed, determine the cause of the error based on the details and then resolve the error.

(4) Illegal URI template for sub-resource method aa....aa: bb....bb

aa....aa: Sub-resource method name

bb....bb: Details

Description

The URI template for the sub-resource method is invalid.

Action

Remove the cause of the error based on the displayed details. For the examples on details, see 8.6 Inner messages displayed in the sub-messages (details when the URI template is invalid). If details not existing in 8.6 Inner messages displayed in the sub-messages (details when the URI template is invalid) are displayed, determine the cause of the error based on the details and then resolve the error.

(5) Illegal URI template for sub-resource locator aa....aa: bb....bb

aa....aa: Sub-resource locator name

bb....bb: Details

Description

The URI template for the sub-resource locator is invalid.

Action

Remove the cause of the error based on the displayed details. For the examples on details, see 8.6 Inner messages displayed in the sub-messages (details when the URI template is invalid). If details not existing in 8.6 Inner messages displayed in the sub-messages (details when the URI template is invalid) are displayed, determine the cause of the error based on the details and then resolve the error.

(6) Missing dependency for method aa....aa at parameter at index bb....bb

aa....aa: Method name

bb....bb: Position of the parameter

Description

The dependency for the method parameter cannot be resolved.

Action

Use a supported parameter type in the injection annotation.

(7) Method, aa....aa, annotated with bb....bb of resource, cc....cc, is not recognized as valid resource method.

aa....aa: Method name

bb....bb: Request method identifier

cc....cc: Class name

Description

The annotated method is not recognized as a valid resource method.

Action

Check the conditions for the resource method, sub-resource method, and sub-resource locator. If the conditions do not match, make the corrections.

(8) The class aa....aa is an interface and cannot be instantiated.

aa....aa: Interface name

Description

The interface cannot be instantiated.

Action

Do not use the Path annotation and Provider annotation in the interface.

(9) A sub-resource locator, aa....aa, cannot have an entity parameter. Try to move the parameter to the corresponding resource method.

aa....aa: Method name

Description

A sub-resource locator containing an entity parameter was detected.

Action

Move the entity parameter to an appropriate resource method or sub-resource method.

(10) The class aa....aa does not have a public constructor and cannot be instantiated.

aa....aa: Class name

Description

The class does not have a public constructor and cannot be instantiated.

Action

Define a public constructor.

(11) A (sub-)resource method, aa....aa, should have only one HTTP method designator. It currently has the following designators defined: bb....bb

aa....aa: Method name

bb....bb: List of request method identifiers

Description

A resource method or sub-resource method containing multiple request method identifiers was detected.

Action

Use only one request method identifier for a resource method or sub-resource method.

(12) Conflicting URI templates. The URI template aa....aa for root resource class bb....bb and the URI template cc....cc transform to the same regular expression dd....dd

aa....aa: URI template

bb....bb: Class name

cc....cc: URI template

dd....dd: Expression after resolution

Description

The URI templates of the root resource classes are conflicting. Two URI templates are similar, or regular expressions resolved to the same expression are being used.

Action

Make sure that the URI template of each root resource class is different. Also, make sure that the regular expressions are not resolved to the same expression.

(13) Conflicting URI templates. The URI template aa....aa for sub-resource locator bb....bb and the URI template cc....cc transform to the same regular expression dd....dd

aa....aa: URI template

bb....bb: Class name

cc....cc: URI template

dd....dd: Expression after resolution

Description

The URI templates of the sub-resource locators are conflicting. Two URI templates are similar, or regular expressions resolved to the same expression are being used.

Action

Make sure that the URI template of each sub-resource locator is different. Also, make sure that the regular expressions are not resolved to the same expression.

(14) Consuming media type conflict. The resource methods aa....aa and bb....bb can consume the same media type

aa....aa: Method name

bb....bb: Method name

Description

The MIME media types specified in the Consumes annotation are conflicting.

Action

Specify a non-conflicting MIME media type in the Consumes annotation.

(15) Producing media type conflict. The resource methods aa....aa and bb....bb can produce the same media type

aa....aa: Method name

bb....bb: Method name

Description

The MIME media types specified in the Produces annotation are conflicting.

Action

Specify a non-conflicting MIME media type in the Produces annotation.

(16) A sub-resource locator, aa....aa, MUST return a non-void type.

aa....aa: Method name

Description

The return value of the sub-resource locator is void.

Action

The return value of the sub-resource locator must not be void.

(17) A HTTP GET method, aa....aa, should not consume any entity.

aa....aa: Method name

Description

The method annotated in the GET request method identifier has an entity parameter.

Action

The method annotated in the GET request method identifier must not include an entity parameter.

(18) A resource method, aa....aa, MUST be public scoped otherwise the method is ignored

aa....aa: Method name

Description

A non-public resource method was detected. The detected resource method is ignored.

Action

A resource method must be public scoped.

(19) A sub-resource method, aa....aa, MUST be public scoped otherwise the method is ignored

aa....aa: Method name

Description

A non-public sub-resource method was detected. The detected sub-resource method is ignored.

Action

A sub-resource method must be public scoped.

(20) A sub-resource locator, aa....aa, MUST be public scoped otherwise the method is ignored

aa....aa: Method name

Description

A non-public sub-resource locator was detected. The detected sub-resource locator is ignored.

Action

A sub-resource locator must be public scoped.

(21) A HTTP GET method, aa....aa, MUST return a non-void type.

aa....aa: Method name

Description

The return value of the method annotated in the GET request method identifier is void.

Action

The return value of the method annotated in the GET request method identifier must not be void.

(22) The class aa....aa is an abstract class and cannot be instantiated.

aa....aa: Class name

Description

An abstract class cannot be instantiated.

Action

Do not use the Path annotation and Provider annotation in the abstract class.

(23) Return type aa....aa of method bb....bb is not resolvable to a concrete type

aa....aa: Return value type

bb....bb: Method name

Description

A method having a return value with a non-resolvable type parameter was detected.

Action

Review, and if necessary revise, the return value type.

(24) Parameter aa....aa of type bb....bb from cc....cc is not resolvable to a concrete type

aa....aa: Position of the parameter

bb....bb: Type

cc....cc: Method signature

Description

A method having an entity parameter with a non-resolvable type parameter was detected.

Action

Review, and if necessary revise, the entity parameter type.