yes I do
-----
<!-- Process a user logon -->
<action path="/logon"
type="org.apache.struts.webapp.example.LogonAction"
name="logonForm"
scope="session"
input="logon">
<exception
key="expired.password"
type="org.apache.struts.webapp.example.ExpiredPassword
Exception"
path="/changePassword.jsp"/>
</action>
------------
the thing is I have another jsp page in my application which does a
re-direct to a struts action instead of being a form submit and that works
perfectly fine. So I'm guessing it reads struts-config.xml ok, or maybe in
some situations it does not recognize it? If anyone has tried
struts-examples.war on websphere 4.01, I'd like to hear their experiences.
The frustrating part is I have no exceptions or errors to look into and
debug.
thanks
rajiv
-----Original Message-----
From: Weston Aiken [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 12, 2002 11:32 AM
To: struts-user
Subject: RE: Servlet Mapping *.do problem
I meant struts-config.xml of course...
-----Original Message-----
From: [EMAIL PROTECTED]
at INTERNET
Sent: Monday, August 12, 2002 11:00 AM
To: Aiken, Weston - Raleigh, NC; [EMAIL PROTECTED] at
INTERNET
Subject: RE: Servlet Mapping *.do problem
-----------------------------------------
What is your apps context root? Check your application.xml. If your
context root is myapp for example, then your servlet url would be...
http://localhost/myapp/logon.do
By default, WSAD sets your context root to the name of the webapp
project.
----------------------------
The context root is actually "/struts-example"
so the logon action url does appear correctly as
"http://ibm1.va.mercator.com/struts-example/logon.do";. but it just
does'nt
work. Feels like Websphere is simply not resolving the "*.do" to
"action"
mapping
It does'nt seem to be a seamless install on Websphere. Ideally I'd like
to
drop the war file and be good to go. It works on tomcat, weblogic why
not
websphere and this is 4.01
but, thanks for your efforts
rajiv
-----Original Message-----
From: [EMAIL PROTECTED]
at INTERNET
Sent: Monday, August 12, 2002 9:55 AM
To: Aiken, Weston - Raleigh, NC; [EMAIL PROTECTED] at
INTERNET
Subject: RE: Servlet Mapping *.do problem
>>Some suggest turning this off b/c for security reasons you might not
want
>>users to be able to access any old servlet through this mapping. My
>>thinking is, you want them to access them through the manner that you
set
up
>>in your struts framework and not arbitrarily.
I am aware of the security problem, but i just turned it on for
debugging
purposes.
>>It sounds like you've got the servlet deployed but that there might be
a
>>problem with the deployment descriptor which should be handling your
>>mapping.
>>What URL are you trying for the example?
Yes the ActionServlet is deployed coz i can see some debug info, the
web.xml
is out of the box from struts example war file. I am just trying to
login
from login page (http://localhost/logon.jsp), although I don't know the
login/password I was hoping to get at least a sensible error page but
all i
got was a page not found and the url was http://localhost/logon.do I am
attaching my web.xml and ibm's xmi files.
I don't get any parser exceptions, it looks like struts-config gets read
fine, during start-up. But the mapping does'nt seem to work.
> After some further testing, i found that I can access some servlets by
name
> as long as they are mapped to "/servlet/...." but since the action
servlets
> are mapped as "*.do", it does'nt seem to like it.
>
thanks
rajiv
------------------------------------------------------------------------
--------
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
File item 2 original document name: web.xml
File item 2 document type: PCDATA
File item 2 size (bytes): 1909
File item 3 original document name: ibm-web-ext.xmi
File item 3 document type: PCDATA
File item 3 size (bytes): 253
File item 4 original document name: ibm-web-bnd.xmi
File item 4 document type: PCDATA
File item 4 size (bytes): 251
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
