Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 339485

Summary:

Deploying Gemini Blueprint in a PAR produces different behaviour compared to plan deployment

Product:

[RT] Virgo

Reporter:

Borislav Kapukaranov <b.kapukaranov>

Component:

runtime

Assignee:

Project Inbox <virgo-inbox>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

major

Priority:

Version:

3.0.0.M01

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

Attachments:

Description	Flags
blueprintTest.jar, consumes a service	none
org.example.blueprint-1.0.0.jar, publishes a service	none
blueprint.par	none
blueprint.plan	none

Description Borislav Kapukaranov

2011-03-10 05:08:25 EST

Gemini Blueprint(GB) can be deployed to Virgo using several mechanisms. Either one-by-one, with a plan or with a PAR. 

When packing the GB bundles in a PAR and deploying it then both blueprintTest.jar and org.example.blueprint-1.0.0.jar can consume and publish a service using their GB xmls, after these test bundles were deployed.

When trying the same exercise with the GB bundles referenced from scoped plan however, produces a ClassNotFoundError for BlueprintNamespaceHandler - attached in trace.txt.

The classloading model of a plan should be identical to a PAR's.

Steps to reproduce:
Failing scenario:
1. Place the GB bundles in repository/usr
2. Deploy the attached here blueprint.plan
3. Deploy the attached here blueprintTest.jar

Passing scenario:
1. Deploy the attached here blueprint.par
2. Deploy the attached here blueprintTest.jar

Comment 1 Borislav Kapukaranov

2011-03-10 05:08:49 EST

Created attachment 190838 [details]
blueprintTest.jar, consumes a service

Comment 2 Borislav Kapukaranov

2011-03-10 05:09:10 EST

Created attachment 190839 [details]
org.example.blueprint-1.0.0.jar, publishes a service

Comment 3 Borislav Kapukaranov

2011-03-10 05:10:09 EST

Created attachment 190840 [details]
blueprint.par

Comment 4 Borislav Kapukaranov

2011-03-10 05:10:40 EST

Created attachment 190841 [details]
blueprint.plan

Comment 5 Borislav Kapukaranov

2011-03-10 07:01:03 EST

Closing the bug. This issue seems to be reproducible also with PARs, although it happens more rarely. The cause might be some kind of a racing condition. Another bug will be raised if necessary.