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

First;
To add some functionality, I`d like to add another option to the available filters in the "External application" tab. The option has to look a lot like "WM Include Filter" (at least Proxy, Server, Method, Protocol, Relatieve URL), and I like to at my own Service, Operation, Binding etc.. (from a WSDL file) untill it reaches the Message level (input/output). I found the "Integration API" documentation very usefull for this, but any tips are very welcome.

Second;
I`d like to select an External Application from within my form handler settings. So that I can somewhat attach my formfields to the WSDL/SOAP-fields from the "input" Message.


Anyone can help me get started with one of those functionalities?


What I found this far;
"Using the ‘External Application Integration’ license component, only existing filters can be used in the application integration module. See the ‘External Application Integration’ license component documentation at http://www.gxdeveloperweb.com/Software/Documentati on.htm#GXD0083 for a description of the standard functioning of the application integration. Using the ‘Integration APIs’ license component, new filters can also be built."

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

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