Skip to main content

ADF Encountered deferred syntax #{ in template text.

OracleJSP error:
oracle.jsp.parse.JspParseException: 
Error: Encountered deferred syntax #{ in template text. 
If intended as a literal, escape it or set directive 
deferredSyntaxAllowedAsLiteral

This normally happens when you have some tag lib dependancy problems but this was 
not the case for me...

My problem: For some reason my model project had web stuff in it(public html etc) 
so I had to remove the public html stuff from my project and manually edit the
Model.jpr project file and remove the tag lib entries at the bottom o the file.
 
Go figure. 

 
 

Comments

  1. You're damn right, bro! It's the JDev being the culprit here.

    ReplyDelete
  2. I had the same error, I realized that the error was due to weblogic server and upon deleting the configuration settings of weblogic[delete directory which stores them, can be found in weblogic properties] and recreating them, it worked successfully

    ReplyDelete
  3. I had the same error, I found that clearing the configuration settings of weblogic server and recreating them solves it.For clearing, delete the directory which stores them, path can be found in weblogic properties in JDeveloper.

    ReplyDelete

Post a Comment

Popular posts from this blog

ADF sort of generic screen for tables with the same structure

We have a couple (about a hundred) of tables with the same structure (Code, Description, Create Date, Update Date). So I wanted to do something simple so that I did not have to create all these screens 1) EO   I created the EO based on one of the tables I had that had the above columns. I then Added a transient attribute called table name to my EO based on a groovy expression. (the expression needs to change as I am reading web tier stuff from the model layer but I will fix this later) I then generated a java class for my EO. And added the following overriden method to my newly created java class. protected StringBuffer buildDMLStatement(int i, AttributeDefImpl[] attributeDefImpl,   AttributeDefImpl[] attributeDefImpl2, AttributeDefImpl[] attributeDefImpl3, boolean b) {   StringBuffer statement = super.buildDMLStatement(   i, attributeDefImpl, attributeDefImpl2, attributeDefImpl3, b); return new StringBuffer(StringUtils.replace(statement.to...

MANIFEST.MF merge JDeveloper for an executable jar

Goto your project > properties. Then click on deployment in the menu. Edit or add a jar deployment profile. Fill in the details under jar options (select Include manifest and give it a main class name) Also remember that the merge functionality only works with a BLANK line at the end of the merge file. REALLY this caught me. My merge file contents: Class-Path: commons-codec-1.3.jar [...empty line here CRLF...]

Util code

public static MethodExpression getMethodExpression( String expr, Class returnType, Class[] argTypes){ FacesContext fc = FacesContext.getCurrentInstance(); ELContext elctx = fc.getELContext(); ExpressionFactory elFactory = fc.getApplication().getExpressionFactory(); return elFactory.createMethodExpression( elctx, expr, returnType, argTypes); } public static javax.faces.el.MethodBinding getMethodBinding( String expr, Class[] argTypes){ FacesContext fc = FacesContext.getCurrentInstance(); ELContext elctx = fc.getELContext(); return fc.getApplication().createMethodBinding(expr, argTypes); } SetPropertyListener listener = new SetPropertyListener( ActionEvent.class.getName()); listener.setFrom(link.getRoute()); listener.setValueExpression("to", JSFUtils.getValueExpression("#{pageFlowScope.route}", String.class)); action.addActionListener(listener); AdfFacesContext.getCurrentInstance().getPageFlowScope() .put("route", lin...