Render:pageURL tag

I am having problems using the render:pageURL tag. It seems to always return null.
Any clues?
Basically, I have a portlet that shows news items. This page has several other
portlets also. What I need to do is - when a user clicks on any news item, I need
to show the detailed news item. I am open to ideas on how to do this - the key
issue is that the detailed news items need more screen space - thus other portlets
need to be hidden. I think the best solution is to call a new page which has a
portlet to handle the detailed news. So all I should have to do is create a link
to this new page, and pass it the newsId. Thus I was using the render:pageURL,
but it seems to return null.
Ideas?
Thanks
Cameron

Thanks for the tips. I was using the same syntax as in the docs, but let me try
this one. Also, maximizing the portlet will not work, because even in the detailed
view, there are a couple other portlets that still need to be shown.
I also tried the syntax suggested below, but it always returns http://localhost:7001/myportal
as the url. Not sure what is going wrong.
L
"George Murnock" <[email protected]> wrote:
>
Another thing to consider instead of switching pages is to simply maximizing
the
news portlet when someone clicks a news item link. Maximizing will a)
make your
news portlet take up all the real estate on the page, and b) stop all
the other
portlets on the page from rendering. You can use the windowUrl tag (http://edocs.bea.com/workshop/docs81/doc/en/portal/taglib/www.bea.com/servers/portal/tags/netuix/render/windowUrl.html)
to do it.
Hope that helps,
George
"Khurram Zafar" <[email protected]> wrote:
Post your code snippet. How are you using render:pageUrl? And how are
you posting
a request parameter to be picked up by the target portal page??? Inthe
meantime,
try this approach, it works for us:
<render:param name="newsId"
value="123"/></render:pageUrl>">This is a News Heading</a>
Cheers
Khurram
"Cameron Rakaai" <[email protected]> wrote:
I am having problems using the render:pageURL tag. It seems to always
return null.
Any clues?
Basically, I have a portlet that shows news items. This page has several
other
portlets also. What I need to do is - when a user clicks on any news
item, I need
to show the detailed news item. I am open to ideas on how to do this
- the key
issue is that the detailed news items need more screen space - thusother
portlets
need to be hidden. I think the best solution is to call a new pagewhich
has a
portlet to handle the detailed news. So all I should have to do iscreate
a link
to this new page, and pass it the newsId. Thus I was using the render:pageURL,
but it seems to return null.
Ideas?
Thanks
Cameron

Similar Messages

  • Using render:pageUrl tag

    Good Day,
    <p>
    I am using the <render:pageUrl> tag to render content in a page/portlet. Selecting a link constructed by the pageUrl tag the page renders OK but only once. I attempt to use the <render:pageUrl> several times to call the same page/portlet but the called page/portlet does not refresh with new content.
    <p>
    The begin() action in the called jpf (Test_Data_Page) is only called once, after the first call it is not called by subsequent calls using the other constructed URLs.
    <p>
    Each of the following URLs exist on a single portlet. I want to render different content based on the selected link. Help please?
    <p>
    a href="<render:pageUrl pageLabel="Test_Data_Page">
    <render:param name="test" value="test1" /></render:pageUrl>">test 1</a>
    <p>
    a href="<render:pageUrl pageLabel="Test_Data_Page">
    <render:param name="test" value="test2" /></render:pageUrl>">test 2</a>
    <p>
    a href="<render:pageUrl pageLabel="Test_Data_Page">
    <render:param name="test" value="test3" /></render:pageUrl>">test 3</a>
    <p>
    Thank you,<br>
    Everette

    Thanks for the tips. I was using the same syntax as in the docs, but let me try
    this one. Also, maximizing the portlet will not work, because even in the detailed
    view, there are a couple other portlets that still need to be shown.
    I also tried the syntax suggested below, but it always returns http://localhost:7001/myportal
    as the url. Not sure what is going wrong.
    L
    "George Murnock" <[email protected]> wrote:
    >
    Another thing to consider instead of switching pages is to simply maximizing
    the
    news portlet when someone clicks a news item link. Maximizing will a)
    make your
    news portlet take up all the real estate on the page, and b) stop all
    the other
    portlets on the page from rendering. You can use the windowUrl tag (http://edocs.bea.com/workshop/docs81/doc/en/portal/taglib/www.bea.com/servers/portal/tags/netuix/render/windowUrl.html)
    to do it.
    Hope that helps,
    George
    "Khurram Zafar" <[email protected]> wrote:
    Post your code snippet. How are you using render:pageUrl? And how are
    you posting
    a request parameter to be picked up by the target portal page??? Inthe
    meantime,
    try this approach, it works for us:
    <render:param name="newsId"
    value="123"/></render:pageUrl>">This is a News Heading</a>
    Cheers
    Khurram
    "Cameron Rakaai" <[email protected]> wrote:
    I am having problems using the render:pageURL tag. It seems to always
    return null.
    Any clues?
    Basically, I have a portlet that shows news items. This page has several
    other
    portlets also. What I need to do is - when a user clicks on any news
    item, I need
    to show the detailed news item. I am open to ideas on how to do this
    - the key
    issue is that the detailed news items need more screen space - thusother
    portlets
    need to be hidden. I think the best solution is to call a new pagewhich
    has a
    portlet to handle the detailed news. So all I should have to do iscreate
    a link
    to this new page, and pass it the newsId. Thus I was using the render:pageURL,
    but it seems to return null.
    Ideas?
    Thanks
    Cameron

  • How to render liquid tags in the console?

    Hello!
    I have been trying to render liquid tags in the browser's console using Javascript, but it doesn't work.  This is what I have been doing:
    document.getElementById('globals').innerHTML = '<pre>{{globals | json}}'</pre>;
    That just seems to write {{globals | json}} to the web page.

    BC's tag parser is only applied to files that are considered 'pages', and only runs once, when the page is served. It doesn't get applied to javascript files, and it is not directly accessible from the browser.
    If you need to refresh the display of globals without reloading the page, you could create dedicated page that contains only {{ globals }} and GET it with the JSON=true parameter.

  • How to render HTML tags in FDF file?

    We're creating PDF files using FDF format. Unfortunately, when it comes to displaying characters like © (&copy;),  ® (&reg;); and ™ (&trade;) they are simply rendering as &copy; rather than the proper symbol they represent.
    Is there a way to tell the FDF to render this properly?
    Dave

    HTML centric jargon, the &[something], is the problem. Each character of a "&[something] has a defined value that maps to Unicode. That is what PDF works with (Ref. ISO 32000-1).
    Try using the actual ANSI number for the characters. Again, PDF is not HTML.
    ANSI 0169 for ©
    ANSI 0174 for ®
    ANSI 0153 for ™
    Be well...

  • Render:resourceUrl Tag exposing Producer IP address

    I have an image yellow1.gif inside ProducerApp running on WLP 10.3.2. When I expose my portlet over WSRP, I use
    <render:resourceUrl contextualpath="/resources/images/yellow1.gif"/> which renders the URL as follows on the ConsumerApp. The image renders right on consumer side.
    http://localhost:7001/ConsumerApp/resource/cs__pageLabel%3Dtest_portal_page_2%26_portlet.portalUrl%3D%252FConsumerApp%252Ftest.portal%26_st%3D%26_windowLabel%3DhelloWorld_1_1/u_/id_/rr_true/po_false/rs_/rc_/iu_http%3A%2F%2F123.45.67.87%3A7001%2FProducerAPP/*wsrp*separator/resources/images/yellow1.gif
    Functiality wise the URL rewriting is fine. But in security terms, it is not good to expose the Producer IP (Please note last 20-30 chars in above URL..U see the producer IP i.e123.45.67.87) that is appering the rendered URL. Is there a way to encryt the URL or any other mechanism to not expose the producer IP?
    Thanks in advance.

    Hello,
    There are a few ways you could hide the producer IP address:
    1) On the consumer machine, define a name for the producer in the consumer machine's OS hostname resolution table and use that instead. For example, in Linux you can put an entry for the producer's IP address in /etc/hosts and give it a name like "producer.sample"-- it doesn't even have to be a "normal" DNS name since it is handled only on the consumer machine.
    2) If your portlet is a JSR286 portlet, you could just make it a portlet-served resource; I believe the producer address information is not encoded directly into those resource URLs.
    3) You could write a WSRP interceptor on the consumer to look for and re-write those URLs, then a resource proxy interceptor (also on the consumer) to take your altered URLs and change them back into something the resource proxy servlet can pin back to the appropriate producer.
    Kevin

  • How to Redirect to a page From a link in Header.

    Hi , I have a link in the Header.jsp to Contactus page. How to navigate to that page From header.jsp.
    Can any one please help me on this

    User render:pageUrl tag
    http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/javadocjsp/framework/render/pageUrl.html
    I assume you mean that you wish to goto the page and not a 'redirect'

  • Link to another page or book in portlet

    Hi,
    is there way to access another book or page in portal from link in JSP portlet?
    I don't want use upper menus. I would like to use some link(anchor) inside the
    portlet.

    thanks!! Solved my problem as well.
    "John Wheeler" <[email protected]> wrote:
    >
    "Mike Roberts" <[email protected]> wrote:
    Hi,
    is there way to access another book or page in portal from link in JSP
    portlet?
    I don't want use upper menus. I would like to use some link(anchor)inside
    the
    portlet.
    Try the following:
    <%@ taglib uri="http://www.bea.com/servers/portal/tags/netuix/render"
    prefix="render"%>
    <render:pageUrl var = "home" pageLabel="home" />
    <netui:anchor href='<%=home %>'>Home</netui:anchor>
    (or alternatively:)
    <netui:anchor href='<%= (String)pageContext.getAttribute("home") >'>Home</netui:anchor>
    Use the <render:pageUrl> tag to generate a URL for the portal page/book
    etc. with
    the given definitionLabel (you can label the page via its properties
    in Workshop).
    The generated URL will be saved in a variable whose name is given in
    the tag's
    "var" argument.
    You can now use this variable directly in a JSP scriptlet, or access
    it via the
    pageContext.
    Hope this helps.
    John Wheeler

  • How do I add web app tags to web app fields and have them render correctly?

    - I have a webapp field entitled "Status".
    - I have a webapp fields entitles "Status-Listed".
    - I want to have a tag in the description field that is {tag_Status-{tag_Status}} to where if the Status field is set to Listed the result will be {tag_Status-Listed} and will return the value in the Status-Listed field.
    - It works, and returns the value:
    <h2>Listed</h2>{tag_county} County<br />{tag_firstname} {tag_lastname} | {tag_address1}, {tag_address2} {tag_city}, {tag_state} | {tag_zipcode} | {tag_phone}<br />{tag_status} | <em>
    - However, this will display as the text entered when the tag is rendered from Design view. If I place the code in the HTML view it will render each tag correctly. What I am seeking to do is apply four different types of stylings to the listing, as in Listed, Not Listed, Rejected, No Answer, etc. That way in my directory I can have the status determine the type of look each listing has based upon the Status field.
    Any thoughts from the community?

    I am not sure I follow what you are explaining, but, I will try to give you an idea. Wrap all of your HTML in a div with a class of {tag_Status-{tag_Status}}. you can then style as necessary. However, if this involves hiding certain elements, then I would suggest using a custom template for each type of listing.

  • How to render custom JSP tags

    We have our own custom JSP tag libraries (some of them extend the Struts tags, but many do not) and want those to render correctly in the design view.
    Is that supported by NitroX Struts, or will it only work with built-in Struts tags?
    If it is supported, how does one get NitroX to run the custom tags?

    It is possible to customize many aspects of the rendering of a custom tag. This is done using a combination of an M7 specific metadata, and standard css rules.
    For example, you can change the label, icon and border of a custom tag by doing the following steps:
    1) Create a folder named "nitrox" where your tld file is located. For example if you have "/WEB-INF/app.tld" then create a
    folder "/WEB-INF/nitrox/".
    2) In the nitrox folder created above, create a file named "app.tlei" (for Tag Library Extra Information). The file name used here should match the name of the tld file. In this case "app".
    3) Paste the following content in the app.tlei file:
    <taglib-extrainfo>
    <css-uri>app.css</css-uri> <!-- an optional css file relative to this tlei file -->
    <tag name="myTag">
    <display-name>My Tag</display-name> <!-- The name displayed in the Tag Libraries view -->
    <rendering-label>{tag-name} ({name})</rendering-label> <!-- This will display the value of the "name" attribute in addition to the tag name in the tag view in the JSP design editor. -->
    <small-icon>images/myTag.gif</small-icon> <!-- The image uri relative to this tlei file. This is used in the Tag Libraries view and in the JSP design editor.-->
    </tag>
    </taglib-extrainfo>
    All customization tags are optional.
    4) Create the css file referenced from the tlei file above (in this example app.css in the same directory containing the tlei file).
    5) Paste the following content in the app.css file:
    myTag {border: 1 solid red; display: "inline"}
    This will render the tag as inline (i.e as one graphical object) even if the tag has nested content.
    In addition, you can use any standard css style property.
    You can customize other tags in the same fashion.
    If a custom tag inherits from a Struts tag, then the tag can inherit the full built-in tag customization as shown in the following example:
    Suppose you have a tag named "myText" that extends the Struts html:text form field tag. To inherit the NitroX html:text customization you follow the steps:
    1) insert the following in the tlei file described above:
    <tag name="myText">
    <inherit taglib-uid="http://jakarta.apache.org/struts/tags-html" tag-name="text" />
    </tag>
    2) Insert the following css rule in the css file referenced from the tlei file:
    myText {m7-inherit: "input-text"; display: inline}
    This will inherit the built-in css style for form text fields.
    Likewise, you can inherit the other Struts tags css styles by using the following rules:
    myPassword {m7-inherit: "input-password"; display: inline}
    myCancel {m7-inherit: "input-submit"; display: inline}
    myCheckbox {m7-inherit: "input-checkbox"; display: inline}
    myRadio {m7-inherit: "input-radio"; display: inline}
    mySelect {m7-inherit: "select"; display: inline}
    myTextarea {m7-inherit: "textarea"; display: inline}
    3) The inherited tag library file (in this example the struts-html.tld), must also be present under the WEB-INF directory.
    M7 Support

  • [ADF] Having Difficulties in Figuring Out Using the af:selectInputText Tag

    This is my first time using the ADF tags.
    The <af:selectInputText> is an input component that can launch a dialog and automatically accept its return value.
    My pop-up is a data table that provides "code" and "description". And the selection made will be return to the parent page and the "code" will be populated in the input field.
    First, I tested if my data table can be constructed successfully. Yes, I am able to use the JSF <h:dataTable> tag to display without problem.
    Second, I have adf-faces-api-10_1_3_0_4.jar and adf-faces-impl-10_1_3_0_4.jar in my WEB-INF/lib directory.
    Third, my web.xml and faces-config.xml work well because I was able to render JSF tags.
    Fourth, I have created the adf-faces-config.xml file with its contents directly copied from the ADF Configuration web site. The adf-faces-config.xml is placed together with the web.xml and faces-config.xml files.
    Fifth, on top of my ***.jsp, I added
    <%@ taglib uri="http://xmlns.oracle.com/adf/faces/EA10" prefix="af" %>
    <%@ taglib uri="http://xmlns.oracle.com/adf/faces/EA10/html" prefix="afh" %>
    However, the IDE says that <af:selectInputText ...> is an unknown tag.
    Besides, for the value of the "action" attribute of the <af:selectInputText ...>, what is supposed to be filled for the "dialog:?????"
    and the compiler starts complaining that the "value" attribute in my <h:dataTable ...> has no value! But, my <h:dataTable ....> worked well before I introduced ADF.
    Here is my code in the ***.jsp:
         <f:view>
              <h:form>
                     <af:selectInputText label="Sex: " id="idInputText"
                       value="#{listOfValuesManagementBean.selectedGender}"
                    popupTitle="Sex Types"
                        action="dialog:????????????" windowWidth="300" windowHeight="200">
                       <h:dataTable id="gender" value="#{listOfValuesManagementBean.genderTypes}" var="genderType">
                            <h:column>
                                 <f:facet name="header">
                                      <h:outputText value="Code"/>
                                 </f:facet>
                                 <h:outputText value="#{genderType.code}"/>
                            </h:column>
                            <h:column>
                                 <f:facet name="header">
                                      <h:outputText value="Description"/>
                                 </f:facet>
                                 <h:outputText value="#{genderType.description}"/>
                            </h:column>                   
                       </h:dataTable>
              </af:selectInputText>             
              </h:form>
         </f:view>

    I use IBM Rational Application Developer (RAD v.7)
    As you know that my JSF code had worked before I started introducing ADF tags.
    Now, I have resoved all the complilation complaints in my ***.jsp where I have the ADF <af:selectInputText ...> tag and all tags inside the <af:selectInputText ...> tag.
    But, I have the "Error 500: Cannot find FacesContext" in the browser when I run the ***.jsp.
    I believe it is in my web.xml file:
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
         <display-name>
         ADF_TEST</display-name>
         <context-param>
              <description>
              The location where state information is saved.
    Valid values are 'server' (typically saved in HttpSession) and 'client' (typically
    saved as a hidden field in the form.
    Default is server.</description>
              <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
              <param-value>client</param-value>
         </context-param>
         <context-param>
              <param-name>javax.faces.CONFIG_FILES</param-name>
              <param-value>/WEB-INF/faces-config.xml</param-value>
         </context-param>
         <context-param>
              <description>
              The default suffix for extension-mapped resources that contain JSF components.
    Default is '.jsp'.</description>
              <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
              <param-value>.jsp</param-value>
         </context-param>
         <context-param>
              <description>
              Number of Views to be stored in the session when Server-Side State Saving is being used.
    Default is 15.</description>
              <param-name>com.sun.faces.NUMBER_OF_VIEWS_IN_SESSION</param-name>
              <param-value>15</param-value>
         </context-param>
         <context-param>
              <description>
              If set to true while server-side state saving is being used, a serialized representation
    of the view is stored on the server. This allows for failover and sever clustering support.
    Default is false. This parameter is not available in JSF 1.0.</description>
              <param-name>com.sun.faces.enableHighAvailability</param-name>
              <param-value>false</param-value>
         </context-param>
         <context-param>
              <description>
              If set to true while client-side state saving is being used, reduces the number of bytes
    sent to the client by compressing the state before it is encoded and written as a hidden field.
    Default is false. This parameter is not available in JSF 1.0.</description>
              <param-name>com.sun.faces.COMPRESS_STATE</param-name>
              <param-value>false</param-value>
         </context-param>
         <context-param>
              <description>
              Monitors Faces JSP files for modifications and synchronizes a running server with
    the changes without restarting the server. If this parameter is set to false or
    removed from the deployment descriptor, any changes made to Faces JSP files may
    not be seen by the server until it is restarted. This parameter is usually set
    to true while the Faces JSP files are being developed and debugged in order to
    improve the performance of the development environment.</description>
              <param-name>com.ibm.ws.jsf.JSP_UPDATE_CHECK</param-name>
              <param-value>true</param-value>
         </context-param>
         <context-param>
              <description>
              Load JSF runtime when the application server starts up. If this parameter is set to false or removed,
    JSF runtime will be loaded and initialized when the first JSF request is processed.
    This may disable custom JSF extensions, such as factories defined in the project.</description>
              <param-name>com.ibm.ws.jsf.LOAD_FACES_CONFIG_AT_STARTUP</param-name>
              <param-value>true</param-value>
         </context-param>
         <context-param>
              <description>
              If set to true disables use of MultipartFacesContext, allowing underlying implementations to be used.
    MultipartFacesContext is required when the FileUpload component is used, and can be disabled otherwise.</description>
              <param-name>com.ibm.faces.DISABLE_JWL_MULTIPART_CONTEXT</param-name>
              <param-value>false</param-value>
         </context-param>
         <context-param>
              <description>
              Value, in milliseconds, to be used for Expires header for resources served by the JavaScript Resource Servlet.
    Default is never (31536000000 milliseconds or 1 year).</description>
              <param-name>com.ibm.faces.RESOURCE_EXPIRE_MS</param-name>
              <param-value>31536000000</param-value>
         </context-param>
         <context-param>
              <description>
              Defines the strictness of the conversion when converting from a string to a date.
    The higher the value, the more exactly the value must conform to the format.
    If 0 (liberal), all 'literals' are ignored while parsing a value, mis-ordered components will be rearranged,
    any missing component is supplied using the current datetime, misspellings and incomplete spellings are allowed
    (to the extent that they can be evaluated), 'E' and other non-unique components are ignored.
    If 1 (strict), all 'literals' are ignored while parsing a value, any missing component is supplied using the current
    datetime, misspellings and incomplete spellings are allowed (to the extent that they can be evaluated),
    'E' and other non-unique components are ignored. For example if the pattern is MMMM dd, yyyy a user can enter 'Feb/02/04'
    and it will be parsed as February 02, 2004.
    If 2 (very strict), an exact match is required except long month names can be 'shortened' to the minimum number of unique
    characters and 'E' and other non-unique components are ignored. Literals must match exactly.
    Default is 1.</description>
              <param-name>com.ibm.faces.DATETIME_ASSIST_STRICTNESS</param-name>
              <param-value>1</param-value>
         </context-param>
         <context-param>
              <description>
              Defines the strictness of the conversion when converting from a string to a number.
    The higher the value, the more exactly the value must conform to the pattern.
    For numbers, currently strictness levels of 0 and 1 are equivalent. If the strictness is 2,
    if number is signed, the sign must be provided (otherwise it's assumed positive).
    Default is 1.</description>
              <param-name>com.ibm.faces.NUMBER_ASSIST_STRICTNESS</param-name>
              <param-value>1</param-value>
         </context-param>
         <context-param>
              <description>
              Defines the path for resources such as JavaScript libraries and images.
    The value can be either:
    1. An empty string. Context path of the current application will be used.
    2. A path string. Example: /project13. A number. Specifies the number of nodes to use from the context path starting from the left.
    Example: With a value of 1 if the context path is /screen/faces/SSID110267549/RID1102676
    the path will be evaluated as /screen
    Default is an empty string.</description>
              <param-name>com.ibm.faces.USE_UNENCODED_CONTEXT_PATH</param-name>
              <param-value></param-value>
         </context-param>
         <context-param>
              <description>
              Sets a custom url-pattern for the JavaScript Resource servlet.
    Should match servlet mapping setting for the JavaScript Resource servlet. If the default default mapping
    value '/.ibmjsfres/*' is modified, this context-param should also be modified.
    </description>
              <param-name>com.ibm.faces.JS_RESOURCE_SERVLET_URL_PATTERN</param-name>
              <param-value>/.ibmjsfres/*</param-value>
         </context-param>
         <context-param>
              <description>
              If set to true, forces JavaScript Resource Servlet to cache all resources on the server.
    This can be useful when client-side caching is turned off.</description>
              <param-name>com.ibm.faces.JS_RESOURCE_SERVLET_CACHE</param-name>
              <param-value>false</param-value>
         </context-param>
         <context-param>
              <description>
              Sets a custom charset mapping properties file similar to converter.properties in WAS.</description>
              <param-name>com.ibm.faces.ENCODING_MAPPING</param-name>
              <param-value>converter.properties</param-value>
         </context-param>
         <context-param>
              <description>
              Number of Views to be stored in the session when Enhanced State Saving is being used.
    Default is 15.</description>
              <param-name>com.ibm.faces.ENHANCED_SERVER_STATE_SAVING_SESSION_STORED_VIEWS</param-name>
              <param-value>15</param-value>
         </context-param>
         <context-param>
              <description>
              If set to true, the entire JavaScript library, containing code for all components, will be included
    in the generated pages as one file. If set to false or removed, multiple smaller JavaScript files will be
    included, depending on the components used on the page.Default is false.</description>
              <param-name>com.ibm.faces.USE_HXCLIENT_FULL</param-name>
              <param-value>false</param-value>
         </context-param>
         <listener>
              <listener-class>com.sun.faces.config.ConfigureListener</listener-class>
         </listener>
         <servlet id="Servlet_1181745021880">
              <servlet-name>Faces Servlet</servlet-name>
              <servlet-class>
              javax.faces.webapp.FacesServlet</servlet-class>
              <load-on-startup> 1 </load-on-startup>
         </servlet>
         <servlet id="Servlet_1181745029380">
              <servlet-name>JavaScript Resource Servlet</servlet-name>
              <servlet-class>
              com.ibm.faces.webapp.JSResourceServlet</servlet-class>
              <load-on-startup>-1</load-on-startup>
         </servlet>
         <servlet-mapping>
              <servlet-name>Faces Servlet</servlet-name>
              <url-pattern>/faces/*</url-pattern>
         </servlet-mapping>
         <servlet-mapping>
              <servlet-name>Faces Servlet</servlet-name>
              <url-pattern>*.faces</url-pattern>
         </servlet-mapping>
         <servlet-mapping>
              <servlet-name>JavaScript Resource Servlet</servlet-name>
              <url-pattern>/.ibmjsfres/*</url-pattern>
         </servlet-mapping>
         <welcome-file-list>
              <welcome-file>index.html</welcome-file>
              <welcome-file>index.htm</welcome-file>
              <welcome-file>index.jsp</welcome-file>
              <welcome-file>default.html</welcome-file>
              <welcome-file>default.htm</welcome-file>
              <welcome-file>default.jsp</welcome-file>
         </welcome-file-list>
    </web-app>and my ***.jsp looks like:
    <%@ page language="java" contentType="text/html; charset=ISO-8859-1"
        pageEncoding="ISO-8859-1"%>
    <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
    <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
    <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
    <%@ taglib uri="http://xmlns.oracle.com/adf/faces" prefix="af" %>
    <%@ taglib uri="http://xmlns.oracle.com/adf/faces/html" prefix="afh" %>
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
    <title>Test the ADF selectInputText Tag</title>
    </head>
    <body>
         <f:view>
              <h:form>
                    <af:selectInputText label="Sex: " id="idInputText"
                       value="#{listOfValuesManagementBean.selectedGender}"
                        action="dialog:chooseGender" windowWidth="300" windowHeight="200">
                       <af:table id="gender" value="#{inputListOfValuesManagementBean.genderTypes}" var="genderType">
                            <af:column>
                                 <f:facet name="header">
                                      <af:outputText value="Code"/>
                                 </f:facet>
                                 <af:outputText value="#{genderType.code}"/>
                            </af:column>
                            <af:column>
                                 <f:facet name="header">
                                      <af:outputText value="Description"/>
                                 </f:facet>
                                 <af:outputText value="#{genderType.description}"/>
                            </af:column>                   
                       </af:table>
                   </af:selectInputText>
              </h:form>
         </f:view>
    </body>
    </html>Message was edited by:
    user537770

  • Can I write Design-time for JSP custom tag(not JSF components)

    I have some old JSP custom tags(not JSF components), and I want to use them in the IDE through the toolbox.
    Now I have already written the BeanInfos for these tags, and they can be drag from the toolbox; but it will throw a Exception when render the tags, and the properties in the Property Editor are not which I describe in the BeanInfos.
    How can I write Design-time for these tags? or whether it is possible to write the Design-time for these tags?
    the Exception is shown as follow:
    java.lang.ClassCastException
         at com.sun.rave.insync.faces.FacesPageUnit.renderNode(FacesPageUnit.java:1347)
    [catch] at com.sun.rave.insync.faces.FacesPageUnit.renderBean(FacesPageUnit.java:1086)
         at com.sun.rave.insync.faces.FacesPageUnit.getFacesRenderTree(FacesPageUnit.java:993)
         at com.sun.rave.css2.FacesSupport.getFacesHtml(FacesSupport.java:152)
         at com.sun.rave.css2.CssContainerBox.addNode(CssContainerBox.java:373)
         at com.sun.rave.css2.CssContainerBox.createChildren(CssContainerBox.java:354)
         at com.sun.rave.css2.DocumentBox.createChildren(DocumentBox.java:90)
         at com.sun.rave.css2.DocumentBox.relayout(DocumentBox.java:160)
         at com.sun.rave.css2.PageBox.layout(PageBox.java:392)
         at com.sun.rave.css2.PageBox.relayout(PageBox.java:454)
         at com.sun.rave.css2.DocumentBox.redoLayout(DocumentBox.java:313)
         at com.sun.rave.css2.PageBox.redoLayout(PageBox.java:460)
         at com.sun.rave.css2.DocumentBox.changed(DocumentBox.java:634)
         at com.sun.rave.designer.DesignerPaneUI$UpdateHandler.changedUpdate(DesignerPaneUI.java:1012)
         at com.sun.rave.text.Document.fireChangedUpdate(Document.java:851)
         at com.sun.rave.text.Document$5.run(Document.java:631)
         at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

    I have some old JSP custom tags(not JSF components), and I want to use them in the IDE through the toolbox.
    Now I have already written the BeanInfos for these tags, and they can be drag from the toolbox; but it will throw a Exception when render the tags, and the properties in the Property Editor are not which I describe in the BeanInfos.
    How can I write Design-time for these tags? or whether it is possible to write the Design-time for these tags?
    the Exception is shown as follow:
    java.lang.ClassCastException
         at com.sun.rave.insync.faces.FacesPageUnit.renderNode(FacesPageUnit.java:1347)
    [catch] at com.sun.rave.insync.faces.FacesPageUnit.renderBean(FacesPageUnit.java:1086)
         at com.sun.rave.insync.faces.FacesPageUnit.getFacesRenderTree(FacesPageUnit.java:993)
         at com.sun.rave.css2.FacesSupport.getFacesHtml(FacesSupport.java:152)
         at com.sun.rave.css2.CssContainerBox.addNode(CssContainerBox.java:373)
         at com.sun.rave.css2.CssContainerBox.createChildren(CssContainerBox.java:354)
         at com.sun.rave.css2.DocumentBox.createChildren(DocumentBox.java:90)
         at com.sun.rave.css2.DocumentBox.relayout(DocumentBox.java:160)
         at com.sun.rave.css2.PageBox.layout(PageBox.java:392)
         at com.sun.rave.css2.PageBox.relayout(PageBox.java:454)
         at com.sun.rave.css2.DocumentBox.redoLayout(DocumentBox.java:313)
         at com.sun.rave.css2.PageBox.redoLayout(PageBox.java:460)
         at com.sun.rave.css2.DocumentBox.changed(DocumentBox.java:634)
         at com.sun.rave.designer.DesignerPaneUI$UpdateHandler.changedUpdate(DesignerPaneUI.java:1012)
         at com.sun.rave.text.Document.fireChangedUpdate(Document.java:851)
         at com.sun.rave.text.Document$5.run(Document.java:631)
         at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

  • Don't render HTML

    Is there a way i can make my JSP file not render HTML tags?
    This is what i have right now. but it doesn't do what i need. How do i do this without using "<"?
    i need to have it display "<", ">" etc etc.
    out.println("<product name=""+x_productName+"" id=""+x_ID+"" FAQ=""  instructions=""+x_productInstructions+"" commercials=""+x_productCommercials+"" awards=""><whereToBuy storeName="" logo="" link="" location=""/><info>"+x_productInfo+"</info></product>");
    } What i need jsp to do is the following
    <products>
    <product name=""+x_productName+"" id=""+x_ID+"" FAQ="" instructions=""+x_productInstructions+"" commercials=""+x_productCommercials+"" awards="">
    <whereToBuy storeName="" logo="" link="" location=""/>
    <info>"+x_productInfo+"</info>
    </product>"<products><product name=""+x_productName+"" id=""+x_ID+"" FAQ="" instructions=""+x_productInstructions+"" commercials=""+x_productCommercials+"" awards=""><whereToBuy storeName="" logo="" link="" location=""/><info>"+x_productInfo+"</info>
    </product>"
    </products>
    );

    To make your browser display < and > symbols you have to escape them.
    http://www.theukwebdesigncompany.com/articles/entity-escape-characters.php
    Replace < with &lt; and > with &gt;
    As an aside, if you use a taglib like JSTL, the c:out tag will escape the nasty characters for you.
    <c:out value="<product name=..."/>alternatively why not do this in JSP
    &lt;produce name="<%= x_productName %>" id="<%= x_ID%>"...Hope this helps,
    evnafets

  • Render pdf

    Hi
    today I tried to render PDF Blob , using render:satelliteblob .I am able to render image file without any issue using render:satelliteblob
    but I'm not sure which table and what service using render for PDF in render:satelliteblob tag.
    thanks
    bala

    Hi jiri
    Thanks for your response , I tried as per your response like my code is
    <render:satelliteblob
                   blobtable='MungoBlobs'
                   blobkey='id'
                   blobwhere='1337377925212'
                   blobcol='urldata'
                   cachecontrol="never"
                   blobnocache="true"
                   container="servlet"
                   blobheader="application/pdf">
                   <render:argument name="blobheadername1" value="Custom-Header-1"/>
                   <render:argument name="blobheadervalue1" value="Custom value for header 1"/>
                   <render:argument name="blobheadername2" value="Custom-Header-2"/>
                   <render:argument name="blobheadervalue2" value="Custom value for header 2"/>
    </render:satelliteblob>
    But requested PDF is not rendering , only showing unavailable image icon .
    just for your reference , view-source of this page is :
    Click here
                   <img src="/cs/BlobServer?blobkey=id&blobnocache=true&blobwhere=1337377925212&blobheader=application%2Fpdf&blobheadername2=Custom-Header-2&blobheadername1=Custom-Header-1&blobheadervalue2=Custom+value+for+header+2&blobheadervalue1=Custom+value+for+header+1&blobcol=urldata&blobtable=MungoBlobs" rendermode="live" />
    I am not sure , when i'm rendering PDF , showing img src in view-source page .
    Thanks
    bala
    Edited by: bala6 on May 17, 2013 11:59 AM

  • JSP 2.0 tag files in jDeveloper 10g

    Hi, I'd like to create a set of UI components using JSP 2.0 tag files and have them available through the jDeveloper component palette for use in the visual edittor. I'd like jDeveloper to render the tags at design time like it can with regular old tags.
    Can this be done, and if so, how? I poked around in jDeveloper and on the web site without figuring it out... If I missed something obvious or there's docs online please point me in the right direction!
    Thanks,
    L.

    OK, so the integrated run-time supports JSP 2.0 and tag files. But what I'm after is support in the design-time components. Specifically, I want to produce a set of user interface components that I can place in the component palette and have rendered in the JSP visual editor.
    As far as I can tell (see previous post), jDeveloper's editor doesn't understand JSP 2.0 features. Therefore I suspect that the design-time as a whole doesn't and so I'll have to use regular Java tags for anything that needs to be able to be rendered at design time.
    Oh well. Maybe I can write a Java tag implementation that somehow invokes a tag file and just write a simple wrapper taglib specifically for use within jDeveloper at design time.
    L.

  • Render:resourceUrl

    I'm using render:resourceUrl tag for images in my jsp page.
    It works fine when I use <img src='<render:resourceUrl path="/resources/images/universal_white.GIF"/>'>
    Also, works when I use
    <%
    String
    imagePath = "/resources/images/universal_white.GIF";
    %>
    <img src='<render:resourceUrl path="<%=imagePath%>"/>'>
    However, does not work when I do like this:
    <%
    String
    imagePath = "/resources/images";
    %>
    <img src='<render:resourceUrl
    path="<%=imagePath%>/universal_white.GIF"/>'>
    Any help would be greatly appreciated

    Hello,
    There are a few ways you could hide the producer IP address:
    1) On the consumer machine, define a name for the producer in the consumer machine's OS hostname resolution table and use that instead. For example, in Linux you can put an entry for the producer's IP address in /etc/hosts and give it a name like "producer.sample"-- it doesn't even have to be a "normal" DNS name since it is handled only on the consumer machine.
    2) If your portlet is a JSR286 portlet, you could just make it a portlet-served resource; I believe the producer address information is not encoded directly into those resource URLs.
    3) You could write a WSRP interceptor on the consumer to look for and re-write those URLs, then a resource proxy interceptor (also on the consumer) to take your altered URLs and change them back into something the resource proxy servlet can pin back to the appropriate producer.
    Kevin

Maybe you are looking for