Problem Transforming XML to JSF tags

I have a fealing there is something I don't know here,
I am transforming XML into a JSP that include tags from taglib http://java.sun.com/jsf/html (prefix="h")
This is an section from my stylesheet
<xsl:template name="forename">
<h:inputText>
<xsl:attribute name="value">#{abyss.myCustomer.forename}</xsl:attribute>
</h:inputText>
</xsl:template>
which transforms my XML to exactly what I expect if a was writting it directly as a jsp
<h:inputText value="#{abyss.myCustomer.forename}"></h:inputText>
but it still looks like this after it is rendered in the browser, and not like
<input type="text" name="dataCapture:j_id_id199" value="Customer Name" />
which is how it looks if I cut and paste the result of the transformation into a jsp, and run that by itself
Does anyone have any idea was the <h:inputText does not evaluate the tag in the browser after the transformation ?
Edited by: OB1 on Nov 23, 2007 1:46 PM
Edited by: OB1 on Nov 23, 2007 2:43 PM

Unfortunatly I do, my jsp is
<%@ taglib prefix="c" uri="http://java.sun.com/jstl/core_rt" %>
<%@ taglib prefix="x" uri="http://java.sun.com/jstl/xml_rt" %>
<%@ taglib prefix="h" uri="http://java.sun.com/jsf/html" %>
<%@ taglib prefix="f" uri="http://java.sun.com/jsf/core" %>
<html>
<c:set value="${abyss.myBusinessServicePath}" var="xmldocpath"></c:set>
<c:import url="${xmldocpath}" var="xmldoc"/>
<c:import url="/xsl/transform.xsl" var="xslt"/>
<x:transform xml="${xmldoc}" xslt="${xslt}"/>
</html>

Similar Messages

Problem transforming XML/XSL Using Xalan

Hi, I am using the xalan apis to transform XML/XSL in a servlet..My servlet code is like...
response.setContentType("text/html; charset=UTF-8");
// Output goes in the response stream.
PrintWriter out = response.getWriter();
boolean environmentOK = (new org.apache.xalan.xslt.EnvironmentCheck()).checkEnvironment (out);
try
TransformerFactory tFactory = TransformerFactory.newInstance();
// Get the XML input document and the stylesheet.
Source xmlSource = new StreamSource("D:\\DATA\\jrun\\test\\test.xml");
Source xslSource = new StreamSource("D:\\DATA\\jrun\\test\\test.xsl");
// Generate the transformer.
Transformer transformer = tFactory.newTransformer(xslSource);
// Perform the transformation, sending the output to the response.
transformer.transform(xmlSource, new StreamResult(out));
I am getting the error ..
javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException: org.xml.sax.SAXException: Namespace not supported by SAXParserjavax.xml.transform.TransformerConfigurationException
That's why I have added the line..
boolean environmentOK = (new org.apache.xalan.xslt.EnvironmentCheck()).checkEnvironment (out);
But that gives me the following error diagnostic information...
ERROR.version.DOM=ERROR attempting to load DOM level 2 class: java.lang.NoSuchMethodException
I have put all the 3 required classes, xml-apis.jar, xercesImpl.jar and xalan.jar in my application servers classpath..
Please let me know what I am doing wrong..and how this can be fixed.
Thanks
Surajit

hey Surajit
Your code is unable to create a transformer from a factory instance.
I would check why it is not creating the Transformer.On my win32 system i usee two forward slashes..to identify the file path
D://xyz//abc....instead of D:\\...i wonder if thats one reason why your code is not able to create a transformer based on the StreamSource u create for the file paths.
Code i use..that works
javax.xml.transform.TransformerFactory tFactory =
                                                            javax.xml.transform.TransformerFactory.newInstance();
                                                  javax.xml.transform.Source xmlSource = new javax.xml.transform.stream.StreamSource                              (xmlInputSource);
                                             javax.xml.transform.Source xslSource = new javax.xml.transform.stream.StreamSource
                                   (xslInputSource);
                                                                                                    // Generate the transformer.
                                                            javax.xml.transform.Transformer transformer = tFactory.newTransformer(xslSource);
                                                                                               // Perform the transformation, sending the output to the response.
                                                            transformer.transform(xmlSource,new javax.xml.transform.stream.StreamResult(out));
                                                                                                    I used jaxp-1.2 with tomcat 4.1.12
Hope that helps.

Transforming XML/XSLT : CDATA problem

Hi!
I have a problem transforming xml with XSLT using the API javax.xml.
The result is correct until I have a CDATA section in my xml document.
The transforming process encodes all the & < > (special characters) it finds in.
This occurs problem for the follow of my treatement because the content of my CDATA is already encoded.
For example, this xml code :
<?xml version='1.0' encoding="ISO-8859-1" ?>
<article>
<article-contenu><![CDATA[Accent : é Signe : <]]></article-contenu>
</article>
produces in my output :
Accent : &eacute; Signe : &lt;
This is my java code :
TransformerFactory tFactory = TransformerFactory.newInstance();
Source xmlSource = new StreamSource(readerXml);
Source xslSource = new StreamSource( fileXsl );
// Generate the transformer.
Transformer transformer = tFactory.newTransformer(xslSource);
// Perform the transformation, sending the output to the response.
transformer.transform(xmlSource, new javax.xml.transform.stream.StreamResult(sw));
How can I tell the transformer not to do that?
Thanks for your answers!

I am having a similar problem. I have enclosed my text data in my xml file like this:
<![CDATA[<b>Hello World!</b>]]>
My select statement in my XSLT sheet is as follows:
<xsl:value-of select="." disable-output-escaping="yes"/>
I have tried setting xsl:output to text, to html, and to xml. The <, >, and & get converted to xhtml entities.
Where should I begin to troubleshoot? If the Xalan xslt jars? My stylesheet. My xml doc? Java code?
Any feedback welcome.

Help Please ! -- transform XML to HTML using xslt tag in JSP

Hello,
I have problem to do XSL transform in JSP.
I have an XSL : test.xsl
I have an XML : test.xml
In JSP I have:
<x:xslt media="html" xml="test.xml">
<x:stylesheet media="html" uri="test.xsl" />
</x:xslt>
But It doesn't work the way it suppose to. What is wrong in my code ? I followed the URL http://e-docs.bea.com/wls/docs81/xml/xml_apps.html
Thanks in advance,
Christina

Basically:
    try{
      //Setting up parameters.
      xml=new StreamSource(new File(xmlInput));
      xsl=new StreamSource(new File(xslInput));
      baos=new ByteArrayOutputStream();
      htmlResult=new StreamResult(baos);
      //Transform input(xml, xsl) onto html output.
      TransformerFactory tfactory=TransformerFactory.newInstance();
      Transformer transformer=tfactory.newTransformer(xsl);
      transformer.transform(xml, htmlResult);
      baos.writeTo(out);
      //System.err.println(htmlResult.getOutputStream().toString());
    catch(...){
    }I havent tested and I havent use this for a while, but I hope this can serve as a staring point.
Regards,
OO

Problems in transforming XML to HTML using HP-UX with Netscape Enterprise Server 4.0 sp3

Hi,
Has anyone ever had any problem using XML in NES 4.0 sp3?
I'm using the libraries com.sun.xml.parser, com.sun.xml.tree, javax.xml.transform.
The html is being created but is not being returned.
(it is not showed in browser)
This same xml application works well in Solaris with Iplanet Web Server 4.1, but it is not working in HP-UX with Netscape Enterprise Server 4.0 sp3.
I'm entirely lost. I don't know if there is a bug in this version (NES 4.0) or if I need other xml libraries or it is a problem of JRE version.
Any comments will be appreciate.
Thanks

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Norbert Clavaux ([email protected]):
Hi,
Last year we built a complete new website, based on XML/XSL.
We assumed all browsers would cope with XSL by now, but that was far to optimistic.
Our company planned to launch the new site this december, but XSL is giving us some major problems:
*** All our customers are obliged to use Internet Explorer 4/5.x. Some don't like that at all: they stick to Netscape.
*** IE users have to download and install the MS-XSL parser. At our pilotsites this is giving a lot of trouble and frustration.
I heard that it is possible to do the parsing at the serverside, using XSLT, creating HTML.
HOW CAN WE INSTALL / IMPLEMENT THIS OPTION IN OUR CONFIGURATION?
(PL/SQL / IAS 9i / Sun Solaris / Oracle 8.1.2)
Thanks in advance,
Norbert Clavaux
Nederlandse Bibliotheek Dienst
The Netherlands<HR></BLOCKQUOTE>
You could use DB Prism / Cocoon CMS.
This CMS is built on top of Apache Cocoon Framework and DB Prism servlet engine.
This CMS stores the assets in the DB (CLOB) and applys the stylesheet at runtime.
If you need more information about this CMS look at is free.
This CMS builts the DB Prism web site at www.plenix.com/dbprism/
Best regards, Marcelo.

Transformation XML problem.

Hello!
I have very easy java code for transform XML document (sorry, for print out XML without changes):
parser = new DOMParser();
parser.setPreserveWhitespace(false);
// parser input XML file
xmlURL = createURL(args[0]);
parser.parse(xmlURL);
xml = parser.getDocument();
// print the transformed document
xml.print(System.out);
But if I have DTD in XML then JDK write many errors: SIGBUS 10* bus error
If XML does not contains DTD then java code work successfuly.
I use JDK 1.2.2, xmlparserv2 for Sun Solaris

Try turning off your JIT.
I've only ever seen core dumps when it was a JIT problem.

Problem with adding Sun JSF RI v1.2 as a new library in JDeveloper 10.1.3.1

Hi,
I have a problem with adding a latest JSF 1.2 RI from Sun (https://javaserverfaces.dev.java.net/files/documents/1866/44998/jsf-1_2_03.zip) to JDeveloper as a new library.
I created a new User library and added into it jsf-impl.jar and jsf-api.jar from JSF 1.2 RI.
Then I try to create two new JSP Tag libraries based from .tld files.
When a .tld file is placed in "TLD File:" field there is no information below about Library Version and Required JSP Version. If I check "Execute Tags in JSP Visual Editor" and click "Customize" button - list of tags in "Customize Tag Library" window is empty.
I have errors when I try to use JSF Tags from this new library in JSP page like :
"Can't create tag instance: f:view (class: null). Make sure, that the tag class or a library contained this class is available in this application"
(free translation to English)
Is this possible to add JSF RI v1.2 as another library in Jdeveloper 10.1.3.1 ?
thanks for help
koli

Hi,
This solution is not exactly for Jdeveloper 10.1.3.x I think.
- "Create a JSF system library." section, point 2. - there is not possible to add library in folder other than User I see, so I added it in User folder.
- "Register the JSF JSP tag libraries." section, point 5. - in JD 10.1.3 there is no dialog box, I checked checkbox "Show Tag Library in Palette". A new library was added to User folder but there is no new libraries in component Palette.
Even as I use "Edit tag libraries .." from Component Palette context menu and add manually new tag libraries to selected, there is no libraries in Component Palette after it.
I feel so problem is with different .tld files format, not with adding libraries method.
Sun RI tld file (from version 1.2_03) fragment:
<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 http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd"
version="2.1">

<description>
The core JavaServer Faces custom actions that are independent of
any particular RenderKit.
</description>
<tlib-version>1.2</tlib-version>
<short-name>f</short-name>
<uri>http://java.sun.com/jsf/core</uri>
tld included in JD:
<!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>f</short-name>
<uri>http://java.sun.com/jsf/core</uri>
<description>
The core JavaServer Faces custom actions that are independent of
any particular RenderKit.
</description>
Did JDeveloper 10.1.3.x maintain with taglib version 1.2 ?
Regards
koli

Exception when running JSF Tags

Hi,
I am using MyEclipse 5.0.1 GA and jboss-4.0.3SP1. I am trying out a small JSF tag where the command button is not getting displayed and if i click the refresh button three i am getting this error. could anyone tell me what exactly the problem is.
Exception
org.apache.jasper.JasperException: /one.jsp(11,4) No tag "form" defined in tag library imported with prefix "f"
     org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:39)
     org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:405)
     org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:196)
     org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:1308)
     org.apache.jasper.compiler.Parser.parseElements(Parser.java:1564)
     org.apache.jasper.compiler.Parser.parseBody(Parser.java:1793)
     org.apache.jasper.compiler.Parser.parseOptionalBody(Parser.java:1060)
     org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:1367)
     org.apache.jasper.compiler.Parser.parseElements(Parser.java:1564)
     org.apache.jasper.compiler.Parser.parse(Parser.java:126)
     org.apache.jasper.compiler.ParserController.doParse(ParserController.java:211)
     org.apache.jasper.compiler.ParserController.parse(ParserController.java:100)
     org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:146)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:267)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:255)
     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:556)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:293)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
     org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
one.jsp
<%@ page contentType="text/html" %>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<html>
<body>
This is my JSF page. <br>
<f:view>
<f:form>
     <h:commandButton id="cmd" action="" value="Submit" />
</f:form>
     </f:view>
</body>
</html>
web.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.4" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<context-param>
<param-name>javax.faces.CONFIG_FILES</param-name>
<param-value>/WEB-INF/faces-config.xml</param-value>
</context-param>
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>0</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>*.faces</url-pattern>
</servlet-mapping>
</web-app>
faces-config.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE faces-config PUBLIC "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN" "http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
<faces-config >
     <application></application></faces-config>

No tag "form" defined in tag library imported with prefix "f"This error is clear and correct: the tag library defined with the prefix f does not have a tag named form. So you cannot use <f:form>. Likely you intended <h:form>.

How to include the first row of detail in every xquery transformed xml?

I am dealing with a XML file,where i need to publish to different BS.
First node will be a common node node which contains vital info,second node goes to one BS and third goes to another BS.
*<header></header>*
*<details></details> (they are unbounded, but the first detail tag which comes in the input file is a mandatory tag in such a way that it needs to be included in every transformed message)*
*<trailer></trailer>*
We need to apply x query transformation on it in such a way:
*</header></header>*
*<1st detail></1st detail>*
*<detail></detail> (2nd row of detail in input file)* -------------------------> Goes to BS1
*<trailer></trailer>..*
*<header></header>*
*<1st detail></1st detail>*
*<detail></detail> (3rd row of detail in input file)* ----------------------------->Goes to BS2
*<trailer></trailer>*..
And so on.
Now, the problem is how to include the first row( *1st detail* ) of detail in every xquery transformed xml?

are you looping of this input with a for each?
/yourdata/details[1] should return always the first detail element.
or before the for each do an assing of this first detail element to "generic_details_var"
and use this var in every looping iteration (in an assign or as input for xquery)

JSF tags are not rendered in error page

I have configured error page for HTTP 404 error in web.xml like this
<error-page>
<error-code>404</error-code>
<location>/Common/error.jspx</location>
</error-page>
Faces Servlet is configured as follows
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>/faces/*</url-pattern>
</servlet-mapping>
My error page (error.jspx) looks like this
<?xml version='1.0' encoding='UTF-8'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1" xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html" xmlns:trh="http://myfaces.apache.org/trinidad/html"
xmlns:tr="http://myfaces.apache.org/trinidad" xmlns:c="http://java.sun.com/jsp/jstl/core">
<jsp:directive.page contentType="text/html;charset=UTF-8"/>
<html>
<head>
<title>Error Page</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
</head>
<body id="b1">
<h4 style="color:red">An Error Occured. Please click Back button or Signout.</h4>
<input type="button" value="Back" onclick="history.back()"/>
<tr:commandButton id="cb1" text="SIGN OUT" action="exit" actionListener="#{Login.LogOut}"/>
</body>
</html>
</jsp:root>
When I deploy application and run into 404 error, page displays error message with only Back button. I don't see SingOut button. I have checked url and it follows /faces/* pattern. Still to double check, I made a change and configured servlet mapping in web.xml as
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>/faces/*</url-pattern>
<url-pattern>*.jspx</url-pattern>
</servlet-mapping>
Still commandButton is not rendered. I understand that my error page don't have access to FacesContext or not going through Faces Servlet. I know this is a small issue, but couldn't figure out what can be done. I have also tried using .xhtml and .jsf as per googled suggestion. But no luck
I have tried different solutions to my problem and googled for solutions. But I couldn't get it resolved.
So can you please provide any suggestions...
Edited by: user1818355 on May 22, 2013 2:29 PM

I think my faces servlet is configured to handle URLs having /faces/* pattern. I don't have any folder named with faces but I can access all my web pages which have /faces/ in their url. All jspx pages in application are configured in task flows. So I think they have access in FacesContext. But error page is configured in only web.xml and some how it is missing access to FacesContext and not rendering JSF tags. Any help?

How to run generated JSF tags ?

I am beginner in JSF. I would like execute JSF tags generated dynamically by XSLT, but in the JSP page,
these tags are not interpreted. Does anyone has the solution ? Thanks a lot.
Example below is only a simple test,
ResearchBean.java :
public String researchAction() {
    // Actually, htmlResponse is the output string after the XSLT transformation, and it contains JSF tags
    htmlResponse = "<h:outputText value=\"Text\"/>";
    return "response";
}response.xhtml :
<f:view xmlns:f="http://java.sun.com/jsf/core
xmlns:h="http://java.sun.com/jsf/html
<html>
#{researchBean.htmlResponse}
</html>
</f:view>In the page received by the browser, <h:outputText value="Text"/> isn't replaced by the html code.
Edited by: wondergarance on Jul 2, 2009 1:24 PM

The JSF tags are apparently generated after the FacesServlet has done its work. You in fact need to pass the generated output through the FacesServlet again. If you're using a servlet/filter to run XSLT, you need to run it before the FacesServlet kicks in. You can control the servlet/filter invocation order in the web.xml.

Unable to view jsp page containing jsf tags

I'm pretty new to this JSF world, so facing lot of problems. I have installed JWSDP ver 1.2 When I start tomcat and specify URL http://localhost:8080 the site goes in waiting phase for ever. So even I'm not able to view/run the samples provided for jsf.
Moreover, i have created a simple appln to test jsf tag, but it's giving following error:
javax.servlet.ServletException: This absolute uri (http://java.sun.com/jsf/core) cannot be resolved in either web.xml or the jar files deployed with this application
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:207)
I don't know where the problem is. The code for sample i have downloaded from http://www.horstmann.com/corejsf/tutorial.html
but with no success in running jsf app.
anyone know the reason, why??
Thanx in Advance,
K.K.

Roger, here are the contents of log file.
Here goes the contents of launcher.server.log :
Sep 17, 2003 10:25:07 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
INFO: Reading descriptors ( dom ) 921
Sep 17, 2003 10:25:07 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
INFO: Reading descriptors ( dom ) 171
Sep 17, 2003 10:25:08 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
INFO: Reading descriptors ( dom ) 781
Sep 17, 2003 10:25:08 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
INFO: Reading descriptors ( dom ) 200
Sep 17, 2003 10:25:09 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
INFO: Reading descriptors ( dom ) 190
Sep 17, 2003 10:25:09 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
INFO: Reading descriptors ( dom ) 71
Sep 17, 2003 10:25:09 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
INFO: Reading descriptors ( dom ) 80
Sep 17, 2003 10:25:09 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
INFO: Reading descriptors ( dom ) 290
Sep 17, 2003 10:25:09 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
INFO: Reading descriptors ( dom ) 110
Sep 17, 2003 10:25:09 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
INFO: Reading descriptors ( dom ) 50
Sep 17, 2003 10:25:10 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
INFO: Reading descriptors ( dom ) 341
Sep 17, 2003 10:25:10 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
INFO: Reading descriptors ( dom ) 170
Sep 17, 2003 10:25:10 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
INFO: Reading descriptors ( dom ) 90
Sep 17, 2003 10:25:12 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8080
Sep 17, 2003 10:25:12 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 6670 ms
Sep 17, 2003 10:25:14 AM org.apache.catalina.core.StandardService start
INFO: Starting service Java Web Services Developer Pack
Sep 17, 2003 10:25:14 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Java Web Services Developer Pack/1.2
Sep 17, 2003 10:25:15 AM org.apache.catalina.core.StandardHost getDeployer
INFO: Create Host deployer for direct deployment ( non-jmx )
Sep 17, 2003 10:25:46 AM org.apache.struts.util.PropertyMessageResources <init>
INFO: Initializing, config='org.apache.struts.util.LocalStrings', returnNull=true
Sep 17, 2003 10:25:46 AM org.apache.struts.util.PropertyMessageResources <init>
INFO: Initializing, config='org.apache.struts.action.ActionResources', returnNull=true
Sep 17, 2003 10:26:15 AM org.apache.struts.util.PropertyMessageResources <init>
INFO: Initializing, config='org.apache.webapp.admin.ApplicationResources', returnNull=true
Sep 17, 2003 10:26:24 AM com.sun.xml.rpc.server.http.JAXRPCContextListener contextInitialized
INFO: JAX-RPC context listener initializing
Sep 17, 2003 10:26:26 AM com.sun.xml.rpc.server.http.JAXRPCServletDelegate init
INFO: JAX-RPC servlet initializing
And here the contents of jwsdp_log :
2003-09-17 10:25:14 createObjectName with StandardEngine[Catalina]
2003-09-17 10:25:14 preRegister with Catalina:type=Logger
2003-09-17 10:25:54 createObjectName with StandardEngine[Catalina].StandardHost[localhost].StandardContext[jaxrpc-HelloWorld]
2003-09-17 10:25:55 preRegister with Catalina:type=Logger,path=/jaxrpc-HelloWorld,host=localhost
2003-09-17 10:26:28 createObjectName with StandardEngine[Catalina].StandardHost[localhost].StandardContext[jsf-cardemo]
2003-09-17 10:26:28 preRegister with Catalina:type=Logger,path=/jsf-cardemo,host=localhost

Problem with XML in APEX ORA-06502

i, I have a problem with XML generation, I developed an application in APEX, and in a html page I have this process:
declare
l_XML varchar2(32767);
begin
select xmlElement
"iva",
xmlElement("numeroRuc",J.RUC),
xmlElement("razonSocial", J.RAZON_SOCIAL),
xmlElement("idRepre", J.ID_REPRE),
xmlElement("rucContador", J.RUC_CONTADOR),
xmlElement("anio", J.ANIO),
xmlElement("mes", J.MES),
xmlElement
"compras",
select xmlAgg
xmlElement
"detalleCompra",
--xmlAttributes(K.ID_COMPRA as "COMPRA"),
xmlForest
K.COD_SUSTENTO as "codSustento",
K.TPLD_PROV as "tpldProv",
K.ID_PROV as "idProv",
K.TIPO_COMPROBANTE as "tipoComprobante",
to_char(K.FECHA_REGISTRO, 'DD/MM/YYYY') as "fechaRegistro",
K.ESTABLECIMIENTO as "establecimiento",
K.PUNTO_EMISION as "puntoEmision",
K.SECUENCIAL as "secuencial",
to_char(K.FECHA_EMISION, 'DD/MM/YYYY') as "fechaEmision",
K.AUTORIZACION as "autorizacion",
to_char(K.BASE_NO_GRA_IVA, 9999999999.99) as "baseNoGraIva",
to_char(K.BASE_IMPONIBLE, 9999999999.99) as "baseImponible",
to_char(K.BASE_IMP_GRAV, 9999999999.99) as "baseImpGrav",
to_char(K.MONTO_ICE, 9999999999.99) as "montoIce",
to_char(K.MONTO_IVA, 9999999999.99) as "montoIva",
to_char(K.VALOR_RET_BIENES, 9999999999.99) as "valorRetBienes",
to_char(K.VALOR_RET_SERVICIOS, 9999999999.99) as "valorRetServicios",
to_char(K.VALOR_RET_SERV_100, 9999999999.99) as "valorRetServ100"
xmlElement
"air",
select xmlAgg
xmlElement
"detalleAir",
xmlForest
P.COD_RET_AIR as "codRetAir",
to_char(P.BASE_IMP_AIR, 9999999999.99) as "baseImpAir",
to_char(P.PORCENTAJE_AIR, 999.99) as "porcentajeAir",
to_char(P.VAL_RET_AIR, 9999999999.99) as "valRetAir"
from ANEXO_COMPRAS P
where P.ID_COMPRA = K.ID_COMPRA
AND P.ID_INFORMANTE_XML = K.ID_INFORMANTE_XML
xmlElement("estabRetencion1", K.ESTAB_RETENCION_1),
xmlElement("ptoEmiRetencion1", K.PTO_EMI_RETENCION_1),
xmlElement("secRetencion1", K.SEC_RETENCION_1),
xmlElement("autRetencion1", K.AUT_RETENCION_1),
xmlElement("fechaEmiRet1", to_char(K.FECHA_EMI_RET_1,'DD/MM/YYYY')),
xmlElement("docModificado", K.DOC_MODIFICADO),
xmlElement("estabModificado", K.ESTAB_MODIFICADO),
xmlElement("ptoEmiModificado", K.PTO_EMI_MODIFICADO),
xmlElement("secModificado", K.SEC_MODIFICADO),
xmlElement("autModificado", K.AUT_MODIFICADO)
from SRI_COMPRAS K
WHERE K.ID IS NOT NULL
AND K.ID_INFORMANTE_XML = J.ID_INFORMANTE
AND K.ID BETWEEN 1 AND 25
).getClobVal()
into l_XML
from ANEXO_INFORMANTE J
where J.ID_INFORMANTE =:P3_MES
and J.RUC =:P3_ID_RUC
and J.ANIO =:P3_ANIO
and J.MES =:P3_MES;
--HTML
sys.owa_util.mime_header('text/xml',FALSE);
sys.htp.p('Content-Length: ' || length(l_XML));
sys.owa_util.http_header_close;
sys.htp.print(l_XML);
end;
Now my table has more than 900 rows and only when I specifically selected 25 rows of the table "ANEXO_COMPRAS" in the where ( AND K.ID BETWEEN 1 AND 25) the XML is generated.+
I think that the problem may be the data type declared "varchar2", but I was trying with the data type "CLOB" and the error is the same.+
declare
l_XML CLOB;
begin
--Oculta XML
sys.htp.init;
wwv_flow.g_page_text_generated := true;
wwv_flow.g_unrecoverable_error := true;
--select XML
select xmlElement
from SRI_COMPRAS K
WHERE K.ID IS NOT NULL
AND K.ID_INFORMANTE_XML = J.ID_INFORMANTE
).getClobVal()
into l_XML
from ANEXO_INFORMANTE J
where J.ID_INFORMANTE =:P3_MES
and J.RUC =:P3_ID_RUC
and J.ANIO =:P3_ANIO
and J.MES =:P3_MES;
--HTML
sys.owa_util.mime_header('text/xml',FALSE);
sys.htp.p('Content-Length: ' || length(l_XML));
sys.owa_util.http_header_close;
sys.htp.print(l_XML);
end;
The error generated is ORA-06502: PL/SQL: numeric or value error+_
Please I need your help. I don`t know how to resolve this problem, how to use the data type "CLOB" for the XML can be generate+

JohannaCevallos07 wrote:
Now my table has more than 900 rows and only when I specifically selected 25 rows of the table "ANEXO_COMPRAS" in the where ( AND K.ID BETWEEN 1 AND 25) the XML is generated.+
I think that the problem may be the data type declared "varchar2", but I was trying with the data type "CLOB" and the error is the same.+
The error generated is ORA-06502: PL/SQL: numeric or value error+_
Please I need your help. I don`t know how to resolve this problem, how to use the data type "CLOB" for the XML can be generate+The likeliest explanation for this is that length of the XML exceeds 32K, which is the maximum size that <tt>htp.p</tt> can output. A CLOB can store much more than this, so it's necessary to buffer the output as shown in +{message:id=4497571}+
Help us to help you. When you have a problem include as much relevant information as possible upfront. This should include:
<li>Full APEX version
<li>Full DB/version/edition/host OS
<li>Web server architecture (EPG, OHS or APEX listener/host OS)
<li>Browser(s) and version(s) used
<li>Theme
<li>Template(s)
<li>Region/item type(s) (making particular distinction as to whether a "report" is a standard report, an interactive report, or in fact an "updateable report" (i.e. a tabular form)
And always post code wrapped in <tt>\...\</tt> tags, as described in the FAQ.
Thanks

Problem in xml query

Hi
I am working on BLS and having problem in xml query.I want to perform some calculation over xml columns.Than total of this as a new column.I can do this part in logic editor itself but can i do these both task by XSLT.
Can be made our own XSLT for this ?
I am feeling kind of fear to xslt. Can anybody help me in this.
Thanks a lot in advance
thomas

Ram,
In xMII there is a list of predefined xslt transforms that do something similar to what you are explaining. The 3 that I think may be what you are looking for are
they are under Calculation Transformations and Subtotal Transformation take a look at these and tell me if they are doing what you want to accomplish. In the xMII help file do a search on Inline Transforms or navigate to Advanced Topics -> Inline Transforms -> Predefined Inline Transforms. In this section there are examples of how to use these transforms and apply them in the query templates. If this is not what you are looking for can you explain in a little more detail along with a simple example of how you want this transform to work. Also why do you want to use xslt if you can already accomplish this in BLS?
Regards,
Erik

JSP ${} expressions in JSF tag attributes

Does anyone know why the expert group decided not to allow ${} style expressions within JSF tag attributes? I understand that a different syntax is needed to implement the 'late binding' #{} expressions used to link input controls to form beans, but not why the JSF tags actually prevent the use of immediately evaluated ${} expressions for accessing variables in the page scope in JSP 2.0.
I know there has been a lot of discussion about this and other threads mention a security loophole that would be opened up by allowing expressions like #{blah.${someProperty}}, but I'm not sure why this sort of thing would cause a problem. Is there any way to enable this behaviour, such as editing the JSF tag library descriptors to allow runtime expressions (horrible though that sounds)? Or perhaps another JSF implementation that supports both immediately evaluated and late-binding expressions? It seems a rather unnecessary restriction that is going to cause much confusion and mistyping for all...
Thanks in advance,
Keith.

Thanks Adam, I see the problem now. It's a fairly obscure loophole but serious nonetheless. Of course, this problem could also be avoided by not using request parameters within JSF tags as it doesn't affect the majority of legitimate uses for expressions.
I have to disagree with you about mixing ${} and #{} expressions though. The majority of developers will be used to writing ${} expressions in JSTL and JSP text and so will expect them to do work the same in JSF tags. Judging by the number of posts in this forum about being unable to use page scope variables in JSF tags this issue is already confusing a lot of people.
As a rule of thumb, "use ${} for expressions that are output to the page and #{} for binding controls to backing beans and invoking methods" (which perform clearly distinct functions) is a lot simpler and easier to learn IMHO than the current one, which is "use ${} for expressions that are output to the page except within a JSF tag, where you use #{} for the same thing and also to update form values and invoke action methods"! (OK, I'm exaggerating a little for effect, but you get the point... :-)
I agree that mixing both types of expression in the same attribute might be a little confusing, but this is an unlikely edge case that should probably be prevented in value binding or action attributes anyway. It's more of an issue for label values where mistyping one for the other is already very common and, although not especially difficult to debug, is just another pitfall awaiting the unwary JSP developer. I'm not sure that JSP expressions would be much more difficult to debug anyway as the value and method bindings will simply not work, which is pretty obvious as soon as you try and test the thing.
Is this something that the EG would be prepared to reconsider for the next release of JSF, or perhaps getting the security loophole addressed in the next JSP spec? In the meantime, is there any reason that developers shouldn't enable runtime expressions in the TLD file provided that they're willing to live with the consequences?
(Sorry to harp on about it, but I've already had several complaints about this after recommending JavaServer Faces for a major development project at ingenta.com.)
Many thanks,
Keith.

Problem Transforming XML to JSF tags

Similar Messages

Maybe you are looking for