Skip navigation.
Home

weblogic

WS-Security, Weblogic 10.2, Service Controls, and legacy namespaces

BEA LogoI was working on a Weblogic Portal application that needed to get information from a secure (WS-Security) third party web service over https. This web service used a legacy (pre-OASIS) WS-Security namespace and modern clients (like the one bundled with Weblogic server) don't create messages that conform to the old specification. Here's what I did to work around this restriction...

XSLT not working with separate web server using BEA plugin (wrong Content-Type)

BEA LogoWe use client side XSLT to generate our pages. After a push to our testing environment, we noticed that the XSLT would fail in Firefox but not IE.

Syndicate content