Re: [Trinidad] Skinning: Change only one occurence of a component
It is possible, here is an example for when you would want to customize a specific instance of the : In your page you could specify a custom CSS class selector: ** *.* ** * * *Then, in your CSS file applied to your app you use the new "custom_accordion" class selector to identify only that panelAccordion and further customize it:* * .custom_accordion af|panelAccordion::content { // apply custom customization to this panel accordion's content } regards, Catalin * On Mon, Mar 29, 2010 at 7:33 PM, schneidc wrote: > > Hi, > > I want to change the width of a , so it isn't so narrow > when empty. doesn't do the > trick as the actual menu is embedded in a table and the style get's applied > on the table and not the menu itself. > > So I figured out that I should change "af|selectOneChoice::content". But > this would alter all the selectOneChoices and I only want to adjust the > width of one. I read the skinning guide but didn't find anything useful. Is > it even possible? > > Cheers > Simon > -- > View this message in context: > http://old.nabble.com/-Trinidad--Skinning%3A-Change-only-one-occurence-of-a-component-tp28071783p28071783.html > Sent from the MyFaces - Users mailing list archive at Nabble.com. > > -- Codebeat www.codebeat.ro
Re: [Trinidad] Skinning: Change only one occurence of a component
You can use to change the menu size. Glauco P. Gomes schneidc escreveu: Hi, I want to change the width of a , so it isn't so narrow when empty. doesn't do the trick as the actual menu is embedded in a table and the style get's applied on the table and not the menu itself. So I figured out that I should change "af|selectOneChoice::content". But this would alter all the selectOneChoices and I only want to adjust the width of one. I read the skinning guide but didn't find anything useful. Is it even possible? Cheers Simon
Re: [Trinidad] Skinning: Change only one occurence of a component
you have to use it like af|selectOneChoice.MyStyle af|selectOneChoice::content { // style properties } and use the MyStyle in the styleClass of the specific selectonechoice that you are using.. On Tue, Mar 30, 2010 at 4:14 PM, Glauco P. Gomes wrote: > You can use to change > the menu size. > > Glauco P. Gomes > > schneidc escreveu: > >> Hi, >> >> I want to change the width of a , so it isn't so >> narrow >> when empty. doesn't do the >> trick as the actual menu is embedded in a table and the style get's >> applied >> on the table and not the menu itself. >> >> So I figured out that I should change "af|selectOneChoice::content". But >> this would alter all the selectOneChoices and I only want to adjust the >> width of one. I read the skinning guide but didn't find anything useful. >> Is >> it even possible? >> >> Cheers >> Simon >> >> > > >
Re: [Trinidad] Skinning: Change only one occurence of a component
Thanks both of you. This expression was what I had in mind .custom_accordion af|panelAccordion::content { // apply custom customization to this panel accordion's content } but this special case also did the trick. -- View this message in context: http://old.nabble.com/-Trinidad--Skinning%3A-Change-only-one-occurence-of-a-component-tp28071783p28082446.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
Facing error after Tomahawk upgrade.
All, I'm getting the following exception when I try to access my application. I have recently updated the following components in my application weblogic8.1 to weblogic 10.3 myfaces 1.1.5 to 1.2.8 richfaces 3.0.1 to 3.3.3 tomahawk 1.1.5 to 12_1.1.10 Struts tiles to tiles 2.0.7 I have also tried with tomahawk 1.1.9 , but I have faced exception in stating "there is no such method error with the method argument expecting 'Valueexpression' instead of String ." Mar 30, 2010 6:39:45 PM org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl buildTilesViewLikeContain er SEVERE: Error rendering tile org.apache.tiles.util.TilesIOException: ServletException including path '/webContent/jsp/searchManager/layout/searchMana gerLayout.jsp'. at org.apache.tiles.servlet.context.ServletTilesRequestContext.wrapServletE xception(ServletTilesRequestContext.j ava:298) at org.apache.tiles.servlet.context.ServletTilesRequestContext.forward(Serv letTilesRequestContext.java:200) at org.apache.tiles.servlet.context.ServletTilesRequestContext.dispatch(Ser vletTilesRequestContext.java:179) at org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.b uildView(JspTilesTwoViewHandlerImpl.j ava:450) at org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.b uildTilesViewLikeContainer(JspTilesTw oViewHandlerImpl.java:354) at org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.r enderTilesView(JspTilesTwoViewHandler Impl.java:154) at org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.r enderView(JspTilesTwoViewHandlerImpl. java:135) at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrappe r.java:100) at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java :176) at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderRespon seExecutor.java:41) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:140 ) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:182) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(St ubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityH elper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:2 92) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java: 42) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:206) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter .java:388) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java: 42) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java: 42) at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFil ter.java:384) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java: 42) at com.pfizer.pgrd.ui.utils.SecurityFilter.doFilter(SecurityFilter.java:92) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java: 42) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.r un(WebAppServletContext.java:3496) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu bject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ letContext.java:2180) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont ext.java:2086) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java :1406) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) Caused by: java.lang.NoSuchMethodError: org.apache.myfaces.custom.document.DocumentBodyTag.setOnload(Ljava/lang/ String;) V at jsp_servlet._webcontent._jsp._searchmanager._layout.__searchmanagerlayou t._jsp__tag4(__searchmanagerlayout.ja va:305) at jsp_servlet._webcontent._jsp._searchmanager._layout.__searchmanagerlayou t._jspService(__searchmanagerlayout.j ava:210) at weblogic.servlet.jsp.JspBase.service(JspBase.java:34) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(St ubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityH elper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl
RE: Facing error after Tomahawk upgrade.
Use component libraries which are compliant with the 1.2 JSF standard and not the 1.1 standard. There is a difference in binding component attributes in JSF 1.2 and 1.1, for example, 1.1 public void set_binding(String _binding) { this.binding = _binding; } public String getBinding() { return binding; } if (getBinding() != null) { if (isValueReference(getBinding())) { inputText.setValueBinding("binding", getValueBinding(getBinding())); } else { inputText.getAttributes().put("binding", getBinding()); } } 1.2 public ValueExpression getBinding() { return binding; } public void setBinding(ValueExpression binding) { this.binding = binding; } if (getBinding() != null) { if (!getBinding().isLiteralText()) { inputText.setValueExpression("binding", getBinding()); } else { inputText.getAttributes().put("binding", getBinding().getExpressionString()); } } This also clearifies the exception you get expected ValueExpression got String. -Original message- From: nilakandan.v...@cognizant.com Sent: Tue 30-03-2010 15:34 To: users@myfaces.apache.org; Subject: Facing error after Tomahawk upgrade. All, I'm getting the following exception when I try to access my application. I have recently updated the following components in my application weblogic8.1 to weblogic 10.3 myfaces 1.1.5 to 1.2.8 richfaces 3.0.1 to 3.3.3 tomahawk 1.1.5 to 12_1.1.10 Struts tiles to tiles 2.0.7 I have also tried with tomahawk 1.1.9 , but I have faced exception in stating "there is no such method error with the method argument expecting 'Valueexpression' instead of String ." Mar 30, 2010 6:39:45 PM org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl buildTilesViewLikeContain er SEVERE: Error rendering tile org.apache.tiles.util.TilesIOException: ServletException including path '/webContent/jsp/searchManager/layout/searchMana gerLayout.jsp'. at org.apache.tiles.servlet.context.ServletTilesRequestContext.wrapServletE xception(ServletTilesRequestContext.j ava:298) at org.apache.tiles.servlet.context.ServletTilesRequestContext.forward(Serv letTilesRequestContext.java:200) at org.apache.tiles.servlet.context.ServletTilesRequestContext.dispatch(Ser vletTilesRequestContext.java:179) at org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.b uildView(JspTilesTwoViewHandlerImpl.j ava:450) at org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.b uildTilesViewLikeContainer(JspTilesTw oViewHandlerImpl.java:354) at org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.r enderTilesView(JspTilesTwoViewHandler Impl.java:154) at org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.r enderView(JspTilesTwoViewHandlerImpl. java:135) at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrappe r.java:100) at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java :176) at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderRespon seExecutor.java:41) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:140 ) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:182) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(St ubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityH elper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:2 92) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java: 42) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:206) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter .java:388) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java: 42) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java: 42) at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFil ter.java:384) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java: 42) at com.pfizer.pgrd.ui.utils.SecurityFilter.doFilter(SecurityFilter.java:92) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java: 42) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.r un(WebAppServletContext.java:3496) at weblogic.security.acl.internal.AuthenticatedSu
Re: Facing error after Tomahawk upgrade.
So do you mean to say tomahawk 1.1.9 along with JSF. 1.2 will do the trick? On Tue, Mar 30, 2010 at 7:20 PM, Rene van Wijk wrote: > > Use component libraries which are compliant with the 1.2 JSF standard and > not the 1.1 standard. > > > > There is a difference in binding component attributes in JSF 1.2 and 1.1, > for example, > > > > 1.1 > > public void set_binding(String _binding) { > this.binding = _binding; > } > > public String getBinding() { > return binding; > } > > > > if (getBinding() != null) { > if (isValueReference(getBinding())) { > inputText.setValueBinding("binding", > getValueBinding(getBinding())); > } else { > inputText.getAttributes().put("binding", getBinding()); > } > } > > > > 1.2 > > public ValueExpression getBinding() { > return binding; > } > > public void setBinding(ValueExpression binding) { > this.binding = binding; > } > > > > if (getBinding() != null) { > if (!getBinding().isLiteralText()) { > inputText.setValueExpression("binding", getBinding()); > } else { > inputText.getAttributes().put("binding", > getBinding().getExpressionString()); > } > } > > > > This also clearifies the exception you get expected ValueExpression got > String. > > -Original message- > From: nilakandan.v...@cognizant.com > Sent: Tue 30-03-2010 15:34 > To: users@myfaces.apache.org; > Subject: Facing error after Tomahawk upgrade. > > All, > > I'm getting the following exception when I try to access my > application. > > > > I have recently updated the following components in my application > > > > weblogic8.1 to weblogic 10.3 > > myfaces 1.1.5 to 1.2.8 > > richfaces 3.0.1 to 3.3.3 > > tomahawk 1.1.5 to 12_1.1.10 > > Struts tiles to tiles 2.0.7 > > > > > > I have also tried with tomahawk 1.1.9 , but I have faced exception in > stating "there is no such method error with the method > argument expecting 'Valueexpression' instead of String ." > > > > > > Mar 30, 2010 6:39:45 PM > org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl > buildTilesViewLikeContain er > > SEVERE: Error rendering tile > > org.apache.tiles.util.TilesIOException: ServletException including path > '/webContent/jsp/searchManager/layout/searchMana > > gerLayout.jsp'. > >at > org.apache.tiles.servlet.context.ServletTilesRequestContext.wrapServletE > xception(ServletTilesRequestContext.j > > ava:298) > >at > org.apache.tiles.servlet.context.ServletTilesRequestContext.forward(Serv > letTilesRequestContext.java:200) > >at > org.apache.tiles.servlet.context.ServletTilesRequestContext.dispatch(Ser > vletTilesRequestContext.java:179) > >at > org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.b > uildView(JspTilesTwoViewHandlerImpl.j > > ava:450) > >at > org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.b > uildTilesViewLikeContainer(JspTilesTw > > oViewHandlerImpl.java:354) > >at > org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.r > enderTilesView(JspTilesTwoViewHandler > > Impl.java:154) > >at > org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.r > enderView(JspTilesTwoViewHandlerImpl. > > java:135) > >at > org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrappe > r.java:100) > >at > org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java > :176) > >at > org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderRespon > seExecutor.java:41) > >at > org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:140 > ) > >at > javax.faces.webapp.FacesServlet.service(FacesServlet.java:182) > >at > weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(St > ubSecurityHelper.java:227) > >at > weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityH > elper.java:125) > >at > weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:2 > 92) > >at > weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) > >at > weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java: > 42) > >at > org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:206) > >at > org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) > >at > org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter > .java:388) > >at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515) > >at > weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java: > 42) > >at > weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java: > 42) > >at > org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(Exten
[Tobago] Using validator in custom tag
Hi all, I try to use a validator dependent on a property within a custom tag class. My class extends TagSupport and overwrites the doStartTag() method. In this method I add a validator depending on a property (see below). First the property is "false" and no validator will be added to the inExtensionTag. Now (next access to the page) the property will change to "true" and the output "Setting validator!" shows me, that the validator has been set. But the validator will never be called! If I always add the validator (not depending on the property), everything works fine. The validator will be called on submit. What is wrong with my approach? Is there another possibility to do what I want? Example: @Override public int doStartTag() throws JspException { InExtensionTag inExtensionTag = new InExtensionTag(); inExtensionTag.setPageContext(pageContext); inExtensionTag.setParent(getParent()); inExtensionTag.setId(id); inExtensionTag.setLabel(label); inExtensionTag.setValue(value); if (isValidationEnabled()) { System.out.println("Setting validator!"); inExtensionTag.setValidator("#validator.validate}"); } inExtensionTag.doStartTag(); inExtensionTag.doEndTag(); return super.doStartTag(); } Best regards, Alf -- GMX DSL: Internet, Telefon und Entertainment für nur 19,99 EUR/mtl.! http://portal.gmx.net/de/go/dsl02
Re: Facing error after Tomahawk upgrade.
Hi Try tomahawk12-1.1.9 jar file. It is known tomahawk for jsf 1.1 + tiles + jsf 1.2 does not work because the ViewHandler spec changes on jsf 1.2. The corrected version is on that jar. regards, Leonardo Uribe 2010/3/30 Now I find myself in question > So do you mean to say tomahawk 1.1.9 along with JSF. 1.2 will do the trick? > > On Tue, Mar 30, 2010 at 7:20 PM, Rene van Wijk < > rw...@transfer-solutions.com > > wrote: > > > > > Use component libraries which are compliant with the 1.2 JSF standard and > > not the 1.1 standard. > > > > > > > > There is a difference in binding component attributes in JSF 1.2 and 1.1, > > for example, > > > > > > > > 1.1 > > > > public void set_binding(String _binding) { > > this.binding = _binding; > > } > > > > public String getBinding() { > > return binding; > > } > > > > > > > > if (getBinding() != null) { > > if (isValueReference(getBinding())) { > > inputText.setValueBinding("binding", > > getValueBinding(getBinding())); > > } else { > > inputText.getAttributes().put("binding", getBinding()); > > } > > } > > > > > > > > 1.2 > > > > public ValueExpression getBinding() { > > return binding; > > } > > > > public void setBinding(ValueExpression binding) { > > this.binding = binding; > > } > > > > > > > > if (getBinding() != null) { > > if (!getBinding().isLiteralText()) { > > inputText.setValueExpression("binding", getBinding()); > > } else { > > inputText.getAttributes().put("binding", > > getBinding().getExpressionString()); > > } > > } > > > > > > > > This also clearifies the exception you get expected ValueExpression got > > String. > > > > -Original message- > > From: nilakandan.v...@cognizant.com > > Sent: Tue 30-03-2010 15:34 > > To: users@myfaces.apache.org; > > Subject: Facing error after Tomahawk upgrade. > > > > All, > > > > I'm getting the following exception when I try to access my > > application. > > > > > > > > I have recently updated the following components in my application > > > > > > > > weblogic8.1 to weblogic 10.3 > > > > myfaces 1.1.5 to 1.2.8 > > > > richfaces 3.0.1 to 3.3.3 > > > > tomahawk 1.1.5 to 12_1.1.10 > > > > Struts tiles to tiles 2.0.7 > > > > > > > > > > > > I have also tried with tomahawk 1.1.9 , but I have faced exception in > > stating "there is no such method error with the method > > argument expecting 'Valueexpression' instead of String ." > > > > > > > > > > > > Mar 30, 2010 6:39:45 PM > > org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl > > buildTilesViewLikeContain er > > > > SEVERE: Error rendering tile > > > > org.apache.tiles.util.TilesIOException: ServletException including path > > '/webContent/jsp/searchManager/layout/searchMana > > > > gerLayout.jsp'. > > > >at > > org.apache.tiles.servlet.context.ServletTilesRequestContext.wrapServletE > > xception(ServletTilesRequestContext.j > > > > ava:298) > > > >at > > org.apache.tiles.servlet.context.ServletTilesRequestContext.forward(Serv > > letTilesRequestContext.java:200) > > > >at > > org.apache.tiles.servlet.context.ServletTilesRequestContext.dispatch(Ser > > vletTilesRequestContext.java:179) > > > >at > > org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.b > > uildView(JspTilesTwoViewHandlerImpl.j > > > > ava:450) > > > >at > > org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.b > > uildTilesViewLikeContainer(JspTilesTw > > > > oViewHandlerImpl.java:354) > > > >at > > org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.r > > enderTilesView(JspTilesTwoViewHandler > > > > Impl.java:154) > > > >at > > org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl.r > > enderView(JspTilesTwoViewHandlerImpl. > > > > java:135) > > > >at > > org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrappe > > r.java:100) > > > >at > > org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java > > :176) > > > >at > > org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderRespon > > seExecutor.java:41) > > > >at > > org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:140 > > ) > > > >at > > javax.faces.webapp.FacesServlet.service(FacesServlet.java:182) > > > >at > > weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(St > > ubSecurityHelper.java:227) > > > >at > > weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityH > > elper.java:125) > > > >at > > weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:2 > > 92) > > > >at > > weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) > > > >at > > weblogic.servlet.internal.Fi
ANNOUNCE: Trinidad in Action Part 2
Hello, In the second installment of the Trinidad series, Matthias Wessendorf shows how Ajax is built into all the Trinidad components. You will also learn how easy it is to use the client- and server-side Ajax API, which gives you a straightforward way to add application-specific Ajax support. Read the full article here: http://www.jsfcentral.com/articles/trinidad_2.html --- Kito D. Mann | twitter: kito99 | Author, JSF in Action Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info | twitter: jsfcentral +1 203-404-4848 x3 Sign up for the JSFCentral newsletter: http://oi.vresp.com/?fid=ac048d0e17
ANNOUNCE: Martin Marinschek on MyFaces 2.0, IRIAN, and Related Topics
Hello, In this podcast, JSFCentral editor-in-chief Kito D. Mann talks with Martin Marinschek about MyFaces, IRIAN, and related topics. This interview was recorded in December of 2009 at the JSF Summit conference in Orlando, Florida. Here is an excerpt: Kito: Let’s talk a little bit about the project. MyFaces was originally just an implementation but now it has grown into a very large set of projects. Tell us a bit about some of the different projects that are part of the MyFaces umbrella. Martin: I hope I don’t miss anything. Of course there is the core MyFaces implementation and API. For the JSF implementation you have to do the API and the Impl, so it is actually two jars which are developed in the core section. Then there are the three component libraries: Trinidad, Tomahawk, and Tobago. Then there is Orchestra, which is a conversation scope implementation for long running conversations with integration to JPA as well. Then there is the JSF Portlet Bridge, and there is ExtVal validation integration for JSF, where you can put annotations on your managed beans and domain objects. It will directly be converted into JSF converters and validators, pretty nicely done. Now that bean validation has been standardized, it is also an implementation of bean validation, so you can use the bean validation annotations together with ExtVal. Read the full article here: http://www.jsfcentral.com/articles/marinschek-03-10.html --- Kito D. Mann | twitter: kito99 | Author, JSF in Action Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info | twitter: jsfcentral +1 203-404-4848 x3 Sign up for the JSFCentral newsletter: http://oi.vresp.com/?fid=ac048d0e17