This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
CASA groups all "consumes" and "provides" endpoints by service units into one big blob, with no indication which might belong together to one service within a service unit or any meaning to its ordering. CASA also does not display the domain language specific information such as what business process or what xslt etc. the specific service is implemented in or invoked from. This can make it very hard and sometimes impossible to tell which endpoints belong together and how they relate to the application logic artifacts - which can make it hard or impossible for the user to link them. Visually it also is hard to comprehend and visualize the linking from/to a service. CASA should group by services, not (just) by Service Unit. It also should display service specific information related to the domain specific service definition (e.g. BP name). There probably is not enough meta-data today in the service units to allow this display enhancement, so we need to add more meta-data as required by CASA.
The BPEL build procedure adds several extensions to jbi.xml that is being generated for the service unit. These extensions are now recognized by CASA and are used to extend its functionality. Extension child elements are added to each provides and consumes element. All these extension elements belong to the http://www.sun.com/jbi/descriptor/service-unit namespace. The extension elements are: * <display-name> -- display name which should be used in CASA for the endpoint. By default, the "endpoint-name" value of the consumes/provides endpoint is used. * <process-name> -- name of the process (e.x., BPEL process), for the lack of a better name, that this endpoint belongs to. * <file-path> -- path to the source file of the process, relative to the module's sources root. An example of BPEL Project's jbi.xml: <?xml version="1.0" encoding="UTF-8" standalone="no"?> <jbi xmlns="http://java.sun.com/xml/ns/jbi" xmlns:ns0="http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1" xmlns:ns1="http://localhost/SynchronousSample/SynchronousSample" xmlns:ns2="http://www.sun.com/jbi/descriptor/service-unit" version="1.0"> <services binding-component="false"> <provides endpoint-name="partnerlinktyperole1_myRole" interface-name="ns1:portType1" service-name="ns0:SynchronousSample"> <ns2:display-name>SynchronousSample</ns2:display-name> <ns2:process-name>SynchronousSample</ns2:process-name> <ns2:file-path>SynchronousSample.bpel</ns2:file-path> </provides> </services> </jbi>
Remove dependency on 124293 since IEP is not part of the 6.1 release.
Support in BPEL, XSLT and SQL has been implemented.
verified by inspection in bpel jbi.xml. I'm not sure how this will be reflected in the GUI, i have no explaination other the xml description, so that is all i can verify.