Win a copy of Rust Web Development this week in the Other Languages forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Junilu Lacar
  • Rob Spoor
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Tim Moores
  • Jesse Silverman
  • Stephan van Hulst
  • Carey Brown
  • Al Hobbs
  • Piet Souris
  • Frits Walraven

How to use jwsdp with weblogic 8.1 sp 4

Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Can someone give me some pointers on how to deplpy a JWSDP developed SOAP service within a weblogic 8.1 sp 4 container.

My SOAP service is developed for document/literal style with no java binding. In other words, I pass SOAPElement directly to my implementation class. This allows me to selectively validate portions of the XML body so that I can do partial processing if possible. I use of Xalan to process the SOAPElement body and ultimately JAXB for the portions I'm going to process fully.

I have the service running beautifully in Tomcat, but my IS Dept will only support WebLogic 8.1 in production. The WebLogic 8.1 SOAPService development tools are not compatible with Xalan processing of the SOAP bodies (see below)


P.S. Info to the unsuspecting - SOAP services developed with WebLogic 8.1 sp 4 (and lower) tools (servicegen, wsdl2service, wspackage) CANNOT use Xalan or Jaxb to process the SOAP message. After hours of work with BEA Support they have confirmed this too. The problem is that the SOAPMessage and SOAPElement passed to implementation class inherits from a proprietary weblogic implementation of SOAPElement which DOES NOT inherit from org.w3c.dom.Node - therefore it cannot be passed into Xalan, Xerces, or JaxB methods.
What's wrong? Where are you going? Stop! Read this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic