Collection valued bean property problem

Hi.
If I have this property:
private List<String> myList;Should I annotate it with @OneToMany etc.. ?
I mean, this is a String.... not custom Entity.

Can someone help anyway ?

Similar Messages

  • Bug/Bad docs trying to bind SelectItem to bean property of type Collection

    Hi,
    I've been trying for the best part of the morning to use a selectOneMenu tag and bind the selectItems value to a backing bean property.
    The tutorial states that:
    "The advantages of using the selectItems tag are as follows:
    You can represent the items using different data structures, including Array, Map, List, and Collection. The data structure is composed of SelectItem instances or SelectItemGroup instances."
    well I've used Map, and List (which are both covered by Collection anyway...) and they don't work. You go silently to the renderResponse phase.
    In all cases the content of my Collection typed property were javax.faces.model.SelectItem instances.
    I changed the backing bean property to be of type SelectItem[] instead and suddenly it works fine.
    It's as if the binding mechanism isn't able to handle collections?
    Is the tutorial wrong or does this just not work?
    I'm using 1.0.
    Neil

    Hi
    I have the same problem whereby my backing beans has implemented as a HashSet of attachments for a client. If this is changed to a type, List say ArrayList, everything works correctly with no errors.
    client.attachments -> contains a HashSet of attachments
    Page goes to display this list and if a Set is used then error below is thrown.
    Has anyone experienced this problem and found a solution, it would very help
    Thanks
    Glenn
    Exception :
    com.sun.facelets.tag.TagAttributeException: /C:/development/42508/apmweb/pages/client/client_notes_list.xhtml @70,53 tes
    t="${not empty note.attachments}" /C:/development/42508/apmweb/pages/client/client_notes_list.xhtml @70,53 test="${not e
    mpty note.attachments}": Bean: org.hibernate.collection.PersistentSortedSet, property: 0
    at com.sun.facelets.tag.TagAttribute.getObject(TagAttribute.java:235)
    at com.sun.facelets.tag.TagAttribute.getBoolean(TagAttribute.java:79)
    at com.sun.facelets.tag.jstl.core.IfHandler.apply(IfHandler.java:49)
    at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
    at com.sun.facelets.tag.jstl.core.ForEachHandler.apply(ForEachHandler.java:168)
    at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
    at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:147)
    at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
    at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:147)
    at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:147)
    at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
    at com.sun.facelets.tag.jsf.core.ViewHandler.apply(ViewHandler.java:94)
    at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
    at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
    at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
    at com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95)
    at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:400)
    at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:434)
    at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:352)
    at javax.faces.webapp.FacesServlet.service(FacesServlet.java:107)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:214)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:120)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at org.apache.myfaces.component.html.util.ExtensionsFilter.doFilter(ExtensionsFilter.java:122)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3020)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1925)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1848)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1288)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    Caused by: javax.el.PropertyNotFoundException: /C:/development/42508/apmweb/pages/client/client_notes_list.xhtml @70,53
    test="${not empty note.attachments}": Bean: org.hibernate.collection.PersistentSortedSet, property: 0
    at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:73)
    at com.sun.facelets.tag.TagAttribute.getObject(TagAttribute.jav
    Code :
    <c:forEach items="#{WriteableClient.notes}" var="note">          
    <c:if test="#{not empty note.attachments}">
    </c:forEach >

  • Problems setting managed bean property of type Integer

    I got a problem when I use valueBinding #{param.productId} in faces-config.xml for my managed bean:
    My property 'productId' in bean Product is of type Integer, and my bean is in request scope. When I try to invoke some action on page, wich should navigate me to another view - JSF is trying to set productId for current view, and of course it is empty (""), and for the reasons given above I'm getting an error:
    javax.faces.FacesException: Can't set managed bean property: 'applicationId'.
    at com.sun.faces.config.ManagedBeanFactory.setPropertiesIntoBean(ManagedBeanFactory.java:576)
    at com.sun.faces.config.ManagedBeanFactory.newInstance(ManagedBeanFactory.java:233)
    at com.sun.faces.application.ApplicationAssociate.createAndMaybeStoreManagedBeans(ApplicationAssociate.java:256)
    ... 60 more
    Caused by: java.lang.NumberFormatException: For input string: ""
    at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
    at java.lang.Integer.parseInt(Integer.java:489)
    at java.lang.Integer.<init>(Integer.java:609)
    at com.sun.faces.config.ManagedBeanFactory.getConvertedValueConsideringPrimitives(ManagedBeanFactory.java:855)
    at com.sun.faces.config.ManagedBeanFactory.setPropertiesIntoBean(ManagedBeanFactory.java:555)
    Should I use requestScope instead of param to have my parameter null, and not "" ?
    If so, how should I pass requestScope parameter using commandLink?

    Hi! I have a problem with setting params too. Probably my one is different.
    I have a jsp page which show a datatable, where I can see a row for each Product. If I click on its name I would navigate to another page that shows product informations, as several ecommerce sites do.
    But I can't understand what and how I must set to inform the details page on which product have to show.
    I read in this forum that it's possible to set a parameter in productBean, and then the constructor of product bean loads others fields knowing its id.
    The snippet of my faces-config.xml is:
      <managed-bean>
        <managed-bean-name>product</managed-bean-name>
        <managed-bean-class>test.backing.ProductBean</managed-bean-class>
        <managed-bean-scope>request</managed-bean-scope>
        <managed-property>
          <property-name>idToLoad</property-name>
          <property-class>java.lang.Integer</property-class>
          <value>#{param.id}</value>
        </managed-property>
      </managed-bean>It is possible? is a correct solution? and if it is, how can I do that?
    Thanks very much if someone can resolve my problem.
    Claudio.

  • Comparing value of bean property/textbox in a form to a field in the db

    How do I compare the value of a bean property or the value of a textbox in a form (e.g. idno) to the value of an idno stored in my database using an SQL statement?
    I actually know that my SQL statement should resemble something similar to the one shown below:
    "SELECT * from user WHERE idno(value in the db) = idno(value entered in the form)"
    My problem is I am placing this SELECT statement on a .java file so I am clueless as to how I will state, using an SQL statement, that I only want to retrieve the record whose idno in the db matches the idno entered by the user in the form (whose value I store in a bean that is also inside the .java file I mentioned earlier).
    Should I place my SQL statement in the .java file or should I place it on my jsp instead?
    Any advice will greatly be appreciated! Thanks in advance!

    Hi
    Details:
    JSP - Contains a Form for entering ID number.
    Java Bean - Stores the ID number entered into the Form of the JSP page and also has the SQL Statement Object
    The Problem: Where should you put the SQL Statement Object ?
    Possible Solution: I think you are confused about SQL statements execution. This is what you can do. The Retrieved Id number from the Form has to be appended to the preformatted String which has the SQL statement stored in it. Once this is done this statement may be executed to retrieve the data associated with the ID number , if it exists.
    Here is a link that should help you build an SQL statement on the fly and execute it. Try out some of the examples.
    http://java.sun.com/docs/books/tutorial/jdbc/
    Good Luck!
    Eshwar Rao
    Developer Technical Support
    Sun mcirosystems inc
    http://www.sun.com/developers/support

  • Can't set managed bean property:

    Hi,
    I am trying to experiment with JSF and I am extending an example I downloaded from the web. When I added a new secret field and extened the bean. I get the following error. I trying to resolve this problem from two days , cant figure out why I get this exception. I tried changed the property name I still get the same error. It is something to do with the bean, I am not sure why its not able to set the property, I know that the get and set methods exist in the class file. Any help would be greatly appreciated . I have pasted the bean file, faces-config.xml, and the inputname.jsp file below. Thanks a lot.
    HTTP Status 500 -
    type Exception report
    message
    description The server encountered an internal error () that prevented it from fulfilling this request.
    exception
    org.apache.jasper.JasperException: javax.faces.FacesException: javax.faces.FacesException: Can't set managed bean property: 'word'.
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:254)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:432)
         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:356)
         at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)
         at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:147)
         at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
         at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
         at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:432)
         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:356)
         at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:430)
         at org.apache.jsp.index_jsp._jspService(index_jsp.java:48)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.invoke(JBossSecurityMgrRealm.java:220)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.jboss.web.tomcat.tc4.statistics.ContainerStatsValve.invoke(ContainerStatsValve.java:76)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2417)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:65)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:577)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:197)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:781)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:549)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:605)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:677)
         at java.lang.Thread.run(Thread.java:536)
    root cause
    javax.servlet.ServletException: javax.faces.FacesException: javax.faces.FacesException: Can't set managed bean property: 'word'.
         at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:531)
         at org.apache.jsp.inputname_jsp._jspService(inputname_jsp.java:94)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:432)
         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:356)
         at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)
         at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:147)
         at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
         at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
         at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:432)
         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:356)
         at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:430)
         at org.apache.jsp.index_jsp._jspService(index_jsp.java:48)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.invoke(JBossSecurityMgrRealm.java:220)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.jboss.web.tomcat.tc4.statistics.ContainerStatsValve.invoke(ContainerStatsValve.java:76)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2417)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:65)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:577)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:197)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:781)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:549)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:605)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:677)
         at java.lang.Thread.run(Thread.java:536)
    My JSP file is
    <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
    <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
    <f:loadBundle basename="demo.bundle.Messages" var="Message"/>
    <HTML>
    <HEAD> <title>Input Name Page</title> </HEAD>
    <body bgcolor="white">
         <f:view>
              <h1><h:outputText value="#{Message.inputname_header}"/></h1>
              <h:messages style="color: red"/>
         <h:form id="helloForm" >
              <h:outputText value="#{Message.prompt}"/>
              <h:inputText id="userName" value="#{GetNameBean.userName}" required="true">
                   <f:validateLength minimum="2" maximum="10"/>
              </h:inputText>
              <h:inputSecret id="word" value="#{GetNameBean.word}" required="true">
                   <f:validateLength minimum="2" maximum="10"/>
              </h:inputSecret>
              <h:commandButton id="submit" action="sayhello" value="Say Hello" />
         </h:form>
    </f:view>
    </HTML>
    My faces-config.xml is as follow
    <?xml version="1.0"?>
    <!DOCTYPE faces-config PUBLIC
    "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
    "http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
    <faces-config>
    <navigation-rule>
    <from-view-id>/inputname.jsp</from-view-id>
    <navigation-case>
    <to-view-id>/greeting.jsp</to-view-id>
    </navigation-case>
    </navigation-rule>
    <managed-bean>
    <description>
    Input Value Holder
    </description>
    <managed-bean-name>GetNameBean</managed-bean-name>
    <managed-bean-class>demo.GetNameBean</managed-bean-class>
    <managed-bean-scope>session</managed-bean-scope>
    <managed-property>
    <property-name>userName</property-name>
    <property-class>java.lang.String</property-class>
    <value></value>
         </managed-property>
         <managed-property>
    <property-name>word</property-name>
         <property-class>java.lang.String</property-class>
         <value></value>
         </managed-property>
    </managed-bean>
    </faces-config>
    My bean file is as follows GetNameBean.java
    package demo;
    * @author Sergey Smirnov. Exadel, Inc.
    public class GetNameBean {
    private String userName;
    private String word;
    * @return User Name
    public String getUserName() {
    return userName;
    * @param User Name
    public void setUserName(String name) {
    this.userName = name;
    * @return Password
    public String getWord() {
    return word;
    * @param Password
    public void setWord(String word) {
    this.word = word;

    Hello,
    Thanks for the reply. I used Camelcase, but its giving me the same error. I am also posting my bean files and jsp files for your reference.
    type Exception report
    message
    description The server encountered an internal error () that prevented it from fulfilling this request.
    exception
    javax.servlet.ServletException: org.apache.jasper.JasperException: javax.faces.FacesException: javax.faces.FacesException: Can't set managed bean property: 'UserName'.
         javax.faces.webapp.FacesServlet.service(FacesServlet.java:121)
         org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
    root cause
    javax.faces.FacesException: org.apache.jasper.JasperException: javax.faces.FacesException: javax.faces.FacesException: Can't set managed bean property: 'UserName'.
         com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:327)
         com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:147)
         com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
         com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
         com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
         javax.faces.webapp.FacesServlet.service(FacesServlet.java:107)
         org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
    note The full stack trace of the root cause is available in the Apache Tomcat/5.5.20 logs.
    LOGIN.JSP file
    <%@ taglib prefix="f" uri="http://java.sun.com/jsf/core" %>
    <%@ taglib prefix="h" uri="http://java.sun.com/jsf/html" %>
    <f:view>
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
    <html>
    <f:verbatim escape="false">
    <head>
    <title>My JSP 'login.jsp' starting page</title>
         <meta http-equiv="pragma" content="no-cache">
         <meta http-equiv="cache-control" content="no-cache">
         <meta http-equiv="expires" content="0">
         <meta http-equiv="keywords" content="keyword1,keyword2,keyword3">
         <meta http-equiv="description" content="This is my page">
         <!--
         <link rel="stylesheet" type="text/css" href="styles.css">
         -->
    </head>
    </f:verbatim>
    <body>
    <h:form rendered="true" id="loginform">
    <f:verbatim escape="false"><br><br> </f:verbatim>
    <h:outputLabel for="userName" rendered="true"></h:outputLabel>
    <h:inputText id="userName" required="true" rendered="true" value="#{UserBean.userName}"></h:inputText>
    <f:verbatim escape="false"><br> </f:verbatim>
    <h:outputLabel for="password" rendered="true"></h:outputLabel>
    <h:inputSecret id="password" redisplay="false" required="true" rendered="true" value="#{UserBean.password}"></h:inputSecret>
    <h:commandButton id="submit" action="#{UserBean.loginUser}" rendered="true" value=" Submit"></h:commandButton><br><br></h:form>
    </body>
    </html>
    </f:view>
    UserBean file
    package com.jsfdemo.bean;
    import javax.faces.application.FacesMessage;
    import javax.faces.context.FacesContext;
    * @author ExterroAdmin
    public final class UserBean extends Object
         private String password;
         private String userName;
         public UserBean()
              super();
         public String getPassword()
              return password;
         public void setPassword(String password)
              this.password = password;
         public String getUserName()
              return userName;
         public void setUserName(String userName)
              this.userName = userName;
         public String loginUser() {
    if("myeclipse".equals(getUserName()) && "myeclipse".equals(getPassword()))
    return "success";
    FacesContext facesContext = FacesContext.getCurrentInstance();
    FacesMessage facesMessage = new FacesMessage(
    "You have entered an invalid user name and/or password");
    facesContext.addMessage("loginForm", facesMessage);
    return "failure";
    If you need any more information, please let me know

  • Output text show Null when access value through property inspector in ADF

    Hi,
    we declare two UIComponents one is Deptno which is InputComboBoxListofValues and othre is Dname as output text.
    we create ManagedBean called "deptBean"(which is in BackingBeanScope) and create a method inside bean "deptnoChanged".
    ValueChangeListener of Deptno pointing to deptnoChanged method of deptBean.
    Inside deptBean we declare a variable private String departmentName which are having setter and getters.
    we can Initialize departmentName based on valueChangeEvent in bean level
    for example:
    if (deptno=10)
    setdepartmentName("Accounts");
    else
    setdepartmentName("Sales");
    Now we Can Access the Value of departmentName.
    The UIComponent(output text field) such as Dname in JSP Page we set value (in property Inspector)
    _#{backingBeanScope.deptBean.departmentName}_
    when we execte the JSP Page Dname show Null as output. but output we expect as Accounts or Sales only.
    Please help us, how to resolve the problem
    Thanks,
    kumar.

    when we execte the JSP Page Dname show Null as output. but output we expect as Accounts or Sales only.The value to be got while debugging should be via EL expressions and stored somewhere.
    If the value Dname is bound to the backing bean then you can view its value in the property inspector using
    #{<BeanScope>.<BeanName>.value} or the like

  • Including Bean-Property in Database-Binding

    Hello,
    I'm testing SJSC and right now I'm testing the Database-Bindings. I was successfull in integrating the MySQL JDBC-driver and creating JNDI-Ressource, JDBC-Ressource and Connection-Pool (I have several "RaveGenerated entrys but this problem will be solved later hopefully).
    My question is how I can integrate the value of a managed Bean in a SQL-Query of a Rowset. n my own Example I have a page where I enter a Short name in an Input-Field. This field is bound to a manged Bean and the name is a Property. I press a Okay-Button and on the next Page I display this Property again. This works finde. Now I will lookup in a database the long name corresponding to the short Name. I bound the Output-Field to a Rowset and the first long name is displayed from the database. I would like to display the long Name of the DB-Column of the entered short name. How can I do that?
    Best regards,
    Thomas

    Does your DbAccess bean have a "setJdbcUser" method?
    ie public void setJdbcUser(String user)Yes. Wouldn't the 'setProperty" tag cause compilation to fail if there was not a corresponding bean property?
    I'll add the standard disclaimer how db connections
    in JSPs is a bad idea. Such code should be in a servlet/bean.I have created context parameters in web.xml with the jdbc configuration values to create the connection. I created a context listener to open the connection on application initialization. My original conception was to create the connection in my controller servlet and then pass it as a request attribute and fetch it in the JSP. But, on further consideration, I could not find a way to do that without using a scriptlet. For that reason, I backtracked and created the DbAccess bean, whose purpose actually is to create the connection. So, the business with the jdbcUser property is really just me "feeling my way" with how these tags work in the JSP. I'm having difficulty in visualizing how to access that connection (or the data feed) in the JSP. I can create the DbAccess object with the JDBC connection in the listener.
    I am certainly open to suggestions as to the best way to make this work. I haven't found much guidance in the documentation I've read.
    Thanks for the reply.
    mp

  • ADFC bean property

    I am having problems settings a bean property in adfc-config.xml and getting the value in the bean class. When I access the property in the java bean, it has not been set, altho I have a value in adfc-config.
    Here are my code details:
    <adfc-config xmlns="http://xmlns.oracle.com/adf/controller" version="1.2">
    <managed-bean>
    <managed-bean-name>agProperties</managed-bean-name>
    <managed-bean-class>oracle.bpel.activityguide.ui.beans.model.AGProperties</managed-bean-class>
    <managed-bean-scope>session</managed-bean-scope>
    <managed-property>
    <property-name>filename</property-name>
    <value>/scratch/cshare/cshare_eventpoc/atgpf/applcore/activityguide/activityguideApps/AGNonUIshellApp/ViewController/activityguide.properties</value>
    </managed-property>
    </managed-bean>
    </adfc-config>
    Java bean:
    package oracle.bpel.activityguide.ui.beans.model;
    public class AGProperties {
    private static String _AGPropertyFilename = "";
    public AGProperties() {
    /** this is set in adfc-config.xml
    * explicit path +filename
    public void setFilename(String filename) {
    _AGPropertyFilename = filename;
    public static void load() {
    propFileName = _AGPropertyFilename;  ///HERE THIS IS NOT SET from adfc-config.xml
    }

    Thanks for the quick response.
    I removed all static definitions from the java and changed the managed bean scope to "application",
    However it is still not getting the value set from adfc-config. (BTW: previously we were using a JAVA_OPTIONS parm on the application cmdline for the filepath and getting that thru the system settings in java code and it worked fine but we were told to use the adfc-config.xml instead for the file path info .)
    Maybe some of the details are the cause of the problem. The managed bean is in a deployed jar file. The application page is in a separately deployed workspace. I've set the managed bean info the adfc-config.xml of the application. (When I also had it in the jar file's adfc-config.xml the log complained of a duplicately defined managed bean, so I removed it from the jar's adfc-config file. )
    When the AGProperty.getProperty method is called, the managed bean property setFilename for AGProperties has still not been called & set yet with adfc-config value. I have set breakpoints in a debug session to verify this. These properties as used for EL values on the initally rendered jsf page fragment, which is included in a region as a task-flow on the main page.
    Is there another way to load this bean managed property directly in Java code from the adfc-config file ? Or iIs there another way to set a filepath for the properties file specific to the application other than using adfc-config.xml ?
    revised Java code:
    public class AGProperties {
    private String _AGPropertyFilename = "";
    public AGProperties() {
    /** this is set in adfc-config.xml
    * explicit path +filename
    public void setFilename(String filename) {  //never getting called
    _AGPropertyFilename = filename;
    adfc-config.xml
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <adfc-config xmlns="http://xmlns.oracle.com/adf/controller" version="1.2">
    <managed-bean>
    <managed-bean-name>agProperties</managed-bean-name>
    <managed-bean-class>oracle.bpel.activityguide.ui.beans.model.AGProperties</managed-bean-class>
    <managed-bean-scope>application</managed-bean-scope>
    <managed-property>
    <property-name>filename</property-name>
    <value>/scratch/cshare/cshare_eventpoc/atgpf/applcore/activityguide/activityguideApps/AGNonUIshellApp/ViewController/activityguide.properties</value>
    </managed-property>
    </managed-bean>
    </adfc-config>
    Edited by: user568107 on Feb 17, 2009 3:20 PM
    Edited by: user568107 on Feb 17, 2009 4:37 PM

  • How to read and update the value of property file

    Hi,
    I am not able read the values from property file.
    Please tell me how to read and update the values from property file using Properties class
    This is my property file : - Config.properties its located in D:\newfolder
    Values
    SMTP = localhost
    Now i need to change the value of the SMTP
    New value :
    SMTP =10.60.1.9
    Pls Help me
    Thanks
    Merlin Rosina,

    Post a small (<1 page) example program that forum members can copy and run that demonstrates your problem.

  • Portal runtime error: Cannot access bean property

    Dear all,
    Does anybody have a clue what problem might couse the <b>Portal Runtime Error</b> described below?
    It does seem to occur when a second user wants to access the <b>Component</b>.
    <b>Portal Runtime Error</b>
    An exception occurred while processing a request for :
    iView : pcd:portal_content/com.xxxxx.luminaires/com.xxxx.iviews/Quotations/EasyQuote
    <b>Component</b> Name : EasyQuoteDemo.EasyQuoteComponent
    Tag tableView attribute model: Cannot access bean property quotationHeader.CurrentTableModel in page context.
    Exception id: 04:50_21/09/04_0070
    See the details for the exception ID in the log file
    Thxs in advance
    Joost

    Hi Dominik,
    Having a closer look at the problem, we found it is not the number of users.
    It seems our JAVA components keeps the conenctions with SAP open and reopens a new one every time we start the component.
    If we finished solving the problem, I will publish the solution.
    Greetings,
    Joost

  • JSF/Spring integration - managed-property problem

    I am using JSF 1.1_01 (MyFaces 1.1), Spring 1.2, Ajax4Jsf.
    The JSF application has h:selectOneMenu .
    On change event of h:selectOneMenu sets "selectedValue" into backing bean as shown below:
    page.jsp
    <h:selectOneMenu value="#{test.selectedDevice}" >
    <f:selectItem itemValue="0" itemLabel="--New--"/>
    <f:selectItem itemValue="1" itemLabel="WorkStation"/>
    <f:selectItem itemValue="2" itemLabel="Router"/>
    <f:selectItem itemValue="3" itemLabel="Switch"/>
    <ajax:support action="#{test.loadDevice}" event="onchange" reRender="t2,t3,t4,t5"/>
    </h:selectOneMenu>
    TestBean.java (Backing Bean)
    public String getSelectedDevice() {
    logger.info(" *** In getSelectedDevice *** ");
    if (selectedDevice == null) {
    selectedDevice = "0"; // This will be the default selected item.
    return selectedDevice;
    public void setSelectedDevice(String selectedDevice) {
    logger.info(" *** In setSelectedDevice *** ");
    this.selectedDevice = selectedDevice;
    Here are the configuration file snippets for integrating JSF Spring
    web.xml
    <listener>
    <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
    </listener>
    <context-param>
    <param-name>contextConfigLocation</param-name>
    <param-value>/WEB-INF/applicationContext.xml</param-value>
    </context-param>
    faces-config.xml
    <application>
    <variable-resolver>org.springframework.web.jsf.DelegatingVariableResolver</variable-resolver>
    </application>
    <managed-bean>
    <managed-bean-name>test</managed-bean-name>
    <managed-bean-class>test.TestBean</managed-bean-class>
    <managed-bean-scope>request</managed-bean-scope>
    <managed-property>
    <property-name>deviceManager</property-name>
    <property-class> test.DeviceTypeManager </property-class>
    <value>#{deviceManager}</value>
    </managed-property>
    </managed-bean>
    The above code results in the following error
    javax.faces.FacesException: Cannot get value for expression '#{test.selectedDevice}'
    The error occurs only if i include <managed-property> inside the <managed-bean> in faces-config.xml.
    The moment i remove <managed-property> from face-config.xml the error disappears & page gets rendered properly.
    The purpose in having <managed-property> inside managed-bean is to call Spring's Manager class (i.e. deviceManager) from JSF application
    Any pointers/suggestions in resolving the error will be highly appreciated
    Regards
    Bansi

    The TestBean have a property for DeviceManager along with setter/getter methods as shown below. Sorry for not including in earlier posting
    TestBean.java (Backing Bean)
    private DeviceTypeManager deviceManager;
    public DeviceTypeManager getDeviceManager() {
         return deviceManager;
    public void setDeviceManager(DeviceTypeManager deviceManager) {
         this.deviceManager = deviceManager;
    Here are the two scenarios
    Scenario 1 : without <managed-property> the code works fine
    Scenario 2 : with <managed-property> the code results in following error
    javax.faces.FacesException: Cannot get value for expression '#{test.selectedDevice}'
    Scenario 1 has only JSF whereas Scenario 2 has JSF-Spring integration
    The Scenario 1 works absolutely fine as the expression '#{test.selectedDevice}' gets its value from setter/getter method in the backing bean(TestBean.java) . This is expected behaviour & wondering why it doesn't work similarly in Scenario 2 instead it complains
    Cannot get value for expression '#{test.selectedDevice}'
    I am willing to upload the war file. Any pointers/suggestions in resolving the error will be highly appreciated
    Regards
    Bansi

  • Getting error after when trying to print managed session bean property.

    Hi All,
    I am reading a file from my local machine. After reading a file , i am storing file details in the property of the same bean.
    After that i am trying to preint contents of that file in one jsp by accessing that stored managed bean property.
    But I am getting following error:
    Nov 15, 2009 2:33:41 PM com.sun.faces.lifecycle.LifecycleImpl phase
    WARNING: executePhase(RENDER_RESPONSE 6,com.sun.faces.context.FacesContextImpl@138c63) threw exception
    javax.faces.FacesException
         at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:135)
         at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
         at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
         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(Unknown Source)
    Caused by: ClientAbortException:  java.net.SocketException: Connection reset by peer: socket write error
         at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:319)
         at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:288)
         at org.apache.catalina.connector.Response.flushBuffer(Response.java:548)
         at org.apache.catalina.connector.ResponseFacade.flushBuffer(ResponseFacade.java:279)
         at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:201)
         at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106)
         ... 15 more
    Caused by: java.net.SocketException: Connection reset by peer: socket write error
         at java.net.SocketOutputStream.socketWrite0(Native Method)
         at java.net.SocketOutputStream.socketWrite(Unknown Source)
         at java.net.SocketOutputStream.write(Unknown Source)
         at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:740)
         at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434)
         at org.apache.coyote.http11.InternalOutputBuffer.flush(InternalOutputBuffer.java:299)
         at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:973)
         at org.apache.coyote.Response.action(Response.java:183)
         at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:314)
         ... 20 more
    Nov 15, 2009 2:33:41 PM org.apache.catalina.core.StandardWrapperValve invoke
    SEVERE: Servlet.service() for servlet Faces Servlet threw exception
    java.net.SocketException: Connection reset by peer: socket write error
         at java.net.SocketOutputStream.socketWrite0(Native Method)
         at java.net.SocketOutputStream.socketWrite(Unknown Source)
         at java.net.SocketOutputStream.write(Unknown Source)
         at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:740)
         at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434)
         at org.apache.coyote.http11.InternalOutputBuffer.flush(InternalOutputBuffer.java:299)
         at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:973)
         at org.apache.coyote.Response.action(Response.java:183)
         at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:314)
         at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:288)
         at org.apache.catalina.connector.Response.flushBuffer(Response.java:548)
         at org.apache.catalina.connector.ResponseFacade.flushBuffer(ResponseFacade.java:279)
         at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:201)
         at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106)
         at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
         at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
         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(Unknown Source)There is no specific reason mentioned for this error. Anyone has faced this problem before?
    Whats wrong here?

    Hi gimbal2,
    I haven't deployed the project yet. I am still in development phase. I am using eclipse. So i am using inbuilt browser from eclipse only.
    I saw this post on the same forum:
    http://forums.sun.com/thread.jspa?threadID=5297862
    This person had the same problem. But his question is not answered yet.
    People here are saying:
    *1)page is getting submitted more than once. Either because the user is clicking on the commandbuttons/links multiple times or through some other event.*
    ->I am not using any javascript. But problem here is whenever i try to load file from my local machine, in first attempt it wont proceed. I need to load file twice or thrice. Is it some problem?
    But one thing to note here is that i am not getting exception after loading the file. I am getting exception after reading the file in managed bean and returning from it with some status.
    *2)This exception can be caused by the browser closing its end of the socket for any number of reasons (user presses stop loading button, clicks another link, closes the browser window, etc.):*
    ->I am not pressing any button or doing any activity once i load the file.
    *3)Sounds like it should be caught and ignored since these are normal user actions. I was just concerned it might be causing some kind of impact that we don't know about.*
    ->I can't ignore it because, my next JSP is not getting loaded after i return from the read file bean.
    Hope People here can help me solve this problem. I am not able to proceed :(

  • How to get a collection of beans using web services

    Hi,
    I'm new to SOAP and Web Services I'd like to know whether the following is possible
    or not.
    I've created an EJB with this business interface:
    public interface Users implements EJBObject {
    public User[] getUsers( ) ...
    Where the User object is a bean with some properties:
    public User implements Serializable {
    public void setName( ... ) ...
    public String getName( ) ...
    public void setAddress( ... ) ...
    public String getAdress( ) ...
    I've create the ejb-jar.xml and weblogic-ejb-jar.xml that contain the definition
    of my EJB and then I try to deploy the web services using the ant task 'wsgen'.
    I get the following exception:
    org.xml.sax.SAXException: Could not find a codec that understood how to convert
    class [LUser; using http://schemas.xmlsoap.org/soap/encoding/
    : [ CodecFactory: http://xml.apache.org/xml-soap/literalxml=null, http://schemas.xmlsoap.org/soap/encoding/=null,
    =null]
    Can someone help to resolve this ? Also, I'd like to know if it's possible that
    a web service return a collection of beans as shown above ?
    Thanks for your help.
    Ludovic.

    Java beans are serialized/deserialized by the soap encoding codec
    itself. you dont have to write custom encoders. I think the error
    is because you dont have the java bean class on the server side.
    Java bean class file should be in the classpath or it should be
    added to the ejb jar file.
    thanks,
    -manoj
    Ludovic Deravet wrote:
    Thanks for your help. Indeed, that was my problem.
    But now I'm facing this one:
    [SOAPException: faultCode=SOAP-ENV:Client; msg=No Deserializer found to
    deserialize a 'urn:local:ns0:return' using encoding style 'http://sch
    emas.xmlsoap.org/soap/encoding/'.;
    targetException=java.lang.IllegalArgumentException: No Deserializer found to
    deserialize a 'urn:local:ns0:
    return' using encoding style 'http://schemas.xmlsoap.org/soap/encoding/'.]
    at org.apache.soap.rpc.Call.invoke(Call.java:246)
    at com.webservices.WSClient.main(WSClient.java:38)
    Did you implement your own deserializer to read your array of beans (called
    Data) ? Or do I need to do something else ?
    Thanks.
    Ludovic.
    "manoj cheenath" <[email protected]> wrote in message
    news:[email protected]...
    You can do this. I guess, the problem is because you have
    not defined a package for the bean.
    Try something like:
    package foo.bar;
    class User{
    I am attaching an example.
    -manoj
    Ludovic Deravet wrote:
    Hi,
    I'm new to SOAP and Web Services I'd like to know whether the following
    is possible
    or not.
    I've created an EJB with this business interface:
    public interface Users implements EJBObject {
    public User[] getUsers( ) ...
    Where the User object is a bean with some properties:
    public User implements Serializable {
    public void setName( ... ) ...
    public String getName( ) ...
    public void setAddress( ... ) ...
    public String getAdress( ) ...
    I've create the ejb-jar.xml and weblogic-ejb-jar.xml that contain thedefinition
    of my EJB and then I try to deploy the web services using the ant task'wsgen'.
    I get the following exception:
    org.xml.sax.SAXException: Could not find a codec that understood how toconvert
    class [LUser; using http://schemas.xmlsoap.org/soap/encoding/
    : [ CodecFactory: http://xml.apache.org/xml-soap/literalxml=null,
    http://schemas.xmlsoap.org/soap/encoding/=null,> > > =null
    Can someone help to resolve this ? Also, I'd like to know if it's
    possible that
    a web service return a collection of beans as shown above ?
    Thanks for your help.
    Ludovic.

  • Compares single value content property to single value property

    Hi,
    I am using WLPS 3.2 with weblogic apps 5.1.
    This is when regarding content selection rules. When u go into the rules
    management and try to create a content selection rule : Then display content
    based on:
    we see 3 templates to choose from. Now if u look at template 2 it says
    :Value with Property Example
    This template compares a single-value content property to another
    single-value property. content.investor_type equals user.investor_type
    It says this template compares "single value" content property to another
    "single-value property". What i did was set up a rule that comared a single
    value content property to a "multiple" value user property (i.e. the user
    property was allowed to have multiple values-check boxes). The rule was set
    up fine. When i ran the rule with the <pz:contentselector> tag it dint
    return the desired content object. Now if i set up the same rule to match a
    single valued user property then it worked!!! Could you please let me know
    why this happens and is this a limitation of the tool. What is an
    alternative solution for me to compare a content property to a multi valued
    user property.
    Thanks,
    --Kapil

    Hi Kapil,
    You're correct on all counts. This workaround does move the content
    selection into the JSP, rather than using a rule -- which is not ideal.
    Also, your suggestion to build one query string to cut down on the number of
    database calls is a good improvement.
    - Ginny
    "kapil khanna" <[email protected]> wrote in message
    news:[email protected]...
    Hi Ginny,
    I really appreciate ur response. This work around was not knew to me. Iwas
    expecting a better work around from some reasons:
    i) The definition of this rule is hard coded and not administered thu the
    tools interface.
    ii) There are multiple database calls for each property value retrieved
    every time the <cm:select> tag is executed which is very expensive.
    iii) The query that i build for the <cm:select> or <pz:contentQuery> tag
    doesnt support the in statement.
    My work around was something like this:
    Build the query string first which would look something like this
    CONTENT.interest like '*Science*' || CONTENT.interest like '*Astronomy*'
    Then run the <cm:select> or <pz:contentQuery> tag so that i have only one
    database call.
    Considering the user has 2 interests chosen Science and astronomy. I usethe
    like so that CONTENT can be tagged to accomodate multiple values which is
    very possible in a real life situation. For eg: <meta name="interest"
    content="Science,Astronomy" >
    Is this a better work around or am i totally out of line.
    Thanks for your help and time
    --Kapil
    "Ginny Peterson" <[email protected]> wrote in message
    news:[email protected]...
    Hi Kapil,
    Yes -- this is a limitation with the phrase templates. The "Value with
    Property" phrase template compares a single-value content property to
    another single-value property. What's key here (and often overlooked)
    is
    that fact that the property you're using must be a single-valueproperty.
    >>
    There is a workaround using the <cm:select> tag rather than the <pz>tags.
    Basically, it involves getting a list of the values for yourmultiple-value
    property, and iterating over that list, selecting the content for each
    of
    the items in the list.
    Here's some sample code. Assume you have a text, multiple, unrestricted
    property called "MyInterests" in property set "TestPropertySet"; a user
    might have values like this: "Science, Astronomy, Cooking".
    <%@ page extends="com.beasys.commerce.axiom.p13n.jsp.P13NJspBase"%>
    <%@ page import="com.beasys.commerce.content.ContentHelper"%>
    <%@ taglib uri="es.tld" prefix="es" %>
    <%@ taglib uri="cm.tld" prefix="cm" %>
    <%@ taglib uri="um.tld" prefix="um" %>
    <!-- Get the user and group names -->
    <%
    String userName = (String)getSessionValue(SERVICEMANAGER_USER,request);
    String groupName = (String)getSessionValue(SERVICEMANAGER_SUCCESSOR,
    request);
    %>
    <!-- Get the profile for the user -->
    <%
    // Check to see if logged in, then getProfile for the user with groupas
    successor
    if(getLoggedIn(request))
    %>
    <um:getProfile scope="session" profileKey="<%= userName %>"
    successorKey="<%= groupName %>" />
    <%
    else // use the default profile for the group
    %>
    <um:getProfile scope="session" profileKey="<%= groupName %>"
    groupOnly="true" />
    <%
    %>
    <!-- Get the property value for the user -->
    <um:getProperty id="areas" propertySet="TestPropertySet"
    propertyName="MyInterests" />
    <br><br>Interests for <%= userName %>:
    <%
    // Multi-valued properties are retrieved as an ArrayList, so cast to a
    Collection so we can iterate through
    Collection c = (Collection)areas;
    String queryString;
    Iterator i = c.iterator();
    while(i.hasNext())
    String nextVal = (String)i.next();
    queryString = "CONTENT.interests == '" + nextVal + "'";
    %>
    <cm:select contentHome="<%= ContentHelper.DEF_CONTENT_MANAGER_HOME %>"
    query="<%= queryString %>" id="docList"/>
    <es:forEachInArray id="aDoc" array="<%= docList %>"
    type="com.beasys.commerce.axiom.content.Content">
    <li>Matched document message:
    <cm:printProperty id="aDoc" name="message" encode="html"/>
    </es:forEachInArray>
    <%
    %>
    FYI, this limitation is not present in WLCS 3.5; it's much more flexiblein
    terms of using mutli-valued properties (and multi-valued meta tags) in
    rules.
    I hope this helps!
    - Ginny
    "kapil khanna" <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    I am using WLPS 3.2 with weblogic apps 5.1.
    This is when regarding content selection rules. When u go into the
    rules
    management and try to create a content selection rule : Then displaycontent
    based on:
    we see 3 templates to choose from. Now if u look at template 2 it says
    :Value with Property Example
    This template compares a single-value content property to
    another
    single-value property. content.investor_type equalsuser.investor_type
    It says this template compares "single value" content property toanother
    "single-value property". What i did was set up a rule that comared asingle
    value content property to a "multiple" value user property (i.e. the
    user
    property was allowed to have multiple values-check boxes). The rule
    was
    set
    up fine. When i ran the rule with the <pz:contentselector> tag it dint
    return the desired content object. Now if i set up the same rule to
    match
    a
    single valued user property then it worked!!! Could you please let me
    know
    why this happens and is this a limitation of the tool. What is an
    alternative solution for me to compare a content property to a multivalued
    user property.
    Thanks,
    --Kapil

  • What is correct row bean property class?

    I'm trying to extend the WL9.0 administrative console
              and I'm tryign to use the templates provided for viewing
              table form content there. The problem is as follows:
              I define a JSP that shows a table, each row showing data
              from my own bean class 'SponsorListItem'
              --->JSP snippet
              <%@ page language="java" %>
              <%@ taglib uri="/WEB-INF/console-html.tld" prefix="wl" %>
              <%@ taglib uri="/WEB-INF/fmt.tld" prefix="fmt" %>
              <%@ taglib uri="/WEB-INF/beehive-netui-tags-template.tld" prefix="beehive-template" %>
              <fmt:setBundle basename="mgmtconsole" var="current_bundle" scope="page"/>
              <beehive-template:template templatePage="/layouts/tableBaseLayout_netui.jsp">
              <beehive-template:section name="configAreaIntroduction">
              <fmt:message key="mysoftware.mgmtconsole.sponsorlist.title" bundle="${current_bundle}"/>
              </beehive-template:section>
              <beehive-template:section name="table">
              <wl:table
              name="sponsorListForm"
              property="sponsors"
              showcheckboxes="false"
              captionEnabled="true"
              controlsEnabled="false"
              bundle="mgmtconsole"
              formEnabled="true"
              showheadings="true"
              singlechange="false">
              <wl:caption>
              <fmt:message key="mysoftware.mgmtconsole.sponsorlist.caption" bundle="${current_bundle}"/>
              </wl:caption>
              <wl:column property="sponsorName" label="mysoftware.mgmtconsole.sponsorlist.sponsorname"/>
              <wl:column property="sponsorCode" label="mysoftware.mgmtconsole.sponsorlist.sponsorcode"/>
              <wl:column property="sponsorId" label="mysoftware.mgmtconsole.sponsorlist.sponsorid"/>
              </wl:table>
              </beehive-template:section>
              </beehive-template:template>
              -->end clip
              My form bean (SponsorListForm) has function
              --->clip
              public SponsorListItem[] getSponsors() { return fArray; }
              <--end clip
              My row bean (SponsorListItem) has the following getters
              -->clip
              public String getSponsorName() { return fName; }
              public String getSponsorCode() { return fCode; }
              public String getSponsorId() { return fId; }
              public String getHandle() { return fId; }
              <--end clip
              So far so good, when I try to view the JSP in the
              mgmt console snippet I get an error:
              java.lang.ClassCastException: java.lang.String
              at com.bea.console.taglib.html.renderer.DefaultCellRenderer.doRender(DefaultCellRenderer.java:36)
              at com.bea.console.taglib.html.TableTag.printTableRows(TableTag.java:749)
              at com.bea.console.taglib.html.TableTag.printTable(TableTag.java:594)
              at com.bea.console.taglib.html.TableTag.doEndTag(TableTag.java:359)
              at jsp_servlet._mgmtconsole._jsp.__mgmtconsole2._jspService(__mgmtconsole2.java:337)
              at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
              at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:214)
              at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:120)
              If I set the getters from SponsorListItem to return null I do not get the error - instead I get the correct number of rows with empty content (naturally as I did not give any content, just nulls). So it seems that the cell renderer assumes that the property is of some class other than java.lang.String but I cannot find from the documentation what is the class it wants. If I had the source of the renderer I could go and have a look at there but naturally I do not have that...
              So, what is the correct class to return for a row bean property?

    It appears the assumed class for getHandle() in the row item bean is com.bea.console.handles.Handle which can be found from the console.jar in the server/lib/consoleapp/webapp/WEB-INF/lib.
              If I subclass this item and then make my row bean return instances of these for the getHandle() then I do not get class cast exception.

Maybe you are looking for

  • NEED HELP ITUNES FREEZES WHEN OPENED PLEASE HELP

    hello all whenever i open itunes on my macbook, the loading pinwheel comes up and doesn't go away until i quit itunes or turn off my computer. my itunes will 'freeze' whenever i open it and will not let me play songs or anything. please help me!

  • Condition type GMPP (GTM Purchase Price)

    Does anyone here have experience working with condition type GMPP? I I am working with Global Trade Contract (Links SD & MM SO with PO) and would like clarification on how GMPP is used. Is GMPP used to capture MM Purchase price, so ir can be statisti

  • Download does not start, error with order

    i've been trying to dowload lightroom 4 for more than a week. the download does not start and when i try to buy the program i get a "error with your order message" any idea what i should try next??

  • Installing Orchestrator on SCSM

    Hi, I would like to install Orchestrator for SCSM. However, I do not have a dedicated server. I have: Service Manager server DW SM server Database server Sharepoint Foundation 2010 / Self service Portal Server On which server I can install Orchestrat

  • Re: E71 gap in case body

    Opening the case or disassembling your Nokia E71 will invalidate your warranty. However, the problem that the original poster has is indeed to do with the chassis assembly at the top of the handset. The metal prongs that the handset is held together