After much investigation and debugging I have confirmed that this is a bug in JBPM-BPEL / JBossWS [ I am not sure exactly where it happens during building partnerlinkTypes or internal to JBossWS]. It cannot read 'portType' correctly if it comes from different namespace. I have verified this in both hello and atm samples. I added debugging messages in WSDL11Reader class. It seems it cannot read any information about operations when portType is in different namespace. It can get to portType name, namespace and operation names but nothing else. For example, if(srcOperation.getStyle()!=null | && false == OperationType.NOTIFICATION.equals(srcOperation.getStyle())) | { | | processOperationInput(srcWsdl, srcOperation, destOperation, srcPortType); | } srcOperation's getStyle() returns 'null' where as it returns 'ONE-WAY' correctly if my hello.wsdl has same namespace as my imported wsdl file. However it can handle it correctly if schema is defined in different namespace. The only usecase that doesn't work is 'portType with different namespace'. So I guess I need to file JIRA issue? Please let me know which module is the correct one to file it - JBPM-BPEL or JBossWS. Also what is the average turnaround time for fixing bugs, I know the answer depends on various factors but some idea would be good. Meghana View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024475#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...