Please use the Apache issue tracking system for new NetBeans issues (https://issues.apache.org/jira/projects/NETBEANS0/issues) !!
Bug 101683 - Add cross-project reference in composite application project
Add cross-project reference in composite application project
Status: RESOLVED FIXED
Product: soa
Classification: Unclassified
Component: Composite Application
6.x
All All
: P1 (vote)
: 6.x
Assigned To: Jun Qian
issues@soa
plan60
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-19 04:12 UTC by Jun Qian
Modified: 2007-06-26 01:20 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jun Qian 2007-04-19 04:12:59 UTC
Add cross-project reference in composite application project.
Comment 1 Jun Qian 2007-05-25 01:16:02 UTC
Implemented in CB #903.
Comment 2 Jun Qian 2007-06-26 00:31:11 UTC
http://www.netbeans.org/issues/show_bug.cgi?id=96737 shows an example of cross-project reference working in compapp.
Comment 3 Jun Qian 2007-06-26 01:20:47 UTC
The following documents the current cross-project reference behavior in CompApp.

When adding a JBI Module into a CompApp, an implicit project reference is created. Since cross-project reference is not
transitive, the CompApp is not aware of any project that its constituent JBI Modules are referencing. This means when
creating new test cases in the CompApp, only WSDLs defined in the CompApp and CompApp's constituent JBI Modules are listed.

The following shows an example:

CompApp1: (has one JBI Module)
    BPELModule1

BPELModule1 (referencing BPELModule2)
    WSDL1
    WSDL2 (importing WSDL4 from BPELModule2)

BPELModule2
    WSDL3
    WSDL4


In CompApp1, the following WSDLs will be listed:
  WSDL1, WSDL2 (WSDL4 is accessible as part of WSDL2)

In order to create a test case for WSDL3, the user needs to explicitly add BPELModule2 as a constituent JBI Module into
CompApp1.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo