Opened 11 years ago

Closed 6 years ago

#5387 closed enhancement (patchwelcome)

Consuming SOAP Web Services

Reported by: guest Owned by: Tom Trenka
Priority: low Milestone: 1.9
Component: Dojox Version:
Keywords: web services soap proxy reviewed Cc: Jared Jurkiewicz
Blocked By: Blocking:

Description (last modified by Tom Trenka)

Currently there is no good way to consume SOAP web services from JavaScript?. There are libraries such as this one, but they are far from complete (e.g. support only .NET web services, but not GlassFish? ones).

It would be amazing if Dojo would be the first library to implement full support for SOAP web services!

Change History (9)

comment:1 Changed 11 years ago by Adam Peller

Component: GeneralDojox
Milestone: 2.0
Owner: changed from anonymous to Tom Trenka

no immediate plans to do this and no contribution, so we may have to close this out, for now

comment:2 Changed 11 years ago by Tom Trenka

I've done it before, but it takes a bit of a huge infrastructure to handle object definition, and conflicts (in part) with dojo.rpc. But let's leave it open without a milestone, perhaps it's possible to pull somewhere.

comment:3 Changed 11 years ago by dylan

Milestone: 1.3

Going to mark at 1.3. Either we get it on the roadmap, or we should close it out when we get there if we haven't made progress towards it.

comment:4 Changed 11 years ago by Tom Trenka

Description: modified (diff)
Milestone: 1.3future

Going to mark this as "future"; not sure when we'd get to implementing something like this, and we'll need real XML support before going this route.

comment:5 Changed 9 years ago by Adam Peller

Cc: Jared Jurkiewicz added

comment:6 Changed 7 years ago by dylan is a bit dated, but shows one way. If anyone wants to create a store for this, or work with rpc, it could be made to work.

I'd like to see if there's actual interest in having this as a dojo module.

comment:7 Changed 7 years ago by Tom Trenka

Priority: highlow
Status: newassigned

I'd like to see if there's any interest as well. The main problem (as I see it) is whether or not we would be trying to implement the full design-time stack (as in, read a WSDL file and create, on the fly, a service to consume SOAP messages)...or to just be able to understand the returned packages from a SOAP service.

If we're just trying to interpret message returns, it should be fairly easy to do. Generating something like what dojox.rpc does is an entirely different story.

comment:8 Changed 7 years ago by Tom Trenka

Keywords: reviewed added

comment:9 Changed 6 years ago by dylan

Milestone: future1.9
Resolution: patchwelcome
Status: assignedclosed

If there's interest in this, it should be done as a separate Dojo Foundation package. Closing as "patchwelcome"

Note: See TracTickets for help on using tickets.