JSTL: header / referer in a JSP Document

Hi all,
I am about to get the HTTP referer in a JSP Document:
<c:forEach items="${headerValues}" var="h">
     <c:if test="${h.key == 'referer'}">
          <c:set var="logReferer" value="${h.value}"></c:set>
     </c:if>
</c:forEach>
However, logReferer has a value like [Ljava.lang.String;@11a542b
I suppose this is a internal hash mapping or something, but how do I get the original String value? Note: when listing the other headers, I get similar results.

However, logReferer has a value like
[Ljava.lang.String;@11a542bIt means it is an array of String. You will have to iterate over it and display.

Similar Messages

HTML Comments in a JSP Document

I am writing a JSP Document that has a number of comments. Some I want to be server-side such as version history and some I want to be client-side.
Using a JSP page this is easily achieved using JSP comments <%-- JSP comment for server-side --%> and HTML Comments.
Using XML syntax a number of things are apparent:
1. There is no XML equivalent of a JSP comment (this has been well doc'd for a long time).
2. In the Java EE tutorials the recommended alternative to a JSP coomment is a HTML comment.
3. Using HTML comments in a JSP document the web container omits these in the page output - and so they are server-side only just like a JSP comment.
Code Snippet:
<template xmlns:jsp="http://java.sun.com/JSP/Page" xmlns:c="http://java.sun.com/jsp/jstl/core" version="1.2">

</template>

So, my question is how do I generate a client-side comment in a JSP Document?
Thanks
Edited by: DJT on Mar 3, 2008 4:28 AM
Edited by: DJT on Mar 3, 2008 4:30 AM

I found this ....
http://www.javaworld.com/javaworld/jw-07-2003/jw-0725-morejsp.html
One significant disadvantage of JSP documents is that no XML-compliant version of JSP comments exists. A JSP document developer can use client-side (HTML-/XML-style) comments or embed Java comments in scriptlets, but there is no JSP document equivalent to <%-- -->. This is a disadvantage because the other two commenting styles JSP documents can use have their own drawbacks. You can see the client-side comments in the rendered page using the browser's View Source option. The Java comments in scriptlets require placing Java code directly in the JSP document.
So try to embed the HTML comment inside scriptlet tags...
<%

%>

JSP documents and namespaces

I have an issue involving JSP documents (i.e. JSP pages that are
          well-formed XML documents). I am using namespaces on children elements
          of the <jsp:root> element, because my JSP page generates XML with
          namespaces. The simple fragment below illustrates this:
          <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page"
          version="1.2">
          <d:document xmlns:d="http://example.org/xml/document">
          <d:head>
          <d:title>Example</d:title>
          </d:head>
          <d:body>
          Some Text.
          </d:body>
          </d:document>
          </jsp:root>
          This example works with Tomcat 4 and Tomcat 5, but fails with WL
          8.1. I get an error like this:
          /example/my.jsp(20): no corresponding open tag for tag extension
          close: //[ ; Line: 20]
          probably occurred due to an error in /example/my.jsp line 20:
          </d:document>
          This seems to be a bug in the WebLogic JSP implementation. It should
          be possible to generate XML documents containing namespaces. The JSP
          1.2 spec is actually silent on this, but it says (JSP.5.2.2):
          "the root is where namespace attributes of taglibs will be inserted.
          All tag libraries used within the JSP document are represented in the
          root element through additional xmlns attributes."
          This to me implies that namespace declarations occurring elsewhere in
          the document are not interpreted as tag libs and therefore should be
          handled like regular tags.
          Any help is appreciated.
          -Erik


          "Erik Bruchez" <[email protected]> wrote in message
          news:[email protected]...
          > Thanks Nagesh,
          >
          > In passing, looking at the latest JSP 2.0 spec, I found out that there
          > may be an additional issue in the future, as the 2.0 spec allows for
          > tag libraries namespace declarations everywhere in the document. How
          > are you going to be able to generate XML documents with namespaces if
          > every namespace is necessarily bound to a tag library? The spec does
          > not seem to address this at all. I have emailed my feedback to the
          > JSR, but it would be interesting to have the opinion of WebLogic
          > developers on this.
          >
          > -Erik
          As far as i can remember, this doesn't restrict the namespaces in themselves
          i.e not attached to any taglibs. Given a namespace which is not resolved as
          a taglib, it will be considered a standard namespace no? .. Am i missing
          something. Also which section and which PFD version of the spec are you
          looking at? It would be great if you can give a little more detail about the
          issue so it can be fixed in the spec if possible..
          I would also be interested in knowing how you are using the Jsp documents
          (in xml format) in general. (since I'm trying to get an insight into the
          various ways in which jsp Docs are being used by customers)
          Nagesh
          >
          > Nagesh Susarla <[email protected]> wrote in message
          news:<[email protected]>...
          > > Hi Erik,
          > >
          > > Indeed this does look like a bug in the wls jsp container. Attributes
          > > with ':' in them are not being lexed correctly. I've opened CR111972 to
          > > track this issue, so please contact [email protected] for necessary
          patches.
          > >
          > > thanks
          > > Nagesh
          > >
          > > Erik Bruchez wrote:
          > > > I have an issue involving JSP documents (i.e. JSP pages that are
          > > > well-formed XML documents). I am using namespaces on children elements
          > > > of the <jsp:root> element, because my JSP page generates XML with
          > > > namespaces. The simple fragment below illustrates this:
          > > >
          > > > <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page"
          > > > version="1.2">
          > > > <d:document xmlns:d="http://example.org/xml/document">
          > > > <d:head>
          > > > <d:title>Example</d:title>
          > > > </d:head>
          > > > <d:body>
          > > > Some Text.
          > > > </d:body>
          > > > </d:document>
          > > > </jsp:root>
          > > >
          > > > This example works with Tomcat 4 and Tomcat 5, but fails with WL
          > > > 8.1. I get an error like this:
          > > >
          > > > /example/my.jsp(20): no corresponding open tag for tag extension
          > > > close: //[ ; Line: 20]
          > > > probably occurred due to an error in /example/my.jsp line 20:
          > > > </d:document>
          > > >
          > > > This seems to be a bug in the WebLogic JSP implementation. It should
          > > > be possible to generate XML documents containing namespaces. The JSP
          > > > 1.2 spec is actually silent on this, but it says (JSP.5.2.2):
          > > >
          > > > "the root is where namespace attributes of taglibs will be inserted.
          > > > All tag libraries used within the JSP document are represented in the
          > > > root element through additional xmlns attributes."
          > > >
          > > > This to me implies that namespace declarations occurring elsewhere in
          > > > the document are not interpreted as tag libs and therefore should be
          > > > handled like regular tags.
          > > >
          > > > Any help is appreciated.
          > > >
          > > > -Erik

Prelude and coda with JSP documents

Hello.
I have problems with adding prelude and coda templates to JSP documents (XML-format JSP).
This is content of my web.xml:
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee" version="2.4"
      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>simple</display-name>
     <jsp-config>
          <jsp-property-group>
               <display-name>simple</display-name>
               <url-pattern>*.jsp</url-pattern>
               <el-ignored>false</el-ignored>
               <scripting-invalid>false</scripting-invalid>
               <is-xml>true</is-xml>
               <include-prelude>/prelude.jspx</include-prelude>
               <include-coda>/coda.jspx</include-coda>
          </jsp-property-group>
     </jsp-config>
</web-app>This is from prelude.jspx:
<?xml version="1.0" ?>
<jsp:root version="2.0" xmlns:jsp="http://java.sun.com/JSP/Page">
     <jsp:directive.page contentType="text/html"/>
     <html xmlns="http://www.w3.org/1999/xhtml">This is coda.jspx:
     </html>
</jsp:root>And this is simple index.jsp of my web application:
<head>
     <title>Simple</title>
</head>
<body>
     <h2>Simple</h2>
</body>When running this on Tomcat 5.0.24 for Windows (Windows 2000 SP4) I get following exception on first request
org.apache.jasper.JasperException: /prelude.jspx(4,45) XML document structures must start and end within the same entity.Anyone have idea why is this happening ? How to include prelude and coda without breaking XML structure ?
Thanks, Nedim

The problem with what you are trying to do is that include will inlcude the response and not the original document.
In other words the jsp engine will try to compile prelude into a servlet, but because your xml document is not valid this would fail. Hence the XML error.
Do you absolutely need to use the xml syntax? Because jsp page syntax would work in this situation.

Problem processing JSP document

Hi,
I'm new to JSP and got such a problem: I have the following JSP document named JSPdoc.jspx
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.0">
<jsp:text>
    <html>
    <head>
    <title> Simple JSP Document </title>
    </head>
    <body>
    <h1>Hello World</h1>
    </body>
    </html>
</jsp:text>
</jsp:root>The problem is that this document is not interpreted, and I get such output in the browser:
−<html>
−<head>
<title> Simple JSP Document </title>
</head>
−<body>
<h1>jsp test</h1>
</body>
</html>I'm using Tomcat 6
Could anyone please explain why the html is not processed. Thank you.

Using the
<jsp:text>tag specifically says that what is inside it is text and not markup. If you want your <html> and so on to be treated as markup then don't use something that says it isn't markup.

How to add a field object to group header section in crystal report document?

Hi All, I have got two questions mentioned below, please share your inputs. 1)I want to know whether it is possible to add a field object to header section in crystal report document programmatically? I am using crystal runtime for visual studio. I know that using RAS we can do it, but I want to do it using managed library of crystal runtime. Please suggest. 2) I am doing a POC where I am using RAS (unmanaged library) to manipulated crystal report document. Please see code below: var dbTable = _reportDocument.ReportClientDocument.DatabaseController.Database.Tables[0]; var dbField = dbTable.DataFields.FindField(item.ColumnName, CrystalDecisions.ReportAppServer.DataDefModel.CrFieldDisplayNameTypeEnum.crFieldDisplayNameName, CrystalDecisions.ReportAppServer.DataDefModel.CeLocale.ceLocaleEnglishUS); CrystalDecisions.ReportAppServer.ReportDefModel.FieldObject fieldObject = new CrystalDecisions.ReportAppServer.ReportDefModel.FieldObject(); fieldObject.DataSourceName = dbField.Name; fieldObject.FieldValueType = dbField.Type; var groupHeaderArea = _reportDocument.ReportClientDocument.ReportDefController.ReportDefinition.GroupHeaderArea[0].Sections[i]; _reportDocument.ReportClientDocument.ReportDefController.ReportObjectController.Add(fieldObject, groupHeaderArea); In above code last line throwing exception : "The report field type is not valid." at CrystalDecisions.ReportAppServer.Controllers.ReportObjectControllerClass.Add(ISCRReportObject ReportObject, Section Section, Int32 nIndex) Thanks, Jai

Hi Jaikumar
As per the SCN Rules of engagement, one question per thread please.
Re. your 1st question. Adding a field to a report is considered to be a report creation APIs (RCAPI). Only the RAS SDK has RCAPIs, so you can not use plain jane crystal APIs. For how to with RAS, see the examples here: NET RAS SDK Samples - Business Intelligence (BusinessObjects) - SCN Wiki
Also, consult the Developer Help Files:
Report Application Server .NET SDK Developer Guide
Report Application Server .NET API Guide
Re. your second question, please create a new discussion.
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow us on Twitter

Howto optionally include an attribute on an element in a JSP document ?

I cannot find a way to optionally include an attribute on an element in a JSP document (JSPX). My JSP document is used to create an XML according to an XML schema where some element are declared as optional by the schema (default for element attributes).
I've tried:
a)
<elem <c:if test="${!empty obj.attr}">attr=${obj.attr}</c:if>>
</elem>b)
<jsp:element name="elem">
   <c:if test="${!empty obj.attr}">
      <jsp:attribute name="attr">${obj.attr}</jsp:attribute>
   </c:if>
   <jsp:body>
   </jsp:body>
</jsp:element>And none of them work. Any ideas?

I cannot find a way to optionally include an attribute on an element in a JSP document (JSPX). My JSP document is used to create an XML according to an XML schema where some element are declared as optional by the schema (default for element attributes).
I've tried:
a)
<elem <c:if test="${!empty obj.attr}">attr=${obj.attr}</c:if>>
</elem>b)
<jsp:element name="elem">
   <c:if test="${!empty obj.attr}">
      <jsp:attribute name="attr">${obj.attr}</jsp:attribute>
   </c:if>
   <jsp:body>
   </jsp:body>
</jsp:element>And none of them work. Any ideas?

Automatically populate fields in jsp documents based on other fields

hello guys. I have a jsp document
that has the following
<af:inputText value="#{bindings.SourceDocumentId.inputValue}"
label="#{bindings.SourceDocumentId.label}"
required="#{bindings.SourceDocumentId.mandatory}"
columns="#{bindings.SourceDocumentId.displayWidth}"
binding="#{backing_transactions_editTransactions.docId}"
id="docId">
<af:validator binding="#{bindings.SourceDocumentId.validator}"/>
<f:convertNumber groupingUsed="false"
pattern="#{bindings.SourceDocumentId.format}"/>
</af:inputText>
<af:inputText value="#{bindings.DocumentName.inputValue}"
label="#{bindings.DocumentName.label}"
required="#{bindings.DocumentName.mandatory}"
columns="#{bindings.DocumentName.displayWidth}"
binding="#{backing_transactions_editTransactions.docName}"
id="docName">
<af:validator binding="#{bindings.DocumentName.validator}"/>
</af:inputText>
And I have created the generated the backing beans automatically.
public class EditTransactions {
private CoreInputText docId;
private CoreInputText docName;
public CoreInputText getDocId() {
return docId;
public void setDocName(CoreInputText inputText7) {
this.docName = inputText7;
public CoreInputText getDocName() {
return docName;
I have a method in appmodule that has this
public String getDocName(Number docId)
{String docName;
return docName
on the document Id field I have to input a certain docId after I input the docId I have to populate automatically the docName based on the doc Id being given.
question
1. how can I set the document name automatically w/out submitting the page ?
2. how can I use my backing bean to set the docName using the method in my AppModule.?
Can anyone help me regarding this one.
Thank in advance
alvin.

A: automatically populate fields in jsp documents based on other fields

here is what you need to do:
1. Change the definitions for your fields as following
<af:inputText value="#{bindings.SourceDocumentId.inputValue}"
                        label="#{bindings.SourceDocumentId.label}"
                        required="#{bindings.SourceDocumentId.mandatory}"
                        columns="#{bindings.SourceDocumentId.displayWidth}"
                        binding="#{backing_transactions_editTransactions.docId}"
                        id="docId" valueChangeListener="#{backing_transactions_editTransactions.docIdChange}"
autoSubmit="true">
            <af:validator binding="#{bindings.SourceDocumentId.validator}"/>
            <f:convertNumber groupingUsed="false"
                             pattern="#{bindings.SourceDocumentId.format}"/>
          </af:inputText>
          <af:inputText value="#{bindings.DocumentName.inputValue}"
                        label="#{bindings.DocumentName.label}"
                        required="#{bindings.DocumentName.mandatory}"
                        columns="#{bindings.DocumentName.displayWidth}"
                        binding="#{backing_transactions_editTransactions.docName}"
                        id="docName"
partialTriggers="docId">
            <af:validator binding="#{bindings.DocumentName.validator}"/>
          </af:inputText>2. add the followig method to your backing bean:
public void docIdChange(ValueChangeEvent valueChangeEvent) {
    getDocName().setValue((String)getDocId().getValue() + "suffix");
}Run your form and enter the value into docId field, then press tab to go to the next field - docName will be populated

JSP Documents (JSP pages in XML format) and Namespaces

I have 1 set of XSLT stylesheets that takes XML and outputs JSP documents.
This 1 set of XSLT supports numerous clients (customers).
I have a new customer that uses a new namespace, let's call it "xyz".
This namespace is the TLD for xyz custom tags.
So, it would look something like this in the resulting jsp:root tag --> xmlns:xyz = "/xyzTagLib".
Where /xyzTagLib has a corresponding entry in web.xml that points to the xyz.tld that is delivered in WEB-INF/TLD.
However, most customers do not have the xyz application installed.
Thus, I added the exclude-namespace-prefixes="xyz" in the xsl:stylesheet tag to conditionally add the xmlns:xyz only if an xyz tag exists. However, this does not add it to the jsp:root tag, but only to each individual xyz tag in the resulting document.
However, the resulting JSP does not work in the runtime environment because it does not recognize the xyz tags.
Is there a known bug with jsp documents declaring namespaces "in line" instead of at the jsp:root level? Is there a way around this?
Thanks,
Brian

Hi Tridib,
the XML content is stored in the .xml file. You'll have to access it in a way that doesn't cause the XML-to-HTML transformation to take a peek at the format. You could probably do this by accessing the repository in question via WebDAV. If you're on a later SP, you should be able to go to /irj/go/km/docs/ in your browser to access the repository via WebDAV. Otherwise, take a look in the details pane of the folder that contains the .xml file in question. Under properties, there'll be a URL to access the folder via WebDAV.

Which table to be refered to get shipping document (VT01N) number created w

Which table to be refered to get shipping document (VT01N) number created with reference to Inbound delivery (VL31N).

Please refer to VTTP and VTTK

HT3384 How do I change margins and header footers on a pages document?

Hi can anyone help me on how do I change margins and header / footers on a pages document?
Many thanks

Oddly, when one enters text that is a paragraph string longer than the width of the the page, the text doesn't wrap. There seems to be something a bit wonky with the margins, but perhaps it's something else. I fiddled with styles to see if I could control it, but to no avail. I'm giving up and boing back to '09. Each time I think I'll switch to iWork 5, I encounter some other restrictive feature that sends me scurrying back to '09.

XSLT to create JSP Document

In the JSP 1.2 spec it talks about using XSLT to generate JSP Documents. I'm not sure if it's talking about generating JSPs at design time or run time. Has anyone attempted creating them at runtime? I've looked around and haven't found anything addressing this. If anyone has done this or has a link to somewhere that talks about this I'd appreciate any direction you can give.
Thanks.

Thank you for the reply but I don't think this addresses my issue. I understand how to use XSLT, XML, and JSP. What I'm looking for is the process of creating JSP Documents at runtime using XSLT. What part of the servlet cycle is this supported so that I can generate a JSP Document and then immediately use it? Is that inherently supported in J2EE?

Problems with JSP Documents (XML Mode)

Hi --
Have been following the spec for JSP as XML documents because I want to produce JSPs using XSLT. Two problems which I've yet to find anything but workarounds for:
1. (Most pressing) JSP Documents do not allow this <%= blah %>. This creates problems when I want to dynamically create an attribute value. The spec recommends this: 'value = "%=var%"', but I've tried this in Tomcat 4.1.12 and the expression gets reproduced literally at run-time. I've searched these forums and not found an answer.
2. Transformer wigs out on colons in "jsp:root" or "c:out" because it signifies a namespace with which it is unfamiliar. It doesn't need to recognize the namespace. Right now I'm putting in placeholders (jsp999root, for example) and replacing them after processing. Is there a better way?
These problems are really getting in the way. Any help would be most appreciated.

Have been following the spec for JSP as XML documents because I want to
produce JSPs using XSLT. Two problems which I've yet to find anything but
workarounds for:
1. (Most pressing) JSP Documents do not allow this <%= blah %>. This creates
problems when I want to dynamically create an attribute value. The spec
recommends this: 'value = "%=var%"', but I've tried this in Tomcat 4.1.12 and
the expression gets reproduced literally at run-time. I've searched these
forums and not found an answer. I am stuck on this also and desperately searching for an answer. Has anyone found anything yet?
2. Transformer wigs out on colons in "jsp:root" or "c:out" because it
signifies a namespace with which it is unfamiliar. It doesn't need to
recognize the namespace. Right now I'm putting in placeholders (jsp999root,
for example) and replacing them after processing. Is there a better way?You can (and should) put multiple namespace declarations in the xsl:stylesheet tag. that will let it know about jsp:* and pass it through appropriately. Try something like:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:jsp="http://java.sun.com/JSP/Page">

JDev 1014 JSF: difference between JSF JSP Page and JSF JSP Document ?

Hi all here ;)
I've been using the new JDev 1014 for some days now, find it very useful, but still... the help docs are not very helpful in one (minor) point: when you create a new JSF JSP item, you have to select either "JSP Page" or "JSP Document". Now, I see the difference in the created code, but what's the difference in it's usage?
thanx in advance
Thomas Nagel

Thomas,
there is none. Its just that the document has an XML format and the page is a typical JSP page. Its nothing specific in JDeveloper and just a matter of taste I guess.
Frank

Trouble displaying JSP document in IE

I am having some trouble displaying a JSP version 2 document in IE (though everything works fine in Mozilla).
All my jsp docs start off as follows:
<jsp:root version="2.0"
    xmlns:jsp="http://java.sun.com/JSP/Page"
    xmlns:f="http://java.sun.com/jsf/core"
    xmlns:h="http://java.sun.com/jsf/html"
    xmlns:c="http://java.sun.com/jsp/jstl/core"
    xmlns:fmt="http://java.sun.com/jsp/jstl/fmt"
    xmlns:sql="http://java.sun.com/jsp/jstl/sql"
    xmlns:x="http://java.sun.com/jsp/jstl/xml"
    xmlns:fn="http://java.sun.com/jsp/jstl/functions">
    <f:view>
     <f:verbatim><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">]]></f:verbatim>
     <html xmlns="http://www.w3.org/1999/xhtml" lang="en">Firstly, IE refuses to show the file offline because it can't retrieve the dtd in the doctype for validation. Is there any way to work around this? Either by turning it off or by downloading the file to a local location?
When I am online (or remove the Doctype declaration) IE displays the file as XML rather than XHTML as the doctype suggests. Does anyone know what is up with that?
Thanks in advance for any help!

not sure what's ur req...but the kind of displaying the order numbers in basic or sec list and then navigating to change/display tcode of the order is easy using HIDE in AT LINE-SELECTION with combination of
SET PARAMETER ID pid FIELD f. and then
CALL TRANSACTION xyz AND SKIP FIRST SCREEN .
RB.

JSTL: header / referer in a JSP Document

Similar Messages

Maybe you are looking for