You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Jeremiah Johnson (JIRA)" <be...@incubator.apache.org> on 2005/02/02 00:37:19 UTC
[jira] Created: (BEEHIVE-228) Controller with JSPs behaving differently than Controller in WEB-INF/src.
Controller with JSPs behaving differently than Controller in WEB-INF/src.
-------------------------------------------------------------------------
Key: BEEHIVE-228
URL: http://issues.apache.org/jira/browse/BEEHIVE-228
Project: Beehive
Type: Bug
Components: NetUI
Environment: I wrote the sample on Fedora Linux deploying to Tomcat 5.0.25.
Reporter: Jeremiah Johnson
If I put Controller.jpf in the same directory as my JSP and specify Controller.jpf before index.jsp in the welcome-file-list of web.xml, then the begin action on Controller.jpf is used; on the other hand, if I put Controller.jpf or Controller.java in WEB-INF/src, then Controller.jpf if skipped over in the welcome-file-list. I expected Controller.jpf to still be used.
I will attach a sample application to demonstrate my concern. Here is the structure of the file:
index.jsp - just links to good and bad directories
good/Controller.jpf - begin is simple action forwarding to nonindex.jsp
good/index.jsp - this should not be seen as welcome because of welcome-file-list
good/nonindex.jsp - should be what the user sees with URL of <contextRoot>/good/
bad/index.jsp - this is the second option in the welcome-file-list
bad/nonindex.jsp - this is what I expected to see based on my controller
WEB-INF/web.xml - contains the welcome-file-list shown below
WEB-INF/src/bad/Controller.jpf - same controller source as good/Controller.jpf
The relevant contents of web.xml:
<welcome-file-list>
<welcome-file>Controller.jpf</welcome-file>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>
- jeremiah
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (BEEHIVE-228) Controller with JSPs behaving differently than Controller in WEB-INF/src.
Posted by "Jeremiah Johnson (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-228?page=history ]
Jeremiah Johnson updated BEEHIVE-228:
-------------------------------------
Attachment: BEEHIVE-228.tar
Here are the steps that I would recommend for the attached file:
$ tar xf BEEHIVE-228.tar
$ cd BEEHIVE-228
$ ant -f /home/jjohnson/projects/beehive/build/dist/apache-beehive-incubating-svn-snapshot/ant/webappRuntimeCore.xml -Dwebapp.dir=/home/jjohnson/projects/BEEHIVE-228 deploy.beehive.webapp.runtime
$ ant -f /home/jjohnson/projects/beehive/build/dist/apache-beehive-incubating-svn-snapshot/ant/buildWebapp.xml -Dwebapp.dir=/home/jjohnson/projects/BEEHIVE-228 build
$ jar cf BEEHIVE-228.war *
$ mv BEEHIVE-228.war $CATALINA_HOME/webapps
The point your browser at http://localhost:8080/BEEHIVE-228/ and click on the links.
- jeremiah
> Controller with JSPs behaving differently than Controller in WEB-INF/src.
> -------------------------------------------------------------------------
>
> Key: BEEHIVE-228
> URL: http://issues.apache.org/jira/browse/BEEHIVE-228
> Project: Beehive
> Type: Bug
> Components: NetUI
> Environment: I wrote the sample on Fedora Linux deploying to Tomcat 5.0.25.
> Reporter: Jeremiah Johnson
> Attachments: BEEHIVE-228.tar
>
> If I put Controller.jpf in the same directory as my JSP and specify Controller.jpf before index.jsp in the welcome-file-list of web.xml, then the begin action on Controller.jpf is used; on the other hand, if I put Controller.jpf or Controller.java in WEB-INF/src, then Controller.jpf if skipped over in the welcome-file-list. I expected Controller.jpf to still be used.
> I will attach a sample application to demonstrate my concern. Here is the structure of the file:
> index.jsp - just links to good and bad directories
> good/Controller.jpf - begin is simple action forwarding to nonindex.jsp
> good/index.jsp - this should not be seen as welcome because of welcome-file-list
> good/nonindex.jsp - should be what the user sees with URL of <contextRoot>/good/
> bad/index.jsp - this is the second option in the welcome-file-list
> bad/nonindex.jsp - this is what I expected to see based on my controller
> WEB-INF/web.xml - contains the welcome-file-list shown below
> WEB-INF/src/bad/Controller.jpf - same controller source as good/Controller.jpf
> The relevant contents of web.xml:
> <welcome-file-list>
> <welcome-file>Controller.jpf</welcome-file>
> <welcome-file>index.jsp</welcome-file>
> </welcome-file-list>
> - jeremiah
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (BEEHIVE-228) Controller with JSPs behaving differently than Controller in WEB-INF/src.
Posted by "Jeremiah Johnson (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-228?page=all ]
Jeremiah Johnson closed BEEHIVE-228:
------------------------------------
Thanks for the docs.
> Controller with JSPs behaving differently than Controller in WEB-INF/src.
> -------------------------------------------------------------------------
>
> Key: BEEHIVE-228
> URL: http://issues.apache.org/jira/browse/BEEHIVE-228
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1
> Environment: I wrote the sample on Fedora Linux deploying to Tomcat 5.0.25.
> Reporter: Jeremiah Johnson
> Assignee: Jeremiah Johnson
> Priority: Trivial
> Fix For: V1
> Attachments: BEEHIVE-228.tar
>
> If I put Controller.jpf in the same directory as my JSP and specify Controller.jpf before index.jsp in the welcome-file-list of web.xml, then the begin action on Controller.jpf is used; on the other hand, if I put Controller.jpf or Controller.java in WEB-INF/src, then Controller.jpf if skipped over in the welcome-file-list. I expected Controller.jpf to still be used.
> I will attach a sample application to demonstrate my concern. Here is the structure of the file:
> index.jsp - just links to good and bad directories
> good/Controller.jpf - begin is simple action forwarding to nonindex.jsp
> good/index.jsp - this should not be seen as welcome because of welcome-file-list
> good/nonindex.jsp - should be what the user sees with URL of <contextRoot>/good/
> bad/index.jsp - this is the second option in the welcome-file-list
> bad/nonindex.jsp - this is what I expected to see based on my controller
> WEB-INF/web.xml - contains the welcome-file-list shown below
> WEB-INF/src/bad/Controller.jpf - same controller source as good/Controller.jpf
> The relevant contents of web.xml:
> <welcome-file-list>
> <welcome-file>Controller.jpf</welcome-file>
> <welcome-file>index.jsp</welcome-file>
> </welcome-file-list>
> - jeremiah
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (BEEHIVE-228) Controller with JSPs behaving differently than Controller in WEB-INF/src.
Posted by "Steve Hanson (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-228?page=history ]
Steve Hanson updated BEEHIVE-228:
---------------------------------
Version: V1
> Controller with JSPs behaving differently than Controller in WEB-INF/src.
> -------------------------------------------------------------------------
>
> Key: BEEHIVE-228
> URL: http://issues.apache.org/jira/browse/BEEHIVE-228
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1
> Environment: I wrote the sample on Fedora Linux deploying to Tomcat 5.0.25.
> Reporter: Jeremiah Johnson
> Assignee: Steve Hanson
> Priority: Trivial
> Attachments: BEEHIVE-228.tar
>
> If I put Controller.jpf in the same directory as my JSP and specify Controller.jpf before index.jsp in the welcome-file-list of web.xml, then the begin action on Controller.jpf is used; on the other hand, if I put Controller.jpf or Controller.java in WEB-INF/src, then Controller.jpf if skipped over in the welcome-file-list. I expected Controller.jpf to still be used.
> I will attach a sample application to demonstrate my concern. Here is the structure of the file:
> index.jsp - just links to good and bad directories
> good/Controller.jpf - begin is simple action forwarding to nonindex.jsp
> good/index.jsp - this should not be seen as welcome because of welcome-file-list
> good/nonindex.jsp - should be what the user sees with URL of <contextRoot>/good/
> bad/index.jsp - this is the second option in the welcome-file-list
> bad/nonindex.jsp - this is what I expected to see based on my controller
> WEB-INF/web.xml - contains the welcome-file-list shown below
> WEB-INF/src/bad/Controller.jpf - same controller source as good/Controller.jpf
> The relevant contents of web.xml:
> <welcome-file-list>
> <welcome-file>Controller.jpf</welcome-file>
> <welcome-file>index.jsp</welcome-file>
> </welcome-file-list>
> - jeremiah
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (BEEHIVE-228) Controller with JSPs behaving differently than Controller in WEB-INF/src.
Posted by "Jeremiah Johnson (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-228?page=history ]
Jeremiah Johnson updated BEEHIVE-228:
-------------------------------------
Priority: Trivial (was: Major)
Changing the priority to trivial since it is a known issue beyond the scope of Beehive. This information should make it into some documentation in order to close the bug.
Struts has this same issue. Take a look here for some more details: http://www.theserverside.com/discussions/thread.tss?thread_id=30190
- jeremiah
> Controller with JSPs behaving differently than Controller in WEB-INF/src.
> -------------------------------------------------------------------------
>
> Key: BEEHIVE-228
> URL: http://issues.apache.org/jira/browse/BEEHIVE-228
> Project: Beehive
> Type: Bug
> Components: NetUI
> Environment: I wrote the sample on Fedora Linux deploying to Tomcat 5.0.25.
> Reporter: Jeremiah Johnson
> Priority: Trivial
> Attachments: BEEHIVE-228.tar
>
> If I put Controller.jpf in the same directory as my JSP and specify Controller.jpf before index.jsp in the welcome-file-list of web.xml, then the begin action on Controller.jpf is used; on the other hand, if I put Controller.jpf or Controller.java in WEB-INF/src, then Controller.jpf if skipped over in the welcome-file-list. I expected Controller.jpf to still be used.
> I will attach a sample application to demonstrate my concern. Here is the structure of the file:
> index.jsp - just links to good and bad directories
> good/Controller.jpf - begin is simple action forwarding to nonindex.jsp
> good/index.jsp - this should not be seen as welcome because of welcome-file-list
> good/nonindex.jsp - should be what the user sees with URL of <contextRoot>/good/
> bad/index.jsp - this is the second option in the welcome-file-list
> bad/nonindex.jsp - this is what I expected to see based on my controller
> WEB-INF/web.xml - contains the welcome-file-list shown below
> WEB-INF/src/bad/Controller.jpf - same controller source as good/Controller.jpf
> The relevant contents of web.xml:
> <welcome-file-list>
> <welcome-file>Controller.jpf</welcome-file>
> <welcome-file>index.jsp</welcome-file>
> </welcome-file-list>
> - jeremiah
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (BEEHIVE-228) Controller with JSPs behaving differently than Controller in WEB-INF/src.
Posted by "Jeremiah Johnson (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-228?page=comments#action_58461 ]
Jeremiah Johnson commented on BEEHIVE-228:
------------------------------------------
I see that this issue isn't unique to Beehive. A struts work-around that I found was to put a fake file in matching the welcome-file token. In my case, the following line executed before bundling the war gives me the expected results:
$ touch bad/Controller.jpf
So perhaps this 'bug' is more of a documentation issue than a bug in Beehive.
- jeremiah
> Controller with JSPs behaving differently than Controller in WEB-INF/src.
> -------------------------------------------------------------------------
>
> Key: BEEHIVE-228
> URL: http://issues.apache.org/jira/browse/BEEHIVE-228
> Project: Beehive
> Type: Bug
> Components: NetUI
> Environment: I wrote the sample on Fedora Linux deploying to Tomcat 5.0.25.
> Reporter: Jeremiah Johnson
> Attachments: BEEHIVE-228.tar
>
> If I put Controller.jpf in the same directory as my JSP and specify Controller.jpf before index.jsp in the welcome-file-list of web.xml, then the begin action on Controller.jpf is used; on the other hand, if I put Controller.jpf or Controller.java in WEB-INF/src, then Controller.jpf if skipped over in the welcome-file-list. I expected Controller.jpf to still be used.
> I will attach a sample application to demonstrate my concern. Here is the structure of the file:
> index.jsp - just links to good and bad directories
> good/Controller.jpf - begin is simple action forwarding to nonindex.jsp
> good/index.jsp - this should not be seen as welcome because of welcome-file-list
> good/nonindex.jsp - should be what the user sees with URL of <contextRoot>/good/
> bad/index.jsp - this is the second option in the welcome-file-list
> bad/nonindex.jsp - this is what I expected to see based on my controller
> WEB-INF/web.xml - contains the welcome-file-list shown below
> WEB-INF/src/bad/Controller.jpf - same controller source as good/Controller.jpf
> The relevant contents of web.xml:
> <welcome-file-list>
> <welcome-file>Controller.jpf</welcome-file>
> <welcome-file>index.jsp</welcome-file>
> </welcome-file-list>
> - jeremiah
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (BEEHIVE-228) Controller with JSPs behaving differently than Controller in WEB-INF/src.
Posted by "Steve Hanson (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-228?page=all ]
Steve Hanson resolved BEEHIVE-228:
----------------------------------
Assign To: Jeremiah Johnson (was: Steve Hanson)
Resolution: Fixed
I added the following note to the doc.
Please re-open if this bug if I haven't captured the problem.
Note
When a folder-path URL is called
http://some.domain.com/foo
the Controller class will not be instantiated, unless (1) you list the class in web.xml's <welcome-file-list>.
<welcome-file-list>
<welcome-file>Controller.jpf</welcome-file>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>
and (2) the Controller.jpf file resides in the folder foo. If the Controller.jpf resides in the WEB-INF/src/ directory, then it will not be instantiated when the folder-path URL is called.
> Controller with JSPs behaving differently than Controller in WEB-INF/src.
> -------------------------------------------------------------------------
>
> Key: BEEHIVE-228
> URL: http://issues.apache.org/jira/browse/BEEHIVE-228
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1
> Environment: I wrote the sample on Fedora Linux deploying to Tomcat 5.0.25.
> Reporter: Jeremiah Johnson
> Assignee: Jeremiah Johnson
> Priority: Trivial
> Fix For: V1
> Attachments: BEEHIVE-228.tar
>
> If I put Controller.jpf in the same directory as my JSP and specify Controller.jpf before index.jsp in the welcome-file-list of web.xml, then the begin action on Controller.jpf is used; on the other hand, if I put Controller.jpf or Controller.java in WEB-INF/src, then Controller.jpf if skipped over in the welcome-file-list. I expected Controller.jpf to still be used.
> I will attach a sample application to demonstrate my concern. Here is the structure of the file:
> index.jsp - just links to good and bad directories
> good/Controller.jpf - begin is simple action forwarding to nonindex.jsp
> good/index.jsp - this should not be seen as welcome because of welcome-file-list
> good/nonindex.jsp - should be what the user sees with URL of <contextRoot>/good/
> bad/index.jsp - this is the second option in the welcome-file-list
> bad/nonindex.jsp - this is what I expected to see based on my controller
> WEB-INF/web.xml - contains the welcome-file-list shown below
> WEB-INF/src/bad/Controller.jpf - same controller source as good/Controller.jpf
> The relevant contents of web.xml:
> <welcome-file-list>
> <welcome-file>Controller.jpf</welcome-file>
> <welcome-file>index.jsp</welcome-file>
> </welcome-file-list>
> - jeremiah
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (BEEHIVE-228) Controller with JSPs behaving differently than Controller in WEB-INF/src.
Posted by "Jeremiah Johnson (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-228?page=history ]
Jeremiah Johnson reassigned BEEHIVE-228:
----------------------------------------
Assign To: Steve Hanson
Steve,
I am hoping that someone on your team can address this in a FAQ or in the Beehive documentation somewhere.
- jeremiah
> Controller with JSPs behaving differently than Controller in WEB-INF/src.
> -------------------------------------------------------------------------
>
> Key: BEEHIVE-228
> URL: http://issues.apache.org/jira/browse/BEEHIVE-228
> Project: Beehive
> Type: Bug
> Components: NetUI
> Environment: I wrote the sample on Fedora Linux deploying to Tomcat 5.0.25.
> Reporter: Jeremiah Johnson
> Assignee: Steve Hanson
> Priority: Trivial
> Attachments: BEEHIVE-228.tar
>
> If I put Controller.jpf in the same directory as my JSP and specify Controller.jpf before index.jsp in the welcome-file-list of web.xml, then the begin action on Controller.jpf is used; on the other hand, if I put Controller.jpf or Controller.java in WEB-INF/src, then Controller.jpf if skipped over in the welcome-file-list. I expected Controller.jpf to still be used.
> I will attach a sample application to demonstrate my concern. Here is the structure of the file:
> index.jsp - just links to good and bad directories
> good/Controller.jpf - begin is simple action forwarding to nonindex.jsp
> good/index.jsp - this should not be seen as welcome because of welcome-file-list
> good/nonindex.jsp - should be what the user sees with URL of <contextRoot>/good/
> bad/index.jsp - this is the second option in the welcome-file-list
> bad/nonindex.jsp - this is what I expected to see based on my controller
> WEB-INF/web.xml - contains the welcome-file-list shown below
> WEB-INF/src/bad/Controller.jpf - same controller source as good/Controller.jpf
> The relevant contents of web.xml:
> <welcome-file-list>
> <welcome-file>Controller.jpf</welcome-file>
> <welcome-file>index.jsp</welcome-file>
> </welcome-file-list>
> - jeremiah
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (BEEHIVE-228) Controller with JSPs behaving differently than Controller in WEB-INF/src.
Posted by "Steve Tocco (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-228?page=history ]
Steve Tocco updated BEEHIVE-228:
--------------------------------
Fix Version: V1
moving to v1 (if not needed for ship, please move to Fix For = TBD)
> Controller with JSPs behaving differently than Controller in WEB-INF/src.
> -------------------------------------------------------------------------
>
> Key: BEEHIVE-228
> URL: http://issues.apache.org/jira/browse/BEEHIVE-228
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1
> Environment: I wrote the sample on Fedora Linux deploying to Tomcat 5.0.25.
> Reporter: Jeremiah Johnson
> Assignee: Steve Hanson
> Priority: Trivial
> Fix For: V1
> Attachments: BEEHIVE-228.tar
>
> If I put Controller.jpf in the same directory as my JSP and specify Controller.jpf before index.jsp in the welcome-file-list of web.xml, then the begin action on Controller.jpf is used; on the other hand, if I put Controller.jpf or Controller.java in WEB-INF/src, then Controller.jpf if skipped over in the welcome-file-list. I expected Controller.jpf to still be used.
> I will attach a sample application to demonstrate my concern. Here is the structure of the file:
> index.jsp - just links to good and bad directories
> good/Controller.jpf - begin is simple action forwarding to nonindex.jsp
> good/index.jsp - this should not be seen as welcome because of welcome-file-list
> good/nonindex.jsp - should be what the user sees with URL of <contextRoot>/good/
> bad/index.jsp - this is the second option in the welcome-file-list
> bad/nonindex.jsp - this is what I expected to see based on my controller
> WEB-INF/web.xml - contains the welcome-file-list shown below
> WEB-INF/src/bad/Controller.jpf - same controller source as good/Controller.jpf
> The relevant contents of web.xml:
> <welcome-file-list>
> <welcome-file>Controller.jpf</welcome-file>
> <welcome-file>index.jsp</welcome-file>
> </welcome-file-list>
> - jeremiah
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira