We can change the deployment-id format to include the appId (the name
of the ear usually), but I wouldn't want to make that change till
after TCK completion.
-David
On May 31, 2007, at 10:02 AM, Prasad Kashyap wrote:
In 2.0-M3, when a bean was deployed, it's deployment-id was prefixed
with geronimo-deploymentUtil9638.tmpdir
Eg: deployment-id=geronimo-deploymentUtil9638.tmpdir/
SimpleStatelessSession
This ensured a unique ID even if beans from across apps had the
same name.
Now, the deployment-id is prefixed with the name of the jar to which
the bean belongs to.
Eg: deployment-id=ejb.jar/SimpleStatelessSession
This eliminates the deployment of another app having a bean with the
same name packaged in a same named jar.
Cheers
Prasad
On 5/29/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
Not too long ago (say around M2-M3), I was able to deploy 2 different
testsupport EARs (test-ear-j2ee-1.3.ear and test-ear-j2ee-1.4.ear)
simultaneously on Geronimo.
But now, a naming conflict in OpenEJB seems to preclude one for the
other. I get the following exception on deploying the 2nd EAR
Caused by: org.apache.openejb.DuplicateDeploymentIdException:
ejb.jar/SimpleStatelessSession: ejb.jar/SimpleStatefulSession:
ejb.jar/SimpleBMPEntity: ejb.jar/SimpleCMPEntity
Now the question is, has the design and code changed as expected and
thus the testcase needs to change ?
Or is this a bug we have introduced in G ?
Cheers
Prasad
