ADF: Query-By-Example table filter bug

Status: open
Applies to JDeveloper: 11.1.1.2, 11.1.1.3

Today I tried if the Bug (discussed in http://forums.oracle.com/forums/message.jspa?messageID=3568706) is still reproducible.
And sadly to say: “Yes the bug still exists!”
The behaviour changed a bit but the table filtering feature still does not working as expected if used INSIDE PAGE FRAGMENT/TASKFLOW.
So take a look at the viewlet where I shortly explain the buggy behaviour.

Free online screen recorder

Download Testcase: http://www.box.net/shared/sviqlzzobp

Related resources

http://forums.oracle.com/forums/message.jspa?messageID=3568706
http://forums.oracle.com/forums/thread.jspa?threadID=2157454

TELDE - What's that?

If you are wondering what telde is all about then I would like to give a hint on a presentation my collegue Ulrich gave at DOAG 2009 : ADF 11g rich client development best practices . We are using TELDE for development, testing and so on...while developing Apps on the oracle stack (currently ADF11g/JDeveleloper/WebLogic/Oracle Enterprise Linux). So TELDE stands for

TEam Linux Development Environment

It consists of the following components right now:

Oracle Enterprise Linux 5.3

Oracle Database 11.1.0.7

Oracle WebLogic Server 11g

Oracle JDeveloper 11.1.1.x

Oracle Team Productivity Center

Hudson Continuous Integration Server 

OpenLDAP

SVN Server

running on VMWare.

So if you are interested in setting up such an environment, look at http://padora.blogspot.com

WLS: Monitoring Oracle JRockit JVM with JRockit Mission Control remotely

Status: resolved
JRockit Mission Control: 3.1.2
WebLogic: 10.3.2

Use case

You have the need to remotely monitor and profile the JRockit JVM(s) of Oracle WebLogic Server.

Solution

1. Install JRockit Mission Control on the client
2. Configure WebLogic Server Domain with JRockit JVM
3. Configure JRockit Management Server

Components/Products

	Product	Download
	Oracle® WebLogic Server	Download from OTN
	Oracle® JRockit Mission Control	Download from OTN

How to

Bereich	Beschreibung
Putty	Login as oracle on telde.local [oracle@telde ~]$ cd middleware/user_projects/domains/base_domain/ [oracle@telde base_domain]$ vi startWebLogic.sh
Putty/vi	Add the following java Options before starting the WLS instance: JAVA_OPTIONS="-Xmanagement:ssl=false,authenticate=false,port=7091" export JAVA_OPTIONS ${DOMAIN_HOME}/bin/startWebLogic.sh $* Save file and Close vi.
Putty	Start WLS [oracle@telde base_domain]$ ./startWebLogic.sh …. Notice the starting of the management server … [JRockit] Management server started on port 7091, ssl=false, authenticate=false. …
Client	Start JRockit Mission Control
JRMC	Create a new connection Enter Host Enter Port Click: Test connection => Status keeps “Unable to connect” Click: Finish Starting the console on the newly created connection you might receive the following exception: Could not open Management Console for telde.local.   com.jrockit.mc.rjmx.ConnectionException: Connection refused to host: 127.0.0.1; nested exception is:     java.net.ConnectException: Connection refused: connect     com.jrockit.mc.rjmx.ConnectionException: Connection refused to host: 127.0.0.1; nested exception is:         java.net.ConnectException: Connection refused: connect         at com.jrockit.mc.rjmx.ConnectionManager.connect(ConnectionManager.java:63)         at com.jrockit.mc.console.ui.actions.StartConsole$1.preConnect… So how to fix?
Putty	Stop WLS
	Edit startWebLogic.sh Add -Djava.rmi.server.hostname=<remotehost> to the java options so that it looks like
Putty/vi	.. JAVA_OPTIONS="-Djava.rmi.server.hostname=telde.local -Xmanagement:ssl=false,authenticate=false,port=7091" export JAVA_OPTIONS ${DOMAIN_HOME}/bin/startWebLogic.sh $* Save file and exit vi.
Putty	Start WLS once again [oracle@telde base_domain]$ ./startWebLogic.sh
JRMC	Now try to test connection again. Result should be
JRMC	Start the console and monitor CPU, Mem, seak for memory leaks, etc.

Resources

java.rmi.server.hostname (1.1 and later)

The value of this property represents the host name string that should be associated with remote stubs for locally created remote objects, in order to allow clients to invoke methods on the remote object. In 1.1.7 and later, the default value of this property is the IP address of the local host, in "dotted-quad" format.