Ilari Moilanen

Why would you post a totally unrelated question to a topic that is THREE (almost four) years old? How can you possibly expect someone to answer you?

ashwani sinha wrote:
In my case, page have lots of requests that I want to retained in new page. could you please elaborate more on how to access the original values.
- thanks in advance.

I still use only JSF 2 so I do not know how this would work with JSF 1 but for example I use the temporay storage called Flash.
In the first action I use
FacesContext.getCurrentInstance().getExternalContext().getFlash().put("nameoftheobject", object);
and then in the receiving side in xhtml I use
<ui:define name="metadata"> <f:event type="preRenderView" listener="#{requestBean.loadDefaultValues}" /> </ui:define>
and then in java code inside the loadDefaultValues method I get the contents with
MyObject object = (MyObject) FacesContext.getCurrentInstance().getExternalContext().getFlash().get("nameoftheobject");

Or if I just want to give simple parameters to receiving side I might use something like this (remove the blanks after & sign)
return "addrequest?faces-redirect=true& amp;id=" + this.id + "& amp;edit=" + this.edit;
and then in the xhtml I use them with
<ui:define name="metadata"> <f:metadata> <f:viewParam name="id" required="true" value="#{requestBean.selectedReqId}" label="#{msgs.id}" requiredMessage="#{msgs.idrequired}" validatorMessage="#{msgs.idnotvalid}"> <f:validateLongRange minimum="1" /> </f:viewParam> <f:viewParam name="edit" value="#{requestBean.edit}" /> </f:metadata> </ui:define>
These are maybe not optimized versions and there probably are easier ways of course...

Check whether controller is null or whether getKelompokBiayaJpaController() method returns null. Based on your error message (I presume that you showed the root cause correctly) the controller object is null. So you have to find out why either MasterBiyanMbean is not present or why fetching the object does not work. Very basic stuff (null checks and all).

Saurabh Saxen,

alas I do not have an example. All I have is code in production use.

But there should be nothing complicated in using the custom validator. As I said above I use JSF 2 (MyFaces) and the above code works as is. I do NOT have anything in the config file(s) since the @FacesValidator annotation above is enough. The validate method throws javax.faces.validator.ValidatorException if the validation fails. You can google the different classes used to find what their API says about them.

I do not use the validator programmatically anywhere, I just tested it because the original poster said that his code does not work. Instead I use the validator in UI like this:
<t:inputCalendar id="startdate" value="#{searchBean.startDate}" renderAsPopup="true" popupDateFormat="#{msgs.formatdateshort}" popupTodayDateFormat="#{msgs.formatdateshort}" popupWeekString="#{msgs.week}" popupTodayString="#{msgs.thedatetoday}" validator="dateValidator" label="#{msgs.startdate}" converterMessage="#{msgs.startdateinvalid}" />
(where t: is defined as xmlns:t="http://myfaces.apache.org/tomahawk")

This is a very common exception and is thrown when you try to use a view that has already expired (expiration depends on many factors).
We need more information of your situation. When exactly are you getting this exception etc

You are welcome.

Allright. This is how I do it. Not my own code so I can not take credit for it and alas I do not remember where I got it. Additionally there might be a better solution (JSF based for example) since this uses basic JDK API.

I have a helper class called LocaleHelper and inside it these two methods: protected static ClassLoader getClassLoader(Object defaultObject) { ClassLoader loader = Thread.currentThread().getContextClassLoader(); if (loader == null) { loader = defaultObject.getClass().getClassLoader(); } return loader; } public static String getLocaleString(String bundle, String key, Object parameters[], Locale locale) { String message = null; ResourceBundle resourceBundle = ResourceBundle.getBundle(bundle, locale, getClassLoader(parameters)); try { message = resourceBundle.getString(key); } catch (MissingResourceException e) { message = "ERROR MESSAGE!"; } if (parameters != null) { StringBuffer stringBuffer=new StringBuffer(); MessageFormat messageFormat = new MessageFormat(message, locale); message = messageFormat.format(parameters, stringBuffer, null).toString(); } return message; }

And you can use it for example with a call like this:
LocaleHelper.getLocaleString("messages", "helloworld", null, FacesContext.getCurrentInstance().getViewRoot().getLocale())
I can explain it further but I think it should be pretty obvious what it does. It uses basic java API as I explained so all the classes there are from java.util package or from java.text package

Good to hear.

But in the long run (if you continue to make more complex applications etc) you should do as bajrang asthana suggested and set the values once and use the from there on (using the @postconstruct or some other way). It is not very efficient to always run the for loop (or do any other kind of complex logic) in the setters/getters since internally JSF may call the setters and getters multiple times during the execution. I have seen this behaviour when I have put logging inside a getter (or setter) and a getter may be called as many as ten times altough the value is used only once on page. I do not know the reason for that but since getters/setters should not contain complex logic the multiple calls do not affect performance normally.

For some reason you changed the xhtml/jsp instead of java code

Just use <h:outputText value="#{Cliente.welcome}"/>
and public String getWelcome() { ... }

argh, I do not have my code here so I can not check how I do it but I will answer tomorrow morning if someone else has not already told you how by then
BTW, do you use JSF 1 or JSF 2?

My original reply applies. You did not even test it? Why?

I know you do not have a property called welcome but it does not matter. JSF expects to find a property and by normal java conventions you access properties via their setters and getters.

JSF expects that you use the proper naming convention. The property name is "welcome" so the getter should be named "getWelcome()" instead of just "welcome()".

Without any info of your setup this is almost impossible to solve.
Show at least your web.xml and faces-config.xml files to us

I am not familiar with richfaces but it seems that you are following somekind of example. Can you show this example to us?

Also, where do you define that your class (called "sorting") is used?

Why the values of the dropdown boxes change to their default values? Have you checked if this behavior occurs even id you do not disable them? If I remember correctly disabled inputs DO NOT send their data to server. So your logic is faulty there. Have you tried readonly (instead of disabled) or similar?

As for how to disable input after the reload I have done something similar (not with JQuery though) and I just do what I have to do (with javascript) when the page has been loaded. I know that it is not a perfect solution but it works in my particular needs.
Something like this:
<h:body onload="init()">
(where the init() is a javascript funtion that can for example disable those dropdown boxes after the reload etc.)