I have recently started to work back on the BPEL reference support, and have been finding couple issues either in our BPEL implementation support or WSDL support. Most of the issues in the BPEL implementation were fixed, and WSDL related issues were workarounded, so let me try to list some of them here :
- WSDL2Java not generating interfaces if WSDL does not have a service declared. I tried to fix this issue, but it wasn't so easy and it looked to me that AXIS2 needed some of the information from the services. So I workarounded by adding the service to my wsdl. (TUSCANY-1882) - Still seeing issues from TUSCANY-1142 in some WSDL (pong.wsdl for example) - WSDL inline schema, defined with Namespace xmlns="http://www.w3.org/2000/10/XMLSchema"; are not being processed by Tuscany. And XSDGenerator throws exceptions and don't generate types on this case. It seems that couple ODE sample WSDL files use this namespace. - I was having some issues around wsdl with namespace like urn:/. Couple of BPEL process and WSDL I was tying to re-use from ODE were failing in our environment. But I can't reproduce this anymore and it might be related to the schema issue mentioned above. <process name="Pong" xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/executable"; targetNamespace="urn:/Pong.bpel" xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:tns="urn:/Pong.bpel" xmlns:pong="urn:/Pong.wsdl" expressionLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0"> In the BPEL invocation chain, data binding transformation is producing unexpected results <message><body><AnyTypeDataObjectImpl_instance><EOPPOSITE_FEATURE_BASE>-1</EOPPOSITE_FEATURE_BASE><anyAttribute/><mixed/><any/></AnyTypeDataObjectImpl_instance></body></message> As for some the issues I have already addressed/fixed : - Better support for multiple BPEL process - Fixing resolve issues when there where multiple BPEL process - Fixing componentType issues when there were multiple BPEL process - Properly generating BPEL invocation message that were affecting more complex BPEL process - Properly process BPEL Executable process Anyway, I'll keep you guys updated on the progress, and any help is appreciated on the wsdl issues. -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
