Access ComponentId in Back Bean

Hello,
I have the jsp :
<h:outputText id="One" value="#{myBean1.textValue}"/>
<h:outputText id="One" value="#{myBean1.textValue}"/>
The Error is :
javax.servlet.ServletException: javax.servlet.jsp.JspException: Component ID 'One' has already been used in the view.
See below for the view up to the point of the detected error.
+id: j_id_id25
type: javax.faces.component.UIViewRoot@1e6d7b6
+id: j_id_id27
type: javax.faces.component.html.HtmlForm@5c1eea
+id: j_id0
type: javax.faces.component.html.HtmlOutputText@1f1ab66
+id: j_id1
type: javax.faces.component.html.HtmlOutputText@12be098
+id: One <===============
type: javax.faces.component.html.HtmlOutputText@1a62b24
How an I access the Id in my Back Bean? Obviously the Id has to be different. If I set the Id's to "One" and "Two", how can I access these Values?
FacesContext context = FacesContext.getCurrentInstance();
System.out.println(context.getViewRoot().getId());
prints only the "j_id_id25" ....
thx

Hello,
the basic functionallity should be :
1. on a table all messages, labels and other infos are stored. That works fine, read with JPA works perfect
2. on the jsp I refer with an Id to that table and read the value from that table
3. displaying that readen value
the The BalusC Code works fine, as long the myBean.text is unique.
<h:outputText binding="#{myBean.text}" value="#{myBean.textValue}">
<f:attribute name="attributename" value="attributevalue" />
</h:outputText>
using the same code twice on the jsp does not work, as you posted earlier.
so after all I am looking for a solution similar to that code, but I want to use only one method and parse parameters so I can read the wanted value from the table ...
I thought, differenciate with the Id like
<h:outputText id="Id1" value="#{myBean1.textValue}"/>
<h:outputText id="Id2" value="#{myBean1.textValue}"/>
could bring me to my solution. if i could read the component Id "Id1" I cann access the database depending on that Id .... then I could use the same outputText with different id ...
hope you can help me ...

Similar Messages

Few basic doubts about accessing AM from backing bean class

Hi ADF experts,
I have just started working in ADF Faces.I made a sample search page.My page is attached to a managed backing bean. I have attached command button on my page to a custom method in backing bean class.
So on, click of button this method is called in backing bean.Now, i have few doubts:
1)How to get values of various UI beans in this event code?
2)I am accesing AM , in my method with this code:
FacesContext facesContext = FacesContext.getCurrentInstance();
ExternalContext extContext = facesContext.getExternalContext();
Application app = facesContext.getApplication();
DCBindingContainer binding = (DCBindingContainer)app.getVariableResolver().resolveVariable(facesContext, "bindings");
//Accessing AM
ApplicationModule am = binding.getDataControl().getApplicationModule();
iS this correct ?
3) After getting handle of am how to call my custom method in AM Class?there was "invokeMethod" API in application module class in OAF, is there any such method here?
Please help me.
--ADF learner.

Thanks for ur response Frank, actually I am from OA Framework back ground.It would be great if help us a little with ur valuble thoughts.
OA Framework also uses bc4j in model layer of framework. We have a requirement where our existing developers from OA Framework have to move to ADF to make a new application where time lines are quite strict.If this would not be possible we will switch to plain jsp and jdbc,but our tech experts say ADF Faces is the best tech.
In OA Framework, Application Module is key class for all busiess logic and Controller is used for page navigation. So, I m just trying to find the same similarity , where we write we add all event codes in custom action methods in the backing bean class of page, which we consider equivalent to process form request method in Controller class of OAF.
But there are two things, I still want to know:
1)While page render, how to call specific AM methods(like setting where clause of certain VOs)
2)In action methods, the way i described(I found that in one thread only)to access AM, what is wrong in that?Also, I went through
http://radio.weblogs.com/0118231/stories/2004/09/23/notYetDocumentedAdfSampleApplications.html
where coule of examples use similar approach to access AM from backing bean class and call custom methods of AM(Doing various, deletes etc from VOs).
3)In these methods can we set any property of beans on the page, I am asking because in OAF, generally we use PPR for js alternatives.But all properties of beans cannot be set in post event.
Thanks and Regards
--ADF Learner

I want to have access from my backing bean to attributes

Hi,
I have a table PERSON with the columns ID (PK), FIRST_NAME, LAST_NAME and SALUTATION_ID (FK).
I have a second table SALUTATION with the columns ID and NAME.
I do use the following lines of code if I want to make changes to the PERSON table and it works fine.
DCBindingContainer dcBind = (DCBindingContainer)getBindings();
DCIteratorBinding iterBind = (DCIteratorBinding)dcBind.get("PersonCollectionIterator");
iterBind.getCurrentRow().setAttribute("FIRST_NAME", "Tobias");
dcBind.getOperationBinding("mergeEntity").execute();
My problem is, that I can't change the SALUTATION_ID of PERSON. I don't have access to that attribute. I did use the following line of code to print out all the available attributes and it only showed ID, FIRST_NAME and LAST_NAME.
iterBind.getCurrentRow().getAttributeNames()
What could I do?
Thank You
Tobias

Hi!
I assume that you use EJBs. Then, you have no foreign keys in your parent entity (Person). Instead you have a mapping to the related entity (Salutation) by which you can access a salutation for a person like this (I'm using EL for simplicity):
Person p = resolve("#{PersonCollectionIterator.currentRow.dataProvider}");
Salutation s = p.getSalutation();
and you can set a salutation by:
p.setSalutation(newSalutation);
where newSalutation is an salutation entity you somehow retrieved from your model. For example, if you enter salutation ID in text box on your page, then in backing bean button action listener you should call findSalutationById method in Fascade which returns a newSalutation entity and then set that new salutation as above. After that, you have a new salutation mapped to person and you can invoke mergeEntity on you Fascade.
Hope this helps.
PaKo

Database access from Managed/Backing bean

Hi,
I would like to authenticate web users from a database table, I get the account details
in the Welcome page, I wish to check if the user exists in the table (from the managed bean), how do I do this?
Is this good practice to access the db from managed bean? If not how do I do this in model component and pass the value back and forth from managed bean?
Thanks,
Jai.

Hi
You can get all the information of logged in user from SecurityContext(you can get this either from ADFContext using ADFContext.getCurrent().getSecurityContext() or using EL expression eg. #{securityContext.userName} shows logged in user name)
API: http://download.oracle.com/docs/cd/E15051_01/apirefs.1111/e10686/oracle/adf/share/security/SecurityContext.html#method_summary
More details on enabling security: http://download.oracle.com/docs/cd/E12839_01/web.1111/b31974/adding_security.htm#BGBCEDDD
Sireesha

How to access backing bean of a xml component , in a managed bean of ADF

Hi,
We wrote a xml component in JSF and this component is used in ADF project by including the component as jar .
In a master detail page , we need to update the value of the xml component, when the master row is changed. How to do this.
We are trying to do this by accessing the backing bean of the xml component in ADF project's managed bean. So when ever the row changes, we can access the managed bean in ADF and then can set the value of the xml component by accessing it's backing bean
But i can't access the backing bean instance of the xml component in the ADF managed bean. Could you let me know how to do this. Thanks .

Thanks for the response Shay. The xml component is added as a custom component , with a separate faces-config.xml file . This component is added to ADF project as a jar with a custom tag.
In the ADF project , i'm having different managed beans and i can access them from a different managed bean.
The issue is, i can't access the added custom component's backing bean which is available from a different jar , defined in a separate faces-config.xml file . This backing bean is defined with request scope.

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!

Class not Found when accessing Proxy class from backing bean in VC.

Hi All,
I'm attempting to access a class of a webservice(generated as a proxy) within my ADF application and invoke the method within a backing bean of the View Controller(bean scope : backing bean). The proxy has generated an ObjectFactory class among other classes. When I access this Object factory class from within the backing bean, the application throws a Class not found error.
I don't know where the error lies since I've declared the View Controller of the ADF application dependent on the Proxy and I've imported the class and accessing it within a backing bean. How would you suggest I approach resolveing this.
JDev : 1.1.1.4
Thank you.
Regards
PP.

Hello Arun,
Thank you for suggesting a Data control, but my requirement isn't to drag and drop the method as a button. It's more of a behind the scnes updating data via a database adapter requirement.
I've resolved the issue. turns out, my deployment archive didn't include the proxy.jpr. Once included it works likea charm.
Thanks
PP.

JSF backing bean accessibility from external class

I am using JSF in my application. Consider i am assigning a value of the inputtext field to a string in my managed bean. This bean has the getters and setters for the string.
Now my requirement is to get the value of the string i.e. the string value entered in the input text field in another class file. If "A" is a backing bean, I want a class B to access the values(in this case the inputtext value) from A.
Thanks in Advance.

Below is the code where i am using the inputtext tag in the JSP page
<h:inputText value="#{person.name}" />
"person" is the backing bean which is declared in the faces-config.xml
PersonBean code:*
package jsfExample;
public class PersonBean {
     private String name;
public void setName(String name) {
          this.name = name;
public String getName() {
          return this.name;
Now i have another class in the same package as shown below.
package jsfExample;
public class worker extends PersonBean{
//this function should use the variable name present in the backing bean//
     public void access(){
     PersonBean person= new PersonBean();
     String str=person.getName();
     System.out.println(str);
//I am getting null value in the str variable inside here//
but if i print the variable inside the backing bean(*PersonBean*) it is working fine.

ADF BC how to access session backing bean value in servlet

Hi everyone,
How do I access session backing bean value in a servlet?

Frank, thanks for your reply.
I'm not sure how I can incorporate this example into my situation. Let me explain more detail about my problem.
"servlet" in my post here actually means a custom servlet I wrote for rendering an image that is stored in db as ordimage. In this servlet, I get hold of my appmodule by using Configuation.createRootApplicationModule(). By doing so (If I'm not wrong) a new database session/connection is created. What I'm going to achieve is set application context for this new session/connection in db with the data stored in a session backing bean in the view layer.
I can pass the required data to the servlet thru url parameter, but I don't want to do it this way for the reason that the data may contains sensitive information.
I hope I have explained myself well.
Message was edited by:
bsmt

Accessing a JSF element from a back bean method

Hi,
short question, can I access the JSF element from a back bean method?
So, for example, if I have the following JSF code:
<h:panelGroup id="test1" rendered="#{bean.someMethod}">...</h:panelGroup>
<h:panelGroup id="test2" rendered="#{bean.someMethod}">...</h:panelGroup>
<h:panelGroup id="test3" rendered="#{bean.someMethod}">...</h:panelGroup>
Can I found out in some way, which element (esp. which ID) calls the someMethod-method?
Kind regards
Matthias

There are more possibilities as well. If you depend it on for example the User's rights/groups, then you can also do for example:
rendered="#{user.admin}" // getter = public boolean isAdmin()
rendered="#{user.groupName == 'admin'}" // getter = public String getGroupName()
rendered="#{user.groupId > 1}" // getter = public int getGroupId()
rendered="#{fn:contains(user.groups, 'admin')}" // getter = public String[] getGroups() or public List<String> getGroups()
etc..I think it's after all just a matter of learning about the capabilities of EL a bit more.

Back bean access entityImpl file?

Hello Guru,
Just a quick question:
Can I use back beans to access entityImpl java file?
--If yes, how to initiate the entityImpl file, I assue EntityImpl entity= new EntityImpl() is not the right option.
--If no, what's the work around?
thanks.

That's a nice demonstration of how to get a DBTransaction object (presumably to execute some straight JDBC code) from your backing bean without a discussion of when doing that is a good idea (i.e., nearly never - database code belongs in the model layer, not in the view layer). Without a clear description of what the OP is trying to do, I don't think anyone can give a reasonable solution, other than a guess. However, I can say that doing JDBC calls in your backing bean is generally "frowned upon" as it breaks the MVC separation of concerns principle. If you need to do a JDBC call, put it in a service method in your AM and call it that way.
Best,
John

Have a backing bean in request scope; need to access parameters sent to it

I have a request scope backing bean in my app, 'projectBean'. This has a property called 'id'.
/** in request scope in faces-config.xml */
projectBean {
    id               // set by the param from the previous page
    downloadAction() // activated by commandlink, depends on id
}There is another backing bean in session scope called 'projectListingBean', which has a dataTable that lists a bunch of projectBeans. In this 'projectListingBean', I can click on any row. That row, when clicked initializes a 'id' parameter, which is then passed to the new 'projectBean'. 'projectBean' then initializes itself based on the id.
In the jsp page backed by 'projectBean', I also have a link to download something specific to that 'projectBean'. Naturally enough, I have a commandlink with actionBinding to a method in my 'projectBean', downloadXXXAction().
The problem arises because the downloadXXX() method relies on a 'id'. Remember, this id was orinigally set 2 requests back from the datatable. Since the page backed by 'projectBean' is in request scope, the id is lost, and my method call doesn't work. I tried changing the scope of 'projectBean' to session, but JSF complains that I already setting the 'id' property as a param, I can't set the whole managed bean to something 'higher' like session.
Of course, the ideal fix to this probelm would be the ability to have beans in page scope, but what other ways (hacks??) are there to get around this?

Hi, I'm posting some code snippets if it helps with understanding the problem.
faces-config.xml:

<managed-bean>
     <managed-bean-name>projectListingBean</managed-bean-name>
     <managed-bean-scope>session</managed-bean-scope>
     <managed-property>
          <property-name>projectBeans</property-name>
          <property-class>java.util.List</property-class>
          <list-entries>
               <value-class>
                    com.sun.sleuth.omcmweb.view.bean.ProjectBean
               </value-class>
          </list-entries>
     </managed-property>
</managed-bean>

<managed-bean>
     <managed-bean-name>projectBean</managed-bean-name>
     <managed-bean-class>
     </managed-bean-class>
     <managed-bean-scope>request</managed-bean-scope>
     <managed-property>
          <property-name>projectId</property-name>
          <property-class>java.lang.String</property-class>
          <value>#{param.projectId}</value>
     </managed-property>
</managed-bean>projectlsting.jsp (page backed by projectListingBean)
<h:dataTable value="#{projectListingBean.projectBeans}"
     var="projectBean" ...>
     <h:column>
          <f:facet name="header">
          </f:facet>
          <h:commandLink action="#{projectListingBean.viewProjectSUmmary}">
               <h:outputText value="#{projectBean.projectId}" />
               <f:param name="projectId" value="#{projectBean.projectId}" />
          </h:commandLink>
     </h:column>
</h:dataTable>projectsummary.jsp (page backed by request scoped projectBean)
<h:commandLink action="#{projectBean.assessmentAction}" value="..." />
...Flow:
projectlisting.jsp (projectListingBean - session) -param id passed->
projectsummary.jsp (projectBean - request) -commandLink clicked and id lost-->
projectSummary.jsp (projectBean - request)

Access AM method from backing bean - best practice

Hello,
I need to call an appModule method from a backing bean. What is better?
1. Resolve bindings.AMDataControl.dataProvider, get AM and invoke the method directly
or
2. Create method action in page definition, resolve OperationBinding from it's binding expression and execute the operationBinding
I don't need to have a button on the page for this method.
Rado

Good question Rado.
With a "flexible" framework like Oracle ADF, I also ask myself sometimes what would be the preferred approach to do things.
See also these forum threads:
- about "ADF Faces: Passing values from a managed bean to ADF BC module"
http://forums.oracle.com/forums/thread.jspa?threadID=486742
- about : "ADF Faces: getting selected row data in multi select table ..."
http://forums.oracle.com/forums/thread.jspa?threadID=503248
regards
Jan Vervecken

How to access query based view object in backing bean

Hi
I am using JDev11.1.2.1.0
I want to use the query result of query based view object in backing bean.
How can i do the same
Please Solve this
Thanks

Hi,
Assuming ADF is in the picture
1. Create a PageDef file for the page (right mouse click "Go to Page Definition")
2. In the Executable section, create an iterator for the View Object
3. In the managed bean:
BindingContext bctx = BindingContext.getCurrent();
BindingContainer bindings = bctx.getCurrentBindingsEntry();
DCIteratorBinding iter = (DCIteratorBinding ) bindings.get("name of Iterator");
iter.execute();
// ... navigate the iterator rows ...//
Frank

How to validate values from selectInputDate in backing bean

I have two selectInputDate fields, arrivalDate and departureDate.
I want to validate that arrivalDate cannot be greater than departureDate.
java.lang.ClassCastException is raised at below line in the backing bean:
Timestamp newArrivalDate = (Timestamp)newValue;
I tried to use below in the backing bean for arrivalDate validation.
import java.sql.Timestamp;
public void arrivalDateValidator(FacesContext facesContext,
UIComponent uiComponent, Object newValue) {
//The new value is passed into us
try {
Timestamp newArrivalDate = (Timestamp)newValue; --> java.lang.ClassCastException raised at this line.
//Get the Departure Date which is already bound on this screen
Timestamp departureDate =
(Timestamp)ADFUtils.getBoundAttributeValue("departureDate");
// Now compare and raise an error if the rule is broken
if (newArrivalDate.compareTo(departureDate) > 0)
throw new ValidatorException(JSFUtils.getMessageFromBundle
("Arrival Date cannot be greater than Departure Date", FacesMessage.SEVERITY_ERROR));
} catch(Exception e) {
System.out.println("Some exception raised");
e.printStackTrace();
08/12/26 13:30:08 Some exception raised
08/12/26 13:30:08 java.lang.ClassCastException
08/12/26 13:30:08      at opera.activity.view.backing.app.TestApp.arrivalDateValidator(ActivityMain.java:1524)
08/12/26 13:30:08      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
08/12/26 13:30:08      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
08/12/26 13:30:08      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
08/12/26 13:30:08      at java.lang.reflect.Method.invoke(Method.java:324)
08/12/26 13:30:08      at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:146)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXEditableValue.validateValue(UIXEditableValue.java:400)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXEditableValue.validate(UIXEditableValue.java:206)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXEditableValue._executeValidate(UIXEditableValue.java:522)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXEditableValue.processValidators(UIXEditableValue.java:302)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXShowDetail.processValidators(UIXShowDetail.java:86)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
08/12/26 13:30:08      at javax.faces.component.UIForm.processValidators(UIForm.java:190)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildrenImpl(UIXComponentBase.java:855)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.validateChildren(UIXComponentBase.java:839)
08/12/26 13:30:08      at oracle.adf.view.faces.component.UIXComponentBase.processValidators(UIXComponentBase.java:689)
08/12/26 13:30:08      at javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:932)
08/12/26 13:30:08      at javax.faces.component.UIViewRoot.processValidators(UIViewRoot.java:362)
08/12/26 13:30:08      at com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:98)
08/12/26 13:30:08      at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:245)
08/12/26 13:30:08      at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:110)
08/12/26 13:30:08      at javax.faces.webapp.FacesServlet.service(FacesServlet.java:213)
08/12/26 13:30:08      at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
08/12/26 13:30:08      at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._invokeDoFilter(AdfFacesFilterImpl.java:228)
08/12/26 13:30:08      at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._doFilterImpl(AdfFacesFilterImpl.java:197)
08/12/26 13:30:08      at oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl.doFilter(AdfFacesFilterImpl.java:123)
08/12/26 13:30:08      at oracle.adf.view.faces.webapp.AdfFacesFilter.doFilter(AdfFacesFilter.java:103)
08/12/26 13:30:08      at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
08/12/26 13:30:08      at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:162)
08/12/26 13:30:08      at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
08/12/26 13:30:08      at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
08/12/26 13:30:08      at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
08/12/26 13:30:08      at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
08/12/26 13:30:08      at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
08/12/26 13:30:08      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
08/12/26 13:30:08      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)
08/12/26 13:30:08      at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
08/12/26 13:30:08      at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
08/12/26 13:30:08      at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
08/12/26 13:30:08      at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
08/12/26 13:30:08      at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
08/12/26 13:30:08      at java.lang.Thread.run(Thread.java:534)
Can someone suggest a solution?
Thanks in advance.

Hi user:
Use the class oracle.jbo.domain.Date in the date component then is very easy using the compareTo Method (Returns -1 if DATE is less than date, 0 if DATE and date are equal (==), 1 if DATE is greater than date).
Good Luck.

Access ComponentId in Back Bean

Similar Messages

Maybe you are looking for