[jadeite1000]

Hi:

In the past, I added the following statement to my weblogic.xml for weblogic 8.1:

<jsp-descriptor>
<jsp-param>
<param-name>verbose</param-name>
<param-value>TRUE</param-value>
</jsp-param>
<jsp-param>
<param-name>pageCheckSeconds</param-name>
<param-value>1</param-value>
</jsp-param>
<jsp-param>
<param-name>printNulls</param-name>
<param-value>false</param-value>
</jsp-param>
<jsp-param>
<param-name>debug</param-name>
<param-value>true</param-value>
</jsp-param>
<jsp-param>
<param-name>keepgenerated</param-name>
<param-value>true</param-value>
</jsp-param>

</jsp-descriptor>

and I have no problem debugging the jsp using myEclipse 5.1.1.
But when I tried it on weblogic 9.2, I cannot debug the jsp pages at all.
It doesn’t gives me source not found error.

When I used only the following parameter in weblogic.xml, at least I get the error source not found but gives me the line number of the jsp pages:

<jsp-descriptor>
<jsp-param>
<param-name>keepgenerated</param-name>
<param-value>true</param-value>
</jsp-param>
</jsp-descriptor>

Please note, I am running weblogic 92 on MyEclipse. In the past, I also ran weblogic 8.1 on myEclipse with no problem debugging the jsp pages.

Yours,

Frustrate.

[Scott Anderson]

I’m really sorry you’re seeing this but I think I know what’s going on here. The bad news it may be a known bug that crops up from time to time that we’re going to be able to fix in 5.5. The good news is that there is a workaround.

What we need to do is create a debug launch configuration for your instance of the WebLogic server. That’s really easy as all you have to do is navigate to Window > Preferences > MyEclipse > WebLogic 9 > Launch and hit the ‘Create Launch Configuration’ button. Once the dialog comes up, go to the Source tab and add all the projects in your workspace that you’ll be deploying to WebLogic. Save the launch configuration. Now, to launch WebLogic use the Debug… menu to launch with the configuration you saved. Using that configuration, which you added your projects to, the debug machinery should be able to find the source just fine.

In fact, once you simply create the launch configuration simply starting the server off the Server view should cause debugging to work fine as well, even if you don’t launch with the new configuration. Odd, but it seems to work.

[jadeite1000]

@support-scott wrote:

I’m really sorry you’re seeing this but I think I know what’s going on here. The bad news it may be a known bug that crops up from time to time that we’re going to be able to fix in 5.5. The good news is that there is a workaround.

What we need to do is create a debug launch configuration for your instance of the WebLogic server. That’s really easy as all you have to do is navigate to Window > Preferences > MyEclipse > WebLogic 9 > Launch and hit the ‘Create Launch Configuration’ button. Once the dialog comes up, go to the Source tab and add all the projects in your workspace that you’ll be deploying to WebLogic. Save the launch configuration. Now, to launch WebLogic use the Debug… menu to launch with the configuration you saved. Using that configuration, which you added your projects to, the debug machinery should be able to find the source just fine.

In fact, once you simply create the launch configuration simply starting the server off the Server view should cause debugging to work fine as well, even if you don’t launch with the new configuration. Odd, but it seems to work.

Hi:

You’re right, I am now able to debug the jsp pages using MyEclipse 5.1.1 running Weblogic 9.2.

But I can’t see the variables and their values.
I added the variable “nextVisisbleObj” in the expression tab and all it shows me is this:

“nextVisibleObj”

There is no values in the object. There should be a value in the object.
In the past, in the java class code, the this tab will show me a list of variables and their values. But for the jsp page, there are the list of variables:

this
arg0
arg1

but when I expanded the this variables I cannot see the values for code such as this:
<%
Boolean prevVisibleObj = (Boolean)ic.getAttribute(Constrain.PAGE_TEST_VIEW+Constrain.CONTROL_PREV_BUTTON_ENABLED);
boolean prevVisible = (prevVisibleObj!=null)? ((Boolean)prevVisibleObj).booleanValue():false;
Boolean nextVisibleObj = (Boolean)ic.getAttribute(Constrain.PAGE_TEST_VIEW+Constrain.CONTROL_NEXT_BUTTON_ENABLED);
boolean nextVisible = (nextVisibleObj!=null)? ((Boolean)nextVisibleObj).booleanValue():false;

String hasData = “false”;
if(ic.getAttribute(“hasData”) != null) {
hasData = (String)ic.getAttribute(“hasData”);
}

%>

Why is the above occurring.

Frustrated.

[Scott Anderson]

Did you change your webloic.xml back to the first version with full debug turned on? If not, your JSP pages are likely being compiled and optimized, thus removing the symbolic information.

[jadeite1000]

@support-scott wrote:

Did you change your webloic.xml back to the first version with full debug turned on? If not, your JSP pages are likely being compiled and optimized, thus removing the symbolic information.

Hi:

I turned my weblogic.xml with full information:
<jsp-descriptor>
<jsp-param>
<param-name>verbose</param-name>
<param-value>TRUE</param-value>
</jsp-param>
<jsp-param>
<param-name>pageCheckSeconds</param-name>
<param-value>1</param-value>
</jsp-param>
<jsp-param>
<param-name>printNulls</param-name>
<param-value>false</param-value>
</jsp-param>
<jsp-param>
<param-name>debug</param-name>
<param-value>true</param-value>
</jsp-param>
<jsp-param>
<param-name>keepgenerated</param-name>
<param-value>true</param-value>

I can debug the jsp perfectly following your instructions but I cannot see the variables created in the jsp,therefore I cannot see the values of those variables.

Is there some way I can do to fix this problem.

Yours,

Frustrate.

[Scott Anderson]

Is there some way I can do to fix this problem.

From your other posts it seems you’re using an Ant script to deploy your application. When users do this, they often recompile their code in such a way that debugging information is lost. This seems like the same symptom and revolves around whether Ant accepts debug=”true” or debug=”on” as a parameter in the script.

[Author]

Posts