You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by ajTreece <aj...@sun.com> on 2002/04/12 22:36:05 UTC
A beginners look at the *.do process
If this is way that things are suppose to work then just bear with me and tell
me to get over it. Here is my question....
I have a webapp that when deployed will execute via the reference
http://<any-server>/sentinel The thing that is unclear to me is what is actually
happening when a <form> action is executed. What I'm finding is that my form
line must read like:
<FORM METHOD="post" NAME="mainForm" ACTION="/sentinel/logon.do">
This executes correctly. The struts-config.xml (see excerpt below) leads me to
believe that the form action should be just ACTION="/logon.do", but this returns
an error stating that http::/<any-server>/logon does not exist... Which is true.
<!-- ========== Global Forward Definitions ============================== -->
<global-forwards>
<forward name="logon" path="/logon.do"/>
</global-forwards>
<!-- ========== Action Mapping Definitions ============================== -->
<action-mappings>
<!-- Process a user logon -->
<action path="/logon"
type="com.sun.sentinel.action.LogonAction"
name="logonForm"
scope="request"
input="logon.page">
</action>
</action-mappings>
If this is how the whole *.do action is suppose work that's A.O.K. with me. My
concern is that down the road after I've completed a couple dozen jsp's someone
will decide that sentinel is not the name anymore and it must be deployed as
joe_blows_app. Now I've got to go back and fix all the jsp's.
Am I doing something wrong or is it just a fact of life that the jsp's may need
modifications because of a deployment name change... If there is a better way to
accomplish this so that the jsp's are a little less dependent on the webapp
deployed name then I'm all ears.
Later, ajTreece (aka. aj Treece - eRAS Services Development - Sun Microsystems)
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: A beginners look at the *.do process
Posted by Joseph Barefoot <jo...@hereuare.com>.
doh! sorry, I didn't notice your earlier posting....I actually have no idea
what's causing your problem, but it appears to be a problem with the tiles'
tags handling of your nested Struts tags (I'm sure you already knew that).
That exception is pretty vague though...are you sure that your usage of
tiles is not (somehow) resulting in <html:form> tags or other Struts tags
being nested or something like that?
good luck,
Joe Barefoot
-----Original Message-----
From: ajTreece [mailto:aj.treece@sun.com]
Sent: Friday, April 12, 2002 3:21 PM
To: Struts Users Mailing List
Subject: Re: A beginners look at the *.do process
Thanks Joe for the tip, but alas it causes a problem I posted earlier today.
I'm running:
Solaris v5.8
iPlanet Web Server v6.0 sp2
Java 1.3
Struts v1.1 nightly build 04092002 with tiles
Excuse the lenghty output, but here is the error I get:
[12/Apr/2002:16:40:24] failure ( 9404): Internal error: servlet service
function
had thrown ServletException (uri=/sentinel/tiles/logon/getProperties.jsp):
javax.servlet.ServletException: Exception creating bean of class
com.sun.sentinel.form.LogonForm: {1}, stack: javax.servlet.ServletException:
Exception creating bean of class com.sun.sentinel.form.LogonForm: {1}
at
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp
l.java:453)
at
_jsps._tiles._logon._getProperties_jsp._jspService(_getProperties_jsp.java:2
22)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.ja
va:247)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.access$6(JspServlet.j
ava:237)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:520)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:589)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.iplanet.server.http.servlet.NSServletRunner.invokeServletService(NSServl
etRunner.java:897)
at
com.iplanet.server.http.servlet.WebApplication.service(WebApplication.java:1
065)
at
com.iplanet.server.http.servlet.NSServletRunner.ServiceWebApp(NSServletRunne
r.java:959)
at com.iplanet.server.http.servlet.NSServletSession.internalRedirect(Native
Method)
at
com.iplanet.server.http.servlet.NSRequestDispatcher.include(NSRequestDispatc
her.java:93)
at
org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:408)
at
org.apache.struts.taglib.tiles.InsertTag$InsertHandler.doEndTag(InsertTag.ja
va:757)
at org.apache.struts.taglib.tiles.InsertTag.doEndTag(InsertTag.java:369)
at
_jsps._layouts._eRasAppLayout_jsp._jspService(_eRasAppLayout_jsp.java:307)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.ja
va:247)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.access$6(JspServlet.j
ava:237)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:520)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:589)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.iplanet.server.http.servlet.NSServletRunner.invokeServletService(NSServl
etRunner.java:897)
at
com.iplanet.server.http.servlet.WebApplication.service(WebApplication.java:1
065)
at
com.iplanet.server.http.servlet.NSServletRunner.ServiceWebApp(NSServletRunne
r.java:959)
at com.iplanet.server.http.servlet.NSServletSession.internalRedirect(Native
Method)
at
com.iplanet.server.http.servlet.NSRequestDispatcher.include(NSRequestDispatc
her.java:93)
at
org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:408)
at
org.apache.struts.taglib.tiles.InsertTag$InsertHandler.doEndTag(InsertTag.ja
va:757)
at org.apache.struts.taglib.tiles.InsertTag.doEndTag(InsertTag.java:369)
at _jsps._tiles._logon._index_jsp._jspService(_index_jsp.java:83)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.ja
va:247)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.access$6(JspServlet.j
ava:237)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:520)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:589)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.iplanet.server.http.servlet.NSServletRunner.invokeServletService(NSServl
etRunner.java:897)
at
com.iplanet.server.http.servlet.WebApplication.service(WebApplication.java:1
065)
at
com.iplanet.server.http.servlet.NSServletRunner.ServiceWebApp(NSServletRunne
r.java:959)
, root cause: javax.servlet.jsp.JspException: Exception creating bean of
class
com.sun.sentinel.form.LogonForm: {1}
at org.apache.struts.taglib.html.FormTag
[12/Apr/2002:16:40:26] info ( 9404): jsp: init
I'm open for suggestions on this one!!! I would very much like to use
struts-html.
Thanks, ajTreece
Joseph Barefoot wrote:
> Yes, that would definitely suck if you had to modify all the JSPs when you
> changed the application name. Fortunately, that is not the case. You
> should use the Struts custom tags to render your form tags, like so:
>
> <html:form action="/logon" method="post" name="mainForm" />
>
> This struts tag will correctly prepend the relative context root (i.e.,
your
> application name) to the action URI before outputting the html form tag in
> the response. Also, you don't have to specify the form name, unless you
> want to...if omitted, Struts will use the one associated with the action
in
> your actionmapping.
>
> cheers,
> Joe Barefoot
>
> -----Original Message-----
> From: ajTreece [mailto:aj.treece@sun.com]
> Sent: Friday, April 12, 2002 1:36 PM
> To: Struts Users Mailing List
> Subject: A beginners look at the *.do process
>
>
> If this is way that things are suppose to work then just bear with me and
> tell
> me to get over it. Here is my question....
>
> I have a webapp that when deployed will execute via the reference
> http://<any-server>/sentinel The thing that is unclear to me is what is
> actually
> happening when a <form> action is executed. What I'm finding is that my
form
> line must read like:
>
> <FORM METHOD="post" NAME="mainForm" ACTION="/sentinel/logon.do">
>
> This executes correctly. The struts-config.xml (see excerpt below) leads
me
> to
> believe that the form action should be just ACTION="/logon.do", but this
> returns
> an error stating that http::/<any-server>/logon does not exist... Which is
> true.
>
> <!-- ========== Global Forward Definitions
> ============================== -->
> <global-forwards>
> <forward name="logon" path="/logon.do"/>
> </global-forwards>
>
>
> <!-- ========== Action Mapping Definitions
> ============================== -->
> <action-mappings>
> <!-- Process a user logon -->
> <action path="/logon"
> type="com.sun.sentinel.action.LogonAction"
> name="logonForm"
> scope="request"
> input="logon.page">
> </action>
> </action-mappings>
>
> If this is how the whole *.do action is suppose work that's A.O.K. with
me.
> My
> concern is that down the road after I've completed a couple dozen jsp's
> someone
> will decide that sentinel is not the name anymore and it must be deployed
as
> joe_blows_app. Now I've got to go back and fix all the jsp's.
>
> Am I doing something wrong or is it just a fact of life that the jsp's may
> need
> modifications because of a deployment name change... If there is a better
> way to
> accomplish this so that the jsp's are a little less dependent on the
webapp
> deployed name then I'm all ears.
>
>
> Later, ajTreece (aka. aj Treece - eRAS Services Development - Sun
> Microsystems)
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: A beginners look at the *.do process
Posted by ajTreece <aj...@sun.com>.
Thanks Joe for the tip, but alas it causes a problem I posted earlier today.
I'm running:
Solaris v5.8
iPlanet Web Server v6.0 sp2
Java 1.3
Struts v1.1 nightly build 04092002 with tiles
Excuse the lenghty output, but here is the error I get:
[12/Apr/2002:16:40:24] failure ( 9404): Internal error: servlet service function
had thrown ServletException (uri=/sentinel/tiles/logon/getProperties.jsp):
javax.servlet.ServletException: Exception creating bean of class
com.sun.sentinel.form.LogonForm: {1}, stack: javax.servlet.ServletException:
Exception creating bean of class com.sun.sentinel.form.LogonForm: {1}
at
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:453)
at _jsps._tiles._logon._getProperties_jsp._jspService(_getProperties_jsp.java:222)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:247)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.access$6(JspServlet.java:237)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:520)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:589)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.iplanet.server.http.servlet.NSServletRunner.invokeServletService(NSServletRunner.java:897)
at com.iplanet.server.http.servlet.WebApplication.service(WebApplication.java:1065)
at
com.iplanet.server.http.servlet.NSServletRunner.ServiceWebApp(NSServletRunner.java:959)
at com.iplanet.server.http.servlet.NSServletSession.internalRedirect(Native Method)
at
com.iplanet.server.http.servlet.NSRequestDispatcher.include(NSRequestDispatcher.java:93)
at org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:408)
at
org.apache.struts.taglib.tiles.InsertTag$InsertHandler.doEndTag(InsertTag.java:757)
at org.apache.struts.taglib.tiles.InsertTag.doEndTag(InsertTag.java:369)
at _jsps._layouts._eRasAppLayout_jsp._jspService(_eRasAppLayout_jsp.java:307)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:247)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.access$6(JspServlet.java:237)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:520)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:589)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.iplanet.server.http.servlet.NSServletRunner.invokeServletService(NSServletRunner.java:897)
at com.iplanet.server.http.servlet.WebApplication.service(WebApplication.java:1065)
at
com.iplanet.server.http.servlet.NSServletRunner.ServiceWebApp(NSServletRunner.java:959)
at com.iplanet.server.http.servlet.NSServletSession.internalRedirect(Native Method)
at
com.iplanet.server.http.servlet.NSRequestDispatcher.include(NSRequestDispatcher.java:93)
at org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:408)
at
org.apache.struts.taglib.tiles.InsertTag$InsertHandler.doEndTag(InsertTag.java:757)
at org.apache.struts.taglib.tiles.InsertTag.doEndTag(InsertTag.java:369)
at _jsps._tiles._logon._index_jsp._jspService(_index_jsp.java:83)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:247)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.access$6(JspServlet.java:237)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:520)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:589)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.iplanet.server.http.servlet.NSServletRunner.invokeServletService(NSServletRunner.java:897)
at com.iplanet.server.http.servlet.WebApplication.service(WebApplication.java:1065)
at
com.iplanet.server.http.servlet.NSServletRunner.ServiceWebApp(NSServletRunner.java:959)
, root cause: javax.servlet.jsp.JspException: Exception creating bean of class
com.sun.sentinel.form.LogonForm: {1}
at org.apache.struts.taglib.html.FormTag
[12/Apr/2002:16:40:26] info ( 9404): jsp: init
I'm open for suggestions on this one!!! I would very much like to use struts-html.
Thanks, ajTreece
Joseph Barefoot wrote:
> Yes, that would definitely suck if you had to modify all the JSPs when you
> changed the application name. Fortunately, that is not the case. You
> should use the Struts custom tags to render your form tags, like so:
>
> <html:form action="/logon" method="post" name="mainForm" />
>
> This struts tag will correctly prepend the relative context root (i.e., your
> application name) to the action URI before outputting the html form tag in
> the response. Also, you don't have to specify the form name, unless you
> want to...if omitted, Struts will use the one associated with the action in
> your actionmapping.
>
> cheers,
> Joe Barefoot
>
> -----Original Message-----
> From: ajTreece [mailto:aj.treece@sun.com]
> Sent: Friday, April 12, 2002 1:36 PM
> To: Struts Users Mailing List
> Subject: A beginners look at the *.do process
>
>
> If this is way that things are suppose to work then just bear with me and
> tell
> me to get over it. Here is my question....
>
> I have a webapp that when deployed will execute via the reference
> http://<any-server>/sentinel The thing that is unclear to me is what is
> actually
> happening when a <form> action is executed. What I'm finding is that my form
> line must read like:
>
> <FORM METHOD="post" NAME="mainForm" ACTION="/sentinel/logon.do">
>
> This executes correctly. The struts-config.xml (see excerpt below) leads me
> to
> believe that the form action should be just ACTION="/logon.do", but this
> returns
> an error stating that http::/<any-server>/logon does not exist... Which is
> true.
>
> <!-- ========== Global Forward Definitions
> ============================== -->
> <global-forwards>
> <forward name="logon" path="/logon.do"/>
> </global-forwards>
>
>
> <!-- ========== Action Mapping Definitions
> ============================== -->
> <action-mappings>
> <!-- Process a user logon -->
> <action path="/logon"
> type="com.sun.sentinel.action.LogonAction"
> name="logonForm"
> scope="request"
> input="logon.page">
> </action>
> </action-mappings>
>
> If this is how the whole *.do action is suppose work that's A.O.K. with me.
> My
> concern is that down the road after I've completed a couple dozen jsp's
> someone
> will decide that sentinel is not the name anymore and it must be deployed as
> joe_blows_app. Now I've got to go back and fix all the jsp's.
>
> Am I doing something wrong or is it just a fact of life that the jsp's may
> need
> modifications because of a deployment name change... If there is a better
> way to
> accomplish this so that the jsp's are a little less dependent on the webapp
> deployed name then I'm all ears.
>
>
> Later, ajTreece (aka. aj Treece - eRAS Services Development - Sun
> Microsystems)
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: A beginners look at the *.do process
Posted by Joseph Barefoot <jo...@hereuare.com>.
Yes, that would definitely suck if you had to modify all the JSPs when you
changed the application name. Fortunately, that is not the case. You
should use the Struts custom tags to render your form tags, like so:
<html:form action="/logon" method="post" name="mainForm" />
This struts tag will correctly prepend the relative context root (i.e., your
application name) to the action URI before outputting the html form tag in
the response. Also, you don't have to specify the form name, unless you
want to...if omitted, Struts will use the one associated with the action in
your actionmapping.
cheers,
Joe Barefoot
-----Original Message-----
From: ajTreece [mailto:aj.treece@sun.com]
Sent: Friday, April 12, 2002 1:36 PM
To: Struts Users Mailing List
Subject: A beginners look at the *.do process
If this is way that things are suppose to work then just bear with me and
tell
me to get over it. Here is my question....
I have a webapp that when deployed will execute via the reference
http://<any-server>/sentinel The thing that is unclear to me is what is
actually
happening when a <form> action is executed. What I'm finding is that my form
line must read like:
<FORM METHOD="post" NAME="mainForm" ACTION="/sentinel/logon.do">
This executes correctly. The struts-config.xml (see excerpt below) leads me
to
believe that the form action should be just ACTION="/logon.do", but this
returns
an error stating that http::/<any-server>/logon does not exist... Which is
true.
<!-- ========== Global Forward Definitions
============================== -->
<global-forwards>
<forward name="logon" path="/logon.do"/>
</global-forwards>
<!-- ========== Action Mapping Definitions
============================== -->
<action-mappings>
<!-- Process a user logon -->
<action path="/logon"
type="com.sun.sentinel.action.LogonAction"
name="logonForm"
scope="request"
input="logon.page">
</action>
</action-mappings>
If this is how the whole *.do action is suppose work that's A.O.K. with me.
My
concern is that down the road after I've completed a couple dozen jsp's
someone
will decide that sentinel is not the name anymore and it must be deployed as
joe_blows_app. Now I've got to go back and fix all the jsp's.
Am I doing something wrong or is it just a fact of life that the jsp's may
need
modifications because of a deployment name change... If there is a better
way to
accomplish this so that the jsp's are a little less dependent on the webapp
deployed name then I'm all ears.
Later, ajTreece (aka. aj Treece - eRAS Services Development - Sun
Microsystems)
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: A beginners look at the *.do process
Posted by Niall Pemberton <ni...@btInternet.com>.
Try removing the leading "/"
<FORM METHOD="post" NAME="mainForm" ACTION="logon.do">
Niall
> -----Original Message-----
> From: ajTreece [mailto:aj.treece@sun.com]
> Sent: 12 April 2002 21:36
> To: Struts Users Mailing List
> Subject: A beginners look at the *.do process
>
>
> If this is way that things are suppose to work then just bear
> with me and tell
> me to get over it. Here is my question....
>
> I have a webapp that when deployed will execute via the reference
> http://<any-server>/sentinel The thing that is unclear to me is
> what is actually
> happening when a <form> action is executed. What I'm finding is
> that my form
> line must read like:
>
> <FORM METHOD="post" NAME="mainForm" ACTION="/sentinel/logon.do">
>
> This executes correctly. The struts-config.xml (see excerpt
> below) leads me to
> believe that the form action should be just ACTION="/logon.do",
> but this returns
> an error stating that http::/<any-server>/logon does not exist...
> Which is true.
>
> <!-- ========== Global Forward Definitions
> ============================== -->
> <global-forwards>
> <forward name="logon" path="/logon.do"/>
> </global-forwards>
>
>
> <!-- ========== Action Mapping Definitions
> ============================== -->
> <action-mappings>
> <!-- Process a user logon -->
> <action path="/logon"
> type="com.sun.sentinel.action.LogonAction"
> name="logonForm"
> scope="request"
> input="logon.page">
> </action>
> </action-mappings>
>
> If this is how the whole *.do action is suppose work that's
> A.O.K. with me. My
> concern is that down the road after I've completed a couple dozen
> jsp's someone
> will decide that sentinel is not the name anymore and it must be
> deployed as
> joe_blows_app. Now I've got to go back and fix all the jsp's.
>
> Am I doing something wrong or is it just a fact of life that the
> jsp's may need
> modifications because of a deployment name change... If there is
> a better way to
> accomplish this so that the jsp's are a little less dependent on
> the webapp
> deployed name then I'm all ears.
>
>
> Later, ajTreece (aka. aj Treece - eRAS Services Development - Sun
> Microsystems)
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>