You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by be...@incubator.apache.org on 2004/10/08 20:07:51 UTC
[jira] Created: (BEEHIVE-17) TomcatServerAdapter for Tomcat 5.x
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/BEEHIVE-17
Here is an overview of the issue:
---------------------------------------------------------------------
Key: BEEHIVE-17
Summary: TomcatServerAdapter for Tomcat 5.x
Type: New Feature
Status: Unassigned
Priority: Major
Project: Beehive
Components:
NetUI
Fix Fors:
TBD
Versions:
TBD
Assignee:
Reporter: Rich Feit
Created: Fri, 8 Oct 2004 11:07 AM
Updated: Fri, 8 Oct 2004 11:07 AM
Description:
For server-specific features, NetUI depends on implementations of an interface (org.apache.beehive.netui.pageflow.ServerAdapter). Most features work with the default ServerAdapter, but this fills in holes like login/logout and container-based security checks.
In the past, we had a TomcatServerAdapter that worked with Tomcat 4. It basically put the bulk of the implementation in a class in tomcat/server/lib (where it can see other tomcat-specific classes), and then added an interface in tomcat/common/lib to allow the webapp-scoped TomcatServerAdapter to access the functionality.
We should add a Tomcat 5-enabled version of this. It may be trivial or it may be totally different -- I haven't looked into it yet. I will attach the old version of the code shortly.
---------------------------------------------------------------------
JIRA INFORMATION:
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-17) TomcatServerAdapter for Tomcat 5.x
Posted by "Alejandro Ramirez (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-17?page=all ]
Alejandro Ramirez closed BEEHIVE-17:
------------------------------------
Verified fixed. I have executed login against tomcat 5.0.25 and that is working.
> TomcatServerAdapter for Tomcat 5.x
> ----------------------------------
>
> Key: BEEHIVE-17
> URL: http://issues.apache.org/jira/browse/BEEHIVE-17
> Project: Beehive
> Type: New Feature
> Components: NetUI
> Versions: V1Beta
> Reporter: Rich Feit
> Assignee: Alejandro Ramirez
> Fix For: V1Beta
>
> For server-specific features, NetUI depends on implementations of an interface (org.apache.beehive.netui.pageflow.ServerAdapter). Most features work with the default ServerAdapter, but this fills in holes like login/logout and container-based security checks.
> In the past, we had a TomcatServerAdapter that worked with Tomcat 4. It basically put the bulk of the implementation in a class in tomcat/server/lib (where it can see other tomcat-specific classes), and then added an interface in tomcat/common/lib to allow the webapp-scoped TomcatServerAdapter to access the functionality.
> We should add a Tomcat 5-enabled version of this. It may be trivial or it may be totally different -- I haven't looked into it yet. I will attach the old version of the code shortly.
--
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] Resolved: (BEEHIVE-17) TomcatServerAdapter for Tomcat 5.x
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-17?page=history ]
Rich Feit resolved BEEHIVE-17:
------------------------------
Assign To: Alejandro Ramirez (was: Rich Feit)
Resolution: Fixed
I did this work a while ago -- forgot to resolve the issue here. If our Tomcat integration (login/security) is working, then this bug is fixed.
> TomcatServerAdapter for Tomcat 5.x
> ----------------------------------
>
> Key: BEEHIVE-17
> URL: http://issues.apache.org/jira/browse/BEEHIVE-17
> Project: Beehive
> Type: New Feature
> Components: NetUI
> Versions: V1Beta
> Reporter: Rich Feit
> Assignee: Alejandro Ramirez
> Fix For: V1Beta
>
> For server-specific features, NetUI depends on implementations of an interface (org.apache.beehive.netui.pageflow.ServerAdapter). Most features work with the default ServerAdapter, but this fills in holes like login/logout and container-based security checks.
> In the past, we had a TomcatServerAdapter that worked with Tomcat 4. It basically put the bulk of the implementation in a class in tomcat/server/lib (where it can see other tomcat-specific classes), and then added an interface in tomcat/common/lib to allow the webapp-scoped TomcatServerAdapter to access the functionality.
> We should add a Tomcat 5-enabled version of this. It may be trivial or it may be totally different -- I haven't looked into it yet. I will attach the old version of the code shortly.
--
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] Assigned: (BEEHIVE-17) TomcatServerAdapter for Tomcat 5.x
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://nagoya.apache.org/jira/browse/BEEHIVE-17?page=history ]
Rich Feit reassigned BEEHIVE-17:
--------------------------------
Assign To: Rich Feit
> TomcatServerAdapter for Tomcat 5.x
> ----------------------------------
>
> Key: BEEHIVE-17
> URL: http://nagoya.apache.org/jira/browse/BEEHIVE-17
> Project: Beehive
> Type: New Feature
> Components: NetUI
> Versions: V1Beta
> Reporter: Rich Feit
> Assignee: Rich Feit
> Fix For: V1Beta
>
> For server-specific features, NetUI depends on implementations of an interface (org.apache.beehive.netui.pageflow.ServerAdapter). Most features work with the default ServerAdapter, but this fills in holes like login/logout and container-based security checks.
> In the past, we had a TomcatServerAdapter that worked with Tomcat 4. It basically put the bulk of the implementation in a class in tomcat/server/lib (where it can see other tomcat-specific classes), and then added an interface in tomcat/common/lib to allow the webapp-scoped TomcatServerAdapter to access the functionality.
> We should add a Tomcat 5-enabled version of this. It may be trivial or it may be totally different -- I haven't looked into it yet. I will attach the old version of the code shortly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.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-17) TomcatServerAdapter for Tomcat 5.x
Posted by "Kenneth Tam (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-17?page=history ]
Kenneth Tam updated BEEHIVE-17:
-------------------------------
Version: V1Beta
(was: V1Alpha)
Fix Version: V1Beta
(was: V1Alpha)
> TomcatServerAdapter for Tomcat 5.x
> ----------------------------------
>
> Key: BEEHIVE-17
> URL: http://issues.apache.org/jira/browse/BEEHIVE-17
> Project: Beehive
> Type: New Feature
> Components: NetUI
> Versions: V1Beta
> Reporter: Rich Feit
> Fix For: V1Beta
>
> For server-specific features, NetUI depends on implementations of an interface (org.apache.beehive.netui.pageflow.ServerAdapter). Most features work with the default ServerAdapter, but this fills in holes like login/logout and container-based security checks.
> In the past, we had a TomcatServerAdapter that worked with Tomcat 4. It basically put the bulk of the implementation in a class in tomcat/server/lib (where it can see other tomcat-specific classes), and then added an interface in tomcat/common/lib to allow the webapp-scoped TomcatServerAdapter to access the functionality.
> We should add a Tomcat 5-enabled version of this. It may be trivial or it may be totally different -- I haven't looked into it yet. I will attach the old version of the code shortly.
--
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