Hi,
Well, I had the same problem with WSIF regarding the usage of complex types. In fact even in WSDL4J this is not supported and like Jeff has mentioned, you can use schema classes from the WSIF libraries to have an object model for the schemas.
My approach has been a little bit different. We are using Castor Schema object model for XSD, and in the <types> element we have several schemas (normally one per input/output structure with different namespace, but it is not required). Then, I have loaded the document in a DOM4J document and process it like a normal XML extracting the XSDs from the <types> element, and then I keep them in a cache. This solution is a little bit more expensive, but if you load the information only one time and a good use of caches, it is more easy. Anyway, I don't serialize the complete structures in beans and the other way around, I think that it is not necessary, and the XSDs are useful just for validation of input and output XML documents.
This is my approach and hopefully is useful for someone.
Best regards,
Alfredo Navarro [EMAIL PROTECTED]
From: Jeff Greif <[EMAIL PROTECTED]> Reply-To: [email protected] To: [email protected] Subject: Re: Why no WSIF release recently? Date: Thu, 05 May 2005 10:04:07 -0700
Archives: http://marc.theaimsgroup.com/?l=wsif-user&r=1&w=2
Yes, org.apache.wsif.schema classes are used to collect the various types and declared elements from the wsdl and all the imported schemas. We also then get all the schema definitions loaded into the grammar pool of a Xerces parser, and use the org.apache.xerces.xs (Xerces' implementation of the XML Schema API) classes to analyze the types etc.
Jeff
james hu wrote:
Jeff,
Thanks for the information. Can you point me to those archives? We don't like statical binding the XML to bean but processing XML tree at run-time is kind of approach we prefer. Does it use WSIF API to process XML since all the schema information is defined in wsdl which can be accessed via WSIF?
Thanks a lot,
James
*/Jeff Greif <[EMAIL PROTECTED]>/* wrote:
Lack of support for complex parameters for dynamic invocation in WSIF is a myth! My company's product consumes arbitrary web services dynamically using WSIF and deals with complex parameters most of the time. The product has some limitations in what it can handle, but these are not usually limitations of WSIF.
Whle I can't provide code samples, I've given info on this mailing list several times about approaches. Please check the archives or write me privately. Essentaily, we do it by processing the XML trees as is, in the context of the XML Schema data types describing it, rather than trying to bind the contents to Beans or other objects.
Jeff
james hu wrote:
> We ( one of HP's software division ) start actively looking into > possibility of utilizing wsif as a dynamic web service invoker. > Problem we have so far is the lack of complex input/output parameter > support. besides JROM ( which we don't know if we can use it or not ) > is there any plan to support complex parameters for dynamic > invocation in near future? Or, do you have any suggestions for the > best ( simple but effective ) approach to resolve this issue? > > Thanks, > James > */Aleksander Slominski /* wrote: > > Xu, Peng (GE Healthcare) wrote: > > > Hi, I'm new to WSIF and plan to use it. I noticed that there has > been > > no new release since Sept. 2003. Could someone tell me why? > > > there were no significant changes in WSIF CVS except for bug fixes. > nonethless with final Axis i plan to propose a release of updated > WSIF. > > is it anything particular that you want WSIF to do that it is not > doing now? > > thanks, > > alek > > -- > The best way to predict the future is to invent it - Alan Kay > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com >
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
