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.

Bug 175327

Summary:	Support non-project-based JBI module (.war)
Product:	soa	Reporter:	Jun Qian <jqian>
Component:	Composite Application	Assignee:	Venkat Chellasamy <vchellasamy>
Status:	NEW ---
Severity:	blocker
Priority:	P3
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	ENHANCEMENT	Exception Reporter:

Description Jun Qian 2009-10-23 18:57:13 UTC

On Thu, Oct 15, 2009 at 5:43 PM, Jim Whiteley <jimmy@whiteley.org> wrote:
 
> I have a .war file built outside of the netbeans environment.  This
> .war has WS Consumers, which need to access WS Providers in another
> .war (which is built in the NB environment) through the NMR.  I would
> like to make them both part of the same service assembly.
>
> How is this accomplished?  The "Add JBI Module" dialog in NB seems to
> be strictly project-based.

Comment 1 Jun Qian 2009-10-23 18:57:54 UTC

Andreas Egloff wrote:
> CompApp folks would be better to answer, I don't think though that this is directly a feature in the composite app
project; there should be ways to achieve what you're looking for though.
>
> Besides starting to modify the build scripts one way (which I don't know if acceptable and I have not tried) might be
to have your war packaged into an ear; e.g. create and add a "Java EE/Enterprise Application", in project properties add
"JAR/Folder" and remove what's not needed. Or you could add a "Java EE/packaged archive" which point to your war to the
enterprise app.