Invalid child element in Policy file

Invalid child element in Policy file

Post by Q29saW4gRm » Sat, 23 Sep 2006 12:09:01


Hi,

I've just started looking at WSE, and I'm looking at passing UsernameTokens.

I've created a web service that used a custom UsernameTokenManager, and it
worked fine. I then programmatically created a policy, with a custome
assertion that created a simple input filter, at that worked fine.

Now I'm trying to set up the policy declaratively, amd I'm getting an error
in devstudio that seems to indicate that the extension for the assertion is
not a valid entry for the subsequent policy element.

My policy file is as follows


<policies xmlns=" http://www.yqcomputer.com/ ">
<extensions>
<extension name="usernameAssertion" type="ServiceUsernameAssertion" />
</extensions>
<policy name="ServerPolicy">
<usernameAssertion />
</policy>
</policies>


the error is

The element 'policy' in namespace
' http://www.yqcomputer.com/ '
has invalid child element 'usernameAssertion' in namespace
' http://www.yqcomputer.com/ '. List of possible elements
expected: 'usernameForCertificateSecurity, usernameOverTransportSecurity,
mutualCertificate10Security, mutualCertificate11Security,
anonymousForCertificateSecurity, kerberosSecurity, authorization,
requireSoapHeader, requireActionHeader' in namespace
' http://www.yqcomputer.com/ ' as well as any element in
namespace '##other'.

Hopefully someone can let me know where the problem lies.

Thanks in advance.


--
Colin Foulkes
 
 
 

1. Deserialization failed: The element has invalid child element

2. Possible to traverse the children of an element without specifying child element names?

Is it possible to traverse the values of children of an element, and
no need to specify
the children's element names in XSLT element?

The XML file can be

<bio>
<skills>
<languages>
<language>XML</language>
<language>Java</language>
</languages>
<databases>
<database>Oracle</database>
</databases>
</skills>
</bio>

Approach #1: This will just append all data in a sequence of strings,
not good
<UL>
<xsl:for-each select="/bio/skills">
<LI><xsl:value-of select="."/></LI>
</xsl:for-each>
</UL>

Approach #2: correct approach, but it's tedious to specify all element
names that
need to traverse
<UL>
<xsl:for-each select="/resume/skills">
<xsl:for-each select="languages/language">
<LI><xsl:value-of select="."/></LI>
</xsl:for-each>
<xsl:for-each select="databases/database">
<LI><xsl:value-of select="."/></LI>
</xsl:for-each>
</xsl:for-each>
</UL>

any ideas? please advise. thanks!!

3. XSLT: iterating all child elements and accessing homonymous children in sibling elements

4. Mapping Multiple Child elements to one child element...

5. XML question on elements, child and children of childs...

6. <Compilation> invalid child element

7. Invalid Path to File in Templates & Add-ins Word 2000

8. Invalid Path to File in Templates & Add-ins

9. How to add children elements to main element container...

10. Specified element is already the logical child of another element.

11. XSLT: remove multiple elements having same child element content

12. How to get list of all potential element's child elements.

13. Creating a dynamic element name from one of its children elements

14. element.children.length v/s element.childNodes.length

15. newb: recurse over elements children and disable all form elements