Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Without running your code myself it is a little tricky to understand why my example doesn't work in your scenario. However, in a attempt to debug this I would try the following:</p> <p>Stick a breakpoint on this line:</p> <pre><code>XmlElement securityToken = token.GetXml(new XmlDocument()); </code></pre> <p>And after stepping through this line, see what the securityToken XML looks like. It is this XML which is being injected into the security header. It isn't any more complicated than that. You coudl create this XML manually if you want. I used the WSE 3.0 classes because I didn't want to hand code the XML myself.</p> <p>I also notice that your security token definition looks slightly different to mine. My example was:</p> <pre><code>MessageHeader securityHeader = MessageHeader.CreateHeader("Security", "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd", securityToken, false); </code></pre> <p>Yours:</p> <pre><code>MessageHeader securityHeader = MessageHeader.CreateHeader("Security", "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#UsernameToken", securityToken, false); </code></pre> <p>The namespaces are different. Any reason for this?</p> <p>If the breakpoint added from the step above isn't hit then it would suggest that the behavior isn't actually being applied. In which case, you'll probably need to double check your configs to make sure that the behavior is correctly applied on the client. Alternatively (as my example shows) you can programatically add the custom behavior before sending the message.</p> <p>I recommend to anyone dealing with WCF issues, that they first turn on verbose logging and also use fiddler to see what is actually going over the wire.</p>
    singulars
    1. This table or related slice is empty.
    1. POAccidentally sticking SOAP Body inside of SOAP Header attempting to access WSE service with WCF client
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJunto
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAccidentally sticking SOAP Body inside of SOAP Header attempting to access WSE service with WCF client
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COActually now that I look at it (the inner XML that is), I see the nonce and the created date. I wonder why on earth my body is being injected into the header?
      singulars
      1. PO
      1. USSoftwareSavant
    2. COAlso, about the header being different, I am not sure why I changed that now that I think about it. I was experiementing with different things I guess.
      singulars
      1. PO
      1. USSoftwareSavant
    3. COI have no clue why it is doing this... I stop where you tell me, but I don't see any where in there where it injects the body into the header... I have to be missing something.
      singulars
      1. PO
      1. USSoftwareSavant
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload