Memory Leaking message when run the log in page in Jdev 11.1.2

Question

Hi
I am re design our 10g application in Jdev 11.1.2, I am using .jsf and ADF business component.
at the moment, the project has only two pages. login and home page.
when I run the login page, I see the message below. this is happening during the deployment process to the embeded weblogic
<ADFContext> <getCurrent> Automatically initializing a DefaultContext for getCurrent.
Caller should ensure that a DefaultContext is proper for this use.
Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
This message may be avoided by performing initADFContext before using getCurrent().
For more information please enable logging for oracle.adf.share.ADFContext at FINEST level.
Anyone know why?
thanks

Answer 1

Hi Timo
Thanks for your reply, I read the thread you pointed to.
however, I am not sure my is related to the case mentioned. I am re design the application from scratch in Jdev 11.1.2, and my adfc-config.xml is as simple as this:
<?xml version="1.0" encoding="windows-1252" ?>
<adfc-config xmlns="http://xmlns.oracle.com/adf/controller" version="1.2">
<view id="Login">
<page>/commom/Login.jsf</page>
</view>
<view id="home">
<page>/commom/home.jsf</page>
</view>
<control-flow-rule id="__2">
<from-activity-id>*</from-activity-id>
<control-flow-case id="__3">
<to-activity-id>Login</to-activity-id>
</control-flow-case>
</control-flow-rule>
<control-flow-rule id="__4">
<from-activity-id>Login</from-activity-id>
<control-flow-case id="__5">
<from-outcome>success</from-outcome>
<to-activity-id>home</to-activity-id>
</control-flow-case>
</control-flow-rule>
<managed-bean id="__1">
<managed-bean-name>backing_login</managed-bean-name>
<managed-bean-class>com.mycompany.view.backing.login</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
</adfc-config>
also, I am using a session filter registered in web.xml --- basically, if the page is not Login.jsf then redirect to Login.jsf page. but even though I removed the session filter.java from the web.xml , it still show the message.