Bug 1337618 - [GSS](6.4.z) PicketLink should default to using the JAXP TCCL in jboss
Summary: [GSS](6.4.z) PicketLink should default to using the JAXP TCCL in jboss
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: PicketLink
Version: 6.4.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.11
Assignee: Miroslav Sochurek
QA Contact: Josef Cacek
URL:
Whiteboard:
Depends On:
Blocks: eap6411-payload 1362250
TreeView+ depends on / blocked
 
Reported: 2016-05-19 15:57 UTC by dhorton
Modified: 2019-09-12 10:00 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-17 13:12:11 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-4636 0 Major Verified (7.0.z) PicketLink should default to using the JAXP TCCL in jboss 2020-07-28 01:55:35 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.