[
https://issues.apache.org/jira/browse/DELTASPIKE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696726#comment-13696726
]
Gerhard Petracek commented on DELTASPIKE-384:
---------------------------------------------
@john for sure the overall issue is cdi specific, since the configs are
collected in an extension-instance (like all the other extensions do currently)
-> depending on the server you are using, you will get even more issues and
side-effects at a later point.
-> we really need DS-335. everything else is a waste of time, since we have to
review all parts based on the final approach for DS-335 anyway.
currently use-cases which really need ds as a shared lib in an EAR are broken
anyway (in most servers).
(if you don't have use-cases which really need it, you can do it differently
and you won't/shouldn't have an issue with it.)
> ViewConfigUtils.toNodeList() fails in EAR
> -----------------------------------------
>
> Key: DELTASPIKE-384
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-384
> Project: DeltaSpike
> Issue Type: Bug
> Components: JSF-Module
> Affects Versions: 0.4
> Environment: JBoss AS 7.2.0.Final (EAP 6.1.0.Alpha1)
> Reporter: Richard DiCroce
> Assignee: John D. Ament
> Fix For: 0.5
>
> Attachments: deltaspike-384.patch
>
>
> ViewConfigUtils.toNodeList() does not work in my EAR.
> ClassUtils.tryToLoadClassForName() returns null for every class that
> toNodeList() uses it to try to load. This eventually results in a
> NullPointerException.
> To work around the problem, I have substituted my own version of the
> ViewConfigUtils class, containing the below rewrite of toNodeList() which is
> equivalent but doesn't require use of any classloaders:
> {code}
> public static List<Class> toNodeList(Class nodeClass) {
> List<Class> treePath = new ArrayList<Class>();
> do {
> treePath.add(0, nodeClass);
> nodeClass = nodeClass.getEnclosingClass();
> } while (nodeClass != null);
> return treePath;
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
