Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8257107
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 8, 20262026-06-08T02:05:19+00:00 2026-06-08T02:05:19+00:00

After upgrading to JSF2 (probably) one special accessor in an .xhtml file generates IllegalArgumentExceptions

  • 0

After upgrading to JSF2 (probably) one special accessor in an .xhtml file generates IllegalArgumentExceptions but I can’t really find out why. Running the app on my local JBoss (4.2.2) does not generate this exception but this can be related to a difference between debug and live data.

Following stack trace is generated that I could extract from the production server log:

Caused by: javax.el.ELException: /xy/xy-subtemplate1.xhtml @131,45 value="#{someClass.someProperty}": java.lang.IllegalArgumentException
    at com.sun.facelets.el.TagValueExpression.setValue(TagValueExpression.java:101)
    at javax.faces.component.UIInput.updateModel(UIInput.java:818)
    ... 36 more
Caused by: java.lang.IllegalArgumentException
    at sun.reflect.GeneratedMethodAccessor1134.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at javax.el.BeanELResolver.setValue(BeanELResolver.java:108)
    at com.sun.faces.el.DemuxCompositeELResolver._setValue(DemuxCompositeELResolver.java:255)
    at com.sun.faces.el.DemuxCompositeELResolver.setValue(DemuxCompositeELResolver.java:281)
    at org.apache.el.parser.AstValue.setValue(AstValue.java:114)
    at org.apache.el.ValueExpressionImpl.setValue(ValueExpressionImpl.java:249)
    at com.sun.facelets.el.TagValueExpression.setValue(TagValueExpression.java:93)
    ... 37 more

someClass is being iterated over in a list and has the following methods to access someProperty:

public int getSomeProperty() {
    return this.getSomeRelatedEnum().ordinal();
}

public void setSomeProperty( final int index) {
    this.setSomeRelatedEnum( SomeRelatedEnum.fromOrdinal( index) );
}

How can this lead to the IllegalArgumentException mentioned above?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-08T02:05:20+00:00Added an answer on June 8, 2026 at 2:05 am

    That can happen when the setter method after all expects a different argument type than the one which is provided from EL on.

    I guess that it’s related to the fact that hardcoded/unconverted numbers in EL are by default treated as long and not as int. Try either changing the int to be long, or providing an explicit integer converter on the input component like so <h:someInput converter="javax.faces.Integer">.

    By the way, why don’t you just get/set the enum itself directly? Getting/setting the enum by its ordinal is whacky.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

After upgrading to Lion, and installing XCode 4.3 I can't get Hello, World to
After upgrading to Lion I can still start MySQL via System Preferences -> MySQL
Until now deploying my Application with macdeployqt worked fine, but after upgrading to Qt
After upgrading Magento to 1.5.1 when a customer orders their screen refreshed, but it
After upgrading to Lion, and upgrading Xcode, make can't seem to locate headers and
After upgrading to xcode 4.2.1 on lion, I tried to do NSLog(@testing...); but it's
After upgrading to Rails 2.3.11, I can no longer use SlickGrid to create what
This might sound silly, but my umbraco 5.1 application (after upgrading from 5.0) simply
After upgrading to a newer hibernate version (guess it came with the switch from
After upgrading node to v0.8.1, bundled Meteor apps now throw an error: node: symbol

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.