JSF Rendering messages component

Hi All,
I am having a t:messages tag on my jsf page which displayes all the error messages
I want to make it fixed size possible by placing it in a textarea, Can i do this ?
There is an attribute layout to t:messages tag which supports table and list but is there a way to render these ?
when i set the style attribute or use the styleClass attribute it is applied only to the span tag ( which is generated by t:messages tag ) but not to either table or list, Can anyone suggest a way to do this
Do get back to me if i am not clear
Thanks in advance

While this is in no way complete, you can check out my check list for Iin my opinion) a good overview of what it takes to write a JSF component:
http://blogs.steeplesoft.com/2006/12/14/jsf-component-writing-check-list/
The Burns/Schalk book, JavaServer Faces:  The Complete Reference (http://tinyurl.com/2ndoye) is also an excellent resource. If you can be patient, you might also keep on eye on java.net, as Ken Pauslen (of JSFTemplating and GlassFish fame) and I will have an article coming out on this very topic.

Similar Messages

  • Jsf - how set text from "message component"?

    hi.
    Sorry my bad English.
    How I make to edit the errors messages of the "message component" entailed to the one text field? it is that I want the messages in Portuguese.
    thanks
    venom

    I assume that you are talking about the adf faces message component? If so, take a look at one of the SRDemo samples - both use localized strings for error messages. You can find the developer's guide and instructions for downloading the sample application that uses the same technology stack as your application does, here:
    http://www.oracle.com/technology/products/adf/learnadf.html
    Hope this helps,
    Lynn Munsinger
    JDeveloper Product Management

  • Possible to create a custom renderer for rendering standard component ?

    This is in context for creating dynamic Data tables. Is it possible to create a custom Renderer for rendering component (standard) without creating a custom component?
    namanc

    Let's assume you want to create a custom renderer which will be used to render the error-messages (the h:messages tag). The component-family in this case is: javax.faces.Messages, the renderer-type javax.faces.Messages.
    Therefor in your application's faces-config.xml add this renderer-statement (inside a render-kit, obviuosly):
    <faces-config>
      <!-- other stuff like components, managed beans, navigation-rules,... -->
      <render-kit>
        <renderer>
          <component-family>javax.faces.Messages</component-family>
          <renderer-type>javax.faces.Messages</renderer-type>
          <renderer-class>my.very.special.MessagesRenderer</renderer-class>
        </renderer>
      </render-kit>
      <!-- other renderers... -->
    </faces-config>The code for MessagesRenderer is very dependent on your needs, therefor I will not post something here. Basically you need to extend javax.faces.render.Renderer. For help in that camp, surf to the online tutorials or get yourself a book (I learned a lot from Kito Mann's "JSF in Action"). Additionally grab the source for Sun's RI AND Myfaces and dig into that java-code. There is a huge learning potential looking at that source-material.
    hth
    Alexander

  • JSF error message - retain ?

    HI all,
    i am using jsf <h:messages />. its getting cleared, if i click a commandlink which shows a popup div. That popup div is rendered in a bean.
    How to retain the error messages after getting the response.
    Samething happened when i change a select option which processes in valueChangeListener. After Changes made in Select option (getting the response) how to retain the error message ?
    Help me. Thanks in advance.
    Srinivas.R

    Thanks for ur replies.
    i am using tomahawk div (t:div) to show a
    small popup div when the user clicks a link. for
    changing Serial id (for my application) which calls
    backing bean for rendering & perform action
    regarding.
    Also when the Country select option changed, i
    am populating relavant state list in another select
    component, its internally calling backing bean. this
    also clears the error messages.
    How to retain the error messages without changing
    this business.At this point you are pretty much outside the regular functionality provided by JSF. I still think the best approach will be to eliminate the reloading of the page. You could accomplish this via AJAX. There are a few libraries out there for using AJAX with JSF; ajax4jsf for sure and I think JBoss Seam, RichFaces, ICEFaces, Trinidad and I'm sure I missed some.

  • Fatal error while rendering UI component  since we are in BI 4.1 SP2 patch 4

    Hello,
    Since we are in BI 4.1 SP2 patch 4, we have one Analysis for Olap report  which have this message : Fatal error while rendering UI component.
    This report gets 7  folders  : 5 of them gets this error message and 2 of them works well
    It's the same problem with patch 6.
    Could you please help us to find a solution ?
    I don't know how to investigate.
    Regards,
    Nicolas

    Hey Nicolas
    We are experiencing a similar error. It appears when we try to create a conditional formatting rule on one of the reports.
    Were you able to find a solution to this?
    Regards
    Antonette

  • Jsf data table component + print null cell

    I am using the jsf data table component and binding the column values to a backing bean.
    <h:dataTable binding="#{backing_showDifferences.dataTable2}"
    id="dataTable2">
    <h:column binding="#{backing_showDifferences.userColumn1}"/>
    <h:column binding="#{backing_showDifferences.userColumn2}"/>
    <h:column binding="#{backing_showDifferences.userColumn3}"/>
    </h:dataTable>
    - some code from my showDifferences.java
    HtmlOutputText column1Text = new HtmlOutputText();
    vb =
    FacesContext.getCurrentInstance().getApplication().createValueBinding("#{users.uclass}");
    column1Text.setValueBinding("value", vb);
    usercolumn1.getChildren().add(column1Text);
    HtmlOutputText column2Text = new HtmlOutputText();
    vb =
    FacesContext.getCurrentInstance().getApplication().createValueBinding("#{users.ue1}");
    column2Text.setValueBinding("value", vb);
    usercolumn2.getChildren().add(column2Text);
    HtmlOutputText column3Text = new HtmlOutputText();
    vb =
    FacesContext.getCurrentInstance().getApplication().createValueBinding("#{users.ue2}");
    column3Text.setValueBinding("value", vb);
    usercolumn3.getChildren().add(column3Text);
    ResultSetDataModel dataModel = new ResultSetDataModel();
    dataModel.setWrappedData(rs);
    dataTable2.setValue(dataModel);
    The raw HTML:
    <table id="form1:dataTable2" class="iuptable" border="1">
    <thead>
    <tr>
    <th scope="col">Heading 1</th>
    <th scope="col">Heading 2</th>
    <th scope="col">Heading3</th>
    </tr>
    </thead>
    <tbody>
    <tr>
    <td>some data in this column</td>
    <td>X</td>
    <td></td>
    </tr>
    <tr>
    <td>Some more data in this row</td>
    <td>X</td>
    <td></td>
    </tr>
    </tbody>
    </table>
    My problem is this...in the raw HTML the <td></td> tag is not formatted nicely on my table output. I have lines around my entire table and each cell within it. When the <td></td> prints there are no lines. I am new to the JSF table data component, but if I were writing some JSP or servlet code I would check that if value was null I would append an &nbsp to the <td> tag (ex. <td>&nbsp</td>) and the table would be formatted properly. The backing bean that I am binding to is pulling the data from a database table...so my sql looks like this:
    SELECT uclass, ue1, ue2 from table1; my problem is when ue1 or ue2 is a null value.
    Any ideas would be greatly appreciated!

    Hi,
    the h:dataTable belongs to the JSF Reference Implementation from Sun, not to Oracle ADF Faces. The rendering is within this component set and I suggest to report your issue on one of the SUN forums (http://forum.java.sun.com/forum.jspa?forumID=427) as we have no handle to e.g. fix an issue if it exists in the component set.
    Frank

  • Visual editor JSF rendering not working

    Hi,
    I'm trialing the 10.1.0.3EA version of JDeveloper and I can't seem to get the JSF rendering working in the visual editor. I thought that perhaps I'd changed some settings or something so I completely uninstalled and then reinstalled JDeveloper. After the install I created a new application using the default web tech. scope, created default business components from the order and order_items tables in the oe schema, opened the JSF navigation, added a page and tried to drag and drop a read only table onto the page. Instead of the rendering I am getting a hierarchical view of tags with just the tag names, i'm not even getting any of the binding information shown, other than in the property inspector. I'v checked to make sure that the JSP tag libraries in the project settings all have "Execute tags in JSP Visual Editor" checked and in the preferences I have made sure that "Show JSP Tag Names Only" is unchecked. Does this functionality not work by default from the install or am I missing something?
    Any help would be appreciated!
    Thanks,
    Lee Proctor.

    Of course, use the value attribute of the component and set it to EL representing the desired property.

  • Render Related -JSF Third party Component

    Hai All
    I am having doubt regarding JSF Third party component like Jmaki ,MyFaces or something like that . How the third party component match with JSF life cycle even though there is no java classes for managing and rendering the Third party component . what i basically mean to say is if we use <h:inputText> in our JSF page , the inputText component will managed by many java class like UIInput.class and HtmlInputText and InputTextRender and so on. next if we use dojo.dropdowndatepicker ,there is component for managing this component like UIDate, HtmlData .
    could you tell me how third party component working without any problem.
    Thanks for advance
    Selvakumar.k

    If you look in the jar files for the libraries, you will find a faces-config.xml file containing such configurations.

  • How to obtain JSF Validation Messages Key?

    When a validation error occurs an error message component placed next to the component displays the message like "validation error:value is required".
    I know how to customize this message by having ur own resourece bundles. But i have this new requirement where i need to find not the message but the key corresponding to the message like 'javax.faces.component.UIInput.REQUIRED'.
    But when i look at the FacesMessage API all it has is summary and detail and no way to get this key of what hapenned. Is there anyway to do this using JSF API that iam unaware of or is it not possible at all?

    I knew how to customize the messages and the key. All i wanted to know is if i have an API that i cud use to find out the error key like javax.faces.UIInput.REQUIRED from a given FacesMessage instance?

  • JSF error messages

    has anybody successful using JSF error messages. Im using JSF portlet framework to display error msgs using h:messages tag. Im able to display validation/conversion errors with h:message tag.
    Im unable to display general messages that are result of an application exception. Has anybody ever done that?
    Help would be appreciated.
    Thanks
    -Sri

    If I understand you correctly ...
    FacesContext context = FacesContext.getCurrentInstance();
    FacesMessage message = new FacesMessage("New Message");
    context.addMessage(null, message);

  • Error Rendering JSP Component After Upgrade to SP12

    Hi everyone,
    I have developed an application in SP9 that uses a JSPDynPage Portal Component. The application was working fine before the upgrade.
    After I did my upgrade to SP12, it sometimes gives me the following error: "Error rendering jsp component". And without me doing anything, the problem after a while gets fixed by itself.
    The problem has been on and off now for two days. Any ideas of why this error is happening.

    Hey Dmitry,
    Is this the log you are talking about?
    #1.5#C0000A090B1800530000009A00003EE90003FE006FF9EDF7#1123702762237#com.sapportals.portal.prt.service.config.ConfigDeploymentService#sap.com/irj#com.sapportals.portal.prt.service.config.ConfigDeploymentService#qasema#18175####73447ad009d611dac181d87f0a090b18#SAPEngine_Application_Thread[impl:3]_9##0#0#Info##Plain###An upload sequence will start now. Please do not stop the server or serious deployment issues may arise.#
    #1.5#C0000A090B1800530000009B00003EE90003FE007008E880#1123702763218#com.sapportals.portal.prt.service.config.ConfigDeploymentService#sap.com/irj#com.sapportals.portal.prt.service.config.ConfigDeploymentService#qasema#18175####73447ad009d611dac181d87f0a090b18#SAPEngine_Application_Thread[impl:3]_9##0#0#Info##Plain###The upload sequence is now complete, all the upgrades have been performed.#
    #1.5#C0000A090B1800670000007D00003EE90003FE007071F8EE#1123702770092#com.sap.portal.prt.runtime.servlet_jsp#sap.com/irj#com.sap.portal.prt.runtime.servlet_jsp#qasema#18177####77f1fd5009d611dab416d87f0a090b18#SAPEngine_Application_Thread[impl:3]_16##0#0#Error#1#/System/Server#Java###Error in Compiling.
    [EXCEPTION]
    #1#com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the compilation of java generated from the jsp
    at com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.launchCompilerProcess(J2eeCompiler_6_30.java:577)
    at com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.compileExternal(J2eeCompiler_6_30.java:371)
    at com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.compile(J2eeCompiler_6_30.java:676)
    at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2160)
    at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:81)
    at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:140)
    at com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:279)
    at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:129)
    at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
    at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
    at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
    at com.sapportals.portal.htmlb.page.JSPDynPage.doOutput(JSPDynPage.java:76)
    at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)
    at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:154)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:392)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
    at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
    Caused by: java.io.IOException: Not enough space
    at java.lang.UNIXProcess.forkAndExec(Native Method)
    at java.lang.UNIXProcess.<init>(UNIXProcess.java:52)
    at java.lang.Runtime.execInternal(Native Method)
    at java.lang.Runtime.exec(Runtime.java:566)
    at java.lang.Runtime.exec(Runtime.java:491)
    at java.lang.Runtime.exec(Runtime.java:457)
    at com.sap.engine.lib.lang.RunExec.exec(RunExec.java:62)
    at com.sap.engine.lib.lang.RunExec.exec(RunExec.java:53)
    at com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.launchCompilerProcess(J2eeCompiler_6_30.java:556)
    at com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.compileExternal(J2eeCompiler_6_30.java:371)
    at com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.compile(J2eeCompiler_6_30.java:676)
    at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2160)
    at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:81)
    at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:140)
    at com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:279)
    at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:129)
    at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
    at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
    at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
    at com.sapportals.portal.htmlb.page.JSPDynPage.doOutput(JSPDynPage.java:76)
    at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)
    at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:154)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:392)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
    at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)

  • Missing Renderer Message

    I've been using the MPE Hack with my GTX 260 and now it longer works.  I get the Missing Renderer message when I fire up a project.  The one that says I will have to use the Software part of MPE and not the Hardware of MPE.  Anyway, I searched and read all the forum posts on this topic.  I downloaded the latest Nvidia driver for this card and that didn't fix it.  I did it twice just to be sure.  I also rolled the driver back to the one from last May and that didn't work either.  Hmmm?  Anyone with an idea of what might be going on?  I also went to the cuda_supported_cards text file and saw that my original hack was missing so I opened up Notepad and resaved it with the GeForce GTX 260 added but that didn't do it either.  Here is the list that shows in that text file.
    GeForce GTX 260
    GeForce GTX 285
    Quadro CX
    Quadro FX 3800
    Quadro FX 4800
    Quadro FX 5800
    Thanks if you can help me.
    Ragnar

    Fixed it myself.  I was saving that text file in the wrong location.  All is right again.  Thanks for looking.
    Ragnar

  • Launching instant messaging component from web dynpro

    Hi
    We have a requirement to launch instant messaging component from a web dynpro java link. Could you tell me what APIs can be used here? Is it possible to launch the component in a new browser window through some API calls?
    From collaboration launch pad if we take the link of instant message from properties and try to open it a new browser instance, we find a message staing "Session not started" and there is some java script error in the page. Also the Send button is invisible and the other buttons Leave Session, Close Session are inactive. Is it possible to launch the messaging window from a url?
    The url we used to launch it is as below.
    http://host:port/irj/servlet/prt/portal/prtroot/com.sap.netweaver.coll.appl.ui.rtc.RTCComponent?jspName=Chat.jsp&paramIndex=2&initiator=X
    Looking forward for your comments.
    Thanks
    Sudeep

    It's possible. On your alv you have to add botton with action to call bsp.
    You can use the following coding to determine the object type...
    CALL METHOD lr_mapping_srv->determine_ui_object_of_bor
        EXPORTING
          iv_bor_object_key  = lv_bor_object_key
          iv_bor_object_type = ls_orderadm_h-object_type
          iv_logical_system  = ls_orderadm_h-logical_system
        RECEIVING
          rv_result          = lv_ui_object_type.
    Then you have to build bsp...
    lv_orderadm_h_guid_c = ls_orderadm_h-guid.
      CONCATENATE
        lc_par0 sy-mandt
        lc_par1 lv_ui_object_type
        lc_par2 lc_display
        lc_par3 lv_orderadm_h_guid_c
        lc_par4 'nocookie'
      INTO lv_query.
      CALL METHOD cl_bsp_runtime=>if_bsp_runtime~construct_bsp_url
        EXPORTING
          in_application = lc_bsp_application
          in_page        = lc_bsp_page
        IMPORTING
          out_abs_url    = lv_open_url.
      CONCATENATE lv_open_url lv_query INTO lv_open_url.
    and finally you have to call browser...
    lo_api_component  = wd_comp_controller->wd_get_api( ).
      lo_window_manager = lo_api_component->get_window_manager( ).
      CALL METHOD lo_window_manager->create_external_window( EXPORTING url = lv_open_url
                                                             RECEIVING window = lo_window ).
      lo_window->open( ).

  • Message component from palette

    Hi,
    I've got just a simple question. I'm trying to learn jdeveloper 2.0 with a book for version 1.0. According to the book, I can add a message component from the dialogs page of the component palette.
    In jdeveloper2.0 however, I cannot find this component (or the dialog page).
    Is there a possibility to get this message component on the palette or some other way to get in the source code (besides programming it yourself).
    Thanks!

    To write both a summary message and a detail message to the Message Group component, use code like the following statement. The first argument is the summary message and the second argument is the detail message.
    FacesContext.getCurrentInstance().addMessage(
    null, new FacesMessage("Summary Message", "Detail Message"));I try to add a Message Group component to every page. This helps me figure out problems, especially when it appears that an action component (Button, Radio Button, Hyperlink, and so forth) is not working.

  • Messages show without message component

    Hello,
    in netweaver 2004s, sp09, we use in webdynpro for abap
    "messages show without message component"
    but in netweaver 2004s, sp12 we don´t find the option.
    Is this option depricated?
    Best regards
    Oliver Prodinger

    Hi Oliver,
    we made this change together with changes in the message area in SP11. These changes were done due to usability and UI Design specifications. Futhermore there are missing features implemented.
    For details have a look at:
    http://help.sap.com/saphelp_nwmobile71/helpdata/en/d8/2a934259a5cb6ae10000000a155106/frameset.htm
    Regards,
    Rainer

Maybe you are looking for