Jdeveloper ADF

Tip - Hiding unwanted display attributes in Control Hints

2011-01-31T13:43:00.000-08:00

For Search Query Screens:

At times we add transient attributes to the View Object maybe for some internal calculations and they are unwanted for display.
These unwanted display attributes show up in the "Add Fields" option of the Query screen.
Make sure you hide these attributes from Control Hints at the time of development. Edit Attribute --> Control Hints -->Display Hint. Change this to "Hide".

This avoids user confusion for search criterion and certainly does not haunt you as bugs in development cycle :)

Do you deal with Master-Child applications in your application?

2010-08-18T09:15:00.000-07:00

Some tips if your ADF application has child applications included as jars to your Master application.
1. Always have a defined directory structure for the model. Do not use the default provided by the framework.
e.g. The Model.jpx of Master app should be orgName.appName.model
whilel the Model.jpx for Child app should be orgName.appName.childappName.model

2. There should also be a defined/different directory structure for DataBindings.cpx
e.g. The DataBindings.cpx of Master app should be under orgName.appName.view
and that of Child app should be orgName.appName.childappName.view

This helps avoiding the below warning
WARNING: The commonly named resources listed below could cause reusability errors for your consumers.

and eventually the Error
oracle.jbo.JboException: JBO-34010: The "view/DataBindings.cpx" descriptor appears in the application classpath more than once:

You might also want to do a clean build if you face this error or delete the remains of the application from
JDeveloper\system11.1.1.2.36.55.36\o.j2ee\drs folder.

Custom Splash screen for ADF Faces

2010-06-18T12:27:00.000-07:00

Do you want to get rid of the deafult oracle "O Loading..." splash screen to display your own message?

I had to replace this logo to put my company logo.
Here is what I did

The blog from Frank Nimphius explains it
http://www.oracle.com/technology/products/jdev/tips/fnimphius/custom_splash_screen/index.html

However to incorporate this into your own application which includes n number of skins and css style sheets.
1. You need to have the extended resourcce bundle name() under each that you have.
2. yo uneed not change your trinidad-config.xml file since it is designed to retrieve whatever number of s you have.
3. You need to insert the customized splash screen definition in each css sheet that you have.
4. Make sure you insert your image under af|document::spalsh-screen-icon
5. The text to displayed under the icon can be modified in the ResourceBundle provided in Frank's blog.
af_document.LABEL_SPLASH_SCREEN is where you can put your custom message.
Rest all the custom labels can be commented or used as required.

Hope this helps. It helped me :)

Quick Debug watch - very useful

2010-04-21T14:16:00.000-07:00

Just thought to sharing a feature of Jdeveloper 11G.
while debugging Jdeveloper gives you an option of quick debug watch on your variable.
For this just click on your variable in java file and you will see tiny tootip kinda popups.

You certainly can add your variables to watch list in a traditional way but this is something thats just quick and handy :)

Integrating XML BI Publisher using WebServices - Coming Soon--- Its here now

2010-04-18T11:43:00.000-07:00

Finally I am able to change the status of this article from COming Soon to actually writing it.
Things have just been busy at work with integration of XML BI Publisher and related improvisations.
I recently did a assignment of integrating BI publisher reports with the ADF application through webservices.
Once you get the get the core of this functionality you can easily adapt it to your application specific needs.
My need was to call bi publisher reports from commanLink on a table column.
SO the core of the functionality starts below.
1. Start with getting the WSDL for you projects Bi publisher :)
usually it is : http://XXXXX.XX/xmlpserver/services/PublicReportService?WSDL
2. Now using this WSDL we need to generated the Webservice proxy in our project.

Right click on your Model - >New - >Web Service Proxy

3. Go through the setup of setting up proxy as in below screens

In the next steps mention your package name and finish creating the proxy.

4. Next you need to set the necessary parameters to call your report and call necessary methods to run the reports. lets work with the generic report of world Sales.

From the generated proxy open the PublicReportServiceClient.java. This class has the main method where we can do the quick testing of our report.

You have to do 4 things to make this happen

1. Form the Request object

2. call runReport() with the request object.

3. return the response object

4. Write the report on the local drive or display the report on Fly.

Below code would write the report on local drive for us however I had to open the report on fly giving the user of saving the report. Just a small little java tweak in step 4 would give you that.

public static void main(String [] args) {

try{ publicReportServiceService = new PublicReportServiceService();

PublicReportService publicReportService = publicReportServiceService.getPublicReportService();

PublicReportServiceClient myPort = new PublicReportServiceClient();

String userName = "Admin"; String passWord = "Admin";

ReportRequest repReq = new ReportRequest(); //request

ReportResponse repRes = new ReportResponse(); //reponse

// Setting the parameters

repReq.setAttributeFormat("pdf");

repReq.setAttributeLocale("en-US");

repReq.setAttributeTemplate("World Sales");

repReq.setReportAbsolutePath("/Sales Manager/World Sales/World Sales.xdo ");

repRes = publicReportService.runReport(repReq, userName, passWord);

byte[] binaryBytes = repRes.getReportBytes(); OutputStream out = new FileOutputStream("C:\\XXX\\BI_Reports\\report.pdf");

out.write(binaryBytes);

out.close();

}catch(Exception e){

e.printStackTrace();

}

Volla!!! and you get the report.

You would have to play with ParamNameValue if you have any extra parameters to be set for the report e.g. report_number

Run the code and see for yourself and tweak the code as per your project need.

Post me questions if any.

Enjoy!!

Simple SelectOnChoice tip

2010-04-16T13:44:00.000-07:00

Taking a small time off this friday to blog.
There is a simple selectOneChoice tip that I came across.
In the JSp page if you have a selectOneChoice where a selectItems list comes from a java bean
and if this list does not have a default null value to show as first element.
Then you can specify the 1st value as blank with the following code.
af:selectOneChoice id="soc7" value="#{java.xyz}" autoSubmit="true" binding="#{javaBean.list}"
f:selectItem itemValue=" " itemLabel=" "/
f:selectItems value="#{javaBean.list}"id="si8"
af:selectOneChoice

This functionality can be achieved easily through viewobject where attribute has associated LOV with it. But not alwasy we would have an attribute associated with LOV.. so this tip is just for those exceptions.
Have a good Weekend!!

How ridiculous is that??

2010-03-23T14:48:00.001-07:00

Lately I have been facing some wierd problems with Jdeveloper.

The first.....

One of the viewObjects with a transient column stopped the application from running throwing a nullpointerException.

After removing the viewobject from dataModel and removing the transient column everything works fine. I recreate the viewobject with transient column again. I get the same error nullpointerException. Ok so I think the problem is transient column. But I need it.
Now I add back the transient column back to view object and try to run the application. And guess what It works. I am still wondering what the problem was.

Any takes????

Ok the second one is hilarious......

I added some code to my jspx page and when I ran the page i got the error while clicking the
java.net.ProtocolException: Didn't meet stated Content-Length .....blah blah blah...... ....

I made a trip all around the world to debug the error..
Called in my colleague for debug... there was some commented piece of code lying around... since it was uncomfortable to look at that redundant commented code that he removed it....

Guess what the page ran fine....
Why on earth a commented code would cause me a
Still wondering..
Am I missing something ????

Login Page : Default focus on UserName field and Login operation on Enter Key

2010-02-09T14:50:00.000-08:00

Today my task demanded me to focus on username field
Task : 1. Default focus on UserName field when page loads.
2. Login operation when user hits Enter key

Solution 1 : For a simple page the tasks becomes much easier
You just need these 2 lines of code.
af:document intialFocusId="inputText1" --- the intialFocusId property of af:document decides the focus of the field. It needs the id of the field in question.

af:inputText label="User Name" id="inputText1" clientComponent="true" ----clientComponent property should be set to true.

In my case there was a twist , where UserName field is on template and the af:document on home page that consumed the template.
Now I need to pass in the id of the inputText from template to the Home page.
I chose a backing bean way to do it.Luckily I had a backing bean associated with my template.

test.java
private String userNameId;
public void setUserNameId (String onLoadId) {
this.userNameId = userNameId; }
public String getUserNameId() {
FacesContext facesContext = FacesContext.getCurrentInstance();
String id = username.getClientId(facesContext);
this.setUserNameId(id);
return userNameId; }

The userNameId returns the Id of inputText from the template
This can be passed to the Home page something like this
af:document intialFocusId="#{test.userNameId}"

Solution 2: When user hits the enter key we need the login operationt o happen this can be achieved by setting the defaultCommand with the login button id.
something like this: af:form defaultCommand="loginButton"

Task Completed!! Time for Coffee.

Using ADF Faces popup with partialSubmit

2009-10-28T06:51:00.000-07:00

Recently I had tiff with popup functionality. So I decided to blog it out. The functionality I was implementing seemed simple at first but when I digged into several issues and improvisations.
Lets start with the basic popup functionality.
The popup functionality works with 2 components and
1. Using the popup Add component to the commandButton. e.g. af:commandButton id="id1" af:showPopupBehavior triggerType="click" popupId="feedbackPopup" align="afterStart" alignId="pt_cl6" af:commandToolbarButton

2. Defining the popup Below/above/anywhere on the page Add the component af:popup id="feedbackPopup" contentDelivery="lazyUncached" af:panelWindow modal="true" closeIconVisible="false"

You can add the required inputText / outputText fields and a Save button inside panelWindow.

3.Now we want a partilaSubmit functionality, by cliking the Save button data is committed to the database and the popup closes. For this we set partilaSubmit to true on Save button. e.g. af:commandButton text="Save" id="id2" partialSubmit="true" actionListener="#{testBean.onSaveActionListener}" af:commandButton

4. We add a backing bean testBean.java which processes the actionListener. The onSaveActionListener method performs 2 operations a. Commit the data by invoking commit() on Appmodule transaction b. actionListener does not close the popup in save action hence we need to close it with a javascript after commit(). e.g. FacesContext context = FacesContext.getCurrentInstance(); String popupId = popup.getClientId(context); StringBuilder jscript = new StringBuilder(); jscript.append("var popup = AdfPage.PAGE.findComponent('").append(popupId).append ("'); ").append("if (popup.isPopupVisible()==true) { ").append("popup.hide();}"); ExtendedRenderKitService erks = Service.getService(context.getRenderKit(), ExtendedRenderKitService.class); erks.addScript(context, jscript.toString());

5. we also need to add following to take care of popup component binding. Add this to af:popup on page binding="#{testBean.popup}"
Add this to testBean.java private RichPopup popup; public void setFeedbackpopup(RichPopup fpopup) { this.popup = popup; } public RichPopup getpopup() { return popup; }

Any other suggestions to implement the same are welcome.