[JBoss JIRA] (AS7-3831) EL problem javax.faces.el.MethodNotFoundException in Seam 3 Booking example
by Tomas Remes (JIRA)
Tomas Remes created AS7-3831:
--------------------------------
Summary: EL problem javax.faces.el.MethodNotFoundException in Seam 3 Booking example
Key: AS7-3831
URL: https://issues.jboss.org/browse/AS7-3831
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.0.Final, 7.1.0.CR1
Reporter: Tomas Remes
If you try to build WAR from https://github.com/seam/examples/tree/master/booking deploy it and run steps to reproduce, you will get following exception:
javax.faces.el.MethodNotFoundException: javax.el.MethodNotFoundException: /hotel.xhtml @14,75 action="#{bookingAgent.selectHotel(_hotelId)}": Method not found: Proxy for view class: org.jboss.seam.examples.booking.booking.BookingAgent of EJB: BookingAgent.selectHotel(java.lang.String)
at org.jboss.seam.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:65)
at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
at org.jboss.seam.faces.component.UIViewAction.broadcast(UIViewAction.java:381)
at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794)
at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259)
at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
at com.ocpsoft.pretty.PrettyFilter.doFilter(PrettyFilter.java:115)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:734)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:541)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:479)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:407)
at com.ocpsoft.pretty.PrettyFilter.doFilter(PrettyFilter.java:107)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50)
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
at java.lang.Thread.run(Thread.java:662)
Caused by: javax.el.MethodNotFoundException: /hotel.xhtml @14,75 action="#{bookingAgent.selectHotel(_hotelId)}": Method not found: Proxy for view class: org.jboss.seam.examples.booking.booking.BookingAgent of EJB: BookingAgent.selectHotel(java.lang.String)
at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:109)
at org.jboss.seam.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:63)
... 32 more
On AS7.1.0.CR1b displays following message immediately after deployment and typing localhost:8080/seam-booking to your browser:
The identifier [transient] is not a valid Java identifier as required by section 1.19 of the EL specification (Identifier ::= Java language identifier). This check can be disabled by setting the system property org.apache.el.parser.SKIP_IDENTIFIER_CHECK to true.
When I set that property to false, then the above exception is thrown. This functionality was ok on 7.1.0.Beta1b
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] (AS7-3835) Allowed index attribute on caches need to be all caps
by Stan Silvert (JIRA)
Stan Silvert created AS7-3835:
---------------------------------
Summary: Allowed index attribute on caches need to be all caps
Key: AS7-3835
URL: https://issues.jboss.org/browse/AS7-3835
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.0.Final
Reporter: Stan Silvert
Assignee: Richard Achmatowicz
Allowed attributes are usually all caps. I think this is probably causing a problem in console where I present a dropdown with all-caps values for selection.
/profile=default/subsystem=infinispan/cache-container=aaaa/local-cache=*/:read-resource-description(operations=false,inherited=false,recursive=false,proxies=false)
{noformat}
"indexing" => {
"type" => STRING,
"description" => "If enabled, entries will be indexed when they are added to the cache. Indexes will be updated as entries change or are removed.",
"expressions-allowed" => false,
"nillable" => true,
"default" => "NONE",
"allowed" => [
"none",
"local",
"all"
],
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "all-services"
},
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months