generated jsp source weblogic

[google]

Is there a way to keep or view the source that is generated when the
jsp is compiled? I am getting an error, as I sometimes do, and feel I
could much more quickly identify the problem if I could actually view
the source.

Thanks for your help!

bill

 

[kaeli]

Is there a way to keep or view the source that is generated when the
jsp is compiled? I am getting an error, as I sometimes do, and feel I
could much more quickly identify the problem if I could actually view
the source.

Thanks for your help!

Well, there is with my server, which is IPlanet. It sticks the compiled
source in a particular spot.
I assume weblogic would have a way, too. Did you look around the server
directories? That's how I found mine.

Sometimes the error message is helpful and tells you the name of the file
that generated the error. Take a look around the web server directories for
it. If you use *nix, you can grep or ls for it.

--

 

[google]

Thanks for the reply, but no luck.

I've searched throughout the server directories for the source name and
cannot find it :-(
To verify I searched properly, I could find the class and the jsp.

I'm sure what I want to do is somehow possible, but I could not find
any documentation that explained how to do so. FWIW, I am using WL 6.1
sp 5.

bill

 

[kaeli]

Thanks for the reply, but no luck.

I've searched throughout the server directories for the source name and
cannot find it :-(
To verify I searched properly, I could find the class and the jsp.

I'm sure what I want to do is somehow possible, but I could not find
any documentation that explained how to do so. FWIW, I am using WL 6.1
sp 5.

It's possible it discards the intermediate source, depending on your
settings.
(you're just using plain JSP files, right, not a war or ear?)

Perusing the documentation and Google...

It appears that weblogic will put the .java file in the same directory as
your stuff is, but removes it when it compiles it to .class. (default
behavior)
Since the server only removes the .java file if the JSP actually compiles (if
it doesn't have that setting in there) you could always intentionally stick a
small syntax error in it, like a missing semi-colon.

These might help.

http://e-docs.bea.com/wls/docs60/jsp/reference.html#57794 (about the
compiler)

http://www.rgagnon.com/javadetails/java-0446.html (tells you how to keep the
generated java files)

--

 

[Subramanian.ganesh]

Is there a way to keep or view the source that is generated when the
jsp is compiled? I am getting an error, as I sometimes do, and feel I
could much more quickly identify the problem if I could actually view
the source.

Thanks for your help!

bill

I'm using tomcat server, I'm able to find the .java files in it.

Even weblogic might be storing the .java file. But it won't be the
exact file name as your .jsp name. They will embedd some other text in
the file name. So searching part of the jsp file name may do good for
you.

Thanks,
Ganesh

 

[yog]

See first you can have a nitrox editor which u could also get coupled
with eclipse.But in this way u could view only the static content of
the particular jsp.If they are dyanamic tags used in jsp which are
compiled at runtime u may not be able to view them.U will have to run
the application to view it.
I hope this solves the pblm

 

[bill turner]

I don't know how you found the documentation when I couldn't, but I
surely appreciate the help. Sorry for not replying sooner. Google
rolled the message faster than I could get back to it and had to get
to a time when I could get the messages at home.

 

[kaeli]

I don't know how you found the documentation when I couldn't, but I
surely appreciate the help.

It's a talent.

You're welcome.

--