This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
The following policy expression requires:
• Transport or message-level security. Additionally there is a policy assertion informing clients that the service performs logging of some kind. This policy assertion may be completely ignored, as specified by the wsp:Ignorable attribute.
Don't both mean the same here??
SCJP 1.4 90%, SCWCD5 94%, Next SCDJWS--> In Naescent stage. Researching abt exam and material itself.
First of all, this is the policy expression discussed:
The <All> element means that all contained policies are required (but it is not as simple, so read on! ).
The <mtom:OptimizedMimeSerialization> element says that MIME serialization is required, until we encounter the Optional attribute, which suddenly makes MIME serialization optional. Note that the Optional attribute only affects the MIME serialization policy!
The <wsam:Addressing> element says that addressing is required. Period.
The <log:Logging> element says that logging is required, until we see the Ignorable attribute with a value "true" which tells us that the requirement regarding logging may be ignored. Again, this only affects the policy element in which the Ignorable attribute appears, which is logging.
Then there is an <ExaclyOne> element, which means that exactly one of the policies contained in this element is required.
Hope this clarifies!
thanks for the reply. However probably my question was not clear. I already understood each policy expression element from your notes. However I was confused how using Optional and Ignorable elements affects each expression. So in this example if we consider the following snippet.
How would it impact the overall policy if I rewrite it like this (note I have switched the attributes)
Point being that if each attribute causes the particular policy to be optional/ignorable (which I am taking means implementer may or may not implement it), why two attributes, why not just one.