本文整理汇总了Java中com.sun.xml.internal.ws.api.config.management.policy.ManagedClientAssertion.monitoringAttribute方法的典型用法代码示例。如果您正苦于以下问题：Java ManagedClientAssertion.monitoringAttribute方法的具体用法？Java ManagedClientAssertion.monitoringAttribute怎么用？Java ManagedClientAssertion.monitoringAttribute使用的例子？那么恭喜您, 这里精选的方法代码示例或许可以为您提供帮助。您也可以进一步了解该方法所在类com.sun.xml.internal.ws.api.config.management.policy.ManagedClientAssertion的用法示例。
在下文中一共展示了ManagedClientAssertion.monitoringAttribute方法的2个代码示例，这些例子默认根据受欢迎程度排序。您可以为喜欢或者感觉有用的代码点赞，您的评价将有助于系统推荐出更棒的Java代码示例。
示例1: createManagedObjectManager
import com.sun.xml.internal.ws.api.config.management.policy.ManagedClientAssertion; //导入方法依赖的package包/类
/**
* Client monitoring is OFF by default because there is
* no standard stub.close() method. Therefore people do
* not typically close a stub when they are done with it
* (even though the RI does provide a .close).
* <pre>
* prop | no assert | assert/no mon | assert/mon off | assert/mon on
* -------------------------------------------------------------------
* not set | off | off | off | on
* false | off | off | off | off
* true | on | on | off | on
* </pre>
*/
@NotNull public ManagedObjectManager createManagedObjectManager(final Stub stub) {
String rootName = stub.requestContext.getEndpointAddress().toString();
final ManagedClientAssertion assertion =
ManagedClientAssertion.getAssertion(stub.getPortInfo());
if (assertion != null) {
final String id = assertion.getId();
if (id != null) {
rootName = id;
}
if (assertion.monitoringAttribute() == Setting.OFF) {
return disabled("This client", rootName);
} else if (assertion.monitoringAttribute() == Setting.ON &&
clientMonitoring != Setting.OFF) {
return createMOMLoop(rootName, 0);
}
}
if (clientMonitoring == Setting.NOT_SET ||
clientMonitoring == Setting.OFF)
{
return disabled("Global client", rootName);
}
return createMOMLoop(rootName, 0);
}
示例2: createManagedObjectManager
import com.sun.xml.internal.ws.api.config.management.policy.ManagedClientAssertion; //导入方法依赖的package包/类
/**
* Client monitoring is OFF by default because there is
* no standard stub.close() method. Therefore people do
* not typically close a stub when they are done with it
* (even though the RI does provide a .close).
* <pre>
* prop | no assert | assert/no mon | assert/mon off | assert/mon on
* -------------------------------------------------------------------
* not set | off | off | off | on
* false | off | off | off | off
* true | on | on | off | on
* </pre>
*/
@NotNull public ManagedObjectManager createManagedObjectManager(final Stub stub) {
EndpointAddress ea = stub.requestContext.getEndpointAddress();
if (ea == null) {
return ManagedObjectManagerFactory.createNOOP();
}
String rootName = ea.toString();
final ManagedClientAssertion assertion =
ManagedClientAssertion.getAssertion(stub.getPortInfo());
if (assertion != null) {
final String id = assertion.getId();
if (id != null) {
rootName = id;
}
if (assertion.monitoringAttribute() == Setting.OFF) {
return disabled("This client", rootName);
} else if (assertion.monitoringAttribute() == Setting.ON &&
clientMonitoring != Setting.OFF) {
return createMOMLoop(rootName, 0);
}
}
if (clientMonitoring == Setting.NOT_SET ||
clientMonitoring == Setting.OFF)
{
return disabled("Global client", rootName);
}
return createMOMLoop(rootName, 0);
}