Skip to main content

JDeveloper 11.1.1.4.0

Ok so I have upgraded to the new version of JDev today, all seems good.
Let the fun and games commence. Will update this post once I have anything I spot.

Hmmn Gridlink Datasource and MultiData Source lots of reading up to do.
New Entitlement Grants in jazn look good.

Our applications seems to be working as before...

Spoke to soon :
1) java.sql.SQLException: Attempt to set a parameter name that does not occur in the SQL: defaultSelection
A) Dont map a bind variable with a default to a transient attribute in VO.

2) oracle.security.idm.ObjectNotFoundException: No User found matching the criteria
A) Think this is to do with the fact that our provider is the first in the list. Will investigate later as it has no impact.

3) One Screen is now vastly slower.
A) Make sure your tuning parameters are set this fixed it for me.

4) When trying to run one of our sub projects stand alone: oracle.adf.controller.security.AuthorizationException: ADFC-0619: Authorization check failed: 'oracle.jbo.uicli.binding.JUFormDef@192172f' 'VIEW'.
A) ???

Comments

  1. Haven't you faced the problem 2 ("No User found matching the criteria") on Jdev 11.1.1.3 ? I haven't upgraded to 11.1.1.4 yet, but I'm already getting this exception, since I have a custom authenticator in the providers list (and all of them are SUFFICIENT). Any ideas?

    ReplyDelete
  2. Hi Tomy,

    Havent got his on 11.1.1.3 but here is my config used on 11.1.1.3 and I didnt get the error:

    1) Added my custom authenticator
    2) Moved the my authenticator to the FIRST provider in the list.
    3) Marked it as SUFFICIENT
    4) Marked only the DefaultAuthenticator as SUFFICIENT.

    This worked for me. If this doesnt help answer the following questions for me:

    1) Is this error preventing you from logging in?
    2) Have you configured any other providers in your providers list.
    3) Your jazn-data.xml may not be configured correctly

    ReplyDelete
  3. Thanks! What should we do if we have to map a transient attribute to a Bind variable in a ViewCriteria?

    ReplyDelete

Post a Comment

Popular posts from this blog

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.    

JBO-25013: TooManyObjectsException

oracle.jbo.TooManyObjectsException: JBO-25013: Too many objects match the primary key oracle.jbo.Key[Key null ]. Ok so for you it may be trying to insert a duplicate record this should explain your problem (also check trigger they could be the cause.) NOTE: You can also try to create a new duplicate EO if you have a page with two VO's using the same EO. This could sort your problems. For me I needed to add a launch listener on my LOV and clear the cache of my vo. LOV <af:inputListOfValues id="NameId" popupTitle="#{bindings.Name.hints.label}" value="#{bindings.RolName1.inputValue}" label="#{bindings.RolName1.hints.label}" model="#{bindings.RolName1.listOfValuesModel}" required="#{bindings.RolName1.hints.mandatory}" columns="#{bindings.RolName1.hints.displayWidth}" shortDesc="#{bindings.RolName1.hints.tooltip}" launchPopupListener="#{backingBeanScope.backingBean.launchPop

OJDeploy: Documentation for the tool

Real DOCS:  http://docs.oracle.com/cd/E26098_01/user.1112/e17455/deploying_apps.htm#OJDUG645 OJDeploy Documentation if you run it from the command line - I keep looking for this so I though I would post it here so I remeber. Oracle JDeveloper Deploy 11.1.2.1.0.6081 Copyright (c) 2003, 2010, Oracle and/or its affiliates. All rights reserved. Usage:   ojdeploy -profile <name> -workspace <jws> [ -project <name> ] [ <options> ]   ojdeploy -buildfile <ojbuild.xml> [ <options> ]   ojdeploy -buildfileschema Arguments:   -profile               the name of the Profile to deploy   -workspace      full path to the JDeveloper Workspace file(.jws)   -project              name of the JDeveloper Project within the .jws where the Profile can be found. If omitted, the Profile is assumed to be in the Workspace.   -buildfile            full path to a build file for batch deploy   -buildfileschema  print XML Schema for the build file