[ http://jira.jboss.com/jira/browse/BPEL-218?page=all ] Alejandro Guizar updated BPEL-218: ---------------------------------- Description: Currently, WSDL documents imported by a process are not examined during resolution of partner services, because an alternate, dynamic service catalog (e.g. an XML registry) is expected to be in place. However, in trivial scenarios, such as deployment from the designer, no alternate catalog exists. The only source of partner information is the list of imported documents. (was: wsdl documents imported by a process are not examined during resolution of partner services, because an alternate, more dynamic service catalog (e.g. an XML registry) is expected to be in place. however, in trivial scenarios, such as deployment from the designer, no alternate catalog exists and the main, if not sole, source of partner information is the list of imported documents.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/BPEL-218?page=all ] Alejandro Guizar updated BPEL-218: ---------------------------------- Fix Version/s: jBPM BPEL 1.1.1 (was: jBPM BPEL 1.1.GA) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/BPEL-218?page=all ] Alejandro Guizar updated BPEL-218: ---------------------------------- Original Estimate: 3 days Remaining Estimate: 3 days -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/BPEL-218?page=all ] Alejandro Guizar updated BPEL-218: ---------------------------------- Summary: introduce a central service catalog (was: make the imported wsdl documents a source of partner service descriptions) Description: In scenarios where full deployment information is missing (e.g. deployment from the eclipse designer) there is no source of partner service descriptions. An earlier proposal mentioned the imported WSDL documents. However, it is not a good solution as most BPEL processes are defined "in the abstract", i.e. without port-specific information. A better alternative is to maintain a central service catalog available to all processes. Registration in the central catalog can be either programmatic (ant task) or manual (web console). There are two registration modes: containment and reference. In the first mode, the WSDL document is stored in the jBPM database. In the second, only the document URL is remembered; the actual content is retrieved on demand. was:Currently, WSDL documents imported by a process are not examined during resolution of partner services, because an alternate, dynamic service catalog (e.g. an XML registry) is expected to be in place. However, in simple scenarios, such as deployment from the designer, no alternate catalog exists. The only source of partner service descriptions is the imported WSDL documents. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/BPEL-218?page=all ] Alejandro Guizar closed BPEL-218. --------------------------------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira