[JBoss Seam] - Problems with el
by m.schuetz
The following code doesn't work:
<h:outputText rendered="#{trialManager.elTest(elHelper.manager)}">GESCHAFFT..</h:outputText>
| 16:45:13,131 ERROR [STDERR] Feb 2, 2007 4:45:13 PM com.sun.facelets.FaceletViewHandler handleRenderException
| SEVERE: Error Rendering View[/user/trial/trialHome.xhtml]
| com.sun.facelets.tag.TagAttributeException: /user/trial/trialHome.xhtml @29,69 rendered="#{trialManager.elTest(elHelper.manager)}" Error Parsing: #{trialManager.elTest(elHelper.manager)}
| at com.sun.facelets.tag.TagAttribute.getValueExpression(TagAttribute.java:259)
| at com.sun.facelets.tag.jsf.ComponentRule$ValueBindingMetadata.applyMetadata(ComponentRule.java:90)
| at com.sun.facelets.tag.MetadataImpl.applyMetadata(MetadataImpl.java:36)
| at com.sun.facelets.tag.MetaTagHandler.setAttributes(MetaTagHandler.java:62)
| at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:140)
| at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
| at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:295)
| at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:165)
| at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
| at com.sun.facelets.tag.ui.DefineHandler.apply(DefineHandler.java:58)
| at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:128)
| at com.sun.facelets.impl.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:306)
| at com.sun.facelets.impl.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:279)
| at com.sun.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:68)
| at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
| at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
| at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
| at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
| at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:248)
| at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:294)
| at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:273)
| at com.sun.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:143)
| at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:113)
| at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
| at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
| at com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95)
| at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:510)
| at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:553)
| at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:46)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:32)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: javax.el.ELException: Error Parsing: #{trialManager.elTest(elHelper.manager)}
| at com.sun.el.lang.ExpressionBuilder.createNodeInternal(ExpressionBuilder.java:140)
| at com.sun.el.lang.ExpressionBuilder.build(ExpressionBuilder.java:157)
| at com.sun.el.lang.ExpressionBuilder.createValueExpression(ExpressionBuilder.java:201)
| at com.sun.el.ExpressionFactoryImpl.createValueExpression(ExpressionFactoryImpl.java:74)
| at org.jboss.seam.ui.facelet.SeamExpressionFactory.createValueExpression(SeamExpressionFactory.java:105)
| at com.sun.facelets.tag.TagAttribute.getValueExpression(TagAttribute.java:256)
| ... 54 more
| Caused by: com.sun.el.parser.ParseException: Encountered "(" at line 1, column 22.
| Was expecting one of:
| "}" ...
| "." ...
| "[" ...
| ">" ...
| "gt" ...
| "<" ...
| "lt" ...
| ">=" ...
| "ge" ...
| "<=" ...
| "le" ...
| "==" ...
| "eq" ...
| "!=" ...
| "ne" ...
| "&&" ...
| "and" ...
| "||" ...
| "or" ...
| "*" ...
| "+" ...
| "-" ...
| "?" ...
| "/" ...
| "div" ...
| "%" ...
| "mod" ...
|
| at com.sun.el.parser.ELParser.generateParseException(ELParser.java:1651)
| at com.sun.el.parser.ELParser.jj_consume_token(ELParser.java:1531)
| at com.sun.el.parser.ELParser.DeferredExpression(ELParser.java:134)
| at com.sun.el.parser.ELParser.CompositeExpression(ELParser.java:61)
| at com.sun.el.lang.ExpressionBuilder.createNodeInternal(ExpressionBuilder.java:103)
| ... 59 more
By the way: following code DOES work:
| <h:form id="elManager">
| <h:commandButton action="#{trialManager.elTest(elHelper.manager)}"
| value="Los" /></h:form>
I absolutely do not understand. Thank you for helping.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010089#4010089
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010089
19Â years, 2Â months
[JBoss Portal] - Re: HTTP Status 401 Error on Admin Page (can't access page a
by mwolfson
(Bad HTML Formatting in previous message, this one is better...)
Thanks for the great idea. I tried that, and it definately worked.
Unfortunately, I over achieved, and I basically overwrote everything I did previously (the first time I brought up the Portal, I got all the default pages - with my new "NewAdmin" page of course). I changed the tag to overwrite for the entire portal (probably should have just done it for the specific I was working on).
I guess this is a learning experience, and it won't take me nearly as long to redo everything as it did to create it in the first place.
----------------
Update...
Fortunately, I saved a copy of my old Portal before I started messing around (save early, save often!), so I was able to recover easily.
So, I tried again. I copied everything, between the "page" and "/page" tags related to Admin, and renamed the page NewAdmin. The NewAdmin page tags are within the same "deployment" tags as Admin. I also changed the "if-exists" tag to overwrite (it was - keep).
The NewAdmin page doesn't show up. I guess I could create a new deployment "defaultNew" and try that, but I am not sure if I would be able to change the attributes on the old deployment (the original Admin page, which is the original goal).
So, I guess I am still not 100% there. This is frustrating, the Admin page should be external to the actual Portal (enhancement request - maybe I will see about working on that myself when I get past my current deadline, and get some free time).
BTW, I am using 2.4 on Ubuntu Linux.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010084#4010084
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010084
19Â years, 2Â months
[JBoss Portal] - Re: HTTP Status 401 Error on Admin Page (can't access page a
by mwolfson
Thanks for the great idea. I tried that, and it definately worked.
Unfortunately, I over achieved, and I basically overwrote everything I did previously (the first time I brought up the Portal, I got all the default pages - with my new "NewAdmin" page of course). I changed the tag to overwrite for the entire portal (probably should have just done it for the specific I was working on).
I guess this is a learning experience, and it won't take me nearly as long to redo everything as it did to create it in the first place.
----------------
Update...
Fortunately, I saved a copy of my old Portal before I started messing around (save early, save often!), so I was able to recover easily.
So, I tried again. I copied everything, between the and tags related to Admin, and renamed the page NewAdmin. The NewAdmin page tags are within the same tags as Admin. I also changed the <if-exists> tag to overwrite (it was - keep).
The NewAdmin page doesn't show up. I guess I could create a new deployment "defaultNew" and try that, but I am not sure if I would be able to change the attributes on the old deployment (the original Admin page, which is the original goal).
So, I guess I am still not 100% there. This is frustrating, the Admin page should be external to the actual Portal (enhancement request - maybe I will see about working on that myself when I get past my current deadline, and get some free time).
BTW, I am using 2.4 on Ubuntu Linux.
At any rate, thanks for the idea. It totally fixed my problem.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010082#4010082
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010082
19Â years, 2Â months
[JBoss Portal] - Re: HTTP Status 401 Error on Admin Page (can't access page a
by mwolfson
Thanks for the great idea. I tried that, and it definately worked.
Unfortunately, I over achieved, and I basically overwrote everything I did previously (the first time I brought up the Portal, I got all the default pages - with my new "NewAdmin" page of course). I changed the tag to overwrite for the entire portal (probably should have just done it for the specific I was working on).
I guess this is a learning experience, and it won't take me nearly as long to redo everything as it did to create it in the first place.
----------------
Update...
Fortunately, I saved a copy of my old Portal before I started messing around (save early, save often!), so I was able to recover easily.
So, I tried again. I copied everything, between the and tags related to Admin, and renamed the page NewAdmin. The NewAdmin page tags are within the same tags as Admin. I also changed the <if-exists> tag to overwrite (it was - keep).
The NewAdmin page doesn't show up. I guess I could create a new deployment "defaultNew" and try that, but I am not sure if I would be able to change the attributes on the old deployment (the original Admin page, which is the original goal).
So, I guess I am still not 100% there. This is frustrating, the Admin page should be external to the actual Portal (enhancement request - maybe I will see about working on that myself when I get past my current deadline, and get some free time).
BTW, I am using 2.4 on Ubuntu Linux.
At any rate, thanks for the idea. It totally fixed my problem.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010080#4010080
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010080
19Â years, 2Â months