Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>That will set the username and password for Basic HTTP authentication. If you've tested it in SoapUI, I'm guessing the 'PasswordText' value you speak of is the 'WSS-Password Type' in the request details pane. That sets WSS security, not HTTP security.</p> <p>With JAX-WS in Java6 you need to attach a SOAPHandler to inject the WSS-Usertoken into the SOAP Header. There are plenty of bits and bobs about this round the net, but I couldn't find one single link to post, so here's some code instead to get you going...</p> <p>To add a handler you need something like:</p> <pre><code>final Binding binding = ((BindingProvider) servicePort).getBinding(); List&lt;Handler&gt; handlerList = binding.getHandlerChain(); if (handlerList == null) handlerList = new ArrayList&lt;Handler&gt;(); handlerList.add(new SecurityHandler()); binding.setHandlerChain(handlerList); // &lt;- important! </code></pre> <p>Then the SecurityHandler class will do the deed. Handlers are general things and get called for both successful messages and for faults, but perhaps more importantly they get called in <em>both</em> message directions - for the outgoing request and then again for the incoming response. You only want to handle outgoing messages. So you'll need something like:</p> <pre><code>public final class SecurityHandler implements SOAPHandler&lt;SOAPMessageContext&gt; { ... @Override public boolean handleMessage(final SOAPMessageContext msgCtx) { // Indicator telling us which direction this message is going in final Boolean outInd = (Boolean) msgCtx.get(MessageContext.MESSAGE_OUTBOUND_PROPERTY); // Handler must only add security headers to outbound messages if (outInd.booleanValue()) { try { // Get the SOAP Envelope final SOAPEnvelope envelope = msgCtx.getMessage().getSOAPPart().getEnvelope(); // Header may or may not exist yet SOAPHeader header = envelope.getHeader(); if (header == null) header = envelope.addHeader(); // Add WSS Usertoken Element Tree final SOAPElement security = header.addChildElement("Security", "wsse", "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"); final SOAPElement userToken = security.addChildElement("UsernameToken", "wsse"); userToken.addChildElement("Username", "wsse").addTextNode("MyWSSUsername"); userToken.addChildElement("Password", "wsse").addTextNode("MyWSSPassword"); } catch (final Exception e) { LOG.error(e); return false; } } return true; } ... // Other required methods on interface need no guts } </code></pre> <p>I've made a few assumptions here, but hopefully it'll get you going!</p> <p>Kind regards.</p>
    singulars
    1. This table or related slice is empty.
    1. POJAX-WS Password Type PasswordText
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USSimonB
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POJAX-WS Password Type PasswordText
      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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks. This worked perfectly and your answer was almost impossible to find by Googling, so allow me to add some keywords. JAX-WS WSSE
      singulars
      1. PO
      1. USJimmy2Times
    2. COWhen using this code I got the following exception in by log: `com.sun.xml.internal.messaging.saaj.soap.impl.ElementImpl addChildElement SEVERE: SAAJ0101: Parent of a SOAPBodyElement has to be a SOAPBody`.
      singulars
      1. PO
      1. USVic
 

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