Method and Description |
---|
org.jboss.security.xacml.sunxacml.cond.FunctionFactory.addAbstractConditionFunction(FunctionProxy, URI)
As of version 1.2, replaced by
FunctionFactory.addAbstractFunction(FunctionProxy,URI) .
The new factory system requires you to get a factory
instance and then call the non-static methods on that
factory. The static versions of these methods have been
left in for now, but are slower and will be removed in
a future version. |
org.jboss.security.xacml.sunxacml.cond.FunctionFactory.addAbstractGeneralFunction(FunctionProxy, URI)
As of version 1.2, replaced by
FunctionFactory.addAbstractFunction(FunctionProxy,URI) .
The new factory system requires you to get a factory
instance and then call the non-static methods on that
factory. The static versions of these methods have been
left in for now, but are slower and will be removed in
a future version. |
org.jboss.security.xacml.sunxacml.cond.FunctionFactory.addAbstractTargetFunction(FunctionProxy, URI)
As of version 1.2, replaced by
FunctionFactory.addAbstractFunction(FunctionProxy,URI) .
The new factory system requires you to get a factory
instance and then call the non-static methods on that
factory. The static versions of these methods have been
left in for now, but are slower and will be removed in
a future version. |
org.jboss.security.xacml.sunxacml.attr.AttributeFactory.addAttributeProxy(String, AttributeProxy)
As of version 1.2, replaced by
AttributeFactory.addDatatype(String,AttributeProxy) .
The new factory system requires you to get a factory
instance and then call the non-static methods on that
factory. The static versions of these methods have been
left in for now, but are slower and will be removed in
a future version. Note that this operates only on the
default factory. |
org.jboss.security.xacml.sunxacml.combine.CombiningAlgFactory.addCombiningAlg(CombiningAlgorithm)
As of version 1.2, replaced by
CombiningAlgFactory.addAlgorithm(CombiningAlgorithm) .
The new factory system requires you to get a factory
instance and then call the non-static methods on that
factory. The static versions of these methods have been
left in for now, but are slower and will be removed in
a future version. |
org.jboss.security.xacml.sunxacml.cond.FunctionFactory.addConditionFunction(Function)
As of version 1.2, replaced by
FunctionFactory.addFunction(Function) .
The new factory system requires you to get a factory
instance and then call the non-static methods on that
factory. The static versions of these methods have been
left in for now, but are slower and will be removed in
a future version. |
org.jboss.security.xacml.sunxacml.cond.FunctionFactory.addGeneralFunction(Function)
As of version 1.2, replaced by
FunctionFactory.addFunction(Function) .
The new factory system requires you to get a factory
instance and then call the non-static methods on that
factory. The static versions of these methods have been
left in for now, but are slower and will be removed in
a future version. |
org.jboss.security.xacml.sunxacml.cond.FunctionFactory.addTargetFunction(Function)
As of version 1.2, replaced by
FunctionFactory.addFunction(Function) .
The new factory system requires you to get a factory
instance and then call the non-static methods on that
factory. The static versions of these methods have been
left in for now, but are slower and will be removed in
a future version. |
org.jboss.security.xacml.sunxacml.attr.AttributeFactory.createAttribute(Node)
As of version 1.2, replaced by
AttributeFactory.createValue(Node) .
The new factory system requires you to get a factory
instance and then call the non-static methods on that
factory. The static versions of these methods have been
left in for now, but are slower and will be removed in
a future version. |
org.jboss.security.xacml.sunxacml.attr.AttributeFactory.createAttribute(Node, String)
As of version 1.2, replaced by
AttributeFactory.createValue(Node,String) .
The new factory system requires you to get a factory
instance and then call the non-static methods on that
factory. The static versions of these methods have been
left in for now, but are slower and will be removed in
a future version. |
org.jboss.security.xacml.sunxacml.attr.AttributeFactory.createAttribute(Node, URI)
As of version 1.2, replaced by
AttributeFactory.createValue(Node,URI) .
The new factory system requires you to get a factory
instance and then call the non-static methods on that
factory. The static versions of these methods have been
left in for now, but are slower and will be removed in
a future version. |
org.jboss.security.xacml.sunxacml.attr.AttributeFactory.createAttribute(URI, String)
As of version 1.2, replaced by
AttributeFactory.createValue(URI,String) .
The new factory system requires you to get a factory
instance and then call the non-static methods on that
factory. The static versions of these methods have been
left in for now, but are slower and will be removed in
a future version. |
org.jboss.security.xacml.sunxacml.combine.CombiningAlgFactory.createCombiningAlg(URI)
As of version 1.2, replaced by
CombiningAlgFactory.createAlgorithm(URI) .
The new factory system requires you to get a factory
instance and then call the non-static methods on that
factory. The static versions of these methods have been
left in for now, but are slower and will be removed in
a future version. |
org.jboss.security.xacml.sunxacml.PDP.evaluate(InputStream)
As of 1.2 this method should not be used. Instead, you
should do your own stream handling, and then use one of
the other
evaluate methods. The problem
with this method is that it often doesn't handle stream
termination correctly (eg, with sockets). |
org.jboss.security.xacml.sunxacml.attr.AttributeValue.evaluatesToBag()
As of 2.0, you should use the
returnsBag
method from the super-interface Expression . |
org.jboss.security.xacml.sunxacml.attr.AttributeDesignator.evaluatesToBag()
As of 2.0, you should use the
returnsBag
method from the super-interface Expression . |
org.jboss.security.xacml.sunxacml.attr.AttributeSelector.evaluatesToBag()
As of 2.0, you should use the
returnsBag
method from the super-interface Expression . |
org.jboss.security.xacml.sunxacml.cond.Apply.evaluatesToBag()
As of 2.0, you should use the
returnsBag
method from the super-interface Expression . |
org.jboss.security.xacml.sunxacml.cond.Condition.evaluatesToBag()
As of 2.0, you should use the
returnsBag
method from the super-interface Expression . |
org.jboss.security.xacml.sunxacml.cond.VariableReference.evaluatesToBag()
As of 2.0, you should use the
returnsBag
method from the super-interface Expression . |
org.jboss.security.xacml.sunxacml.cond.Evaluatable.evaluatesToBag()
As of 2.0, you should use the
returnsBag
method from the super-interface Expression . |
org.jboss.security.xacml.sunxacml.finder.ResourceFinderModule.findChildResources(AttributeValue)
As of version 1.2, replaced by
ResourceFinderModule.findChildResources(AttributeValue,EvaluationCtx) .
This version does not provide the evaluation context,
and will be removed in a future release. Also, not that
this will never get called when using the default PDP. |
org.jboss.security.xacml.sunxacml.finder.ResourceFinder.findChildResources(AttributeValue)
As of version 1.2, replaced by
ResourceFinder.findChildResources(AttributeValue,EvaluationCtx) .
This version does not provide the evaluation context to
the modules, and will be removed in a future release. |
org.jboss.security.xacml.sunxacml.finder.ResourceFinderModule.findDescendantResources(AttributeValue)
As of version 1.2, replaced by
ResourceFinderModule.findDescendantResources(AttributeValue,EvaluationCtx) .
This version does not provide the evaluation context,
and will be removed in a future release. Also, not that
this will never get called when using the default PDP. |
org.jboss.security.xacml.sunxacml.finder.ResourceFinder.findDescendantResources(AttributeValue)
As of version 1.2, replaced by
ResourceFinder.findDescendantResources(AttributeValue,EvaluationCtx) .
This version does not provide the evaluation context to
the modules, and will be removed in a future release. |
org.jboss.security.xacml.sunxacml.ctx.RequestCtx.getAction() |
org.jboss.security.xacml.sunxacml.ctx.Subject.getAttributes() |
org.jboss.security.xacml.sunxacml.cond.Apply.getConditionInstance(Node, String)
As of 2.0 you should avoid using this method, since it
does not provide a
Condition instance and
does not handle XACML 2.0 policies correctly. If you need
a similar method you can use the new version that
accepts a VariableManager . This will return
an Apply instance for XACML 1.x policies. |
org.jboss.security.xacml.sunxacml.ctx.RequestCtx.getEnvironmentAttributes() |
org.jboss.security.xacml.sunxacml.attr.AttributeDesignator.getInstance(Node, int)
As of 2.0 you should avoid using this method and should
instead use the version that takes a
PolicyMetaData instance. This method will
only work for XACML 1.x policies. |
org.jboss.security.xacml.sunxacml.PolicyReference.getInstance(Node, PolicyFinder)
As of 2.0 you should avoid using this method and should
instead use the version that takes a
PolicyMetaData instance. This method will
only work for XACML 1.x policies. |
org.jboss.security.xacml.sunxacml.Target.getInstance(Node, String)
As of 2.0 you should avoid using this method and should
instead use the version that takes a
PolicyMetaData instance. This method will
only work for XACML 1.x policies. |
org.jboss.security.xacml.sunxacml.Rule.getInstance(Node, String)
As of 2.0 you should avoid using this method and should
instead use the version that takes a
PolicyMetaData instance. This method will
only work for XACML 1.x policies. |
org.jboss.security.xacml.sunxacml.attr.AttributeSelector.getInstance(Node, String)
As of 2.0 you should avoid using this method and should
instead use the version that takes a
PolicyMetaData instance. This method will
only work for XACML 1.x policies. |
org.jboss.security.xacml.sunxacml.cond.Apply.getInstance(Node, String)
As of 2.0 you should avoid using this method, since it
does not handle XACML 2.0 policies correctly. If you need
a similar method you can use the new version that
accepts a
VariableManager . This will return
an Apply instance for XACML 1.x policies. |
org.jboss.security.xacml.sunxacml.TargetMatch.getInstance(Node, String, String)
As of 2.0 you should avoid using this method and should
instead use the version that takes a
PolicyMetaData instance. This method will
only work for XACML 1.x policies. |
org.jboss.security.xacml.sunxacml.ctx.RequestCtx.getResource() |
org.jboss.security.xacml.sunxacml.ctx.RequestCtx.getSubjects() |
org.jboss.security.xacml.sunxacml.cond.Apply.isCondition()
As of 2.0 this method should not be used, since an
Apply is never a Condition. |
Constructor and Description |
---|
org.jboss.security.xacml.sunxacml.cond.Apply(Function, List, boolean)
As of 2.0
Apply is no longer used for
Conditions, so the isCondition parameter
is no longer needed. You should now use the 2 parameter
constructor. This constructor will be removed in a
future release. |
org.jboss.security.xacml.sunxacml.ctx.Attribute(URI, URI, String, DateTimeAttribute, AttributeValue)
As of version 1.1, replaced by
Attribute(URI,String,DateTimeAttribute,AttributeValue) .
This constructor has some ambiguity in that it allows a
specified datatype and a value that already has some
associated datatype. The new constructor clarifies this
issue by removing the datatype parameter and using the
datatype specified by the given value. |
org.jboss.security.xacml.sunxacml.Rule(URI, int, String, Target, Apply)
As of 2.0 you should use the Constructor that accepts
the new
Condition class. |
org.jboss.security.xacml.sunxacml.ctx.Subject(Set) |
org.jboss.security.xacml.sunxacml.ctx.Subject(URI, Set) |
Copyright © 2023 JBoss by Red Hat. All rights reserved.