Automatic amendment of jsf when backing beans refactored: tool support ?

Hi there,
Whenever I refactor backing beans I have to adjust EL expressions in all my jsf files manually.
That is annoying, time-consuming and finally prevents me from refactoring regularly.
Does anybody know an IDE or tool that supports refactoring of backing beans ?
Many thanks in advance
Ott

Similar Messages

JSF Page -- Backing Bean -- Non-JSF Page ...

Hi
I have a JSF page where the user enters data and submits by clicking on the Submit button. My backing bean then takes the data and processes it. After successful processing, I want to direct the user to a non-JSF page.
What is the best way of achieving this?
Thanks

I am doing the following to get the desired effect now:
FacesContext ctx = FacesContext.getCurrentInstance();
ExternalContext ectx = ctx.getExternalContext();
HttpServletResponse response = (HttpServletResponse)ectx.getResponse();
String nextUrl = "....";
response.sendRedirect(nextUrl);
Is there a better way?

Problem with Commit button When Backing bean is in Request Scope...

HI Everybody,
I have a Backing Bean in request scope having over 1000 lines of code, And in my JSPX page I have a table binding with a view object and At run time when user select the row in table and click the edit button so user will be able to edit that selected row in the same table at run time.. but the problem is : when the user enters some data in the Editable inputTexts and then clicks save(Commit), then the save button doesn't work..but when i delete any selected row and then press save then it is working fine..
And to test it in Session scope i made another sample page where every thing is working very fine..
Now i want to know What is the difference between Session scope and request scope bean...
And is there any solution to Save editable input text in Request scope?.
Also want to know that is it safe to set the scope of my main bean class to session scope without effecting the current running functionality? which is having over 1000 lines of code and lot of component has been placed...
Please help me to resolve this problem...
Thanks in Advance to all of you
Fizzz..

Hi Frank...
In my code i used almost same logic as Andrejus Baranovskis has explained in his Editable Table example...
You can refer that example to see what problem I'm facing...
http://andrejusb.blogspot.com/2007/04/create-edit-and-delete-operations-in.html
The Bean Scope in this Example is Session scope...Save button is working fine...
But as i Change the bean scope to Request scope then Save button is not working for Edit but it is working for Delete Action very well..
I want that save button should work also for Edit action in Request Scope..
Please Make me understand that why it is happened like that..
and help me to find the solution..
and Also if you have a better document to Explain the life cycle of Application in Different Bean Scope...So please provide me that Doc to me...
It would be a great help for me to understand the concept of session...
Thanks Frank
Fizzz...

How to pass object from JSF to backing bean

Hi,
I have a JSF page using repeater and RichFace Toolbar:
 <h:form id="professional-profile">
 <a4j:repeat value="#{profilesBean.profiles}" var="lang" binding="#{profilesRepeaterBean.repeater}">
 <rich:togglePanel styleClass="data-input-panel" switchType="client" stateOrder="closed, opened">
 <f:facet name="closed">
 <rich:toolBar>
 <rich:toggleControl switchToState="opened">
 <h:graphicImage style="border-width:0" value="../Images/open_btn.gif" />
 <rich:toolTip value="#{pp_msg.tooltipOpensPanel}" direction="top-right" showDelay="${config.toolTipDelay}" styleClass="tool-tip"/>
 </rich:toggleControl>
 <h:outputText value="#{lang.language}"/>
 </rich:toolBar>
 </f:facet>
 <f:facet name="opened">
 <h:panelGrid style="width: 100%" columns="1">
 <rich:toolBar>
 <rich:toolBarGroup location="left">
 <rich:toggleControl switchToState="closed"
 onclick="if(!ConfirmUnsavedForAction('#{common_msg.unsavedDataWarning}')){return false;}">
 <h:graphicImage style="border-width:0" value="../Images/close_btn.gif" />
 <rich:toolTip value="#{pp_msg.tooltipClosesPanel}" direction="top-right" showDelay="${config.toolTipDelay}" styleClass="tool-tip"/>
 </rich:toggleControl>
 <h:outputText value="#{lang.language}"/>
 
 (#{pp_msg.remainingChars}:<h:outputText class="counterColor" id="charsCounter" value="${config.profestionalProfileMaxLength-fn:length(lang.profile)}"/>
 )
 </rich:toolBarGroup>
 <rich:toolBarGroup location="right">
 <a4j:commandLink id="submit"
 action="#{cvData.editUsr}" <<<<<<<<<<<<<<<<<< THIS LINE
 value="#{common_msg.buttonSave}"
 messagePlace="textarea"
 onclick="CommandOnClick(#{rich:element('textarea')},'#{common_msg.dataSaving}','#{common_msg.dataSaved}');"
 data="#{facesContext.maximumSeverity.ordinal ge 2}"
 oncomplete="CommandOnComplete(#{rich:element('textarea')},data,1500); DataSaved();">
 </a4j:commandLink>
 </rich:toolBarGroup>
 </rich:toolBar>
 <h:inputTextarea
 id="textarea"
 rows="10"
 styleClass="professional-profile-input-area"
 binding="#{profilesRepeaterBean.profileInput}"
 value="#{lang.profile}"
 label="#{pp_msg.header}"
 </h:inputTextarea>
 </h:panelGrid>
 </f:facet>
 </rich:togglePanel>
 
 </a4j:repeat>
 </h:form>Currently all data are stored for all panels at "Save" button click. I want to change it to save only changed panel. For each toolbar an instance of "lang" object is created which i want to send to backing bean where I planned to merge with JPA.
 public void SaveCVProfile(ICvProfileLang profile) {
 cvData.editChangedProfile(profile);
 }All combinations I try gave me just String as parameter value, not an Object reference.
Any ideas?

Thanks BalusC,
I must have messed up my previous tries.
I used you hint with "f:setPropertyActionListener ".
<a4j:commandLink id="submit"
 value="#{common_msg.buttonSave}" <<<<<< "action" - REMOVED
 messagePlace="textarea"
 onclick="CommandOnClick(#{rich:element('textarea')},'#{common_msg.dataSaving}','#{common_msg.dataSaved}');"
 data="#{facesContext.maximumSeverity.ordinal ge 2}"
 oncomplete="CommandOnComplete(#{rich:element('textarea')},data,1500); DataSaved();">
 <rich:toolTip value="#{pp_msg.tooltipButtonSave}" direction="top-left" showDelay="${config.toolTipDelay}" styleClass="tool-tip"/>
 <f:setPropertyActionListener target="#{profilesBean.saveCVProfile}" value="#{lang}" />
</a4j:commandLink>I removed "action" from commandLink and passed the object to action listener.
It works as intended now, even without using UIData#getRowData().

How do I eliminate the automatic pop-up created when using the Rectangle Tool?

For some odd reason, Acrobat 9 is now adding a pop-up every time I use the Rectangle Tool. I am using the Rectangle Tool merely to draw a box around text but I do NOT want there to be an associated pop-up. Is there a way to change it so the pop-up will not be automatically created and all I will get is the rectangle itself?
Thanks for your help!
Jim

Something to try -
Open Acrobat's Preferences. Select the Commenting category. The second (middle) pane has Pop-Up Open Behavior configuration settings. Playing with what is or is not ticked may provide the desired pop-up behavior.
Be well...

Differences between servlet and backing bean

Could anyone please tell me whether everywhere that servlet can be used, backing bean and JSF can be used too? Are JSF and backing beans the new alternatives for JSP and servlets? please clarify the relations between these concepts for me.
Thanks
Laura

Laura_Jlover wrote:
Thank you. You mean backing beans can do every thing that servlets can do? Yes.
JSF pages can work with servlets? Strictly speaking, every JSF page gets passed through the FacesServlet which does all the task. The lifecycle, creating the FacesContext, putting the request parameters in backing beans, rendering the response, etcetera.
what are the advantages of servlet and the advantages of backing beans? what's the disadvantages? In general, which one is better?In context of JSF, you should be using backing beans, not Servlets. There is nothing what a Servlet can offer you as an advantage in the JSF context. It is simply not an option/alternative. You can't even call a Servlet (directly) using a JSF h:form. You, however, can access backing beans in any JSP or Servlet outside the JSF context.
Just carefully read the JSF specification or buy a JSF book and the picture will be clear.
JSF spec: [http://jcp.org/aboutJava/communityprocess/final/jsr252/index.html].
JSF book: [http://www.amazon.com/JavaServer-Faces-Complete-Reference/dp/0072262400].

Why the backing Bean ?

how use backing Bean in jsf page

A backing bean or a managed bean is where you put business logic that reacts to user interface events.
A backing bean usually has references to specific components on a JSF page, a managed bean usually doesn't tie itself to a specific page.
http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JSFIntro8.html

How to call javascript function in back bean of jsf

hi,
i am trying to call java script function in back bean but not done. Is there any code for call javascript function in bean file.

Java runs at server side.
JSF produces HTML output.
Server sends HTML output to client.
Java stops running.
HTML runs at client side.
JS starts to run in HTML.
Clear? Java is a server side language. JS is a client side language. To run JS using JSF, simply print it out to the HTML so that it get invoked when the HTML runs.

Removing Automatic Backing Bean Updates in Jdev 11.1.2.2.0

Hi,
in the User Guide and in the book "Jdeveloper 11g Handbook" I'm reading:
Remove Automatic Backing Bean Updates
1. Click page.jspx file tab. Click the Design tab
2. Select Design | Page Properties and click the Component Binding tab. Unselect Auto Bind.
Why I cannot locate Page Properties and the Component Bind tab?
Where is? Can help me with some print screen?
Thansk in advice

Hi,
Actually first chance to switch it off is when you create a new page: There is a managed bean tab in which you can do this. For existing pages, open the page in the visual editor and choose Design --> Page Properties from teh JDeveloper menu. In the opened dialog there is a "Component Binding" tab you press
Frank

Calling from an EJB into a JSF Backing Bean

Hello all,
I'm looking for some help in making calls from an EJB into a Backing Bean (the converse is fairly straightforward). My basic question is: what is regarded as the best way to do this?
However, for anybody who's interested, I'll describe what I've been trying...
Here's my situation (I'm working with OC4J 10.1.3.2). I have a simple application-scoped backing bean:
   public class BackingBean implements SimpleInterface, Serializable {
       private String greeting = "Hello, World";
       private SessionEJBRemote blBeanRemote = null;
       public BackingBean() {
           // get hold of EJB
           // [ ... code to obtain EJB's remote interface snipped ... ]
           // set the callback with the EJB
           try {
               blBeanRemote.setCallback(this);
           } catch (Exception ex) {
               ex.printStackTrace();
       // methods to manipulate the greeting string
       public String getGreeting() {
           return greeting;
       public void setGreeting(String greeting) {
           this.greeting = greeting;
   }SimpleInterface, which my Backing Bean implements is, well, a simple interface:
   public interface SimpleInterface {
       public void setGreeting(String greeting);
   }And my EJB is also pretty straightforward:
   @Stateful(name="SessionEJB")
   public class SessionEJBBean implements SessionEJBRemote, SessionEJBLocal {
       private SimpleInterface callback = null;
       public void setCallback(SimpleInterface callback) {
           this.callback = callback;
           callback.setGreeting("Goodbye, World");
   }Now, by using SimpleInterface, my intention was to ensure a one-way dependency: i.e. the JSF-level code would depend on the EJB-level code, but not vice versa.
However, my experimentation has shown that when I make the call to blBeanRemote.setCallback, the parameter appears to be passed by value rather than by reference. This means firstly that, at runtime, by EJB needs to have access to my backing bean class and secondly, that the call to callback.setGreeting has no effect.
Can anybody suggest how to work around this? Is it possible to pass the backing bean by reference? Is there a better way to achieve this callback? I appreciate that these questions might be more general Java/AppServer queries rather than JSF-specific ones - but hopefully this is something that all you JSF experts have encountered before.
(Incidentally, I realise that what I'm doing in this example is pointless - what I'm building towards is using the ICEFaces framework to have the EJBs prod a backing bean which will in turn cause a user's browser to rerender.)
Many thanks - any help very much appreciated!
Alistair.

Hi Raymond - yes, you've pretty much got that spot on: an event occurs (say receipt of a JMS message - which is spontaneous, as far as the users are concerned). As a result of that event, the client's view (in their browser) needs to be re-rendered.
ICEFaces uses the AJAX technique to allow server-pushes, and rather than refreshing the whole page it uses "Direct-to-DOM" rendering to maninpulate the page components. If you've not come across it, and you're interested, then there are some pretty interesting demos here: http://www.icefaces.org/main/demos/ - the "chat" feature of the Auction Monitor demo (if you open it up in two browsers) is the nearest to the effect I'm looking for.
The Auction Monitor demo uses a number of session-scoped beans, each implementing the ICEFaces "Renderable" interface, and each of which registers itself with an application-scoped bean. The application-scoped bean can thus iterate through each of the session-scoped beans and cause the corresponding browser to refresh.
Unfortunately, in the Auction Monitor demo, the entry point is always from a browser - albeit the result is then mirrored across all connected browsers. I haven't found any examples of this processing being driven by an external event, hence my experimentation in this area!

Moving Scriptlet Code to backing bean when converting from JSP - Facelets

Hello!
We are converting our application from jsf1.2 to 2.0 and all jsps are being converted to XHTML. Some are trivial while others had very complex scriptlets.
I would like to know what are some of the recommended ways of moving Scriptlet Code to backing bean when converting from JSP -> Facelets.
I have thought about listeners, actionListeners, putting code getXXXX() of the backing bean and then calling #{bean.XXXX} but not sure whats the best way.
I do appreciate the response!
Eg of a jsp page:
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<%@ taglib uri="/WEB-INF/xxx-jsf.tld" prefix="l" %>
<%@ taglib uri="/WEB-INF/yyy-pp.tld" prefix="p" %>
<%@ page import="com.ttyy.search.beans.jsf.AdvancedSearchFormManagedBean" %>
<%@ page import="com.kkee.util.*"%>
<%
 AdvancedSearchFormManagedBean advancedSearchFormManagedBean = (AdvancedSearchFormManagedBean) request.getSession().getAttribute("AdvancedSearchFormManagedBean");
 if (advancedSearchFormManagedBean == null) {
 advancedSearchFormManagedBean = new AdvancedSearchFormManagedBean();
 request.getSession().setAttribute("AdvancedSearchFormManagedBean", advancedSearchFormManagedBean);
 advancedSearchFormManagedBean.initializeForAdvancedSearchOptions();
 advancedSearchFormManagedBean.setQuickSearch();
 request.setAttribute("portletHeader", "Hello " + advancedSearchFormManagedBean.getPerson().getFirstname() + ", check out the latest programs in your practice areas and jurisdictions");
%>
<h:form id="MYCenterForm">
 <p:portletRenderer portletSetName="test of portlet"
 portletContainer="#{PortletContainerManagedBean}"
 id="MYCenter"
 portletScope = "TEST_SCOPE"
 suppressIfNoData="true"
 portletSkinName="SOME_SKIN">
 <f:facet name="persistenceToolkit">
 <h:commandLink id="persistenceToolkitLink"
 actionListener="#{PortletContainerManagedBean.persistPortletSetStateListener}">
 <h:outputText value="Save State Of Portlet Set" id="persistenceToolkitLinkText"/>
 </h:commandLink>
 </f:facet>
 </p:pagePortletSetRenderer>
</h:form>
<%
 String flag = PropertyItems.getInstance().getPropertyItem("response.time.flag");
 if("1".equals(flag)){
 ResponseTime rt = (ResponseTime) session.getAttribute("responseTime");
 if(rt!=null){
 rt.setDesc("my cle loaded");
 long now = System.currentTimeMillis();
 long start = rt.getStart() + rt.getTotal();
 rt.setInterval(now-start);
 rt.setTotal(rt.getTotal()+rt.getInterval());
 LogUtil.log(rt.toString(), LogUtil.DEBUG_LEVEL);
 session.setAttribute("responseTime", rt);
%>

That helps.
This could be another topic question but itst kind of related to what i am doing right now. while converting JSP to facelet (in jsf2) I came across another issue.
<h:commandLink id="Save" rendered="#{RegistrationBean.isNOTInOrigionalRegistrationMode}" action="#{RegistrationBean.updateProfile2Submit}" styleClass="#{portalSkinManagedBean.contentPortletSkin.strongTextStyle}">
 <l:htmlSkinnedImage id="SaveImage" style="border:0;" url="save.gif" alt="Save Information"/>
</h:commandLink>When I click on the generated link, I get this. And this is happening for all the h:commandLink in the application.
http://localhost:9080/registration/updateProfile2.jsf[request.getQueryString()=null][request.getRequestedSessionId()=F1CCE237DD81D301F1C4DBA6910FFD8A][request.isRequestedSessionIdFromCookie()=true][request.isRequestedSessionIdFromURL()=false][request.isRequestedSessionIdValid()=true]Parameters:[rolePracticeAreasForm:title=rolePracticeAreasForm:primaryPracticeArea=10002javax.faces.ViewState=-2943345291093118815:-4400303399130292206rolePracticeAreasForm:practiceAreasMod2=10148.1rolePracticeAreasForm:practiceAreasMod1=10002.1rolePracticeAreasForm:Save=rolePracticeAreasForm:SaverolePracticeAreasForm=rolePracticeAreasFormrolePracticeAreasForm:otherField=rolePracticeAreasForm:fromMyAccount=1]||
javax.servlet.ServletException: Index: 0, Size: 0
 at javax.faces.webapp.FacesServlet.service(FacesServlet.java:325)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at com.legaledcenter.util.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:250)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:198)
 at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:75)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at com.jscape.framework.galileo.support.upload.UploadFilter.doFilter(UploadFilter.java:71)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
 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:293)
 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
 at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
 at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
 at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
 at java.util.ArrayList.RangeCheck(ArrayList.java:547)
 at java.util.ArrayList.get(ArrayList.java:322)
 at javax.faces.component.AttachedObjectListHolder.restoreState(AttachedObjectListHolder.java:161)
 at javax.faces.component.UIComponentBase.restoreState(UIComponentBase.java:1427)
 at com.sun.faces.application.view.StateHolderSaver.restore(StateHolderSaver.java:121)
 at com.sun.faces.application.view.StateManagementStrategyImpl$4.invokeContextCallback(StateManagementStrategyImpl.java:289)
 at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:1253)
 at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:672)
 at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:1262)
 at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:672)
 at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:1262)
 at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:672)
 at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:1262)
 at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:672)
 at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:1262)
 at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:672)
 at com.sun.faces.application.view.StateManagementStrategyImpl.restoreView(StateManagementStrategyImpl.java:284)
 at com.sun.faces.application.StateManagerImpl.restoreView(StateManagerImpl.java:177)
 at com.sun.faces.application.view.ViewHandlingStrategy.restoreView(ViewHandlingStrategy.java:119)
 at com.sun.faces.application.view.FaceletViewHandlingStrategy.restoreView(FaceletViewHandlingStrategy.java:434)
 at com.sun.faces.application.view.MultiViewHandler.restoreView(MultiViewHandler.java:143)
 at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:199)
 at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
 at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:110)
 at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
 at javax.faces.webapp.FacesServlet.service(FacesServlet.java:312)
 ... 22 more
********** Message End *************Thanks

JSF Backing Bean State Being Lost Prior to Submit

ISSUE
I have an attribute in a backing bean for a drop-down list in a JSF that loses its state before I submit the page, which causes data updates to the backing bean dependent upon its state to be ignored.
CONTEXT
The JSF in question has a selectOneMenu drop-down list that determines whether or not several inputText fields will be rendered. The selectOneMenu is bound to an enum in the backing bean, and there are conditional accessors allowing the JSF to determine which inputTexts should be included in the current view. The three valid values of the drop-down are "ALL", "RANGE" and "SINGLE". The page is request scoped, a requirement of this project.
Here is the JSF tag for the selectOneMenu drop-down list:
<h:selectOneMenu disabled="#{not backingBean.newEntry}"
 id="tCriteria"
 value="#{backingBean.tCriteria}"
 onchange="submit()">
 <f:selectItems value="#{backingBean.possibleTCriteria}" />
</h:selectOneMenu>And here are the RANGE selection-specific inputText controls:
<h:inputText disabled="#{not backingBean.newEntry}"
 rendered="#{backingBean.tRange}"
 id="startTIndex"
 value="#{backingBean.tIndex}" />
<h:inputText disabled="#{not backingBean.newEntry}"
 rendered="#{backingBean.tRange}"
 id="endTIndex"
 value="#{backingBean.endTIndex}" />Here is how I initialize the backing bean for the drop-down list attribute:
* The current "t" criteria.
private TCriteria tCriteria = TCriteria.ALL;And there are basic accessor/mutator methods for it. All of this works pretty well, with one problem. If I select "RANGE" in the drop-down, the appropriate inputText fields appear in the view. When I submit the page with values in the inputText fields, the value of the drop-down in the backing bean has been reset to its default initial value ("ALL") without having been updated through its mutator. Thus, when values in the backing bean are updated from the JSF, the conditional inputText fields are ignored, as they appear to have been deemed irrelevant during the update phase by the invalid state of the backing bean for the drop-down.
To test my theory, I changed the default value of the backing bean attribute for the drop-down to be "RANGE", and made it final. The page behaves perfectly in updating the backing bean with the values entered for the conditionally-displayed inputText controls. This tells me that the invalid state of the backing bean drop-down list attribute must be the problem. Furthermore, I have tried using "disabled=", "readonly=" and "rendered=" on the conditional inputText fields, and none of that seems to make a difference. I also tried using a ValueChangeHandler, but that didn't do anything about it.
Note - the backing bean does realize that the correct state for the drop-down should be "RANGE", but only AFTER the backing bean has received its updated values from the page controls.
Has anyone seen anything like this? I haven't read anything in previous posts about an issue like this, but it has to be something someone has seen before. Maybe related to using the enum type? Thanks.

Hi,
did your web.xml file had any parameter regarding explicitly indicating the way to save state?
I mean something like
<context-param>
 <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
 <param-value>server</param-value>
</context-param>One last question: did you stay with request scope beans or session ones?
Greetings.
MogaRick

JSF Backing bean / JSP interaction questions

A few questions about JSF beans and JSP page interactions. Bear in mind that I'm new to both JSP and JSF, so a solution that might be obvious to the rest of the world may be new to me.
1. Can I pass a parameter to the backing bean method from an "action" attribute:
<h:commandLink action="#{TableData.SortRec}">
<h:outputText value="#{msgs.selectedHeader}"/>
</h:commandLink>
I'd like to call the same method from several controls, but pass it a parameter to determine which field to sort on.
2) Is there a way for a backing bean method to determine which control invoked it?
3) Is there a way to access JSF backing bean methods from JSP tags. I'd like to do some conditional page assembly based on a JSF bean property... JSF doesn't appear to have a conditional like JSP's <c:if>, but I could use JSP's if it could access the JSF bean.

Could you pl tell me how to pass parameter thru CommandButton
I have the following situation
1) greetingList.faces which list the Ids & greeting Text
Id Text
1 Hello World
2 Hello World
2) Pl note Ids are h:commandLink. A click on the Id will render greetingForm.faces with data pertaining to that Id and with Update h:CommandButton
3) When i click Update button it results in the following error
javax.faces.FacesException: Error calling action method of component with id greetingForm:_id4
Caused by: javax.faces.el.EvaluationException: Exception while invoking expression #{greetingForm.update}
Caused by: java.lang.NullPointerException
So i verified with h:message that Id is passed as Null when click on Update button. I also checked greetingForm.faces has a not null value by printing <h:outputText value="#{greetingForm.message.id}"/>
So i guess the Id value is overwriteen with null. Also i have defined Id as property in managed bean
<managed-bean-name>greetingForm</managed-bean-name>
<managed-bean-class>com.mycompany.GreetingForm</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<managed-property>
<property-name>id</property-name>
<value>#{param.id}</value>
</managed-property>
Any pointers/suggestions at the earliest on how to pass the value of Id on a click of update button from greetingForm.faces to greetingForm.java will be highly appreciated
I am willing to upload my war file
Regards
Bansi

SelectOneMenu: How can I fire a backing bean method just when click

I want that when just I click one option of Dropdown list it fires a backing bean method.
The method must take the new value of dropdown, to execute a SQL to populate a new (another one) dropdown list and refresh the page.
My code
 <h:commandButton id="button1" style="left: 216px; top: 216px; position: absolute" value="Cancelar"/>
 <h:commandButton id="button2" style="left: 312px; top: 216px; position: absolute" value="Generar"/>
 <h:outputLabel for="componentLabel5" id="componentLabel5" style="left: 120px; top: 0px; position: absolute">
 <h:outputText id="componentLabel5Text" value="Título de la Página"/>
 </h:outputLabel>
 <h:selectOneMenu immediate="true" value="#{fgstb.ctoId}" valueChangeListener="#{fgstb.cambiaValorCtos}" id="dropdown1" style="left: 264px; top: 72px; position: absolute; width: 120px">
 <f:selectItems id="dropdown1SelectItems" value="#{fgstb.ctos}"/>
 </h:selectOneMenu>
 <h:selectOneRadio id="radioButtonList1" layout="pageDirection" style="left: 48px; top: 48px; position: absolute" value="#{fgstb.modo}">
 <f:selectItem id="radioButton1" itemLabel="Generar Campeonato" itemValue="1"/>
 <f:selectItem id="radioButton2" itemLabel="Generar desde Campeonato" itemValue="2"/>
 <f:selectItem id="radioButton3" itemLabel="Generar Todos Campeonatos" itemValue="3"/>
 </h:selectOneRadio>It works fine but when I push a button and I would like it works when I click over dropdown list.
Thank you

Hi,
You can simply add onchange="submit()" attribute to your component to allow form to be submited when the coomponent value is changed, and add also a value change listener to allow JSF to be notiifed for component value change event :
<h:selectOneMenu onchange="submit()" valueChangeListener="#{fgstb.cambiaValorCtos}"
 immediate="true" value="#{fgstb.ctoId}" id="dropdown1" style="left: 264px; top: 72px; position: absolute; width: 120px">
 <f:selectItems id="dropdown1SelectItems" value="#{fgstb.ctos}"/>
</h:selectOneMenu>

Adding JSF 2 composite component at runtime from backing bean

Hello,
I try to add a custom composite component to a JSF page from a backing bean method in this way:
+//-----------------------------------------------------------------------------------------------------+
+public String addCC(){+
+//create my comoposite component's istance+
ccPageLoader = new CCPageLoader();
+//set a property+
ccPageLoader.setSrc("one.xhtml");
+//get the object on the JSF page that must contains the comp.comp.+
UIComponent c = this.findComponentInRoot("container");
+//ADD THE COMPOSITE COMPONENT TO THE PAGE+
c.getChildren().add(ccPageLoader);
return null;
+}+
+//-----------------------------------------------------------------------------------------------------+
Now, the method doesn't get errors, the beginEncode() method of the composite component is called, but I cannot see the composite component in the page...
Instead, if a try to add a standard JSF component, using the same code, I can see the JSF component in the page.
Any suggestion?
Thank you, F. ...

I removed all my assertions to see how far the submission could go when going unsane.
I discovered that JSF attempts to redisplay my web page, and not to follow on the next one...
... so I have one explanation.
Except that:
There is no fields in the form that require a validation.
(three hidden text fields, and a <h;inputTextarea> but that is not checked or mandatory).
The form is not supposed to fail,
and even if it had too, why the validation step doesn't carry the current managed bean at redisplay time, but instead re-create an empty managed bean?
My form starts with a:
<h:form id="${someId}"> where ${someId} is a scoped variable.
Can it causes a problem during submission? Shall I use only a constant id for my form?
What can you suggest me to do?
Do I have a way to discover what JSF is about to complain against, before it tries to redisplay the page? I see nothing in my logs, but may be I shall redefine a log level somewhere, add one handler or something else?
Regards,
Grunt.

Automatic amendment of jsf when backing beans refactored: tool support ?

Similar Messages

Maybe you are looking for