JSF 2.0: Facelets: No tag libraries (TLDs)?

Hi, I'm currently concerned with JSF 2.0 and Facelets. I found:
- Tags are no longer defined in taglibs (TLDs) (instead they appear to be hard-coded in Java code)
- On the other hand, jsf-impl.jar does ship two taglibs (for HTML and JSF Core), however, these solely include tags that have been existing since JSF 1.2 (the new tags are not defined there)
OK, that may be fine. Nonetheless, now there's a problem with code completion and validation in IDEs (Eclipse in my case).
Any ideas on how to get over that?
Thanks

[1] https://mojarra.dev.java.net/source/browse/mojarra/trunk/jsf-api/doc/web-facelettaglibrary_2_0.xsd?rev=6738&view=log
Excuse me, that's the XSD schema for facelet-taglib. I'd be requesting TLDs or XSDs that contain definitions for commandButton, button, etc.
[2] https://javaserverfaces.dev.java.net/nonav/docs/2.0/pdldocs/facelets/index.html
That's not a XSD or TLD definition file but just documentation. Moreover, it only covers JSF 1.2 tags, not JSF 2.0 tags. (I do know that it does ship with the JSF 2.0 specification.)
- Please remember that my final goal would be to have code completion and validation for JSF 2.0 in common IDEs, including Eclipse.
Thanks

Similar Messages

Need JSF fuego tag libraries

Hi,
In our project we are going to use JSF for UI. For JSP , there is online documentation for fuego tag libraries. But there is no documentation for JSF tag libraries. Only the one example available with Studio installation. But we have requirements like calling BPM Object methods in UI. But since the syntax is not available , we are not abel to proceed with development. It will be very helpful if some one provides details of JSF fuego tag libraries
Thanks,
Bharath

Hi All,
This requirement is a sure stopper for our project. I need some documentation or examples for "JSF fuego tag libraries". Online documentation is available for "JSP fuego tag libraries" at Link: [http://download.oracle.com/docs/cd/E13154_01/bpm/docs65/taglib/index.html]. The tags like <f:invoke> are working properly in JSP pages. I tried to use the same in JSF pages, but they are giving error.
The tags is different in JSF and JSP. For e.g.. to post the results back to bpm engine in JSP we use <f:postResult> in the action attribute of form tag whereas for JSF it is "returnToFuego" which has to be added in the action attribute of button.
Please guide me with some examples.
Thanks,
Bharath

JSF - How to set up tag libs in web.xml file?

Hello all,
I have a doubt... that in an JSF application we are using two tag libraries, one for the core and other for html components. Both these *.tld files are jared inside "jsf-impl.jar" file.
The problem is that when i start the web server (Tomcat4.0.6) the console shows that taglib tag must be configured... this means that we have to specify the "<taglib></taglib>" elements in the web.xml file of the jsf application... but how do configure the jar file...
please guide...

Putting the JAR files in WEB-INF/lib and using the standard URIs in the taglib directives are all that's needed; the container locates the TLDs in the JAR files at startup.
If this doesn't work, it's a bug in the container. You may want to upgrade to a later version of Tomcat; 4.0.6 is ancient, and may very well be buggy in this area.

Has anyone successfully implemented the JSF Viewer with Facelets?

We have recently started integrating Crystal into one of our web apps that is using JSF + Facelets + Seam.
I've built a taglib for the jsf viewer and configured it in web.xml and faces-config. I'm pulling an IReportSource from a backing bean using com.crystaldecisions.reports.sdk.ReportClientDocument and that is using a .rpt file stored on a directory. This all seems to be working, as I can step through the code and see the IReportSource being generated.
However, when the page loads, I am seeing the crystal javascript being converted in the page source, but nothing is loading on the page.
Has anyone seen an issue similar to this tied to Facelets? I've seen numerous documentation on Crystal and JSP, but very little on JSF or Facelets.
Has anyone been able to get a setup like this or similar to work properly?
I've also noticed an error when adding the viewer:
java.io.IOException: Recover report client document state failed.
at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.readExternal(SourceFile:1492)
at com.crystaldecisions.sdk.occa.report.application.AdvancedReportSource.readExternal(SourceFile:131)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
I believe this to be related to me switching over to the serializable ReportClientDocument: com.crystaldecisions.sdk.occa.report.application.ReportClientDocument versus using the nonserializable version.
When using the non-serializable version, I am seeing a constructor issue with the JPEReportSource
Exception: java.io.InvalidClassException: com.crystaldecisions.reports.reportengineinterface.JPEReportSource; no valid constructor
Has anyone seen this issue before or able to offer any suggestions?

Well, according to the tutorials I have seen on the internet, I believe CrystalReport was successfully implemented and tested with jsp, to have it working with Facelets, we need to do a little bit of work around. We need to make a new JSF custom component and assign it to an external renderer. then we can use it to view the report
please follow these and it should work after then,
1- bring the following jars into your libs
commons-configuration-1.2.jar
Concurrent.jar
CrystalCommon.jar
CrystalContentModels.jar
CrystalDatabaseConnectors.jar
CrystalFormulas.jar
CrystalQueryEngine.jar
CrystalReportEngine.jar
CrystalReportingCommon.jar
icu4j.jar
jrcadapter.jar
jrcerom.jar
keycodeDecoder.jar
MetafileRenderer.jar
rasapp.jar
rascore.jar
rpoifs.jar
serialization.jar
URIUtil.jar
webreporting.jar
webreporting-jsf.jar
xercesImpl.jar
xml-apis.jar
2- bring the folder "crystalreportviewers115" right under the "WebContent".
3- implement the custom FacesComponent and make it extend the "UIReportPageViewer" as follows;
import packagename.CustomReportRenderer;
@FacesComponent ("packagename.newReportViewer")
public class UIReportViewer extends com.crystaldecisions.report.web.jsf.UIReportPageViewer implements Serializable{
    public UIReportViewer () {
        this.setRendererType("packagename.CustomReportRenderer");
4- implement the renderer and make it extend the "ViewerHtmlRenderer" as follows;
@FacesRenderer(componentFamily="CrystalReports.DHTMLViewer", rendererType="packagename.CustomReportRenderer")
public class CustomReportRenderer extends com.crystaldecisions.report.web.jsf.ViewerHtmlRenderer implements Serializable {
5- make a new tag library xml file next to the web.xml so the application can find the tag configurations. name it "taglib.xml" and add the following inside it;
<facelet-taglib xmlns="http://java.sun.com/xml/ns/javaee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee"
    version="2.0">
    <namespace>http://new-jsf-custom-components/</namespace>
    <tag>
        <tag-name>ReportViewer</tag-name>
        <component>
            <component-type>packagename.newReportViewer</component-type>
            <renderer-type>packagename.CustomReportRenderer</renderer-type>
        </component>
    </tag>
</facelet-taglib>
6- configure the web.xml with the following
<context-param>
        <description>
        State saving method: 'client' or 'server' (=default). See JSF Specification 2.5.2</description>
        <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
        <param-value>server</param-value>
    </context-param>
    <context-param>
          <param-name>javax.faces.FACELETS_LIBRARIES</param-name>
        <param-value>/WEB-INF/taglib.xml</param-value>
    </context-param>
    <context-param>
        <param-name>crystal_image_uri</param-name>
        <param-value>../../crystalreportviewers115</param-value>
    </context-param>
7- implement the reportViewer.xhtml and make sure you have the following;
- in the tag libraries add the namespace schema xmlns:crystalnmcps="http://new-jsf-custom-components/"
- add the new reportViewer component
<crystalnmcps:ReportViewer reportSource="#{youController.reportSource}" displayToolbarLogo="false" parameterFields="#{youController.parameterFields}" allowParameterPrompting="false" />
Now run your app.
I hope this helps. good luck

Problem using JSTL tag libraries with OC4J 9.0.3

Hi
I'm using the JSTL tag libraries with OC4J 9.0.3. I'm using JDeveloper10.1.2. I put the fmt.tld and c.tld in the WEB-INF directory and I'm adding the jstl.jar and standard.jar library to the EAR file. Both tlds have:
<tlib-version>1.0</tlib-version>
<jsp-version>1.2</jsp-version>
And OC4J 9.0.3 is compatible with tlib version 1.0 and jsp version 1.2. When I run the web app I get:
OracleJSP: oracle.jsp.parse.JspParseException: Line # 1, <%@ taglib uri="/WEB-INF/fmt.tld" prefix="fmt"%>
Error: oracle.xml.parser.v2.XMLParseException ( /dataSource.jsp ):
line #:1 column #:48 : FIXED type Attribute value not equal to the default value 'http://java.sun.com/xml/ns/j2ee'.
line #:2 column #:18 : Attribute 'xmlns:xsi' used but not declared.
line #:3 column #:19 : Attribute 'xmlns:acme' used but not declared.
line #:4 column #:27 : Attribute 'xsi:schemaLocation' used but not declared.
line #:7 column #:16 : Attribute 'version' used but not declared.
line #:14 column #:15 : Invalid element 'tag-class' in content of 'tag', expected elements '[tagclass]'.
line #:14 column #:15 : Element 'tag-class' used but not declared.
line #:15 column #:18 : Invalid element 'body-content' in content of 'tag', expected elements '[tagclass]'.
line #:15 column #:18 : Element 'body-content' used but not declared.
line #:16 column #:15 : Invalid element 'attribute' in content of 'tag', expected elements '[tagclass]'.
line #:18 column #:12 : Invalid element 'type' in content of 'attribute', expected elements '[required, rtexprvalue]'.
line #:18 column #:12 : Element 'type' used but not declared.
line #:22 column #:15 : Invalid element 'attribute' in content of 'tag', expected elements '[tagclass]'.
line #:24 column #:12 : Invalid element 'type' in content of 'attribute', expected elements '[required, rtexprvalue]'.
line #:24 column #:12 : Element 'type' used but not declared.
line #:28 column #:15 : Invalid element 'attribute' in content of 'tag', expected elements '[tagclass]'.
line #:30 column #:12 : Invalid element 'type' in content of 'attribute', expected elements '[required, rtexprvalue]'.
line #:30 column #:12 : Element 'type' used but not declared.
line #:34 column #:15 : Invalid element 'attribute' in content of 'tag', expected elements '[tagclass]'.
line #:36 column #:12 : Invalid element 'type' in content of 'attribute', expected elements '[required, rtexprvalue]'.
Any ideas?

Hi
Thanks for the reply.
I tried it and I get the same error:
OracleJSP: oracle.jsp.parse.JspParseException: Line # 1, <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt"%>
Error: oracle.xml.parser.v2.XMLParseException ( /dataSource.jsp ):
line #:1 column #:48 : FIXED type Attribute value not equal to the default value 'http://java.sun.com/xml/ns/j2ee'.
line #:2 column #:18 : Attribute 'xmlns:xsi' used but not declared.
line #:3 column #:19 : Attribute 'xmlns:acme' used but not declared.
line #:4 column #:27 : Attribute 'xsi:schemaLocation' used but not declared.
line #:7 column #:16 : Attribute 'version' used but not declared.
line #:14 column #:15 : Invalid element 'tag-class' in content of 'tag', expected elements '[tagclass]'.
line #:14 column #:15 : Element 'tag-class' used but not declared.
line #:15 column #:18 : Invalid element 'body-content' in content of 'tag', expected elements '[tagclass]'.
line #:15 column #:18 : Element 'body-content' used but not declared.
line #:16 column #:15 : Invalid element 'attribute' in content of 'tag', expected elements '[tagclass]'.
line #:18 column #:12 : Invalid element 'type' in content of 'attribute', expected elements '[required, rtexprvalue]'.
line #:18 column #:12 : Element 'type' used but not declared.
line #:22 column #:15 : Invalid element 'attribute' in content of 'tag', expected elements '[tagclass]'.
line #:24 column #:12 : Invalid element 'type' in content of 'attribute', expected elements '[required, rtexprvalue]'.
line #:24 column #:12 : Element 'type' used but not declared.
line #:28 column #:15 : Invalid element 'attribute' in content of 'tag', expected elements '[tagclass]'.
line #:30 column #:12 : Invalid element 'type' in content of 'attribute', expected elements '[required, rtexprvalue]'.
line #:30 column #:12 : Element 'type' used but not declared.
line #:34 column #:15 : Invalid element 'attribute' in content of 'tag', expected elements '[tagclass]'.
line #:36 column #:12 : Invalid element 'type' in content of 'attribute', expected elements '[required, rtexprvalue]'.

Frame work problem along with tag libraries...

Hi..
I am new to jsp and am making a project in it, I am following MVC architecture but my problem is i am unable to understand all this concept of frameworks like struts, spring etc... i need some help with what they actually are..??
also i am not using any tag libraries in my project i am using simple jsp files with minimum java coding at the front end and class files at the logic layer... and then the databse layer... i want to know is it better to use tag libraries and for using them will i have to follow any particular framework.. and are these tag libraries different for different frameworks..??... will i be missing something if i don't use tag libraires or don't follow a particular framework...???

Those taglibs are particularly for the view layer of the MVC pattern. In a MCV framework you use taglibs to associate beans from the model/controller layer with the view layer. The framework will care about getting and setting the bean properties during the HTTP request-response cycle. With for example Sun JSF framework the relevant part of your JSP page would look like:
<h:form>
    <h:inputText value="#{myBean.input}" />
    <h:commandButton value="submit" action="#{myBean.submit}" />
</h:form>The JSF framework will generate this as something like<form name="someGeneratedName" method="post" action="currentPage.jsf">
    <input type="text" id="someGeneratedId" name="someGeneratedName" value="theInputValueFromMyBeanIfAny" />
    <input type="submit" id="someGeneratedId" name="someGeneratedId" value="submit" />
</form>The MyBean class would look like something as:public class MyBean {
    private String input;
    public void submit() {
        System.out.println("The framework has already set the input value: " + input);
        // You can do with this whatever you want. Eg persisting in DB:
        DAOFactory.getInstance("dbname").getSomeDAO().save(new SomeDTO(input));
    public String getInput() {
        return input;
    public void setInput(String input) {
        this.input = input;
}The average MVC framework also provides customizable Converters (convert between String for output and the desired Object type in model/controller layer) and Validators (required values, numeric values, date values, etc). Each MVC framework have its own taglibraries. For example JSF with the URI's http://java.sun.com/jsf/core and /html. Struts has another taglibs. Further on there is also the Java Standard Tag Library (JSTL) with the URI's http://java.sun.com/jsp/jstl/core, /functions and so on. Mixing of the taglibs is possible, but not always recommended. You should prefer the taglib of the framework used, but if the framework doesn't provide the tag with the desired functionality, then you can add another taglib, such as JSTL or, in case of JSF, Apache Tomahawk and JBoss Ajax4jsf.
If you want to learn more about JSF, you may find this article useful: [http://balusc.blogspot.com/2008/01/jsf-tutorial-with-eclipse-and-tomcat.html].

Problems with JSP and Tag Libraries in JBoss using Tomcat 5.5.9

Hi,
I am experiencing a really weird situation here. When running a deployed EJB3 ear application in a JBoss 4.0.3sp1 application using Tomcat service 5.5.9, Jasper is unable to compile any JSP file using Tag Libraries. To be more precise, when generating the Java source file (looking in the 'work' directory) everything in the file after the first occurance of a Tag Library usage is commented out (with "//"), causing the Java source to be invalid and outputs an error when accessing the page via a browser saying:
"org.apache.jasper.JasperException: Unable to compile class for JSP
Generated servlet error:
Syntax error, insert "}" to complete ClassBody
Generated servlet error:
Syntax error, insert "}" to complete Block
Generated servlet error:
Syntax error, insert "finally" to complete TryStatement
Generated servlet error:
Syntax error, insert "}" to complete MethodBody"
etc... where every error row is a suggestion of steps to take to make the source file valid. (of course).
The Tag Library jar files are located in the web application WEB-INF/lib folder as they should be. The descriptive Tag Library Definition files (tld:s) are located in the WEB-INF folder and every JSP file references these tld files directly via this path (WEB-INF/).
Any hints are most appreciated!!
Cheers!
/Henrik

Hi,
I am experiencing a really weird situation here. When running a deployed EJB3 ear application in a JBoss 4.0.3sp1 application using Tomcat service 5.5.9, Jasper is unable to compile any JSP file using Tag Libraries. To be more precise, when generating the Java source file (looking in the 'work' directory) everything in the file after the first occurance of a Tag Library usage is commented out (with "//"), causing the Java source to be invalid and outputs an error when accessing the page via a browser saying:
"org.apache.jasper.JasperException: Unable to compile class for JSP
Generated servlet error:
Syntax error, insert "}" to complete ClassBody
Generated servlet error:
Syntax error, insert "}" to complete Block
Generated servlet error:
Syntax error, insert "finally" to complete TryStatement
Generated servlet error:
Syntax error, insert "}" to complete MethodBody"
etc... where every error row is a suggestion of steps to take to make the source file valid. (of course).
The Tag Library jar files are located in the web application WEB-INF/lib folder as they should be. The descriptive Tag Library Definition files (tld:s) are located in the WEB-INF folder and every JSP file references these tld files directly via this path (WEB-INF/).
Any hints are most appreciated!!
Cheers!
/Henrik

What controls whats in the Tag Libraries View?

Hi,
I have a file which imports the following taglibs:
<%@ page language="java" errorPage="/error.jsp" pageEncoding="UTF-8" contentType="text/html; charset=utf-8" %>
<%@ taglib uri="http://www.springframework.org/tags/commons-validator" prefix="html" %>
<%@ taglib uri="http://www.springframework.org/tags" prefix="spring" %>
<%@ taglib uri="http://jakarta.apache.org/taglibs/request-1.0" prefix="r" %>
<%@ taglib uri="http://displaytag.sf.net/el" prefix="display" %>
<%@ taglib uri="http://struts-menu.sf.net/tag-el" prefix="menu" %>
<%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %>
<%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %>
<%@ taglib uri="http://java.sun.com/jstl/sql" prefix="sql" %>
<%@ taglib uri="/oscache" prefix="cache" %>
<%@ taglib uri="http://www.opensymphony.com/sitemesh/decorator" prefix="decorator"%>
<%@ taglib uri="http://www.opensymphony.com/sitemesh/page" prefix="page"%>
[/code:1:619d89d208]
but for some reason only some of them show up in the tag libraries view and hence auto complete only works for some of them.
Where am I going wrong? I am using eclipse 3.1 with nitrox 411 build.
thanks, Andrew

>
NitroX resolves tag libraries based on the following
* .tld present in a jar file and the jar file configured for Project Libraries (Project > Properties > Java Build Path > Libraries). Then using <uri> value of .tld for "uri" attribute of <%@taglib..%>
This did not work for my web-projects with the 407 and 411 builds of NitroX. I had to change all my taglib references to the >
* .tld present at any level within WEB-INF folder and using .tld path for "uri" attribute of <%@taglib ..%>
method.
At the time I was working with Greg Stachnick over the phone and he confirmed that the "jar-<uri>" approach should have worked for me and was going to try and find out why it didn't. I'd like to change my code back to using the "jar-<uri>" method, but don't want to waste time trying and then having to revert back. Has anything changed in NitroX since those builds that might have fixed this problem?

Weblogic 8.1 Portal Tag Libraries

With Weblogic Portal 8.1 there is a jar file (portlet-container.jar) that seems to contain tag libraries, but there is no TLD for it. Does this exist someplace?

Its in META-INF directory in the jar.
Seenu.

Register Tag libraries?

I just started usign BEA Workshop, it looks great except it is not behaving well with my function tags.
I have:
<jsp:root version="1.2"
xmlns:funk = "http://myurl/functions" >
${funk:contentURL(entry)}This works fine when i run it, but in the environment, I get an error:
"The prefix "funk" is not associated with an imported tag library"
Is there a way to tell it what taglibs i am using? The .tlds are in the META-INF directory for an included project.
thanks
ryan

Workshop recognizes all .tld files present below WEB-INF (or within its sub-folder).
i. if you have defined the tld file in web.xml then you can use the <taglib-uri> entry in defining <%@ taglib...%> directive
ii. in case you do not define <taglib> in web.xml then you can directly use the <uri> defined in .tld file
Workshop also handles the situation when .tlds are not physically present within WEB-INF but instead present within .jar file which is on classpath
IMPORTANT:
Tag Libraries view does not populate with tags for tlds picked from .jar file, unless defined in the page using taglib directive.

JSP, Tag Libraries, Tomcat 4.1

Due to an internal decision to place all content within certain categories: for example, we would like all our JSP pages to be in one directory, our TLD files to be in one directory, our images to be in one directory, etc. I would like to be able to set up two Tomcat Contexts (sites). One for /jsp and one for /tld. Is it possible to load the tld and tag class handler in one context and the jsp in another context and call the tag handler even though they are in separate sites? The first reaction someone might have is to just place everything in separate directories under the same context. Well, we do not want to do this because we do not want to use relative URLs. Our testing systems are Window 2000 so it is not a big deal. But our production server is OPENVMS. We want to use aliases for everything. /jsp for JSP pages. /tld for tag libraries, etc. Any thoughts?
Thank you.

Yes, this is a follow-up question to my initial question. However, I was trying to take a different approach after reading the inital comments and doing lots and lots of stupid little tests.
I have tried all three methods of using the mappings that you have suggested. And in every case, I cannot get the JSP page to recognize the location of the TLD from the URI unless I use a context in Tomcat or a relative URL for the URI declaration in the JSP page. So I must be doing something wrong. I am going to post what information is not business sensitive and see if you can find an error.
However, with that being said. We have a specific alias/directory structure we must maintain on the OPEN VMS system. In order to do so, so we can maintain a programmer and a "live" environment we must be able to use these aliases for all our file types. Don't get me wrong, we can use these alias' within the same context of Tomcat, but we must make sure that we can still access or JSP, TLD, and servlets using some sort of alias and NOT using relative URLs. All the dynamic stuff in Tomcat while trying to use Apache for the static content. On OPENVMS, there are things called logicals which can basically be set up as an alias. The logical can point to a specific value, a directory, a group of directories, or even a specific file name or command procedure or anything else you can logically use it for. We have to use these logicals in order to set up our site. These logicals are part of the system security of OPENVMS and this helps us determine which enviroment we need to use for which user.
Hope this gives a bit more informed information.
Currently, the tld and .class file are packaged into a webMenuTag.jar file in the "vsjsp" site.
There are no references to the TLD or Tag Library in the web.xml file. So here is the tld file and also the snippet of the jsp file. The class file is called webMenuTagHandler.class.
Thank you.
TLD:
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE taglib
PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.2//EN"
"http://java.sun.com/dtd/web-jsptaglibrary_1_2.dtd">
<taglib>
<tlib-version>1.0</tlib-version>
<jsp-version>1.2</jsp-version>
<short-name>webMenu</short-name>
<uri>webMenuTag</uri>
<description>
Tag library to print the menu on WWW site pages
</description>
<tag>
<name>webMenuTagHandler</name>
<tag-class>com.xxxxx.webMenuTagHandler</tag-class>
<description>Create menu and framework for web pages.</description>
<attribute>
     <name>menuStyle</name>
     <required>false</required>
     <rtexprvalue>true</rtexprvalue>
</attribute>
<attribute>
     <name>docTitle</name>
     <required>false</required>
     <rtexprvalue>true</rtexprvalue>
</attribute>
<attribute>
     <name>pageHeading</name>
     <required>false</required>
     <rtexprvalue>true</rtexprvalue>
</attribute>
<attribute>
     <name>navBarName</name>
     <required>false</required>
     <rtexprvalue>true</rtexprvalue>
</attribute>
<attribute>
     <name>navBarLocation</name>
     <required>false</required>
     <rtexprvalue>true</rtexprvalue>
</attribute>
<attribute>
     <name>htmLocation</name>
     <required>true</required>
     <rtexprvalue>true</rtexprvalue>
</attribute>
</tag>
</taglib>
JSP:
<%@ page contentType="text/html; charset=iso-8859-1" language="java" import="com.xxxxx.*,java.io.*,java.util.*,javax.servlet.*,javax.servlet.http.*,javax.servlet.jsp.*,org.apache.jasper.runtime.*"%>
<%@ taglib uri="webMenuTag" prefix="webMenu" %>
<html>
<webMenu:webMenuTagHandler docTitle="Test Page" htmLocation="top" navBarName="HOME"/>
... content...
</html>

Using BEA tag libraries for XML/XSL translation

Hi, I am new to using XML within Weblogic and have been struggling with using the
built in JSP tags to transform XML into HTML. When I try to display the jsp page,
I get the following error message in the browser:
Only one top level element is allowed in an XML document. Error processing resource
'http://localhost:7001/plims/testXML.jsp'. Line 20, Position 12
</style> script tag removed <!--- script language="javascript1.2"> -----------^
Here is the jsp code :
<%@ taglib uri="xmlx.tld" prefix="x"%>
<%
String myMedia = "html";
String content = new String();
%>
<x:xslt media="<%=myMedia%>">
<x:xml>
<?xml version="1.0" encoding="ISO-8859-1"?>
<tree> </tree>
</x:xml>
<x:stylesheet media="html" uri="qjTree.xsl"/>
</x:xslt>
I used the instructions on BEA's help docs to configure the app to use the tag
libraries, but it didnt work.
http://e-docs.bea.com/wls/docs70/xml/xml_apps.html#1082507
I am using a very simple xml tree for now to keep things simple. Any helping in
finding a solution would be much appreciated

Make sure you have the tld files and all the related tag libraries
available.
SP
"Rachel McCarthy" <[email protected]> wrote in message
news:[email protected]..
>
Hi, I am new to using XML within Weblogic and have been struggling withusing the
built in JSP tags to transform XML into HTML. When I try to display thejsp page,
I get the following error message in the browser:
Only one top level element is allowed in an XML document. Error processingresource
'http://localhost:7001/plims/testXML.jsp'. Line 20, Position 12
</style> script tag removed <!--- scriptlanguage="javascript1.2"> -----------^
>
>
>
>
Here is the jsp code :
<%@ taglib uri="xmlx.tld" prefix="x"%>
<%
String myMedia = "html";
String content = new String();
%>
<x:xslt media="<%=myMedia%>">
<x:xml>
<?xml version="1.0" encoding="ISO-8859-1"?>
<tree> </tree>
</x:xml>
<x:stylesheet media="html" uri="qjTree.xsl"/>
</x:xslt>
I used the instructions on BEA's help docs to configure the app to use thetag
libraries, but it didnt work.
http://e-docs.bea.com/wls/docs70/xml/xml_apps.html#1082507
I am using a very simple xml tree for now to keep things simple. Anyhelping in
finding a solution would be much appreciated

How to handle external tag-libraries in JSPs using Oracle Stellent?

I have already started the execution of JSP engine in Oracle Stellent, and also could run the sample Tomcat web-application and basic JSPs in Oracle UCM. What I need to do, is to customize my JSP to be able to show/hide some content using Oracle Stellent.
I have a JSP, from web application, which is using some some tag-libraries from spring, etc.
+<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%>+
+<%@ taglib uri="http://www.springframework.org/tags/form" prefix="form"%>+
+<%@ taglib uri="http://www.springframework.org/tags" prefix="s"%>+
+<%@ taglib prefix="security"+
uri="http://www.springframework.org/security/tags"%>
+<%@taglib uri="http://www.springframework.org/tags" prefix="s"%>+
+<%@ page import = "idcserver.*" %>+
+<jsp:useBean id="sb" class="idcserver.ServerBean" />+
+<%+
sb.init(request);
....and so on
I have checked in the above file, and when trying to preview in Oracle UCM, I get the following error:
Content Server Request Failed
+!csStellentTomcatErrorWhileProcessing,/idca/groups/jsp/documents/pix/11.jspThe absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application:org.apache.jasper.JasperException: The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application+
at org.apache.jasper.compiler.DefaultErrorHandler.jspError(Unknown Source)
at org.apache.jasper.compiler.ErrorDispatcher.dispatch(Unknown Source)
at org.apache.jasper.compiler.ErrorDispatcher.jspError(Unknown Source)
at org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(Unknown Source)
at org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(Unknown Source)
at org.apache.jasper.compiler.Parser.parseTaglibDirective(Unknown Source)
at org.apache.jasper.compiler.Parser.parseDirective(Unknown Source)
at org.apache.jasper.compiler.Parser.parseElements(Unknown Source)
at org.apache.jasper.compiler.Parser.parse(Unknown Source)
at org.apache.jasper.compiler.ParserController.doParse(Unknown Source)
at org.apache.jasper.compiler.ParserController.parse(Unknown Source)
at org.apache.jasper.compiler.Compiler.generateJava(Unknown Source)
at org.apache.jasper.compiler.Compiler.compile(Unknown Source)
at org.apache.jasper.compiler.Compiler.compile(Unknown Source)
at org.apache.jasper.compiler.Compiler.compile(Unknown Source)
at org.apache.jasper.JspCompilationContext.compile(Unknown Source)
at org.apache.jasper.servlet.JspServletWrapper.service(Unknown Source)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(Unknown Source)
at org.apache.jasper.servlet.JspServlet.service(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Unknown Source)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(Unknown Source)
at org.apache.catalina.core.StandardWrapperValve.invoke(Unknown Source)
at org.apache.catalina.core.StandardValveContext.invokeNext(Unknown Source)
at org.apache.catalina.core.StandardPipeline.invoke(Unknown Source)
at org.apache.catalina.core.StandardContextValve.invokeInternal(Unknown Source)
at org.apache.catalina.core.StandardContextValve.invoke(Unknown Source)
at org.apache.catalina.core.StandardValveContext.invokeNext(Unknown Source)
at org.apache.catalina.core.StandardPipeline.invoke(Unknown Source)
at org.apache.catalina.core.StandardHostValve.invoke(Unknown Source)
at org.apache.catalina.core.StandardValveContext.invokeNext(Unknown Source)
at org.apache.catalina.valves.ErrorReportValve.invoke(Unknown Source)
at org.apache.catalina.core.StandardValveContext.invokeNext(Unknown Source)
at org.apache.catalina.core.StandardPipeline.invoke(Unknown Source)
at org.apache.catalina.core.StandardEngineValve.invoke(Unknown Source)
at org.apache.catalina.core.StandardValveContext.invokeNext(Unknown Source)
at org.apache.catalina.core.StandardPipeline.invoke(Unknown Source)
at org.apache.catalina.core.ContainerBase.invoke(Unknown Source)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(Unknown Source)
at tomcatprovider.StellentProtocol$StellentWorkThread.runIt(StellentProtocol.java:304)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)
Edited by: 980473 on Jan 8, 2013 2:01 AM

Hi ,
Check if you have jstil.jar in WEB-INF/lib location , if missing manually add jstl.jar into WEB-INF/lib restart UCM Managed server .
Hope this helps.
Thanks,
Srinath

Jsp tag libraries

hi All,
I am receiving an error when i come to start a jsp page, it returns null pointer exception. so when I checked it is coming from the JSP tag Libraries. instead of the jsp libraries there is a null pointer exception . so any clue how to fix that ?
thanks
Amgad

Yes, marika, download the Jakarta JSTL implementation, unzip it, and put it everything in its /lib directory in your WEB-INF/lib. Then you can refer to the taglib in your JSPs like this:
<%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>That's all you need to do. No <taglib> in your web.xml or anything else. - MOD

How to use framework tag libraries

i need to create a new masthead using framework tag libraries.i got the purpose of that tag libraries from the help.sap.com site.
but i want some sample codes for the usage of that tags.i already have a masthead code using navigation tag libraries.can i make changes in that by using framework tags.if yes how and where to change.
or if u have any new solutions also please tell me.
if anyone has idea about it please share.
regards,
karthick

yes Mr.michael i checked with the help.sap.com site.but i cant get any sample code or solution.they have given the available tags and function of them in one line.no other details.
what u have given is a sample code for navigation tag libraries.i have it already.now i need a sample code with framework tag libraries.both have different functionalities i think so.if u find anything please send it.
thanks for ur reply.
regards,
karthick

JSF 2.0: Facelets: No tag libraries (TLDs)?

Similar Messages

Maybe you are looking for