Skip to main content

ADF Custom declarative component error 11.1.2

OK so I though the components where broken in 11.1.2 but it turns out it was just me who was broken.

Here a a couple of things I struggled with:

Naming yes I got the name of my custom component in declarativecomp-metadata.xml component file I had an extra l in my taglib-name. (if you get a blank page like me check the spelling then check it again)

I also put the folloing in my consuming project - dont know if it is necessary but it made me feel good:


<context-param>
  <param-name>javax.faces.FACELETS_VIEW_MAPPINGS
  <param-value>*.jsf;*.xhtml
<context-param>
<context-param>
  <param-name>javax.faces.FACELETS_SKIP_XML_INSTRUCTIONS
  <param-value>true
<context-param>
<context-param>
  <param-name>javax.faces.FACELETS_SKIP_COMMENTS
  <param-value>true
<context-param>
<context-param>
  <param-name>javax.faces.FACELETS_DECORATORS
  <param-value>oracle.adfinternal.view.faces.facelets.rich.AdfTagDecorator
<context-param>
<context-param>
  <param-name>javax.faces.FACELETS_RESOURCE_RESOLVER
  <param-value>oracle.adfinternal.view.faces.facelets.rich.AdfFaceletsResourceResolver
<context-param>


Also small tip for those who live in history the tab lib is Faclets Tag Libraries not JSP Tag Libraries this may save you a few seconds.


This article helped me a LOT:
http://download.oracle.com/docs/cd/E18941_01/tutorials/jdtut_11r2_40/jdtut_11r2_40.html

Labels

Labels:

Comments

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...
Post a Comment
Read more

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...
Post a Comment
Read more

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...]
1 comment
Read more