Extends "external application" & modify form handler selection/parameters

patricka — do, 19 nov 2009 10:01:43 GMT

First off, I'm not a webservices expert. So if you have a grain of salt lying around, this would be the time to take it.

I don't know the bigger picture in which you are doing this, but my instincts tell me it would be wiser to just build your own integration for the external application.

Why use application integration if you can simply call some webservices that give you straight answers right away?

As for using Axis; recent insights seem to indicate that CXF is the way to go nowadays.

I know little about that topic so I can't help you there, sorry.

Greetings,

Patrick

Extends "external application" & modify form handler selection/parameters

RdeW — wo, 11 nov 2009 09:37:29 GMT

Any help/example on this one?

"SOAP service
It frequently occurs that a SOAP service is required in a form flow. Apache Axis comes standard with GX WebManager. This web service implementation of Apache allows creating Java stubs for SOAP web services. These stubs can then be used in a handler. This is also how the Microsoft CRM connector is realized.
It functions as follows:
- Using Apache Axis, a Java client stub is generated from the WSDL (Web Services Description Language) definition of the web service.
- This client stub is requested from a handler.
- The results of the request are processed (for example, by putting something in the session)."
http://www.gxdeveloperweb.com/documentation/GX-WebManager-9.10/Software-Development-Kit/GXD0052_en-GX-WebManager-9.10-Integration-APIs-20090710.pdf