Infrastructure Software

Try restarting JDeveloper - it tends to solve the issue.
If you have reproducable steps to duplicate the problem let us know.

I have isolated this issue down to the faces-config file. I have two phase-listeners that I install. In the faces-config these go into the lifecycle.
If I have the statements
<lifecycle>
<phase-listener>eig.faces.lifecycle.RenderResponsePhaseListener</phase-listener>
<phase-listener>eig.faces.lifecycle.RestoreViewPhaseListener</phase-listener>
</lifecycle>
I only get rectangular boxes. If I remove the phase listener(s) with the statement
<lifecycle>
</lifecycle>
I get the appropriate components rendered in design view. I need my phase listeners, is there any workaround or fix to this problem? I did try removing one (since I have see issues in RAD which will not accept two listeners) but this had no effect.

I am facing the same problems too. It happened suddenly and I have not been able to restore it to the design view that it initially came up with. I tried to delete what you suggested and it still does not work. In my case I had:

<lifecycle>
<phase-listener>oracle.adf.controller.faces.lifecycle.ADFPhaseListener</phase-listener>
</lifecycle>
and I tried deleting the <phase-listener> and restarting JDeveloper.

The 'box' view is simply irritating.

I narrowed this down exactly to the phase listener. In fact I had a custom component that I thought might be causing the problem but I eliminated that as the cause. The only thing I will say is that during each "test" that I did I had to shutdown and restart JDeveloper. Just eliminating the phase-listener did not solve the problem UNTIL I restarted the tool

Changing faces-config.xml to remove the <phase-listener> tag and restarting JDeveloper does not help for me.
Can you please tell me the exact steps you are doing so I am sure I am not missing anything?
Thanks.

I am hoping someone from JDeveloper can give us a reason why. My current thinking is that JDeveloper is running some portion of the JSF Lifecycle in order to generate the design view. Extrapolating that, anything you might do to plugin to that cycle could cause this problem. Examples include areas in <application>, <factory>, <lifecycle>.

Note: After writing above I went back because I remembered I also had both a variable resolver and property resolver that was removed in my initial test. Sure enough if I put my variable and property resolver in there it also breaks design view. This sort of confirms my theory, if you plugin anything that might effect lifecycle process you will break design view. Thus I have three ways of breaking design view, adding a phase listener, adding a variable resolver, or adding a property resolver.

Does the phase listener compile and run successfully? If not, this could prevent the current VE from rendering correctly. The following works for me when I build the phase listener before registering it in the faces-config.

faces-config.xml:
<faces-config xmlns="http://java.sun.com/JSF/Configuration">
<lifecycle>
<phase-listener>project1.MyPhaseListener</phase-listener>
</lifecycle>
</faces-config>

MyPhaseListener.java:
package project1;

import javax.faces.event.PhaseListener;
import javax.faces.event.PhaseEvent;
import javax.faces.event.PhaseId;

public class MyPhaseListener implements PhaseListener
{

public MyPhaseListener()
{
}

public void beforePhase(PhaseEvent pe)
{
if (pe.getPhaseId() == PhaseId.RESTORE_VIEW)
System.out.println("Processing new Request!");

System.out.println("before - " + pe.getPhaseId().toString());
}


public void afterPhase(PhaseEvent pe)
{
System.out.println("after - " + pe.getPhaseId().toString());

if (pe.getPhaseId() == PhaseId.RENDER_RESPONSE)
System.out.println("Done with Request!\n");
}

public PhaseId getPhaseId()
{
return PhaseId.ANY_PHASE;
}
}

Yup, the phase listener compiles. It is definitely working because my solution depends upon it working. I am very happy with JDeveloper, extremely happy with ADF, and as far as things working I'm in pretty good shape ... with the exception of this design time issue.

Since there is not return value or side effects expected from the calls, I can only assume that when JDeveloper encounters a decorator(s) like these it drops into a raw visual design mode. No other explainatin

The JSF design time does execute the restore and render cycles similar to the runtime behavior.

So, if you have compiled phase listeners, they should be invoked as well.

Is it possible to provide a test case (war) with your phase listeners in place ? Will help us identify any potential bugs.

Ok I have isolated this issue. In my phase listener I had this line of code:

private static final Logger _logger = Logger.getLogger(EigRequest.class.getPackage().getName());

and I changed it to
private static final Logger _logger =
Logger.getLogger(EigRequest.class.getName());

and design mode started to work. I guess either of the above works for me although I do not understand why the line works when you run the application but not in design mode.

Moral to the story is if something fails in any one of these types of decorators you will drop into a raw view mode. The question I have is if errors are occuring how do I figure out where they may be. There is no indication that anything is wrong with the exception that you lose most of the design mode functionality.

This was not a compile issue, this was not a runtime issue. It took me quite a few hours of writing a test program to validate that it was not just writing a phase-listener issue; then launching, editing, relaunching the application to find the problem. I will say that a good portion of the code came from a Eclipse project. If you add the offending lines of code while using JDeveloper you do not loose design mode immediately. You only see the problem the next time you start JDeveloper which complicates finding the problem.

Does turning ON the diagnostic trace info in the preference reveal any useful info ?

Tools->Jsp and HTML Visual Editor->Show Design Time log

I have faced the same problem. I have created a web app from scratch using ADF and BC4J. I like the tool too.

I have a phase listener in place. This phase listener interacts with the BC4J model and is dependent on the fact that a user should be authenticated, and it makes sense that it breaks when it runs out of the application server context.

I have given a solution to this problem: since the design time view does not work when the phase listener breaks, I just made the listener to be unbreakable by surrounding the whole code with a try{}catch sentence, where the catch does not do anything. This is the structure of what I did:

public void beforePhase(PhaseEvent phaseEvent) {
try
{

/*
HERE IS THE WHOLE CODE OF MY LISTENER FUNCTION
*/

}
catch(Exception e)
{
System.out.println("")
}

}

It just worked.

Rafa

that works. I've also seen java.beans.Bean.isDesignTime() logic to make sure RT code does not get run.

st

Hi sdulepet, what menu option you referring with "Jsp and HTML Visual Editor"? I can't see this option in my Tools option.

Thanks in advance

In the menu Tools -> Preferences

Please open new threads for new questions.

Regards,

Didier.

Hi,


a little note follows in case it will be helpful for somebody sometime.

I faced this situation again and the followings did not help:
- reopening the JSF JSP,
- restarting JDeveloper,
- readding libraries,
- disabling PhaseListeners,
- creating and closing a new empty JSF JSP.

Finally I identified the problem in JDeveloper console log: a session-scoped managed bean could not be instantiated due to a null pointer exception.

Fixing the code, cleaning and rebuilding the project, then restarting JDeveloper helped.


Regards,
Patrik