Bug 1292891

Summary: [GSS](6.4.z) WFLY-5882 - BeanELResolver does not support methods that use varargs
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Ingo Weiss <iweiss>
Component: EEAssignee: Dmitrii Tikhomirov <dtikhomi>
Status: CLOSED CURRENTRELEASE QA Contact: Peter Mackay <pmackay>
Severity: high Docs Contact:
Priority: high    
Version: 6.4.0CC: bbaranow, bmaxwell, cdewolf, david.lloyd, dtikhomi, fjuma, jtruhlar, maschmid, pmackay, smarlow, ssilvert
Target Milestone: CR1   
Target Release: EAP 6.4.8   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 12:35:53 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: 1279553, 1319807    
Attachments:
Description Flags
Reproducer none

Description Ingo Weiss 2015-12-18 16:21:11 UTC 
Created attachment 1107219 [details]
Reproducer

When passing BeanELResolver a method that uses varargs, BeanELResolver throws the following exception:

java.lang.IllegalArgumentException: wrong number of arguments
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at javax.el.BeanELResolver.invokeMethod(BeanELResolver.java:834)
	at javax.el.BeanELResolver.invoke(BeanELResolver.java:527)
	at org.apache.el.parser.AstValue.getValue(AstValue.java:156)
	at BeanELResolverTest.readExpressionValue(BeanELResolverTest.java:32)
	at BeanELResolverTest.testMethodWithFixArgumentList(BeanELResolverTest.java:21)

Steps to reproduce:

1. Unzip reproducer
2. Run mvn test
Comment 6 Mike McCune 2016-03-28 22:32:18 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 9 Peter Mackay 2016-05-05 12:00:31 UTC 
Verified with EAP 6.4.8.CP.CR2
Comment 10 Petr Penicka 2017-01-17 12:35:53 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.