For Channel: Phrase or sentence describing the channel.
For Item: The item synopsis.
@author Bill Brown@author Alejandro Abdelnur
@author Alejandro Abdelnur
A default ISO language code will be determined for a publisher at the time that a party establishes permissions to publish at a given operator site or implementation. This default language code will be applied to any description values that are provided with no language code.
@author Steve Viens (sviens@apache.org)
This interface defines the model as known from the MVC pattern. Its purpose is to provide read access to the data stored in the model.
String[] onProvideCompletionsFromMyField(String input) { return . . .; }
In other words, if a WSDL component model is derived from composite WSDL document made up of WSDL imports or includes, then its Description component acts as a container for all of the top-level WSDL components in the WSDL tree, starting with the root <description> element. These top-level WSDL components include Interface, Binding, Service, ElementDeclaration and TypeDefinition. @author John Kaputin (jkaputin@apache.org)
Description
describes a test which is to be run or has been run. Descriptions
can be atomic (a single test) or compound (containing children tests). Descriptions
are used to provide feedback about the tests that are about to run (for example, the tree view visible in many IDEs) or tests that have been run (for example, the failures view). Descriptions
are implemented as a single class rather than a Composite because they are entirely informational. They contain no logic aside from counting their tests.
In the past, we used the raw {@link junit.framework.TestCase}s and {@link junit.framework.TestSuite}s to display the tree of tests. This was no longer viable in JUnit 4 because atomic tests no longer have a superclass below {@link Object}. We needed a way to pass a class and name together. Description emerged from this. @see org.junit.runner.Request @see org.junit.runner.Runner @since 4.0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|