Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1337618

Summary:	[GSS](6.4.z) PicketLink should default to using the JAXP TCCL in jboss
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	dhorton
Component:	PicketLink	Assignee:	Miroslav Sochurek <msochure>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Josef Cacek <jcacek>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.7	CC:	anmiller, bdawidow, bmaxwell, ihradek, jtruhlar, msochure, psilva, pskopek
Target Milestone:	CR1
Target Release:	EAP 6.4.11
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-17 13:12:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1361648, 1362250

Description dhorton 2016-05-19 15:57:47 UTC

Description of problem:

PLINK2-88 made it possible to configure PicketLink to load classes using the class's CL on the TCCL.  This made PicketLink work better with regards to classloading in a modular environment like JBoss EAP 6.x.

However, the default behavior is not to use this functionality.  Right now this functionality must be explicitly enabled using a system property:  -Dpicketlink.jaxp.tccl=true

Should this behavior be the default behavior instead?

Comment 2 Ivo Hradek 2016-10-11 07:50:27 UTC

Verified with EAP 6.4.11.CP.CR1;

Comment 4 Petr Penicka 2017-01-17 13:12:11 UTC

Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.