Forum tags


Top Posters

Last 30 days

  • Antoine (94)
  • talita.pezzi (27)
  • eduardo.lawisch (14)
  • alfons.bataller.diaz (14)
  • sundaravadivel.n (13)
  • ravinderjit.singh (12)
  • hellonico (8)
  • jose.mendoza (8)
  • barry.sperling (7)
  • marcia.martins (7)

All time

  • Antoine (1403)
  • Shivanand (1189)
  • cshekhar (921)
  • psq (795)
  • jag (391)
  • metabyte (370)
  • arnaud (327)
  • jalateras (325)
  • dfrench (263)
  • venkaiah.k (198)

Show last 4 hrs - 12 hrs - 24 hrs

POLL

We are looking for more information to tailor our training to better meet the needs of our customers. Please indicate all options that apply.

I would like to attend specialized training from Intalio on BPM as it relates to my application area:


I would like to attend specialized training from Intalio on BPM as it relates to my job function:


I would like to attend specialized training from Intalio on BPM as it relates to my industry:

Login

MAIN arrow FORUMS
Adobe Flex Builder 3 + Intalio WSDL (0 viewing) 
Go to bottom Post Reply Favoured: 0
TOPIC: Adobe Flex Builder 3 + Intalio WSDL
#14828
dfrench (User)
Gold Boarder
User Offline Click here to see the profile of this user
Adobe Flex Builder 3 + Intalio WSDL 4 Months, 2 Weeks ago Karma: 8  
The structure of the wsdl generated for the business process appears to conflict with the Import Web Service feature of Flex Builder. Only one interface can be selected for a single Flex Builder project but each message is treated by Intalio as a separate interface. For example, in the project posted here, there are 2 separate interfaces created within the single wsdl one for each combination of executable and non-executable pool.
A workaround appears to be to put all the external service interactions into a single pool but this loses some of the semantics of the process.
Has anyone worked out a general approach to working in Flex and Intalio? Yes, I realise that this is a Flex Builder limitation but working well with the major RIA tools seems to be a reasonable target.
Generating a wsdl per interface would solve the issue and arguably fits better with SOA concepts by have the wsdl represent a contract between two independent services.
David
 
Report to moderator   Logged Logged  
 
Last Edit: 2008/07/05 22:47 By dfrench.
  The administrator has disabled public write access.
Go to top Post Reply
get the latest posts directly to your desktop