Custom Tag Issue
I have a large DLL that has been converted to a cfx tag. I
get a generic error when I try to call it. I've been trying to
isolate the problem and believe it has to do with memory
access.
Does anyone know if ColdFusion is limiting access to memory
on that tag? If so, is there a way to adjust this?
Spectra requires 4.5.1 or 5.
Run the Spectra install to set up all the correct mappings
and the webtop. Then copy over the custom application. It's been
awhile since I've dug into the folder structure of the webtop, so I
don't have a complete list of steps required for a Spectra app
deployment. So you still have some work ahead of you.
Just make sure you backup your database before the install,
mirror it, or use a new schema for the installation and then switch
over your datasources.
I would recommend an old Spectra book you can probably find
on eBay.
http://www.forta.com/books/0789723654/
Similar Messages
-
Weblogic 10.3.6 - Custom Tag Issue
We have created custom tag in our application. It is working fine with Tomcat and Jetty Server but on Weblogic 10.3.6 we are getting below issue:
securities.jsp:301:5: The tag handler class was not found "jsp_servlet._tags.__money_tag".
<neutrino:money placeHolderKey="label.security.faceValue" labelKey="label.security.faceValue"
^------------^
securities.jsp:301:20: This attribute is not recognized.
<neutrino:money placeHolderKey="label.security.faceValue" labelKey="label.security.faceValue"
^------------^
securities.jsp:301:62: This attribute is not recognized.
<neutrino:money placeHolderKey="label.security.faceValue" labelKey="label.security.faceValue"
^------^
securities.jsp:302:4: This attribute is not recognized.
mandatory="true" moneyBoxColSpan="4" colSpan="6" validators="amount" errorPath="faceValue"
^-------^
securities.jsp:302:21: This attribute is not recognized.
mandatory="true" moneyBoxColSpan="4" colSpan="6" validators="amount" errorPath="faceValue"
^-------------^
securities.jsp:302:41: This attribute is not recognized.
mandatory="true" moneyBoxColSpan="4" colSpan="6" validators="amount" errorPath="faceValue"
^-----^
securities.jsp:302:53: This attribute is not recognized.
mandatory="true" moneyBoxColSpan="4" colSpan="6" validators="amount" errorPath="faceValue"
^--------^
securities.jsp:302:73: This attribute is not recognized.
mandatory="true" moneyBoxColSpan="4" colSpan="6" validators="amount" errorPath="faceValue"
^-------^
securities.jsp:303:4: This attribute is not recognized.
id="faceValue" path="faceValue" tabindex="13" viewMode="${view}" maxLength="16" />
^^
securities.jsp:303:19: This attribute is not recognized.
id="faceValue" path="faceValue" tabindex="13" viewMode="${view}" maxLength="16" />
^--^
securities.jsp:303:36: This attribute is not recognized.
id="faceValue" path="faceValue" tabindex="13" viewMode="${view}" maxLength="16" />
^------^
securities.jsp:303:50: This attribute is not recognized.
id="faceValue" path="faceValue" tabindex="13" viewMode="${view}" maxLength="16" />
^------^
securities.jsp:303:69: This attribute is not recognized.
id="faceValue" path="faceValue" tabindex="13" viewMode="${view}" maxLength="16" />
^-------^
securities.jsp:308:5: The tag handler class was not found "jsp_servlet._tags.__money_tag".
<neutrino:money placeHolderKey="label.security.price" labelKey="label.security.price"
^------------^
securities.jsp:308:5: The tag handler class was not found "jsp_servlet._tags.__money_tag".
<neutrino:money placeHolderKey="label.security.price" labelKey="label.security.price"
^------------^
securities.jsp:308:20: This attribute is not recognized.
<neutrino:money placeHolderKey="label.security.price" labelKey="label.security.price"
^------------^
securities.jsp:308:58: This attribute is not recognized.
<neutrino:money placeHolderKey="label.security.price" labelKey="label.security.price"
^------^
securities.jsp:309:4: This attribute is not recognized.
mandatory="true" moneyBoxColSpan="4" colSpan="6" validators="amount" errorPath="price"
^-------^
securities.jsp:309:21: This attribute is not recognized.
mandatory="true" moneyBoxColSpan="4" colSpan="6" validators="amount" errorPath="price"
^-------------^
securities.jsp:309:41: This attribute is not recognized.
mandatory="true" moneyBoxColSpan="4" colSpan="6" validators="amount" errorPath="price"
^-----^
securities.jsp:309:53: This attribute is not recognized.
mandatory="true" moneyBoxColSpan="4" colSpan="6" validators="amount" errorPath="price"
^--------^
securities.jsp:309:73: This attribute is not recognized.
mandatory="true" moneyBoxColSpan="4" colSpan="6" validators="amount" errorPath="price"
^-------^
securities.jsp:310:4: This attribute is not recognized.
id="price" path="price" tabindex="14" viewMode="${view}" maxLength="16" />
^^
securities.jsp:310:15: This attribute is not recognized.
id="price" path="price" tabindex="14" viewMode="${view}" maxLength="16" />
^--^
securities.jsp:310:28: This attribute is not recognized.
id="price" path="price" tabindex="14" viewMode="${view}" maxLength="16" />
^------^
securities.jsp:310:42: This attribute is not recognized.
id="price" path="price" tabindex="14" viewMode="${view}" maxLength="16" />
^------^
securities.jsp:310:61: This attribute is not recognized.
id="price" path="price" tabindex="14" viewMode="${view}" maxLength="16" />
^-------^
money.tag:2:25: The encoding specified on the page cannot be different than detected encoding for the file.
<%@ tag language="java" pageEncoding="UTF-8"%>
^----------^
money.tag:2:25: The encoding specified on the page cannot be different than detected encoding for the file.
<%@ tag language="java" pageEncoding="UTF-8"%>
^----------^
>Hi.
I had similar problems with appc.
Try to remove the line "<%@ tag language="java" pageEncoding="UTF-8"%>" or at least the pageEncoding attribute from the *.tag files.
In my case, I had no idea why the compiler complained about encoding. No UTF-8 specific characters were used and both, *.jsp and *.tag set the same encoding by directive.
If you get rid of the "The encoding specified on the page cannot be different than detected encoding for the file.", you will also get rid of the "The tag handler class was not found" and the resulting errors. -
Custom Tag issue and then ApplicationID?
Hello,
is there anybody out there who can help me with the following
problem:
I installed ColdFusion 4.5 Server on my Windows XP machine
and wanted to access an already built CF application. When
accessing
the main default page, i got the following error:
"Cannot find CFML template for custom tag
CFA_APPLICATIONINITIALIZE.
ColdFusion attempted looking in the tree of installed custom
tags but
did not find a custom tag with this name. "
I copied the same Administrator settings, code and folders
from the
working production server to my local machine and it just
doesn't seem
to work. (I couldn't find any differences to the working
application)
I tried to fix it by copying the custom tag folder (located
under allaire/spectra/customtags/) to C:\CFusion\CustomTags which
somehow cleared the previous error but gave me the following new
one:
"Error Occurred While Processing Request > Error
Diagnostic Information > This application can't be located by
name. Use ApplicationID instead"
Please, i appreciate any kind of comment on this post (i have
been trying to fix this for the past 3 days!)
Thanks,
bbintoSpectra requires 4.5.1 or 5.
Run the Spectra install to set up all the correct mappings
and the webtop. Then copy over the custom application. It's been
awhile since I've dug into the folder structure of the webtop, so I
don't have a complete list of steps required for a Spectra app
deployment. So you still have some work ahead of you.
Just make sure you backup your database before the install,
mirror it, or use a new schema for the installation and then switch
over your datasources.
I would recommend an old Spectra book you can probably find
on eBay.
http://www.forta.com/books/0789723654/ -
Hi all,
When my JAVA_HOME env variable is pointing to C:\jdk1.3, the JSP below which contains some custom tags fails to compile in Weblogic 5.1. However, when i change my JAVA_HOME env variable to C:\weblogic\jre1_2\jre, the same JSP compiles and deploys with no problems. I was of the opinion that the jre in jdk 1.3 is the same as jre1_2 which is bundled with weblogic 5.1. Does anyone know of any differences btw the Jre's or why the JSP below cannot be compiled when i use JDK1.3. Thanks for the help.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<%@ page import="java.util.Vector" %>
<%@ page import="com.spcs.premiere.common.framework.errorhandling.ErrorUtility" %>
<%@ page import="com.spcs.premiere.common.framework.errorhandling.PremiereLogger" %>
<%@ page import="org.grnds.structural.web.GrndsServletException" %>
<%@ taglib uri="/tlds/profiling/profile.tld" prefix="profile" %>
<%@ page import="com.spcs.premiere.web.common.HTMLListBuilder" %>
<%@ page import="com.spcs.premiere.web.common.ListParametersDomain" %>
<%@ page import="com.spcs.premiere.web.common.PremiereConstants" %>
<%@ page import="com.spcs.premiere.ejb.authentication.LoginDomain" %>
<html>
<head>
<title>Premiere Business...Assign Credit Class</title>
<LINK HREF="<%= request.getContextPath()%>/stylesheets/premiere.css" REL="stylesheet" TYPE="text/css">
<SCRIPT LANGUAGE="javascript">
var winHandle=window.dialogArguments;
function userFocus()
window.document.SupervisorLoginForm.SupervisorUserName.focus();
</SCRIPT>
</head>
<body onload="userFocus();">
<%
try{
%>
<TABLE WIDTH="100%" HEIGHT="100%" CLASS="groupbox">
<TR>
<TABLE WIDTH="100%" HEIGHT="75%" CLASS="groupbox">
<TR HEIGHT="15%"></TR>
<FORM NAME="SupervisorLoginForm" ACTION="<%= request.getContextPath() %>/Premiere/AddAccountConversation/SupervisorLogin" METHOD="post" TARGET="_self">
<TR HEIGHT="15%">
<TD align=center><LABEL NAME="SupervisorUserNameLabel">User ID:</LABEL></TD></TD>
<TD align=left><INPUT TYPE="text" NAME="SupervisorUserName" MAXLENGTH="20" SIZE="20" TABINDEX="1"></TD></TR>
</TR>
<TR>
<TD align=center> <LABEL NAME="SupervisorPasswordLabel">Password:</LABEL></TD></TD>
<TD align=left><INPUT TYPE="password" NAME="SupervisorPassword" TABINDEX="2" MAXLENGTH="20" SIZE="20" ENABLED></TD>
</TR>
<TR>
<TD COLSPAN="2" ALIGN="center"><BUTTON TYPE="submit" NAME="Login" TABINDEX="3" Class="button">Login</BUTTON></TD>
<TD></TD>
</TR></FORM>
<FORM NAME="CreditClassForm" ACTION="<%= request.getContextPath() %>/Premiere/AddAccountConversation/AssignCreditManually" METHOD="post">
<TR HEIGHT="60%">
<TD align=center> <LABEL NAME="SupervisorCreditClassLabel">Credit Class:</LABEL></TD></TD>
<TD align=left>
<profile:user WidgetName="CreditClass" Context="JSP" SubContext="SupervisorLogin" Evaluate="SUPERVISOR">
<%= HTMLListBuilder.buildHTMLList((ListParametersDomain)session.getAttribute("CreditClassCodes")) %></TD>
</profile:user>
<TD></TD>
</TR>
<TR></TR>
</TR></TBODY></TABLE>
</TR>
<TR>
<TABLE WIDTH="100%" HEIGHT="25%" CLASS="groupbox">
<TD></TD>
<TD align=right><BUTTON NAME="Cancel" Class="button" TABINDEX="4" ONCLICK="window.close()">Cancel</BUTTON>
<profile:user WidgetName="Save" Context="JSP" SubContext="SupervisorLogin" Evaluate="SUPERVISOR">
<BUTTON TYPE="submit" NAME="Save" TABINDEX="6" Class="button">Save</BUTTON>
</profile:user>
</TD>
</TR></TBODY></TABLE>
</TR></TBODY></TABLE>
</FORM>
<%
catch (Exception e)
LoginDomain loginDomain = (LoginDomain)session.getAttribute(PremiereConstants.LOGIN_DOMAIN);
PremiereLogger.log( "ERROR", loginDomain.getUserName()+" General Exception Error: ", e );
request.setAttribute(ErrorUtility.ERROR_CONDITION, ErrorUtility.getMessage(PremiereConstants.GENERIC_JSP_EXCEPTION_ERROR_ID) );
throw new GrndsServletException();
%>
</body>
</html>UUh, interesting.
Try to use the last Service Pack for 5.1 - i think it is sp9.
Hope it'll work. I've had some problems with XML parsing but they resolved when I installed the last SP... -
Hello,
When my JAVA_HOME environmental variable is pointing to c:\jdk1.3,
the JSP below fails to compile and does not deploy on Weblogic 5.1. However, when
i change the JAVA_HOME env variable to
c:\weblogic\jre1_2\jre, the JSP compiles and deploys without any problems. Since
jdk 1.3 uses the same jre1_2 as the jre1_2 that Weblogic 5.1 uses, what do you
guys think might be causing the JSP to fail to compile when i point to the JDK
instead of the JRE. Thanks for your anticipated help.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<%@ page import="java.util.Vector" %>
<%@ page import="com.spcs.premiere.common.framework.errorhandling.ErrorUtility"
%>
<%@ page import="com.spcs.premiere.common.framework.errorhandling.PremiereLogger"
%>
<%@ page import="org.grnds.structural.web.GrndsServletException" %>
<%@ taglib uri="/tlds/profiling/profile.tld" prefix="profile" %>
<%@ page import="com.spcs.premiere.web.common.HTMLListBuilder" %>
<%@ page import="com.spcs.premiere.web.common.ListParametersDomain" %>
<%@ page import="com.spcs.premiere.web.common.PremiereConstants" %>
<%@ page import="com.spcs.premiere.ejb.authentication.LoginDomain" %>
<html>
<head>
<title>Premiere Business...Assign Credit Class</title>
<LINK HREF="<%= request.getContextPath()%>/stylesheets/premiere.css" REL="stylesheet"
TYPE="text/css">
<SCRIPT LANGUAGE="javascript">
var winHandle=window.dialogArguments;
function userFocus()
window.document.SupervisorLoginForm.SupervisorUserName.focus();
</SCRIPT>
</head>
<body onload="userFocus();">
<%
try{
%>
<TABLE WIDTH="100%" HEIGHT="100%" CLASS="groupbox">
<TR>
<TABLE WIDTH="100%" HEIGHT="75%" CLASS="groupbox">
<TR HEIGHT="15%"></TR>
<FORM NAME="SupervisorLoginForm" ACTION="<%= request.getContextPath() %>/Premiere/AddAccountConversation/SupervisorLogin"
METHOD="post" TARGET="_self">
<TR HEIGHT="15%">
<TD align=center><LABEL NAME="SupervisorUserNameLabel">User ID:</LABEL></TD></TD>
<TD align=left><INPUT TYPE="text" NAME="SupervisorUserName" MAXLENGTH="20"
SIZE="20" TABINDEX="1"></TD></TR>
</TR>
<TR>
<TD align=center> <LABEL NAME="SupervisorPasswordLabel">Password:</LABEL></TD></TD>
<TD align=left><INPUT TYPE="password" NAME="SupervisorPassword" TABINDEX="2"
MAXLENGTH="20" SIZE="20" ENABLED></TD>
</TR>
<TR>
<TD COLSPAN="2" ALIGN="center"><BUTTON TYPE="submit" NAME="Login" TABINDEX="3"
Class="button">Login</BUTTON></TD>
<TD></TD>
</TR></FORM>
<FORM NAME="CreditClassForm" ACTION="<%= request.getContextPath() %>/Premiere/AddAccountConversation/AssignCreditManually"
METHOD="post">
<TR HEIGHT="60%">
<TD align=center> <LABEL
NAME="SupervisorCreditClassLabel">Credit Class:</LABEL></TD></TD>
<TD align=left>
<profile:user WidgetName="CreditClass" Context="JSP" SubContext="SupervisorLogin"
Evaluate="SUPERVISOR">
<%= HTMLListBuilder.buildHTMLList((ListParametersDomain)session.getAttribute("CreditClassCodes"))
%></TD>
</profile:user>
<TD></TD>
</TR>
<TR></TR>
</TR></TBODY></TABLE>
</TR>
<TR>
<TABLE WIDTH="100%" HEIGHT="25%" CLASS="groupbox">
<TD></TD>
<TD align=right><BUTTON NAME="Cancel" Class="button" TABINDEX="4" ONCLICK="window.close()">Cancel</BUTTON>
<profile:user WidgetName="Save" Context="JSP" SubContext="SupervisorLogin"
Evaluate="SUPERVISOR">
<BUTTON TYPE="submit" NAME="Save" TABINDEX="6" Class="button">Save</BUTTON>
</profile:user>
</TD>
</TR></TBODY></TABLE>
</TR></TBODY></TABLE>
</FORM>
<%
catch (Exception e)
LoginDomain loginDomain = (LoginDomain)session.getAttribute(PremiereConstants.LOGIN_DOMAIN);
PremiereLogger.log( "ERROR", loginDomain.getUserName()+" General Exception
Error: ", e );
request.setAttribute(ErrorUtility.ERROR_CONDITION, ErrorUtility.getMessage(PremiereConstants.GENERIC_JSP_EXCEPTION_ERROR_ID)
throw new GrndsServletException();
%>
</body>
</html>
[SupervisorLogin.jsp]
UUh, interesting.
Try to use the last Service Pack for 5.1 - i think it is sp9.
Hope it'll work. I've had some problems with XML parsing but they resolved when I installed the last SP... -
Custom tag lib issue with task flow in portal
Dear Experts,
I am facing an issue and need your guidance
I have a ADF task flow which is consumed in portal. My task flow uses a custom tag library.
When I run the task flow on portal I am facing following issue:
Caused by: oracle.jsp.parse.JspParseException:
Error: Encountered deferred syntax #{ in template text. If intended as a literal, escape it or set directive deferredSyntaxAllowedAsLiteral
at oracle.jsp.parse.JspParseTagXMLTextContainer.processAttributeForELFunctions(JspParseTagXMLTextContainer.java:118)
at oracle.jsp.parse.JspParseTagXMLTextContainer.processAttributeValue(JspParseTagXMLTextContainer.java:103)
at oracle.jsp.parse.JspParseTag.parseXMLSrc(JspParseTag.java:1565)
at oracle.jsp.parse.JspParseTag.parse(JspParseTag.java:1610)
at oracle.jsp.parse.JspParseTag.genXMLSrcTag(JspParseTag.java:886)
at oracle.jsp.parse.JspParseTag.parseXMLSrcNextTag(JspParseTag.java:780)
at oracle.jsp.parse.JspParseTag.parseXMLSrcBody(JspParseTag.java:1297)
at oracle.jsp.parse.OpenJspTagHandler.parseXMLSrcBody(OpenJspTagHandler.java:782)
at oracle.jsp.parse.JspParseTag.parseXMLSrc(JspParseTag.java:1572)
at oracle.jsp.parse.JspParseTag.parse(JspParseTag.java:1610)
at oracle.jsp.parse.OpenJspTagHandler.parse(OpenJspTagHandler.java:846)
at oracle.jsp.parse.JspParseTag.genXMLSrcTag(JspParseTag.java:923)
at oracle.jsp.parse.JspParseTag.parseXMLSrcNextTag(JspParseTag.java:780)
at oracle.jsp.parse.JspParseTag.parseXMLSrcBody(JspParseTag.java:1297)
at oracle.jsp.parse.OpenJspTagHandler.parseXMLSrcBody(OpenJspTagHandler.java:782)
at oracle.jsp.parse.JspParseTag.parseXMLSrc(JspParseTag.java:1572)
at oracle.jsp.parse.JspParseTag.parse(JspParseTag.java:1610)
at oracle.jsp.parse.OpenJspTagHandler.parse(OpenJspTagHandler.java:846)
at oracle.jsp.parse.JspParseTag.genXMLSrcTag(JspParseTag.java:923)
at oracle.jsp.parse.JspParseTag.parseXMLSrcNextTag(JspParseTag.java:780)
at oracle.jsp.parse.JspParseTag.parseXMLSrcBody(JspParseTag.java:1297)
at oracle.jsp.parse.OpenJspTagHandler.parseXMLSrcBody(OpenJspTagHandler.java:782)
at oracle.jsp.parse.JspParseTag.parseXMLSrc(JspParseTag.java:1572)
at oracle.jsp.parse.JspParseTag.parse(JspParseTag.java:1610)
at oracle.jsp.parse.OpenJspTagHandler.parse(OpenJspTagHandler.java:846)
at oracle.jsp.parse.JspParseTag.genXMLSrcTag(JspParseTag.java:923)
at oracle.jsp.parse.JspParseTag.parseXMLSrcNextTag(JspParseTag.java:780)
at oracle.jsp.parse.JspParseTag.parseXMLSrcBody(JspParseTag.java:1297)
at oracle.jsp.parse.JspParseTag.parseXMLSrc(JspParseTag.java:1572)
at oracle.jsp.parse.JspParseTagFile.parseXMLSrc(JspParseTagFile.java:341)
at oracle.jsp.parse.JspParseTagFile.parse(JspParseTagFile.java:256)
at oracle.jsp.parse.OracleJsp2Java.transformImpl(OracleJsp2Java.java:439)
at oracle.jsp.parse.OracleJsp2Java.transform(OracleJsp2Java.java:593)
at oracle.jsp.runtimev2.JspPageCompiler.attemptCompilePage(JspPageCompiler.java:691)
at oracle.jsp.runtimev2.JspPageCompiler.compileBothModes(JspPageCompiler.java:490)
at oracle.jsp.runtimev2.JspPageCompiler.parseAndGetTreeNode(JspPageCompiler.java:457)
at oracle.jsp.runtimev2.JspPageInfo.compileAndLoad(JspPageInfo.java:624)
at oracle.jsp.runtimev2.JspPageTable.compileAndServe(JspPageTable.java:645)
... 120 more
<XmlErrorHandler> <handleError> ADF_FACES-60096:Server Exception during PPR, #1Hi,
Make sure you have the JSTL tag library selected in you deployment plan. Go to Project Properties->Deployments->your_deployment_profile->WWB-INF/Lib Contributors and check JSTL.
Let me know if this worked for you!
Regards,
Mihai -
Good evening,
I'm trying to add a custom tag to an image in Aperture 2.0. I've looked all over the internet and find no examples what so ever of AS and Aperture 2.0.
I have a few guesses that produce one of two different errors - but no idea how to actually make this work. Any ideas ?
tell application "Aperture"
copy selection to theSel
repeat with curImg in theSel
class of curImg
--image version
-- make new custom tag at curImg with properties {name:"NewTag", value:"New Tag's Value"}
-- set aNewTag to make new custom tag with properties {name:"NewTag", value:"New Tag's Value"}
-- Aperture got an error: Can’t make or move that element into that container.
-- make new custom tag at end of curImg with properties {name:"NewTag", value:"New Tag's Value"}
-- make new custom tag at end of (curImg) with properties {name:"NewTag", value:"New Tag's Value"}
-- make new custom tag at end of custom tags of curImg with properties {name:"NewTag", value:"New Tag's Value"}
-- make new custom tag at end of curImg's custom tags with properties {name:"NewTag", value:"New Tag's Value"}
--Aperture got an error: Can’t make application "Aperture" into type specifier.
end repeat
end tellIf I recall, it was done because how tags were to be handled in 1.2 was very different from 1.1 and it was felt that developers shouldn't rely on implementation specific classes (unless they were SPI) for several other reasons (application portability being the big one here).
If it's felt that this was the wrong decision, please feel free to log an issue [1] against the RI (to date, no one has).
As to the 'borked' dependency URLs, please log an issue [1] if you find these. We have nightly builds going that work from a clean workspace and checking today's result, it seems ok.
[1] https://javaserverfaces.dev.java.net/issues -
Query reg adding custom tags in SOAP Header - AXIS Receiver Adapter
Hi All,
I need to send custom tags as mentioned below to my traget webservice application. I think I can do this with Receiver AXIS adapter but not sure how it can be done. Can any of you suggest?
<WSContext>
<FromAppId>ABC</FromAppId>
<ToAppId>XYZ</ToAppId>
</WSContext>
Thanks,If you want to add custom tags in the soap header, one possible solution is use XSLT mapping or Java mapping to create header first then do message mapping for mapping the payload structure between your source and target as usual.
So in operation mapping you sequence mapping like this... first XSLT mapping for custom tags for the SOAP Header followed by payload mapping.
Hope that helps.
Search SDN for XSLT Mapping for soap header. Already we have handled these issues. -
Custom Tag: pass my own type in as attribute
I thought I can pass any type as attribute into my custom tag. I tried, but failed. The exception is:
org.apache.jasper.JasperException: Unable to convert '${myType}' to class MyTpye for attribute myAttribute: java.lang.IllegalArgumentException: Property Editor not registered with the PropertyEditorManager.
I know I can pass the value in using PageContext attribute. However, still want to figure out how to do it through custom tag attribute.
Here's my taglig file:
<tag>
<name>myTag</name>
<tag-class>MyTagClass</tag-class>
<body-content>empty</body-content>
<attribute>
<name>myAttribute</name>
<required>true</required>
<rtexprvalue>true</rtexprvalue>
<type>MyType</type>
</attribute>
</tag>
What am I missing here? Thanks.Hi
Pls tell me how did you resolve this issue. I am also facing the same problem.
Thanks
Prakash -
Custom Tag output not being rendered in JSF
Hello,
I have the following for loop in a custom tag that I developed;
out.println("<ul>");
for (int i = 0; i < noOfDays; i++)
//out.println("<li><h:commandLink value=\"" +DateHelper.addDays(dtToday, i)+ "\" action=\"#{BookingBean.showAvailability}\"/></li>");
out.println("<li><a href=\"" +DateHelper.addDays(dtToday, i)+ "\">" DateHelper.addDays(dtToday, i) "</a></li>");
out.println("</ul>");
The issue I have is that the second line prints out fine whereas the first one (when uncommented) prints out the bullet points associated with a list but does not render the h:commandLink.
Any thoughts would be great.
Cheers,
RichHi,
You can not embade a JSF tag in your code as you did, try adding component as children to your custum tag
see this code as exemple : [HTMLDataTable.java|http://www.docjar.com/html/api/org/apache/myfaces/component/html/ext/HtmlDataTable.java.html] -
Custom Tag -- Custom Component problems with iframes
I have a "project" component that originally iterated over a list of models and created/renderered the corresponding (and fairly complex) interactive UI components for those models. On the client-side, the output from these were then organized neatly into "tabs" via CSS ... all on one page. Since these UI Components are so hefty, when any iteraction was done on one of them, the whole page had to re-render and things got just plain slow. To get around this limitation, I decided to have my "project" component no longer create the UI components himself, but instead generate an IFRAME that points to a page that will generate a single component. This way, any iteraction will just cause that single IFRAME to refresh.
Due to the fact that an IFRAME can only be populated by using the src attribute, I have created a page that contains a JSF View (<faces:view>) and inside is a single custom tag of mine (<mine:displayView>). Let's call this page singleDisplayView.jsf. I create iframes that point to singleDisplayView.jsf with different request params for each (singleDisplayView.jsf?modelName=Foo, singleDisplayView.jsf?modelName=Bar, etc.)
The displayView tag has one attribute called requestQueryString and I use the tag like so:
<t:displayView requestQueryString="<%=request.getQueryString()%>" />The displayView tag's class is DisplayViewTag. In DisplayViewTag::setProperties(UIComponent uiComponent) method, I get the model name out of the request map and set this property on the UIComponent.
The problem is that I'm noticing that as the main page (that contains these frames) loads, setProperties() is only being called twice. After that, the components created by subsequent iframes just seem to be using the modelName from the second frame.
Is there a syncronization issue I don't understand?
Any ideas?
Any help would be much appreciated.
Thanks in advance,
MarkOn a possibly related note, I read this in an article of the JSF application lifecycle:
In the first phase of the JSF lifecycle -- restore view -- a request comes
through the FacesServlet controller. The controller examines the request and
extracts the view ID, which is determined by the name of the JSP page.Could it be that the lifecycle is trying to reuse components from a single view, since all these iframes are pointing to the same page? -
Taglib problem: Cannot parse custom tag with short name table
Hello!
I am having problems deploying a jsp tag in web as. The same war file works fine on websphere, jboss. SAP web as seems to be complaining about the short name in the tld.
Can any body me to any known web as issues with jsp tags?
Thanks
[code]
Application error occurs during processing the request.
Details: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: Internal error while parsing JSP page /usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/dispear/servlet_jsp/disp/root/test.jsp.
at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:85)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.getClassName(JSPServlet.java:207)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.compileAndGetClassName(JSPServlet.java:369)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:164)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: com.sap.engine.services.servlets_jsp.lib.jspparser.exceptions.JspParseException: Cannot parse custom tag with short name table.
at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.xmlsyntax.CustomJspTag.action(CustomJspTag.java:129)
at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.ElementCollection.action(ElementCollection.java:52)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.initParser(JSPParser.java:307)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:74)
... 18 more
Caused by: com.sap.engine.services.servlets_jsp.lib.jspparser.exceptions.JspParseException: Unknown class name java.lang.Object.
at com.sap.engine.services.servlets_jsp.lib.jspparser.taglib.TagBeginGenerator.convertString(TagBeginGenerator.java:365)
at com.sap.engine.services.servlets_jsp.lib.jspparser.taglib.TagBeginGenerator.generateSetters(TagBeginGenerator.java:187)
at com.sap.engine.services.servlets_jsp.lib.jspparser.taglib.TagBeginGenerator.generateServiceMethodStatements(TagBeginGenerator.java:212)
at com.sap.engine.services.servlets_jsp.lib.jspparser.taglib.TagBeginGenerator.generate(TagBeginGenerator.java:269)
at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.xmlsyntax.CustomJspTag.action(CustomJspTag.java:127)
... 21 more
[/code]Hi Ray,
I am facing similar kind of issue.
Can you please help to resolve it?
Thanks in advance.
Logs are as below [Here I am using standard tag lib]::
Caused by: com.sap.engine.services.servlets_jsp.jspparser_api.exception.JspParseException: Cannot parse custom tag with short name [out].
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.xmlsyntax.CustomJspTag.action(CustomJspTag.java:183)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:59)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.JspIncludeDirective.action(JspIncludeDirective.java:51)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:59)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.JspElement.customTagAction(JspElement.java:994)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.JspElement.action(JspElement.java:228)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:59)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:69)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.GenerateJavaFile.generateJavaFile(GenerateJavaFile.java:72)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPProcessor.parse(JSPProcessor.java:270)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPProcessor.generateJavaFile(JSPProcessor.java:194)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPProcessor.parse(JSPProcessor.java:126)
at com.sap.engine.services.servlets_jsp.jspparser_api.JSPChecker.getClassName(JSPChecker.java:319)
at com.sap.engine.services.servlets_jsp.jspparser_api.JSPChecker.compileAndGetClassName(JSPChecker.java:248)
at com.sap.engine.services.servlets_jsp.jspparser_api.JSPChecker.getClassNameForProduction(JSPChecker.java:178)
at com.sap.engine.services.servlets_jsp.jspparser_api.JSPChecker.processJSPRequest(JSPChecker.java:109)
at com.sap.engine.services.servlets_jsp.jspparser_api.JspParser.generateJspClass(JspParser.java:154)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:193)
... 47 more
Caused by: com.sap.engine.services.servlets_jsp.jspparser_api.exception.JspParseException: Attribute [value] of [<c:out>] can accept only static values.
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.taglib.TagBeginGenerator.calculateAttributeValue(TagBeginGenerator.java:476)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.taglib.TagBeginGenerator.generateSetters(TagBeginGenerator.java:394)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.taglib.TagBeginGenerator.generateServiceMethodStatements(TagBeginGenerator.java:562)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.taglib.TagBeginGenerator.generate(TagBeginGenerator.java:678)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.xmlsyntax.CustomJspTag.action(CustomJspTag.java:181)
... 64 more
Regards,
Sankalp -
.exception.JspParseExcept Cannot parse custom tag with short name [out].
Hi
I have almost migrated an application from jboss to CE 7.1 sp3 maxdb 32 bit
however I am getting the following error on c:out tag of standard jslt.
Runtime error in processing of the JSP file [C:\usr\sap\CE1\J00\j2ee\cluster\apps\<....>\servlet_jsp\<application_context_name>\root\jsp\view\<jsp_name>.jsp].
Line:----
The error is: com.sap.engine.services.servlets_jsp.jspparser_api.exception.JspParseException: Cannot parse custom tag with short name [out].02004C4F4F50001F0000002D000012B000B0688132009833
Line:----
Do anybody have some idea why is it happening.
My guess would be because of jslt version mismatch. but its working fine in jboss. I am not sure what version cE 7.1 support may be 1.2. any idea how to chek the supported version in the server.
The jsp code is something like
Line:----
<code>
<%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>
<%@ taglib prefix="c_rt" uri="http://java.sun.com/jstl/core_rt" %>
<c:url var="thumbnailStream" value="/do/<action_tag>">
<c_rt:param name="stream_id" value="<%= <variable1> %>"/>
<c:param name="stream_id_type" value="<variable2>"/>
<c:param name="content_kind" value="<variable3>"/>
</c:url>
<img border="0" src="<c:out value="$"/>">
</code>
Line:----
from the SAP help text its said that jslt is being overrided by server to use from global library rather than local webapplication library. Couls woud explain where is this global library located in the server directory.
Thx.
AshutoshHi are you able to solve this issue.I am getting similar kind of issue.
Logs for the same are ::
Caused by: com.sap.engine.services.servlets_jsp.jspparser_api.exception.JspParseException: Cannot parse custom tag with short name out.
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.xmlsyntax.CustomJspTag.action(CustomJspTag.java:183)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:59)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.JspIncludeDirective.action(JspIncludeDirective.java:51)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:59)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.JspElement.customTagAction(JspElement.java:994)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.JspElement.action(JspElement.java:228)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:59)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.ElementCollection.action(ElementCollection.java:69)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.GenerateJavaFile.generateJavaFile(GenerateJavaFile.java:72)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPProcessor.parse(JSPProcessor.java:270)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPProcessor.generateJavaFile(JSPProcessor.java:194)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPProcessor.parse(JSPProcessor.java:126)
at com.sap.engine.services.servlets_jsp.jspparser_api.JSPChecker.getClassName(JSPChecker.java:319)
at com.sap.engine.services.servlets_jsp.jspparser_api.JSPChecker.compileAndGetClassName(JSPChecker.java:248)
at com.sap.engine.services.servlets_jsp.jspparser_api.JSPChecker.getClassNameForProduction(JSPChecker.java:178)
at com.sap.engine.services.servlets_jsp.jspparser_api.JSPChecker.processJSPRequest(JSPChecker.java:109)
at com.sap.engine.services.servlets_jsp.jspparser_api.JspParser.generateJspClass(JspParser.java:154)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:193)
... 47 more
Caused by: com.sap.engine.services.servlets_jsp.jspparser_api.exception.JspParseException: Attribute value of <c:out> can accept only static values.
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.taglib.TagBeginGenerator.calculateAttributeValue(TagBeginGenerator.java:476)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.taglib.TagBeginGenerator.generateSetters(TagBeginGenerator.java:394)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.taglib.TagBeginGenerator.generateServiceMethodStatements(TagBeginGenerator.java:562)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.taglib.TagBeginGenerator.generate(TagBeginGenerator.java:678)
at com.sap.engine.services.servlets_jsp.jspparser_api.jspparser.syntax.xmlsyntax.CustomJspTag.action(CustomJspTag.java:181)
... 64 more -
Using a custom tag with a 2.3 servlet descriptor BUG?
Hi,
I just developed a Custom Tag and I'd like to use in my jsps.
If I add the jsp in my JDev project with the custom tag when I try to build the project I got this error:
Error(11): oracle.xml.parser.v2.XMLParseException: Invalid element 'listener' in content of 'web-app', expected elements '[context-param, servlet, servlet-mapping, session-config, mime-mapping, welcome-file-list, error-page, taglib, resource-ref, security-constraint, login-config, security-role, env-entry, ejb-ref]'.
It seems like when the jsp parser encounters the line with taglib it tries to parse the web.xml against a 2.2 version of the dtd. My web.xml begins with the correct dtd version (2.3). Can anyone tell me if this is a bug and eventually tell me how to solve it?
thanks,
GiovanniI repost this issue again, now with a simple test case.
If I wrote a simple custom tag:
import java.io.IOException;
import javax.servlet.jsp.tagext.TagSupport;
public class MyCustomTag extends TagSupport {
public int doStartTag() {
try {
pageContext.getOut().print("FOO");
} catch (IOException ioe) {
pageContext.getServletContext().log(ioe.getMessage(),ioe);
return(SKIP_BODY);
with the associated tld:
<?xml version = '1.0' encoding = 'windows-1252'?>
<taglib>
<tlibversion>1.0</tlibversion>
<jspversion>1.2</jspversion>
<shortname>try</shortname>
<uri>try</uri>
<info>A short description...</info>
<tag>
<name>mytag</name>
<tagclass>MyCustomTag</tagclass>
<bodycontent>EMPTY</bodycontent>
</tag>
</taglib>
and a jsp using the custom tag:
<%@ page contentType="text/html;charset=windows-1252"%>
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252">
<TITLE>
Hello World
</TITLE>
</HEAD>
<BODY>
<H2>
The current time is:
</H2>
<P>
<% out.println((new java.util.Date()).toString()); %>
<%@ taglib uri="try.tld" prefix="try" %>
<try:mytag />
</P>
</BODY>
</HTML>
all runs fine if I have a web.xml with the dtd version 2.2
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
<web-app>
<description>Empty web.xml file for Web Application</description>
<session-config>
<session-timeout>30</session-timeout>
</session-config>
<mime-mapping>
<extension>html</extension>
<mime-type>text/html</mime-type>
</mime-mapping>
<mime-mapping>
<extension>txt</extension>
<mime-type>text/plain</mime-type>
</mime-mapping>
<welcome-file-list>
<welcome-file>index.jsp</welcome-file>
<welcome-file>index.html</welcome-file>
</welcome-file-list>
</web-app>
but if I use the version 2.3 because I want filters,context listeners and so on:
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/j2ee/dtds/web-app_2_3.dtd">
<web-app>
<description>Empty web.xml file for Web Application</description>
<filter>
<filter-name>FilterRedirector</filter-name>
<filter-class>org.apache.cactus.server.FilterTestRedirector</filter-class>
</filter>
<!-- Filter Redirector URL mapping -->
<filter-mapping>
<filter-name>FilterRedirector</filter-name>
<url-pattern>/FilterRedirector/</url-pattern>
</filter-mapping>
<session-config>
<session-timeout>30</session-timeout>
</session-config>
<mime-mapping>
<extension>html</extension>
<mime-type>text/html</mime-type>
</mime-mapping>
<mime-mapping>
<extension>txt</extension>
<mime-type>text/plain</mime-type>
</mime-mapping>
<welcome-file-list>
<welcome-file>index.jsp</welcome-file>
<welcome-file>index.html</welcome-file>
</welcome-file-list>
</web-app>
I get the error I report in my last post. (the jsp doesn't compile) If I remove the custom tag from my jsp all works fine (filters, listeners,etc). In my project settings I use the 2.3 version of servlet.jar instead of the ServletRuntime that comes with JDeveloper.
Can anyone tell me how to resolve this issue (Using simple custom tag with a web application using the 2.3 servlet specs)?
Thanks in advance,
Giovanni
If I remove the filter secion all -
Custom tag library called multiple times
Hi ppl ,
I have a custom tag library which i use to populate some menu components. When i do call my custom tag library though , it is called multiple times, use case is as follows.
I have menu tabs and menu bars which thanks to Mr.Brenden is working splendidly as so:-
<af:menuTabs>
<af:forEach var="menuTab" items="#{bindings.menu.vwUserMenuTabRenderer.rangeSet}">
<af:commandMenuItem text="#{menuTab.MenuLabel}"
shortDesc="#{menuTab.MenuHint}"
rendered="true"
immediate="true"
selected="#{sessionScope.selectedMenuId == menuTab.MenuId }"
onclick="fnSetSelectedValue('#{menuTab.MenuId}')" >
</af:commandMenuItem>
</af:forEach>
</af:menuTabs>
<af:menuBar>
<af:forEach var="menuBar" items="#{bindings.menu.vwUserMenuBarRenderer.rangeSet}">
<af:commandMenuItem onclick="return clickreturnvalue()"
onmouseover="dropdownmenu(this, event,#{menuBar.MenuId}, '150px')"
onmouseout="delayhidemenu()"
text="#{menuBar.MenuLabel}"
action="#{menuBar.MenuUri}"
rendered="#{menuBar.ParentId == sessionScope.selectedMenuId}"
immediate="true" />
</af:forEach>
</af:menuBar>
</afc:cache>
now all of this code is within a subview , and just directly below the subview tag , i have the call to my custom tag library:-
<myCustomTagLib:menuCascade />
only issue now is that assuming i have in all 7 menu bar components, the doStartTag is called 7 times. the relevant code within my custom tag class is as follows :-
public int doStartTag() throws JspException {
return (EVAL_BODY_INCLUDE);
public int doEndTag() throws JspException {
try {
declareVariables();
return EVAL_PAGE;
}catch (Exception ioe) {
throw new JspException(ioe.getMessage());
and within my declareVariables method i do an out of the jscript ( out.print(jscript.toString()); ) which is a simple string generated based on certain conditions...
now it seems to be working fine on the front end , but when i view the source of the page, i notice that the declaration is called multiple times, and this happens because the doStartTag method is called multiple times, i haven't even nested the call to the custom tag within the menu components , any clue as to whats going wrong ?
Cheers
KHi,
if you add the following print statement
System.out.println("rendering "+FacesContext.getCurrentInstance().getViewRoot().getViewId());
Then the output in my case is
07/04/24 08:14:04 rendering /BrowsePage.jsp
07/04/24 08:14:05 rendering /otn_logo_small.gif
The image comes from the file system, which means it is rendered by the JSF lifecycle. If you reference the image with a URL then the lifecycle doesn't render the image but only refrences it.
To avoid your prepare render code to be executed multiple times, just check for jsp and jspx file extensions, which will guarantee that your code only executes for JSF pages, not for loaded files.
The reason why this happens is because the JSF filter is set to /faces , which means all files that are loaded through that path
Frank
Maybe you are looking for
-
I was told by comcast that we had a computer in the house with a malware virus, they even said that they were going to terminate our service if we did not get it fixed. Now this week we hear that there is a trojan malware virus, how do we get rid of
-
Hi all, When running APP, i faced this messeges 'Payment proposal could not be carried out' means payment proposal not completed. then i try to do manual payment thru f-53, system throwing error is " vendor account is blocked by payment run" How can
-
when ever i am about to add the file i double click on it and the box just dissapears does anyone else have this issue? please help me if you did!
-
At line-selection and user command
hi, is it possible to use both at line selecion and at user command at a time.
-
Argument count mismatch on mx.binding::PropertyWatcher()
I am using Flex Builder 3, and created an app that has imported a Livecycle form. The project "builds" fine, but when I try to run it, I get: ArgumentError: Error #1063: Argument count mismatch on mx.binding::PropertyWatcher(). Expected 3, got 2. If