RE: debug jsp pages and where is the source
Hi Melissa, I didn't get the size for him. To be honest..I cam was working on content and part of my front-end framework the last few times. I will figure this out soon for him and let him know. Next weekend is bad for me to meet too..got two graduations and a special mothers-day/fathers-day dinner for my parents who are in from Florida. But sometime during the week, especially Wednesday night or Thursday would be fine. Site is up. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Scot Weber Sent: Thursday, June 14, 2001 5:27 PM To: Orion-Interest Subject: Re: debug jsp pages and where is the source Wendell, orion-web-app jsp-cache-directory=./persistence servlet-webdir=/servlet development=false-- Change this to true persistence-path=./persistence/state.ser Then . . . Assuming all things are equal and you have a default web app called 'devel-default-web-app' bound to the server you're working with, the persistence (and subsequently the .java files for the .jsp's) will be in the path: /u/orion/application-deployments/default/devel-default-web-app/persistence http://www.mydomain.com/index.jsp will produce the files /u/orion/application-deployments/default/devel-default-web-app/per sistence/index.jsp.java /u/orion/application-deployments/default/devel-default-web-app/per sistence/index.jsp.jspCache peace - scot Wendell Nichols wrote: Well I made the jsp page work by explicitly importing java.lang.String, as opposed to java.lang.* as I had done for other servers. Because this shouldn't bother other servers I'm ok with it. I still need to have access to the jsp.java files for debugging purposes before Orion will be an acceptable server for me... ... snip ... Any help would be appreciated.. Wendell Nichols Amdahl Software Ltd. and Fujitsu Apserv. -- scot weber - [EMAIL PROTECTED] - Given a choice between a folly and a sacrament, one should always choose the folly -- because we know a sacrament will not bring us closer to God and there's always a chance that a folly will. - Erasmus The only man who never makes a mistake is the man who never does anything. - Theodore Roosevelt.
RE: debug jsp pages and where is the source
Kevin, Thanks for that - hope you have a great weekend, and don't post too many messages to the wrong lists! ;) -mike Mike Cannon-Brookes - Founder, Core Developer OpenSymphony - http://www.opensymphony.com The Open Source J2EE Component Project Latest News - Cache in on faster, more reliable JSPs http://www.javaworld.com/javaworld/jw-05-2001/jw-0504-cache.html -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Kevin Duffey Sent: Sunday, June 17, 2001 10:27 AM To: Orion-Interest Subject: RE: debug jsp pages and where is the source Hi Melissa, I didn't get the size for him. To be honest..I cam was working on content and part of my front-end framework the last few times. I will figure this out soon for him and let him know. Next weekend is bad for me to meet too..got two graduations and a special mothers-day/fathers-day dinner for my parents who are in from Florida. But sometime during the week, especially Wednesday night or Thursday would be fine. Site is up. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Scot Weber Sent: Thursday, June 14, 2001 5:27 PM To: Orion-Interest Subject: Re: debug jsp pages and where is the source Wendell, orion-web-app jsp-cache-directory=./persistence servlet-webdir=/servlet development=false-- Change this to true persistence-path=./persistence/state.ser Then . . . Assuming all things are equal and you have a default web app called 'devel-default-web-app' bound to the server you're working with, the persistence (and subsequently the .java files for the .jsp's) will be in the path: /u/orion/application-deployments/default/devel-default-web-app/persistence http://www.mydomain.com/index.jsp will produce the files /u/orion/application-deployments/default/devel-default-web-app/per sistence/index.jsp.java /u/orion/application-deployments/default/devel-default-web-app/per sistence/index.jsp.jspCache peace - scot Wendell Nichols wrote: Well I made the jsp page work by explicitly importing java.lang.String, as opposed to java.lang.* as I had done for other servers. Because this shouldn't bother other servers I'm ok with it. I still need to have access to the jsp.java files for debugging purposes before Orion will be an acceptable server for me... ... snip ... Any help would be appreciated.. Wendell Nichols Amdahl Software Ltd. and Fujitsu Apserv. -- scot weber - [EMAIL PROTECTED] - Given a choice between a folly and a sacrament, one should always choose the folly -- because we know a sacrament will not bring us closer to God and there's always a chance that a folly will. - Erasmus The only man who never makes a mistake is the man who never does anything. - Theodore Roosevelt.
Re: debug jsp pages and where is the source
Hi Wendell,
Take a look at http://bugzilla.orionserver.com/bugzilla/show_bug.cgi?id=497.
Someone else recently posted about this too and so I filed a bug.
Magnus already fixed it and it seems you should be able to use String and
any other Class in the scope of the current jsp's imports.
Marcel
- Original Message -
From: Wendell Nichols [EMAIL PROTECTED]
To: Orion-Interest [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, June 14, 2001 6:05 PM
Subject: Re: debug jsp pages and where is the source
Oops, I got had by a deployment thing, (orion didn't recompile the jsp
file when the TEI class changed...). The thing that actually fixed the jsp
compile problem was changeing the tei class from
new VariableInfo(eCTSResult,
String,
true,
VariableInfo.NESTED),
tonew VariableInfo(eCTSResult,
java.lang.String,
true,
VariableInfo.NESTED),
The import didn't have anything to do with it. :(
I've also figured out how to get access to the jsp source files:
In your config/global-web-application.xml file there is an orion-web-app
node. Add the property:
development=true there, and to any other web-xml files in your
applicatio-deployments tree as necessary. This will cause orion to keep
copies of the jsp.java files in your persistence directory tree, however it
will name them wrong :(
My debugger looks for a source file of the same name of the class where
the jvm is breakstopped so it necessary to rename the source files so that
they conform to the name of the class within so that the ide will find them,
(in this case NetBeans). If you do that you can actually step through the
code.
All tHis being said, there is still one catch: Even with development mode
turned on Orion is compiling the jsp.java files without the -g debugging
switch so you don't have access to all the variable info. Outside of using
an external compiler for jsp's I don't see how to switch debugging on...
If I find out I'll post it here :=)
WCN
Wendell Nichols wrote:
Well I made the jsp page work by explicitly importing
java.lang.String, as opposed to java.lang.* as I had done for other
servers. Because this shouldn't bother other servers I'm ok with it.
I still need to have access to the jsp.java files for debugging purposes
before Orion will be an acceptable server for me...
Wendell Nichols
Amdahl Software Ltd.
Fujitsu Appserv.
Wendell Nichols wrote:
When I access a jsp page which uses a tag library I get an error:
500 Internal Server Error
Error parsing JSP page /ectsdemo/TagLibDemos/booklist.jsp line 15
Bean type 'String' not found
I suspect that this is a problem creating the java file from the jsp
page related to the tag extra info class... At any rate I can't find the
source or class files that Orion generates from jsp pages so it's impossible
to proceed. Does anyone know how to make Orion place java and class files
for jsp pages somewhere where they can be viewed and debugged?
I see jsp cache files which are probably some sort of java archive
internal to Orion, but these don't help me as I can't open them...
Incidentally the jsp line that produced the above error looks like:
ects:eCTSTaglet name=BOOKLIST
The taglib entry for eCTSTaglet:
tag
nameeCTSTaglet/name
tagclasscom.Amdahl.eCTS20.ects2taglet/tagclass
teiclasscom.Amdahl.eCTS20.ects2tagletTEI/teiclass
bodycontentJSP/bodycontent
info
Run a named taglet.
/info
attribute
namename/name
requiredtrue/required
/attribute
attribute
nameresultString/name
requiredfalse/required
/attribute
attribute
nameuserdata/name
requiredfalse/required
/attribute
/tag
Its TEI class :
public VariableInfo[] getVariableInfo(TagData data) {
return new VariableInfo []
{
new VariableInfo(eCTSResult,
String,
true,
VariableInfo.AT_BEGIN),
new VariableInfo(EndMsg,
String,
true,
VariableInfo.AT_BEGIN),
new VariableInfo(ReturnMsg,
String,
true,
VariableInfo.AT_BEGIN)
};
}
Any help would be appreciated..
Wendell Nichols
Amdahl Software Ltd.
and
Fujitsu Apserv.
Re: debug jsp pages and where is the source
Well I made the jsp page work by explicitly importing "java.lang.String",
as opposed to "java.lang.*" as I had done for other servers. Because
this shouldn't bother other servers I'm ok with it.
I still need to have access to the jsp.java files for debugging purposes
before Orion will be an acceptable server for me...
Wendell Nichols
Amdahl Software Ltd.
Fujitsu Appserv.
Wendell Nichols wrote:
When I access a jsp page which uses a tag library
I get an error:
500 Internal Server Error
Error parsing JSP page /ectsdemo/TagLibDemos/booklist.jsp line 15
Bean type 'String' not found
I suspect that this is a problem creating the java file from the jsp page
related to the tag extra info class... At any rate I can't find the
source or class files that Orion generates from jsp pages so it's impossible
to proceed. Does anyone know how to make Orion place java and class
files for jsp pages somewhere where they can be viewed and debugged?
I see jsp cache files which are probably some sort of java archive
internal to Orion, but these don't help me as I can't open them...
Incidentally the jsp line that produced the above error looks like:
ects:eCTSTaglet name="BOOKLIST" >
The taglib entry for eCTSTaglet:
tag>
name>eCTSTaglet/name>
tagclass>com.Amdahl.eCTS20.ects2taglet/tagclass>
teiclass>com.Amdahl.eCTS20.ects2tagletTEI/teiclass>
bodycontent>JSP/bodycontent>
info>
Run a named taglet.
/info>
attribute>
name>name/name>
required>true/required>
/attribute>
attribute>
name>resultString/name>
required>false/required>
/attribute>
attribute>
name>userdata/name>
required>false/required>
/attribute>
/tag>
Its TEI class :
public VariableInfo[] getVariableInfo(TagData data) {
return new VariableInfo []
{
new
VariableInfo("eCTSResult",
"String",
true,
VariableInfo.AT_BEGIN),
new
VariableInfo("EndMsg",
"String",
true,
VariableInfo.AT_BEGIN),
new
VariableInfo("ReturnMsg",
"String",
true,
VariableInfo.AT_BEGIN)
};
}
Any help would be appreciated..
Wendell Nichols
Amdahl Software Ltd.
and
Fujitsu Apserv.
Re: debug jsp pages and where is the source
Oops, I got had by a deployment thing, (orion didn't recompile the jsp
file when the TEI class changed...). The thing that actually fixed
the jsp compile problem was changeing the tei class from
new VariableInfo("eCTSResult",
"String",
true,
VariableInfo.NESTED),
to
new VariableInfo("eCTSResult",
"java.lang.String",
true,
VariableInfo.NESTED),
The import didn't have anything to do with it. :(
I've also figured out how to get access to the jsp source files:
In your config/global-web-application.xml file there is an orion-web-app>
node. Add the property:
development="true" there, and to any other web-xml files in your applicatio-deployments
tree as necessary. This will cause orion to keep copies of the jsp.java
files in your persistence directory tree, however it will name them wrong
:(
My debugger looks for a source file of the same name of the class where
the jvm is breakstopped so it necessary to rename the source files so that
they conform to the name of the class within so that the ide will find
them, (in this case NetBeans). If you do that you can actually step
through the code.
All tHis being said, there is still one catch: Even with development
mode turned on Orion is compiling the jsp.java files without the "-g" debugging
switch so you don't have access to all the variable info. Outside
of using an external compiler for jsp's I don't see how to switch debugging
on...
If I find out I'll post it here :=)
WCN
Wendell Nichols wrote:
Well I made the jsp page work by explicitly importing
"java.lang.String", as opposed to "java.lang.*" as I had done for other
servers. Because this shouldn't bother other servers I'm ok with
it.
I still need to have access to the jsp.java files for debugging purposes
before Orion will be an acceptable server for me...
Wendell Nichols
Amdahl Software Ltd.
Fujitsu Appserv.
Wendell Nichols wrote:
When I access a jsp page which uses a tag library
I get an error:
500 Internal Server Error
Error parsing JSP page /ectsdemo/TagLibDemos/booklist.jsp line 15
Bean type 'String' not found
I suspect that this is a problem creating the java file from the jsp page
related to the tag extra info class... At any rate I can't find the
source or class files that Orion generates from jsp pages so it's impossible
to proceed. Does anyone know how to make Orion place java and class
files for jsp pages somewhere where they can be viewed and debugged?
I see jsp cache files which are probably some sort of java archive
internal to Orion, but these don't help me as I can't open them...
Incidentally the jsp line that produced the above error looks like:
ects:eCTSTaglet name="BOOKLIST" >
The taglib entry for eCTSTaglet:
tag>
name>eCTSTaglet/name>
tagclass>com.Amdahl.eCTS20.ects2taglet/tagclass>
teiclass>com.Amdahl.eCTS20.ects2tagletTEI/teiclass>
bodycontent>JSP/bodycontent>
info>
Run a named taglet.
/info>
attribute>
name>name/name>
required>true/required>
/attribute>
attribute>
name>resultString/name>
required>false/required>
/attribute>
attribute>
name>userdata/name>
required>false/required>
/attribute>
/tag>
Its TEI class :
public VariableInfo[] getVariableInfo(TagData data) {
return new VariableInfo []
{
new
VariableInfo("eCTSResult",
"String",
true,
VariableInfo.AT_BEGIN),
new
VariableInfo("EndMsg",
"String",
true,
VariableInfo.AT_BEGIN),
new
VariableInfo("ReturnMsg",
"String",
true,
VariableInfo.AT_BEGIN)
};
}
Any help would be appreciated..
Wendell Nichols
Amdahl Software Ltd.
and
Fujitsu Apserv.
RE: debug jsp pages and where is the source
You
have to use the fully qualified class name, ie java.lang.String for this to
work.
Michael
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Wendell
NicholsSent: Thursday, June 14, 2001 10:59 AMTo:
Orion-InterestCc: [EMAIL PROTECTED]Subject: debug jsp pages
and where is the sourceWhen I access a jsp page which
uses a tag library I get an error:
500 Internal Server Error
Error parsing JSP page /ectsdemo/TagLibDemos/booklist.jsp line 15
Bean type 'String' not found
I suspect that this is a problem creating the java file
from the jsp page related to the tag extra info class... At any rate I
can't find the source or class files that Orion generates from jsp pages so
it's impossible to proceed. Does anyone know how to make Orion place
java and class files for jsp pages somewhere where they can be viewed and
debugged? I see jsp cache files which are probably some sort of java
archive internal to Orion, but these don't help me as I can't open them...
Incidentally the jsp line that produced the above error looks like:
ects:eCTSTaglet name="BOOKLIST"
The taglib entry for eCTSTaglet: tag
nameeCTSTaglet/name
tagclasscom.Amdahl.eCTS20.ects2taglet/tagclass
teiclasscom.Amdahl.eCTS20.ects2tagletTEI/teiclass
bodycontentJSP/bodycontent
info
Run a named taglet.
/info
attribute
namename/name
requiredtrue/required
/attribute attribute
nameresultString/name
requiredfalse/required
/attribute attribute
nameuserdata/name
requiredfalse/required
/attribute /tag
Its TEI class :
public VariableInfo[] getVariableInfo(TagData data) {
return new VariableInfo []
{
new
VariableInfo("eCTSResult",
"String",
true,
VariableInfo.AT_BEGIN),
new
VariableInfo("EndMsg",
"String",
true,
VariableInfo.AT_BEGIN),
new
VariableInfo("ReturnMsg",
"String",
true,
VariableInfo.AT_BEGIN)
}; }
Any help would be appreciated..
Wendell Nichols Amdahl Software Ltd. and Fujitsu Apserv.
RE: debug jsp pages and where is the source
If you
want to see the java source files compiled from the jsp pages then add
developmenttrue/development to your web-application.xml file. There was another thread that mentions
this with additional information titled Cached code. Karl Avedal was the responder.
email signature goes here
-Original
Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On
Behalf Of Wendell Nichols
Sent: Thursday, June 14, 2001
10:20 AM
To: Orion-Interest
Subject: Re: debug jsp pages and
where is the source
Well I made
the jsp page work by explicitly importing java.lang.String, as
opposed to java.lang.* as I had done for other servers.
Because this shouldn't bother other servers I'm ok with it.
I still need to have access to the jsp.java files for debugging purposes before
Orion will be an acceptable server for me...
Wendell Nichols
Amdahl Software Ltd.
Fujitsu Appserv.
Wendell Nichols wrote:
When I access a jsp page which uses a tag
library I get an error:
500 Internal Server ErrorError parsing JSP page /ectsdemo/TagLibDemos/booklist.jsp line 15Bean type 'String' not found
I suspect that this is a problem creating
the java file from the jsp page related to the tag extra info class... At
any rate I can't find the source or class files that Orion generates from jsp
pages so it's impossible to proceed. Does anyone know how to make Orion
place java and class files for jsp pages somewhere where they can be viewed and
debugged?
I see jsp cache files which are probably some sort of java archive internal to
Orion, but these don't help me as I can't open them...
Incidentally
the jsp line that produced the above error looks like:
ects:eCTSTaglet name=BOOKLIST
The taglib
entry for eCTSTaglet:
tag
nameeCTSTaglet/name
tagclasscom.Amdahl.eCTS20.ects2taglet/tagclass
teiclasscom.Amdahl.eCTS20.ects2tagletTEI/teiclass
bodycontentJSP/bodycontent
info
Run a named taglet.
/info
attribute
namename/name
requiredtrue/required
/attribute
attribute
nameresultString/name
requiredfalse/required
/attribute
attribute
nameuserdata/name
requiredfalse/required
/attribute
/tag
Its TEI class
:
public VariableInfo[] getVariableInfo(TagData data) {
return new VariableInfo []
{
new VariableInfo(eCTSResult,
String,
true,
VariableInfo.AT_BEGIN),
new VariableInfo(EndMsg,
String,
true,
VariableInfo.AT_BEGIN),
new VariableInfo(ReturnMsg,
String,
true,
VariableInfo.AT_BEGIN)
};
}
Any help
would be appreciated..
Wendell
Nichols
Amdahl Software Ltd.
and
Fujitsu Apserv.
Re: debug jsp pages and where is the source
Wendell, orion-web-app jsp-cache-directory=./persistence servlet-webdir=/servlet development=false-- Change this to true persistence-path=./persistence/state.ser Then . . . Assuming all things are equal and you have a default web app called 'devel-default-web-app' bound to the server you're working with, the persistence (and subsequently the .java files for the .jsp's) will be in the path: /u/orion/application-deployments/default/devel-default-web-app/persistence http://www.mydomain.com/index.jsp will produce the files /u/orion/application-deployments/default/devel-default-web-app/persistence/index.jsp.java /u/orion/application-deployments/default/devel-default-web-app/persistence/index.jsp.jspCache peace - scot Wendell Nichols wrote: Well I made the jsp page work by explicitly importing java.lang.String, as opposed to java.lang.* as I had done for other servers. Because this shouldn't bother other servers I'm ok with it. I still need to have access to the jsp.java files for debugging purposes before Orion will be an acceptable server for me... ... snip ... Any help would be appreciated.. Wendell Nichols Amdahl Software Ltd. and Fujitsu Apserv. -- scot weber - [EMAIL PROTECTED] - Given a choice between a folly and a sacrament, one should always choose the folly -- because we know a sacrament will not bring us closer to God and there's always a chance that a folly will. - Erasmus The only man who never makes a mistake is the man who never does anything. - Theodore Roosevelt.
