Win a copy of The Way of the Web Tester: A Beginner's Guide to Automating Tests this week in the Testing forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Problem with "unwrapped" service

Chris Nappin
Ranch Hand
Posts: 36
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
(Apologies for cross-posting but this is an in-depth Web Services issue so some generic J2EE 1.4 experts may be able to provide useful feedback)

I'm trying to decide upon an approach for implementing J2EE 1.4-based Web Services that can be deployed on as many different application servers as possible.

So far I've decided upon:

- WSDL first (because the interface definitions need to be communicated to customers)
- doc/literal wrapped (for WS-I compliance and .Net interoperability)
- using JWSDP to auto-generate the Java interface types (rather than using vendor-specific tools)
- using the JAX-RPC 1.1 "unwrap" mode (results in much nicer method signatures)

This all worked fine, and I have an example working in JBoss. So I'm now trying my code on WebLogic (9.2) and it fails at the first hurdle. What is happening is that the "wrapper" tags are being added twice by WebLogic when creating the SOAP request body.

If I alter my approach to use "wrapped" instead of "unwrapped" parameters then it works fine.

My question is: is it not possible to use JAX-RPC 1.1 unwrapped mode with WebLogic? Is there some extra WebLogic-specific deployment descriptor that I need to create?

Let me give an example of a method signature using unwrapped mode:

public String ping();

This becomes really ugly when using wrapped mode:

public PingResponse ping(Ping ping);

(where "Ping" is a JavaBean with *no* property, and "PingResponse" just has a single property).

Any help or advice gratefully recieved! I've looked through the WebLogic documentation but all the examples are RPC/Literal or Doc/Literal Wrapped.

  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic