Basis Errors and Solutions

Added support wof @WebServiceRef without ‘name’ attribute

July 7, 2009 at 1:25 am

[action attribute] [attribute] [attribute to] [CLIENT] [service] [web] [WebServiceRef] [xml attribute]

1. Changing the default sorting attributeSymptom After a search, the default method of sorting is “Relevance” even though sorting by relevance is not possible here. Therefore, only a blank entry is permitted as the default value. Reason...
2. Error in displaying multiple valued attribute in SearchSymptom Perform Search on documents/Records and provide the value to any of the multiple-valued attributes. The Search result is displayed with the wrong value [ the value of the previous attribute in...
3. BWA 7.00: Incorrect data for attribute types DATE and TIMESymptom You receive incorrect data for queries where the F-table has attributes of type DATE or TIME. You find the following entry in the trace of TREXIndexServer: “Attribute engine function not implemented...
4. Support for overloaded operations in web serviceSymptom The web service provider application with overloaded methods deploys with warning: ‘java.lang.RuntimeException: Duplicate request/response wrapper beans found’ Other terms overloaded web service operations Reason and Prerequisites The overloaded methods of web...

Symptom

@WebServiceRef is used without ‘name’
Other terms

WebServiceRef, web service client
Reason and Prerequisites

According to JAX-WS specification, @WebServiceRef doesn’t require ‘name’ attribute. The fix provides support for @WebServiceRef used without ‘name’.
Solution

Update to 7.20 SP01 or a subsequent SP.

Permalink