Bug 1049999 – [GSS] (6.3) Class-Path: . can cause JBAS011046: A component named 'TestBean' is already defined in this module

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1049999 - [GSS] (6.3) Class-Path: . can cause JBAS011046: A component named 'TestBean' is already defined in this module

Summary:	[GSS] (6.3) Class-Path: . can cause JBAS011046: A component named 'TestBean' ...

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	Server (Show other bugs)
Sub Component:
Version:	6.2.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	DR0
Target Release:	EAP 6.3.0
Assigned To:	Kyle Lape
QA Contact:	Michal Karm Babacek
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1050003
	Show dependency tree / graph

Reported:	2014-01-08 10:31 EST by Brad Maxwell
Modified:	2014-06-29 18:21 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	In previous versions of JBoss EAP 6, some jar libraries in WEB-INF/lib contained a manifest with a Class-Path attribute that contained "." as an entry. This issue caused some resources or components get processed twice, causing warnings in the log. This release of the product ignores "." entries in Class-Path manifest attributes so resources are no longer processed twice.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2014-06-28 11:44:50 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	WFLY-2725	Major	Resolved	Class-Path: . can cause JBAS011046: A component named 'TestBean' is already defined in this module	2017-06-30 16:58 EDT

Groups: None (edit)

Description Brad Maxwell 2014-01-08 10:31:29 EST

'JBAS011046: A component named
'TestBean' is already defined in this module', I have narrowed it
down to it occurs if they have a jar manifest with Class-Path: .
It looks like when deploying it looks at the jar with the manifest
entry which then must be having it scan the jar containing the EJB
again and failing.

Having the Class-Path: . doesn't really make sense to me, however it
also seems like we should not be trying to deploy it twice.

It appears ManifestClassPathProcessor ignores the . when the Class-Path is in a jar at the root of an ear but not when the jar is in a war's WEB-INF/lib

server/src/main/java/org/jboss/as/server/deployment/module/ManifestClassPathProcessor.java

Comment 3 Michal Karm Babacek 2014-02-28 12:53:33 EST

The fix skips . and it's present in the delivered bits, VERIFIED.

Note You need to log in before you can comment on or make changes to this bug.