[JBoss JIRA] Created: (JBREM-713) Check if jbossweb can replace tomcat jars for the http server invoker
2:45 a.m.
Check if jbossweb can replace tomcat jars for the http server invoker
---------------------------------------------------------------------
Key: JBREM-713
URL: http://jira.jboss.com/jira/browse/JBREM-713
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 2.2.0.Beta2 (Bluto)
Reporter: Ron Sigal
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta2 (Bluto)
See if jbossweb has API compatible to tomcat connectors, which would allow it to replace
the tomcar jars for CoyoteInvoker.
See JBREM-705.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:52 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-713) Check if jbossweb can replace tomcat jars for the http server invoker
[ http://jira.jboss.com/jira/browse/JBREM-713?page=all ]
Ron Sigal updated JBREM-713:
----------------------------
Assignee: Ron Sigal (was: Tom Elrod)
Check if jbossweb can replace tomcat jars for the http server
invoker
---------------------------------------------------------------------
Key: JBREM-713
URL: http://jira.jboss.com/jira/browse/JBREM-713
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
See if jbossweb has API compatible to tomcat connectors, which would allow it to replace
the tomcar jars for CoyoteInvoker.
See JBREM-705.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:06 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-713) Check if jbossweb can replace tomcat jars for the http server invoker
[ http://jira.jboss.com/jira/browse/JBREM-713?page=comments#action_12384020 ]
Ron Sigal commented on JBREM-713:
---------------------------------
With a couple of small changes to org.jboss.remoting.transport.coyote.CoyoterInvoker,
org.jboss.remoting.transport.coyote.ssl.RemotingSSLImplementation, and
org.jboss.remoting.transport.coyote.ssl.RemotingSSLSupport, the http transport works with
either the tomcat jars or jbossweb.jar.
Update build.xml so that tests.functional and tests.functional.core run all http related
tests with both jbossweb.jar and tomcat jars.
Added jbossweb/jbossweb.jar to lib directory. jbossweb.jar is version 2.0.0.GA.
Check if jbossweb can replace tomcat jars for the http server
invoker
---------------------------------------------------------------------
Key: JBREM-713
URL: http://jira.jboss.com/jira/browse/JBREM-713
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
See if jbossweb has API compatible to tomcat connectors, which would allow it to replace
the tomcar jars for CoyoteInvoker.
See JBREM-705.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:17 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-713) Check if jbossweb can replace tomcat jars for the http server invoker
[ http://jira.jboss.com/jira/browse/JBREM-713?page=comments#action_12384483 ]
Ron Sigal commented on JBREM-713:
---------------------------------
To elaborate on the changes, they involve adding
1. method event() to CoyoteInvoker
2. method getSSLSupport(SSLSession session) to RemotingSSLImplementation, and
3. constructor RemotingSSLSupport(SSLSession session) to RemotingSSLSupport(SSLSession.
The important thing to note is that, while these changes are necessary to achieve source
compatibility with JBossWeb, they are not necessary for binary compatibility. The
CoyoteInvoker.event() method would only be called when the coyote system is in
"comet" mode, and the RemotingSSLImplementation.getSSLSupport(SSLSession
session) would only be called by the Http11NioProtocol coyote class. Neither of these is
relevant to the current use of the coyote system by Remotig.
So current Remoting releases running in, for example, JBossAS 4.2.0.GA, will work with
jbossweb.jar that ships with JBossAS.
Check if jbossweb can replace tomcat jars for the http server
invoker
---------------------------------------------------------------------
Key: JBREM-713
URL: http://jira.jboss.com/jira/browse/JBREM-713
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
See if jbossweb has API compatible to tomcat connectors, which would allow it to replace
the tomcar jars for CoyoteInvoker.
See JBREM-705.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:07 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-713) Check if jbossweb can replace tomcat jars for the http server invoker
[ http://jira.jboss.com/jira/browse/JBREM-713?page=comments#action_12384674 ]
Ron Sigal commented on JBREM-713:
---------------------------------
It's important to note that jbossweb.jar is built with jdk 1.5, so the http transport
can work with jbossweb only if Remoting is also built with jdk 1.5.
Check if jbossweb can replace tomcat jars for the http server
invoker
---------------------------------------------------------------------
Key: JBREM-713
URL: http://jira.jboss.com/jira/browse/JBREM-713
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
See if jbossweb has API compatible to tomcat connectors, which would allow it to replace
the tomcar jars for CoyoteInvoker.
See JBREM-705.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:19 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-713) Check if jbossweb can replace tomcat jars for the http server invoker
[ http://jira.jboss.com/jira/browse/JBREM-713?page=comments#action_12385207 ]
Ron Sigal commented on JBREM-713:
---------------------------------
CoyoteInvoker.event() is defined:
public boolean event(Request arg0, Response arg1, SocketStatus arg2) throws Exception;
but org.apache.tomcat.util.net.SocketStatus is an enum that does not exist in tomcat. To
get around the problem, I've created an interface
org.apache.tomcat.util.net.SocketStatus, put it in tomcat-addenda.jar, and put
tomcat-addenda.jar in .../lib/apache-tomcat. This way, a SocketStatus will be available
if apache-tomcat/*.jar's are on the classpath.
Also, I've changed the definition of the classpaths in build.xml so that the tomcat
jars are included if jdk is 1.4, and jbossweb.jar is included if jdk is 1.5.
Note: test in build.xml should be jdk 1.5 or greater.
Check if jbossweb can replace tomcat jars for the http server
invoker
---------------------------------------------------------------------
Key: JBREM-713
URL: http://jira.jboss.com/jira/browse/JBREM-713
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
See if jbossweb has API compatible to tomcat connectors, which would allow it to replace
the tomcar jars for CoyoteInvoker.
See JBREM-705.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:16 p.m.
New subject: [JBoss JIRA] Closed: (JBREM-713) Check if jbossweb can replace tomcat jars for the http server invoker
[ http://jira.jboss.com/jira/browse/JBREM-713?page=all ]
Ron Sigal closed JBREM-713.
---------------------------
Resolution: Done
build.xml is now working on cruisecontrol:
1. For the jdk 1.4 test run, the http tests run once with java serialization and tomcat.
2. For the jdk 1.5 test run, the http tests run four times: (java serialization, jboss
serialization) X (jbossweb, tomcat).
Check if jbossweb can replace tomcat jars for the http server
invoker
---------------------------------------------------------------------
Key: JBREM-713
URL: http://jira.jboss.com/jira/browse/JBREM-713
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
See if jbossweb has API compatible to tomcat connectors, which would allow it to replace
the tomcar jars for CoyoteInvoker.
See JBREM-705.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6754
days inactive
7003
days old
6 comments
1 participants
participants (1)
-
Ron Sigal (JIRA)