Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This seems to be a popular question so I'll provide an overview of what we did in our situation.</p> <p>It seems that services built in .NET are following an older ws-addressing standard (<a href="http://schemas.xmlsoap.org/ws/2004/03/addressing/" rel="noreferrer">http://schemas.xmlsoap.org/ws/2004/03/addressing/</a>) and axis2 only understands the newer standard (<a href="http://schemas.xmlsoap.org/ws/2004/08/addressing/" rel="noreferrer">http://schemas.xmlsoap.org/ws/2004/08/addressing/</a>).</p> <p>In addition, the policyCache.config file provided is in a form that the axis2 rampart module can't understand.</p> <p>So the steps we had to do, in a nutshell:</p> <ul> <li>Read the policyCache.config and try to understand it. Then rewrite it into a policy that rampart could understand. (Some <a href="http://www.scribd.com/doc/466238/Official-Documentation-ws-apache-org-Axis2-Part-2" rel="noreferrer">updated docs</a> helped.)</li> <li>Configure rampart with this policy.</li> <li>Take the keys that were provided in the .pfx file and convert them to a java key store. There is a utility that comes with Jetty that can do that.</li> <li>Configure rampart with that key store.</li> <li>Write a custom axis2 handler that backward-converts the newer ws-addressing stuff that comes out of axis2 into the older stuff expected by the service.</li> <li>Configure axis2 to use the handler on outgoing messages.</li> </ul> <p>In the end it was a lot of configuration and code for something that is supposed to be an open standard supported by the vendors.</p> <p>Although I'm not sure what the alternative is...can you wait for the vendors (or in this case, the one vendor) to make sure that everything will inter-op?</p> <p>As a postscript I'll add that I didn't end up doing the work, it was someone else on my team, but I think I got the salient details correct. The other option that I was considering (before my teammate took over) was to call the WSS4J API directly to construct the SOAP envelope as the .NET service expected it. I think that would have worked too.</p>
    singulars
    1. This table or related slice is empty.
    1. POCalling .NET Web Service (WSE 2/3, WS-Security) from Java
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMichael Sharek
    1. USMichael Sharek
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCalling .NET Web Service (WSE 2/3, WS-Security) from Java
      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. COThis ws-addressing issue is a real pain in the ass. Not only does WSS2 use an old, pre-release version of WS-Addressing, it adds propritery elements to the soap header (e.g. wsa:via) that arent part of the schema. What a crock.
      singulars
      1. PO
      1. USskaffman
    2. COEveryone should keep in mind that WSE is obsolete. It was an interim solution to permit .NET web services to use the emerging WS-* stack. It should not be surprising if it does not support the final standards. WCF _does_ support the final standard versions of the WS-* protocols. It has replaced WSE, and should be used for all new development. WSE code should be replaced ASAP.
      singulars
      1. PO
      1. USJohn Saunders
    3. CO@John: people implementing a client don't have much choice what the vendor used to implement the server. I see you make your living doing this stuff, but to devs who have to integrate with this stuff, it really sucks that it is *so* dependent on having just the right tools of just the right version from the One True Vendor. See http://72.249.21.88/nonintersecting/?year=2006&monthnum=11&day=15&name=the-s-stands-for-simple&page
      singulars
      1. PO
      1. USRoboprog
 

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