[jboss-jira] [JBoss JIRA] Resolved: (BPEL-218) introduce a central service catalog

Fri Oct 12 22:55:18 EDT 2007

     [ http://jira.jboss.com/jira/browse/BPEL-218?page=all ]

Alejandro Guizar resolved BPEL-218.
-----------------------------------

    Resolution: Done

Completed the central service catalog, along with a registration servlet for programmatic registration and a console page that allows manual registration.

> introduce a central service catalog
> -----------------------------------
>
>                 Key: BPEL-218
>                 URL: http://jira.jboss.com/jira/browse/BPEL-218
>             Project: JBoss jBPM BPEL
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Engine
>            Reporter: Alejandro Guizar
>         Assigned To: Alejandro Guizar
>             Fix For: jBPM BPEL 1.1 GA
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> 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.

-- 
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