Figure 6 shows a ship operation with an order type parameter that is not present in the ship order operation.
图6显示了具有订单类型参数的船舶操作，该参数在船舶订单操作中不存在。
Require a zeroary constructor for all type parameter instantiations.
需要一个不带参数的(zeroary)构造函数，用于所有类型参数的实例化。
Accessing type parameter information through reflection is somewhat complex.
通过反射访问类型参数信息有些复杂。
Which means that the type parameter of the Box can be t or any subclass of t.
这表示Box的类型参数可以是t或t的任何子类。
Its input type comes from the type parameter of the AsyncTask that you create.
它的输入类型来自您所创建的AsyncTask的类型参数。
Require all instantiations of a type parameter to include a zeroary constructor.
要求类型参数的所有实例化都包括不带参数的(zeroary)构造函数。
The type parameter of that function allows a DER-encoded certificate to be loaded.
这个函数的type参数让我们可以加载使用 DER 编码的证书。
These annotations tell us exactly what constructors we can reliably call on a type parameter.
这些注释确切地告知我们针对类型参数，我们可以可靠地调用什么样的构造函数。
Similarly, it returns an ArrayList because that is the third type parameter of the AsyncTask.
类似地，它返回一个ArrayList，因为这是AsyncTask的第三个类型参数。
Then the type parameter instantiations would be inferred automatically from the method arguments.
然后会自动地从方法参数中推断出类型参数的实例化。
You passed something known to be a t, an unconstrained type parameter, and hence it could be anything.
你只是传递了类型T，一个没有约束的类型参数，所以它可以是任何类型。
If you instantiate a Box using the BoxImpl.make factory, you need only specify the type parameter once.
如果使用BoxImpl .make工厂实例化一个Box，您只需要指定一次类型参数。
But this code does not work — you cannot instantiate an array of a type represented by a type parameter.
但是这段代码不能工作——不能实例化用类型参数表示的类型数组。
Needless to say, this corresponds to the type parameter accepted by the Web service operation (retrieveByType).
不用说，这对应于Web服务操作（retrieveByType）接收的type参数。
Despite this identical bytecode, the type parameter information is recorded in the class format using a new signature attribute.
尽管是相同的字节码，但是类型参数信息用一个新的签名(signature)属性记录在类模式中。
The first part of the signature (within the angle brackets '<...>') is just the list of type parameter definitions for the class.
签名的第一部分（位于尖括号 ‘<...>’ 内）就是该类的类型参数定义清单。
The GenericTemplate instance holds the basic type parameter information for the class, along with the array of fields defined for the class.
GenericTemplate实例包含类的基本类型参数信息，还有为类定义的字段的数组。
Wildcards - the funky question marks where a type parameter should go - are a means of expressing a type constraint in terms of an unknown type.
通配符—使用一个奇怪的问号表示类型参数—是一种表示未知类型的类型约束的方法。
These each take the form of a type parameter name followed by the field descriptors for the class bound and interface bounds (if any) of the type.
这些定义的形式都相同，类型参数名称后接类型的类边界和接口边界(若存在)的字段描述符。
Of course, we could simply leave off the explicit bound and just make sure that we never instantiate the type parameter with an inappropriate type.
当然，我们可以完全不使用显式的范围，只要能确保没有用不适当的类型来实例化类型参数。
Now in the JSR-14 compilers 1.0 and 1.2, if you refer to a type parameter in a static field declaration, the compiler doesn't complain but it should.
现在，在JSR-14编译器 1.0和 1.2 中，如果您在静态字段声明中引用类型参数，编译器不会报错，但它本应该这么做。
Because a mixin's parent may be instantiated with a type parameter, there is no way for the type checker to determine all cases of accidental method overriding.
因为mixin的父类可能用类型参数被实例化，因此类型检查器就不能确定意外方法覆盖的所有情况。
In the case of generic methods, if a type parameter appears only once in the method signature, then it probably should be a wildcard rather than a named type parameter.
就泛型方法来说，如果一个类型参数在方法签名中只出现一次，它很有可能是一个通配符而不是一个命名的类型参数。
Now the code in Listing 3 will compile and do what we want, because we've said that the parameter to put can be a Box whose type parameter is t or any of its subtypes.
现在，清单3中的代码可以进行编译并执行，因为put的参数现在可以是参数类型为t或t的子类型的Box。
But when all we know about our superclass is that it's some instantiation of a type parameter, we have no idea what constructors will be available for a given instantiation.
但是在我们对超类所知的一切只限于它是类型参数的实例化时，对于什么样的构造函数可用于给定的实例化，我们没有任何概念。
But you cannot use a type parameter to access a constructor because, at compile time, you don't know what class is being constructed and therefore what constructors are available.
但是您不能使用类型参数访问构造函数，因为在编译的时候还不知道要构造什么类，因此也就不知道使用什么构造函数。
The only thing it cannot do is call the put method, and this is because it cannot verify the safety of such an operation without knowing the type parameter t for this Box instance.
它惟一不能做的事是调用put方法，这是因为在不知道该Box实例的类型参数t的情况下它不能检验这个操作的安全性。
When a Web service method with a complex type parameter receives a null or an instance with some attributes having null values, Lotus Domino V7.0.2 and Lotus Domino V8 behave differently.
当带有复杂类型参数的Web服务方法收到null或带null值属性的实例时，LotusDominoV7.0.2和Lotus DominoV8的行为不尽相同。
First off, in order to form a legal new expression on a type parameter, such as new T(), it's necessary to make sure that we're calling a constructor that is valid for every instantiation of T.
首先，为了对类型参数构造合法的new表达式（如 newT() ），必须确保我们调用的构造函数对于 T 的每个实例化都有效。
The problem with this extended Box is that we can only put the contents in a Box whose type parameter is exactly the same as the receiving box. So, for example, the code in Listing 3 won't compile
这个扩展Box的问题是，只能将内容放到类型参数与原 box完全相同的 Box 中。
应用推荐