[
https://jira.jboss.org/jira/browse/JBSEAM-4053?page=com.atlassian.jira.pl...
]
Hiroyuki Wada commented on JBSEAM-4053:
---------------------------------------
I tried using trunk (revision is @10292) seam but I got same exception...
Could you check your web.xml in test app whether 'STATE_SAVING_METHOD' is
'client' ?
-- web.xml
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>client</param-value>
</context-param>
--
Because this problem occur when JSF view-state is serialized/deserialized.
(my attached zip file contains this configured web.xml.)
Can't resolve EL Function which serialized to ViewState
-------------------------------------------------------
Key: JBSEAM-4053
URL:
https://jira.jboss.org/jira/browse/JBSEAM-4053
Project: Seam
Issue Type: Bug
Components: EL
Affects Versions: 2.0.2.SP1, 2.1.1.GA
Reporter: Hiroyuki Wada
Assignee: Norman Richards
Fix For: 2.1.2.CR1
Attachments: FunctionMapperImpl.java.patch, myproject.zip
It seems that EL Function which serialized to ViewState can't be resolved when the
object is deserialize. Because the jboss-el directly use
"Class#forName(String)". The code is as follows,
{code:title=org.jboss.el.lang.FunctionMapperImpl.java|borderStyle=solid}
public Method getMethod() {
if (this.m == null) {
try {
Class t = Class.forName(this.owner);
Class[] p = ReflectionUtil.toTypeArray(this.types);
this.m = t.getMethod(this.name, p);
} catch (Exception e) {
{code}
I think the above code cause ClassLoader Scope Problem.
"Thread.currentThread().getContextClassLoader()" should be used.
I found the jboss-el already had utility method for "Class.forName". It's
"ReflectionUtil#forName(String)" method. Please use this method.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira