Can the WS 2.0 soap.tcp transport use the SoapPlainFormatter instead of the SoapDimeFormatter?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Michael Herman $Parallelspace$ - 02 Aug 2004 16:18 GMT

In http://www.codeproject.com/useritems/SoapMSMQ.asp, the author mentions
that the WSE2.0 soap.tcp transport uses the SoapDimeFormatter to format the
SOAP envelope for physical transport the wire.

We'd like to test a simple UNIX/C-based SOAP client application that would
talk to our Windows WSE 2.0 publisher application. ...and it would be
easiest if we could simply open socket and send a SOAP envelope to Windows
WSE 2.0 app. DIME makes this more difficult for what we'd initially like to
achieve.

1. Can the WSE 2.0 soap.tcp transport use the SoapPlainFormatter instead of
the SoapDimeFormatter? If so, how can this be accomplished?

2. If #1 is not easy to do, what is the best Solaris equivalent of the WSE
classes? Note: for now, we're not using any of the advanced WS-I
specifications - just plain of two-way and one-way SOAP messaging.

Thanks,

Signature

Michael Herman
Parallelspace Corporation
Developers of Advanced Business Collaboration Solutions for Microsoft
SharePoint, Microsoft Live Communications Server and Groove Workspace

Portal and Content Migration Solution Specialists:
http://www.parallelspace.net/sharepoint
SharePoint Migration Knowledge Center:
http://groups.yahoo.com/group/sharepointmigration

Reply to this Message

Michael Herman $Parallelspace$ - 02 Aug 2004 17:08 GMT

Based on
http://www.eggheadcafe.com/forums/forumsearchbranch.asp?THREADID=11191&INTID=18,
it appears my WSE 2.0/Unix interop concern may be a (dead) red herring.

I would appreciate it if someone can confirm or disprove the issue with
soap.tcp using/not using the SoapDimeFormatter?

Thanks,

Signature

> In http://www.codeproject.com/useritems/SoapMSMQ.asp, the author mentions
> that the WSE2.0 soap.tcp transport uses the SoapDimeFormatter to format the
[quoted text clipped - 14 lines]
>
> Thanks,

Reply to this Message

Lucien - 03 Aug 2004 22:56 GMT

I'm not seeing anything in that thread that indicates an interop issue. The
last line says it only didn't work with 2.0 beta.

You can either create a DIME compatible client or you create a custom WSE
transport to implement a formatter that you implement.
If you would use plain formatter you still need some custom protocol to know
when the message receive is complete.
So you're probably best off with a custom WSE transport and define semantics
when message is received. Unfortunately there's no sample shipped with WSE
to define a custom protocol but looking at the msmq and other articles on
WSE custom messaging should help you do this. Otherwise let me know and I'll
check if I can find a sample.

By the way WS-I BP 1.0 only allows one way and request response model.

"Michael Herman (Parallelspace)" <longhorn@parallelspace.net.no$#$spam>
wrote in message news:%23rco6rKeEHA.556@tk2msftngp13.phx.gbl...

> Based on

http://www.eggheadcafe.com/forums/forumsearchbranch.asp?THREADID=11191&INTID=18,

> it appears my WSE 2.0/Unix interop concern may be a (dead) red herring.
>
[quoted text clipped - 24 lines]
> >
> > Thanks,

Reply to this Message

Michael Herman $Parallelspace$ - 13 Aug 2004 02:16 GMT

Thanks Lucien.

I'll take another look. In simple terms, I simply want to send a "plain
text" SOAP message from a Unix box to a WSE 2.0 client and visa versa.

Cheers,
Michael.

> I'm not seeing anything in that thread that indicates an interop issue. The
> last line says it only didn't work with 2.0 beta.
[quoted text clipped - 14 lines]
> wrote in message news:%23rco6rKeEHA.556@tk2msftngp13.phx.gbl...
> > Based on

http://www.eggheadcafe.com/forums/forumsearchbranch.asp?THREADID=11191&INTID=18,

> > it appears my WSE 2.0/Unix interop concern may be a (dead) red herring.
> >
[quoted text clipped - 30 lines]
> > >
> > > Thanks,

Reply to this Message

Can the WS 2.0 soap.tcp transport use the SoapPlainFormatter instead of the SoapDimeFormatter?

Free Magazines